Version-Release number of selected component: gtkpod-2.1.3-1.fc19 Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: gtkpod crash_function: gtkpod_init executable: /usr/bin/gtkpod kernel: 3.9.5-301.fc19.x86_64 runlevel: N 5 uid: 10000 xsession_errors: Truncated backtrace: Thread no. 1 (1 frames) #1 gtkpod_init at gtkpod.c:99
Created attachment 762656 [details] File: backtrace
Created attachment 762657 [details] File: cgroup
Created attachment 762658 [details] File: core_backtrace
Created attachment 762659 [details] File: dso_list
Created attachment 762660 [details] File: environ
Created attachment 762661 [details] File: limits
Created attachment 762662 [details] File: maps
Created attachment 762663 [details] File: open_fds
Created attachment 762664 [details] File: proc_pid_status
Created attachment 762665 [details] File: var_log_messages
Created attachment 772199 [details] rpmbuild from gtkpod Hi, I have the same issue and I am trying to find where the issue comes from and it seems to be anjuta dependency which is faulty. I tried to rebuild the src.rpm directly and it fails to build (see attached file). $ rpm -qa | grep anjuta anjuta-devel-3.8.4-1.fc19.x86_64 anjuta-3.8.4-1.fc19.x86_64 I am no expert in GTK but seems to miss defining this function: anjuta_shell_notify_exit
Hi again, I have found that some anjuta_shell defined functions are not within the headers between version 3.7.X and 3.8.X in anjuta. For example, in version 3.7.1, there is in libanjuta/anjuta-shell.h: void anjuta_shell_notify_exit (AnjutaShell *shell, GError **error); Such line is not available in version 3.8.X. I believe there is something that as been depreciated in anjuta? Should this bug be tagged against anjuta?
Ideally gtkpod should be updated to work with the new anjuta, but there isn't a new release as yet. I'll check it out upstream.
I posted here: https://sourceforge.net/p/gtkpod/bugs/315/
The following Patch from archlinux fixes the issue for me: https://projects.archlinux.org/svntogit/community.git/tree/gtkpod/trunk/gtkpod-2.1.3-gdl-3.6.patch It looks like that that anjuta changed the API without changing the SONAME of their library. Otherwise the issue would have been caught earlier due to broken dependencies of the RPM packages. Jon, if you want me to update gtkpod using the patch above, please let me know.
The patch above fixes the issue for me as well.
It's similar to what we had, but updated and a bit more comprehensive. It works for me, and builds are on their way.
gtkpod-2.1.3-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/gtkpod-2.1.3-2.fc19
Package gtkpod-2.1.3-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gtkpod-2.1.3-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-12914/gtkpod-2.1.3-2.fc19 then log in and leave karma (feedback).
gtkpod-2.1.3-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.