GNOME Bugzilla – Bug 640620
GTHUMB Fails to Launch or Crashes After Launch
Last modified: 2011-05-07 02:07:01 UTC
Following a fresh reboot, GTHUMB application will successfully launch and is useable for a short time before spontaneously crashing after a period of full useability. Once the application crashes, subsequent launch attempts fail. The following log messages are received upon first successful launch. Similar messages are returned on subsequent post-crash launch attempts: (gthumb:2508): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed (gthumb:2508): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gthumb:2508): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed (gthumb:2508): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gthumb:2508): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed (gthumb:2508): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gthumb:2508): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed (gthumb:2508): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gthumb:2508): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed (gthumb:2508): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed (gthumb:2508): GLib-GIO-CRITICAL **: g_file_get_path: assertion `G_IS_FILE (file)' failed (gthumb:2508): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed SYSTEM DETAILS: uname -a 2.6.36-ARCH #1 SMP PREEMPT Sat Jan 8 14:15:27 CET 2011 x86_64 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ AuthenticAMD GNU/Linux Physical memory: 6 GB NOTES: I have used an earlier version of GTHUMB for years on this system. The current crash issue was not encountered until a recent upgrade to the OS and system applications.
version: pacman -Qs gthumb local/gthumb 2.12.2-1
Can you run it in gdb to get a better stacktrace? gdb gthumb run thread apply all bt - Mike
Forgot to say: please install the necessary debug symbol packages too.
Michael.... Thanx for the reply. I'm including Arch Dev. in the email thread since I'm new to debugging in this environment. Should have better stack later today. Appreciate your response! --JC
UPDATE: Because the issue occurred after the first reboot following a major system upgrade, I tried a second reboot, hoping to pick up any system changes missed by the first cycle. The GTHUMB application has launched successfully and performed to specs during the last three (3) repro attempts. Each launch produces the above log messages, but the application has not crashed. Over the next couple of days, I'll perform some real-world stress scenarios, including multiple app launches, file management, editing of large numbers of files, and a smoke pass against a wide range of app functions. If issue repros, I'll gather a detailed stack trace. --So far so good. Thanks.
UPDATE: Issue unresolved. Fourth launch attempt reproduced the error. Application will not launch. I'll have the expanded stack trace sometime tomorrow. thanx
Should have stack trace tomorrow afternoon. In the meantime, I identified an interesting workaround: 1. launch Gimp (ver. 2.6) 2. with Gimp running, launch GTHUMB 3. optionally terminate Gimp. 4. enjoy GTHUMB.
OK, I think I'm close to getting a full stack trace. I have: 1. installed gdb 2. familiarized myself with the debugger commands 3. identified what i think are the right GTHUMB symbols for my architecture: http://packages.debian.org/experimental/amd64/gthumb-dbg/download ...now i just need a quick procedural outline, specifically, what to do with the symbols package once downloaded. just install it like any other package? If anyone can give me a quick walk-through, i'm happy to grab the stack trace. All of this may be moot, however, because for my own purposes, I have actually solved the GTHUMB launch failure issue! The last time I was able to launch the app, I disabled all the extensions that were not useful to me, including audio / video support, on-line service uploader tools (picasa, facebook, etc), and other network-aware utils. Now, the application launches consistently and is fast and stable. As a learning experience, I'd still like to do the debugging, at least as far as getting the trace. I'll just need a bit of guidance. If no one has the time or inclination, that's OK. --Thanks.
UPDATE: My remedial workarounds failed. Actually, they may or may not have enhanced the stability of this app, which is still broken on my system, crashing, failing to launch, launching occasionally then crashing, etc. It's hard to tell if any of my desperate workarounds have been effective until root cause is identified. OK, I know this is getting tedious, but I have gdb installed, I have a couple of good tutorials for getting a stack trace with the debugger, and I'm going to try this tomorrow night. So, in case anyone's actually following this bug, I should be able to provide a useful trace sometime in the next day or so. Thanx!
Are you running a gnome desktop? (As opposed to kde, or something else?) - Mike
John, any update about bug or regarding the comment#10 ?