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 468973 - crash in CD Player:
crash in CD Player:
Status: RESOLVED DUPLICATE of bug 380124
Product: gnome-media
Classification: Deprecated
Component: Gnome-CD
2.16.x
Other All
: High critical
: ---
Assigned To: gnome media maintainers
gnome media maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-21 19:44 UTC by victorhantelmann
Modified: 2007-08-22 13:28 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description victorhantelmann 2007-08-21 19:44:46 UTC 
Version: 2.16.1

What were you doing when the application crashed?



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.19-1.2911.6.5.fc6xen #1 SMP Sun Mar 4 16:59:41 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: Enforcing
Accessibility: Disabled

Memory status: size: 92385280 vsize: 0 resident: 92385280 share: 0 rss: 35491840 rss_rlim: 0
CPU usage: start_time: 1187726504 rtime: 0 utime: 132 stime: 0 cutime:91 cstime: 0 timeout: 41 it_real_value: 0 frequency: 8

Backtrace was generated from '/usr/bin/gnome-cd'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209248048 (LWP 12540)]
0x00b63402 in __kernel_vsyscall ()

+ Trace 156934

Thread 1 (Thread -1209248048 (LWP 12540))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 cd_display_parse_theme
  • #5 theme_load
  • #6 preferences_new
  • #7 gconf_client_get_type
    from /usr/lib/libgconf-2.so.4
  • #8 gconf_listeners_notify
    from /usr/lib/libgconf-2.so.4
  • #9 gconf_client_value_changed
    from /usr/lib/libgconf-2.so.4
  • #10 gconf_client_value_changed
    from /usr/lib/libgconf-2.so.4
  • #11 g_source_is_destroyed
    from /lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #15 gtk_dialog_run
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gcd_error
  • #17 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (29255 sec old) ---------------------
CLIENT: SendNotifyTask: emitting finished
CLIENT: SendNotifyTask: Task::done()
CLIENT: SendNotifyTask: emitting finished
CLIENT: SendNotifyTask: Task::done()
CLIENT: SendNotifyTask: emitting finished
CLIENT: SendNotifyTask: Task::done()
CLIENT: SendNotifyTask: emitting finished
CLIENT: SendNotifyTask: Task::done()
CLIENT: SendNotifyTask: emitting finished
CLIENT: Task: Task::done()
CLIENT: Task: emitting finished
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
Very strange! got a DCOPReplyFailed opcode, but we were not waiting for a reply!
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 palfrey 2007-08-22 13:28:16 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 380124 ***