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 500916 - crash in Rhythmbox Music Player: actualizando el sistema
crash in Rhythmbox Music Player: actualizando el sistema
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-12-01 19:38 UTC by rmcruz123
Modified: 2007-12-01 22:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description rmcruz123 2007-12-01 19:38:42 UTC
What were you doing when the application crashed?
actualizando el sistema


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.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 149504000 vsize: 149504000 resident: 35287040 share: 19615744 rss: 35287040 rss_rlim: 4294967295
CPU usage: start_time: 1196537585 rtime: 3115 utime: 2662 stime: 453 cutime:8 cstime: 6 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208822048 (LWP 8596)]
[New Thread -1310233712 (LWP 9016)]
[New Thread -1332745328 (LWP 8727)]
[New Thread -1225163888 (LWP 8699)]
[New Thread -1257784432 (LWP 8651)]
[New Thread -1268274288 (LWP 8624)]
(no debugging symbols found)
0x00312402 in __kernel_vsyscall ()

Thread 2 (Thread -1310233712 (LWP 9016))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/i686/nosegneg/libc.so.6
  • #6 abort
    from /lib/i686/nosegneg/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 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0


----------- .xsession-errors (14 sec old) ---------------------
warning: .dynamic section for "/usr/lib/libsoup-2.2.so.8" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libnotify.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libtotem-plparser.so.1" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
warning: .dynamic section for "/usr/lib/libvorbisenc.so.2" is not at the expected address
warning: difference appears to be caused by prelink, adjusting expectations
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-12-01 22:38:34 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 ***