Gtkpod failing to start

Mr Green · 2013-04-25 05:58:46

Recently wanted to use gtkpod and got this error

(gtkpod:1702): libanjuta-CRITICAL **: anjuta_plugin_manager_list_query: assertion `ANJUTA_IS_PLUGIN_MANAGER (plugin_manager)' failed
Segmentation fault (core dumped)

System is fully up to date and have gtkpod version

gtkpod version 2.1.3

Cannot be sure if this is down to recent gtk+ issues.

Last edited by Mr Green (2013-04-25 05:59:33)

will.price94 · 2013-04-25 09:35:37

I too get the same error (v. 2.1.3)

$ gdb /usr/bin/gtkpod
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0xb2d84b40 (LWP 23138)]

** (gtkpod:23134): WARNING **: Can't load fallback CSS resource: Failed to import: The resource at '/org/gnome/adwaita/gtk-fallback.css' does not exist

** (gtkpod:23134): WARNING **: Can't load fallback CSS resource: Failed to import: The resource at '/org/gnome/adwaita/gtk-fallback.css' does not exist
[New Thread 0xb23c3b40 (LWP 23139)]

(gtkpod:23134): libanjuta-CRITICAL **: anjuta_plugin_manager_list_query: assertion `ANJUTA_IS_PLUGIN_MANAGER (plugin_manager)' failed

Program received signal SIGSEGV, Segmentation fault.
0x00000000 in ?? ()
(gdb) bt
#0  0x00000000 in ?? ()
#1  0xb7ed2219 in anjuta_shell_get_status () from /usr/lib/libanjuta-3.so.0
#2  0x08053ef9 in gtkpod_init ()
#3  0x0804dddd in main ()

Looks like it's libanjuta and not gtkpod though.

Rolling back to libanjuta 3.6.2-2 resolves the issue for me.

Last edited by will.price94 (2013-04-25 09:42:14)

Mr Green · 2013-04-25 09:45:04

Could be, no bug reports on anjuta or libanjuta

Allan · 2013-04-25 11:02:42

Then file one

Mr Green · 2013-04-25 11:10:05

ok

will.price94 · 2013-04-25 11:10:22

I was going to, however reading the wiki put me off; how do I know where to file a bug? It's not immediately obvious to me whether this is an upstream problem or an Arch problem...

EDIT:

Packaging: Packaging basically consists of fetching the source code from upstream, compiling it with relevant options, making sure that it will be correctly installed on an Arch system, and checking that the main functionality works. Packaging at Arch does not consist of adding new functionality or patches for existing bugs; this is the job of the upstream developer.

I guess this should be an Arch bug then because the main functionality doesn't work?

Last edited by will.price94 (2013-04-25 11:11:52)

Allan · 2013-04-25 11:59:49

A segfault should be reported to Arch, although the issue is probably upstream and will need to get reported there too...

gray85 · 2013-04-25 12:17:12

A workaround is to downgrade libanjuta.

Something like this:

# pacman -U /var/cache/pacman/pkg/libanjuta-3.6.2-2-x86_64.pkg.tar.xz

Last edited by gray85 (2013-04-25 12:23:35)

dukefeng · 2013-04-25 12:45:11

Had the same problem, your solution solved the issue, thank you all.

Mr Green · 2013-04-25 13:01:14

https://bugs.archlinux.org/task/34950

Submitted bug report, any more information required just ask....

Arch Linux

#1 2013-04-25 05:58:46

Gtkpod failing to start

#2 2013-04-25 09:35:37

Re: Gtkpod failing to start

#3 2013-04-25 09:45:04

Re: Gtkpod failing to start

#4 2013-04-25 11:02:42

Re: Gtkpod failing to start

#5 2013-04-25 11:10:05

Re: Gtkpod failing to start

#6 2013-04-25 11:10:22

Re: Gtkpod failing to start

#7 2013-04-25 11:59:49

Re: Gtkpod failing to start

#8 2013-04-25 12:17:12

Re: Gtkpod failing to start

#9 2013-04-25 12:45:11

Re: Gtkpod failing to start

#10 2013-04-25 13:01:14

Re: Gtkpod failing to start

Board footer