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 444038 - crash in Rhythmbox Music Player: Trying to listen to Magn...
crash in Rhythmbox Music Player: Trying to listen to Magn...
Status: RESOLVED DUPLICATE of bug 434003
Product: rhythmbox
Classification: Other
Component: general
0.10.0
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-04 17:53 UTC by drushell
Modified: 2007-06-04 19:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description drushell 2007-06-04 17:53:34 UTC
What were you doing when the application crashed?
Trying to listen to Magnatune


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 152137728 vsize: 152137728 resident: 49901568 share: 18870272 rss: 49901568 rss_rlim: 4294967295
CPU usage: start_time: 1180979239 rtime: 1354 utime: 1274 stime: 80 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208571344 (LWP 8632)]
[New Thread -1299154032 (LWP 8866)]
[New Thread -1230595184 (LWP 8830)]
[New Thread -1256535152 (LWP 8822)]
[New Thread -1277908080 (LWP 8811)]
[New Thread -1220105328 (LWP 8760)]
[New Thread -1245709424 (LWP 8702)]
(no debugging symbols found)
0x00ef3402 in __kernel_vsyscall ()

Thread 2 (Thread -1299154032 (LWP 8866))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libgthread-2.0.so.0
  • #10 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #11 ??
  • #12 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #13 ??
  • #14 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #15 ??
  • #16 free
    from /lib/libc.so.6


----------- .xsession-errors (123 sec old) ---------------------
(gnome-about-me:3553): about-me-properties-WARNING **: e_book_get_self: there was no self contact UID stored in gconf
(gnome-about-me:3569): about-me-properties-WARNING **: e_book_get_self: there was no self contact UID stored in gconf
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
error getting update info:  Cannot open/read repomd.xml file for repository: fedora
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x69 specified for 0x1000cd5 ().
Window manager warning: Invalid WM_TRANSIENT_FOR window 0x69 specified for 0x10010a7 ().
(gnome-terminal:3691): Vte-WARNING **: No handler for control sequence `device-control-string' defined.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000021 (Music Play)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Baptiste Mille-Mathias 2007-06-04 19:27:52 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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