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 358425 - crash in gThumb Image Viewer: Ran gthumb from command-...
crash in gThumb Image Viewer: Ran gthumb from command-...
Status: RESOLVED DUPLICATE of bug 358405
Product: gthumb
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
Paolo Bacchilega
Depends on:
Blocks:
 
 
Reported: 2006-09-30 04:15 UTC by Steve Smith
Modified: 2009-04-11 10:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description Steve Smith 2006-09-30 04:15:19 UTC
What were you doing when the application crashed?
Ran gthumb from command-line in non-writable directory (/var/log/bootchart


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.0 2006-09-04 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 99885056 vsize: 0 resident: 99885056 share: 0 rss: 15654912 rss_rlim: 0
CPU usage: start_time: 1159589658 rtime: 0 utime: 84 stime: 0 cutime:76 cstime: 0 timeout: 8 it_real_value: 0 frequency: 0

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 -1227241280 (LWP 7442)]
[New Thread -1270281312 (LWP 7459)]
[New Thread -1239655520 (LWP 7452)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1227241280 (LWP 7442))

  • #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_chooser_button_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_file_chooser_button_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 g_object_newv
    from /usr/lib/libgobject-2.0.so.0
  • #8 glade_standard_build_widget
    from /usr/lib/libglade-2.0.so.0
  • #9 glade_xml_build_widget
    from /usr/lib/libglade-2.0.so.0
  • #10 glade_standard_build_children
    from /usr/lib/libglade-2.0.so.0
  • #11 glade_xml_set_common_params
    from /usr/lib/libglade-2.0.so.0
  • #12 glade_xml_build_widget
    from /usr/lib/libglade-2.0.so.0
  • #13 glade_standard_build_children
    from /usr/lib/libglade-2.0.so.0
  • #14 glade_xml_set_common_params
    from /usr/lib/libglade-2.0.so.0
  • #15 glade_xml_build_widget
    from /usr/lib/libglade-2.0.so.0
  • #16 glade_standard_build_children
    from /usr/lib/libglade-2.0.so.0
  • #17 glade_xml_set_common_params
    from /usr/lib/libglade-2.0.so.0
  • #18 glade_xml_build_widget
    from /usr/lib/libglade-2.0.so.0
  • #19 glade_standard_build_children
    from /usr/lib/libglade-2.0.so.0
  • #20 glade_xml_set_common_params
    from /usr/lib/libglade-2.0.so.0
  • #21 glade_xml_handle_internal_child
    from /usr/lib/libglade-2.0.so.0
  • #22 glade_standard_build_children
    from /usr/lib/libglade-2.0.so.0
  • #23 glade_parser_parse_file
    from /usr/lib/libglade-2.0.so.0
  • #24 glade_xml_set_common_params
    from /usr/lib/libglade-2.0.so.0
  • #25 glade_xml_build_widget
    from /usr/lib/libglade-2.0.so.0
  • #26 glade_standard_build_children
    from /usr/lib/libglade-2.0.so.0
  • #27 glade_xml_construct
    from /usr/lib/libglade-2.0.so.0
  • #28 glade_xml_new
    from /usr/lib/libglade-2.0.so.0
  • #29 gth_browser_new
  • #30 all_windows_update_catalog_list
  • #31 main
  • #0 __kernel_vsyscall

Comment 1 Elijah Newren 2006-09-30 04:21:45 UTC
I suspect this may be a duplicate of bug 358405 (which we've recently seen an influx of duplicates of)...
Comment 2 André Klapper 2006-09-30 10:05:12 UTC
yes it is. filechooser in gtk+ 2.10.4 is broken.

*** This bug has been marked as a duplicate of 358405 ***
Comment 3 Sebastien Bacher 2009-04-11 10:56:45 UTC
*** Bug 578681 has been marked as a duplicate of this bug. ***