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 432247 - crash in gThumb Image Viewer: open dvd
crash in gThumb Image Viewer: open dvd
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-04-22 13:11 UTC by nexer
Modified: 2007-04-22 17:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description nexer 2007-04-22 13:11:42 UTC
What were you doing when the application crashed?
open dvd


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 17:46:00 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 833200128 vsize: 833200128 resident: 144109568 share: 14979072 rss: 144109568 rss_rlim: -1
CPU usage: start_time: 1177242172 rtime: 57448 utime: 55913 stime: 1535 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912507128928 (LWP 3622)]
[New Thread 1136679232 (LWP 3630)]
[New Thread 1126189376 (LWP 3629)]
[New Thread 1115699520 (LWP 3628)]
[New Thread 1105209664 (LWP 3627)]
[New Thread 1094719808 (LWP 3626)]
[New Thread 1084229952 (LWP 3625)]
(no debugging symbols found)
0x0000003e0ec0d96f in waitpid () from /lib64/libpthread.so.0

Thread 1 (Thread 46912507128928 (LWP 3622))

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


----------- .xsession-errors (10234 sec old) ---------------------
KK <xmms/xmms.cpp:593>	int Xmms::getCurrentPos()
KK <xmms/xmms.cpp:531>	QString Xmms::getTitle(int)
KK <xmms/xmms.cpp:593>	int Xmms::getCurrentPos()
KK <xmms/xmms.cpp:531>	QString Xmms::getTitle(int)
KK <xmms/xmms.cpp:593>	int Xmms::getCurrentPos()
KK <xmms/xmms.cpp:531>	QString Xmms::getTitle(int)
KK <xmms/xmms.cpp:593>	int Xmms::getCurrentPos()
KK <xmms/xmms.cpp:531>	QString Xmms::getTitle(int)
KK <xmms/xmms.cpp:593>	int Xmms::getCurrentPos()
KK <xmms/xmms.cpp:531>	QString Xmms::getTitle(int)
KK <xmms/xmms.cpp:593>	int Xmms::getCurrentPos()
KK <xmms/xmms.cpp:531>	QString Xmms::getTitle(int)
KK <xmms/xmms.cpp:593>	int Xmms::getCurrentPos()
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Michael Chudobiak 2007-04-22 17:16:59 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 ***