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 464932 - crash in gThumb Image Viewer: running gimp saving a ch...
crash in gThumb Image Viewer: running gimp saving a ch...
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-08-09 05:21 UTC by thorppe
Modified: 2007-08-09 10:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description thorppe 2007-08-09 05:21:31 UTC 
What were you doing when the application crashed?
running gimp saving a change on picture then trying to get back to evolution to email the saved photo


Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Memory status: size: 239448064 vsize: 0 resident: 239448064 share: 0 rss: 36843520 rss_rlim: 0
CPU usage: start_time: 1186636299 rtime: 0 utime: 514 stime: 0 cutime:489 cstime: 0 timeout: 25 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1228695872 (LWP 6939)]
[New Thread -1338000480 (LWP 6950)]
[New Thread -1329607776 (LWP 6949)]
[New Thread -1321215072 (LWP 6948)]
[New Thread -1312822368 (LWP 6947)]
[New Thread -1286014048 (LWP 6944)]
[New Thread -1245394016 (LWP 6943)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

+ Trace 153892

Thread 1 (Thread -1228695872 (LWP 6939))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/libc.so.6
  • #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 /usr/lib/libgobject-2.0.so.0
  • #6 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #7 g_signal_override_class_closure
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /usr/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_get_type
    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 /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #17 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 main 






Comment 1


Pascal Terjan





          2007-08-09 10:52:04 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 ***