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 408486 - crash in gThumb Image Viewer: moving pictures to a new...
crash in gThumb Image Viewer: moving pictures to a new...
Status: RESOLVED DUPLICATE of bug 353127
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2007-02-16 04:15 UTC by elanorelle
Modified: 2007-02-16 12:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description elanorelle 2007-02-16 04:15:23 UTC 
What were you doing when the application crashed?
moving pictures to a new directory


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 227983360 vsize: 0 resident: 227983360 share: 0 rss: 52817920 rss_rlim: 0
CPU usage: start_time: 1171599226 rtime: 0 utime: 718 stime: 0 cutime:672 cstime: 0 timeout: 46 it_real_value: 0 frequency: 2

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226991424 (LWP 4006)]
[New Thread -1438397536 (LWP 4037)]
[New Thread -1430004832 (LWP 4036)]
[New Thread -1421612128 (LWP 4035)]
[New Thread -1329185888 (LWP 4024)]
[New Thread -1259111520 (LWP 4022)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 111165

Thread 1 (Thread -1226991424 (LWP 4006))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/tls/i686/cmov/libc.so.6
  • #5 _gtk_file_system_model_path_do
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 _gtk_file_chooser_default_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #8 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #9 fs_module_init
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #10 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #14 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 main
  • #0 __kernel_vsyscall 






Comment 1


Michael Chudobiak





          2007-02-16 12:35:39 UTC
        



This is supposed to be fixed in gtk+ 2.10.8 and later. Please check and see what version of libgtk2.0 is installed on your system. If it is 2.10.8 or later, please report the problem in bug 353127.


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