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 450224 - crash in Rhythmbox Music Player: Distribution: Fedora rel...
crash in Rhythmbox Music Player: Distribution: Fedora rel...
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-22 22:58 UTC by bratishka
Modified: 2007-06-23 00:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description bratishka 2007-06-22 22:58:11 UTC 
What were you doing when the application crashed?
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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 147120128 vsize: 147120128 resident: 49762304 share: 19374080 rss: 49762304 rss_rlim: 4294967295
CPU usage: start_time: 1182567267 rtime: 1701 utime: 1609 stime: 92 cutime:2 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 -1209042384 (LWP 15908)]
[New Thread -1239299184 (LWP 15984)]
[New Thread -1305494640 (LWP 15983)]
[New Thread -1326474352 (LWP 15973)]
[New Thread -1261483120 (LWP 15925)]
[New Thread -1250600048 (LWP 15916)]
(no debugging symbols found)
0x00f4f402 in __kernel_vsyscall ()

+ Trace 143017

Thread 2 (Thread -1239299184 (LWP 15984))

  • #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 (125 sec old) ---------------------
yum-updatesd (pid 2433) выполняется...
wpa_supplicant
wpa_supplicant остановлен
wpa_supplicant
wpa_supplicant остановлен
wpa_supplicant
wpa_supplicant остановлен
wpa_supplicant
wpa_supplicant остановлен
wpa_supplicant
wpa_supplicant остановлен
wpa_supplicant
wpa_supplicant остановлен
Предупреждение менеджера окон: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2800021 (Музык)
Предупреждение менеджера окон: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-23 00:21:28 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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