After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 633763 - crash in gThumb: Start application
crash in gThumb: Start application
Status: RESOLVED DUPLICATE of bug 620559
Product: gthumb
Classification: Other
Component: general
0.x
Other All
: Normal critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2010-11-02 01:00 UTC by s.pachasa
Modified: 2010-11-02 02:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30



Description s.pachasa 2010-11-02 01:00:34 UTC
Version: 2.11.2.1

What were you doing when the application crashed?
Start application


Distribution: openSUSE 11.3 (i586)
Gnome Release: 2.30.0 (null) (SUSE)
BugBuddy Version: 2.30.0

System: Linux 2.6.34.7-0.5-desktop #1 SMP PREEMPT 2010-10-25 08:40:12 +0200 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10800000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Sonar
Icon Theme: Gilouche
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 142974976 vsize: 142974976 resident: 13598720 share: 10706944 rss: 13598720 rss_rlim: 18446744073709551615
CPU usage: start_time: 1288659569 rtime: 23 utime: 20 stime: 3 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/local/bin/gthumb'

[Thread debugging using libthread_db enabled]
0xffffe424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6928820 (LWP 13337))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 g_type_check_instance_is_a
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_file_get_path
    from /usr/lib/libgio-2.0.so.0
  • #9 _gth_icon_cache_get_icon_key
    at gth-icon-cache.c line 105
  • #10 gth_icon_cache_get_pixbuf
    at gth-icon-cache.c line 127
  • #11 _gth_browser_add_file_menu_item_full
    at gth-browser.c line 336
  • #12 _gth_browser_update_entry_point_list
    at gth-browser.c line 820
  • #13 _gth_browser_construct
    at gth-browser.c line 4217
  • #14 gth_browser_new
    at gth-browser.c line 4296
  • #15 open_browser_window
    at main.c line 267
  • #16 prepare_application
    at main.c line 350
  • #17 main
    at main.c line 444

	Inferior 1 [process 13337] will be detached.

Quit anyway? (y or n) [answered Y; input not from terminal]


---- Critical and fatal warnings logged during execution ----

** GLib-GIO **: g_file_get_path: assertion `G_IS_FILE (file)' failed 
** GLib-GObject **: g_object_unref: assertion `G_IS_OBJECT (object)' failed 


----------- .xsession-errors (40 sec old) ---------------------
(gnome-screensaver:2217): Gdk-CRITICAL **: gdk_window_set_background: assertion `GDK_IS_WINDOW (window)' failed
(gnome-screensaver:2217): Gdk-CRITICAL **: gdk_window_clear: assertion `GDK_IS_WINDOW (window)' failed
(gnome-screensaver:2217): Gdk-WARNING **: gdkdrawable-x11.c:952 drawable is not a pixmap or window
Error: Couldn't open file '/tmp/userg_revL_e.pdf': Permission denied.
** (evince:6762): WARNING **: Error setting file metadata: No such file or directory
** (evince:6762): WARNING **: Error setting file metadata: No such file or directory
** (evince:6762): WARNING **: Error setting file metadata: No such file or directory
** (evince:6762): WARNING **: Error setting file metadata: No such file or directory
--------------------------------------------------
Comment 1 Fabio Durán Verdugo 2010-11-02 02:34:38 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 620559 ***