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 450088 - crash in gThumb Image Viewer: nothing, it was running ...
crash in gThumb Image Viewer: nothing, it was running ...
Status: RESOLVED DUPLICATE of bug 356623
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-06-22 15:02 UTC by timnugent
Modified: 2007-06-22 15:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description timnugent 2007-06-22 15:02:53 UTC
What were you doing when the application crashed?
nothing, it was running in the background displaying a small png file


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.20-1.2944.fc6 #1 SMP Tue Apr 10 18:46:45 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 855609344 vsize: 0 resident: 855609344 share: 0 rss: 51429376 rss_rlim: 0
CPU usage: start_time: 1181926422 rtime: 0 utime: 7823 stime: 0 cutime:6792 cstime: 0 timeout: 1031 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208322352 (LWP 11641)]
[New Thread -2064901232 (LWP 5306)]
[New Thread -2054411376 (LWP 5305)]
[New Thread -2043921520 (LWP 5304)]
[New Thread -1971729520 (LWP 5303)]
[New Thread -1940259952 (LWP 5302)]
[New Thread -1961239664 (LWP 5301)]
[New Thread -1929770096 (LWP 25223)]
[New Thread -1919280240 (LWP 25222)]
[New Thread -1886573680 (LWP 25221)]
[New Thread -1898300528 (LWP 25220)]
[New Thread -1908790384 (LWP 25219)]
[New Thread -1802417264 (LWP 25218)]
[New Thread -1791927408 (LWP 25053)]
[New Thread -1781437552 (LWP 25052)]
[New Thread -1647314032 (LWP 25051)]
[New Thread -1634006128 (LWP 25050)]
[New Thread -1719506032 (LWP 25049)]
[New Thread -1729995888 (LWP 25048)]
(no debugging symbols found)
0x00a18402 in __kernel_vsyscall ()

Thread 1 (Thread -1208322352 (LWP 11641))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gth_location_new
  • #5 g_cclosure_marshal_VOID__OBJECT
    from /lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 g_signal_chain_from_overridden
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #10 gnome_vfs_volume_monitor_emit_pre_unmount
    from /usr/lib/libgnomevfs-2.so.0
  • #11 gnome_vfs_volume_monitor_client_shutdown_private
    from /usr/lib/libgnomevfs-2.so.0
  • #12 dbus_connection_dispatch
    from /lib/libdbus-1.so.3
  • #13 dbus_server_setup_with_g_main
    from /usr/lib/libdbus-glib-1.so.2
  • #14 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (3332975 sec old) ---------------------
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
QApplication::postEvent: Unexpected null receiver
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-06-22 15:04:41 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 356623 ***