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 457709 - crash in Rhythmbox Music Player: ouvindo musica
crash in Rhythmbox Music Player: ouvindo musica
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-07-17 17:50 UTC by kmal_us
Modified: 2007-07-18 10:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kmal_us 2007-07-17 17:50:33 UTC 
What were you doing when the application crashed?
ouvindo musica		


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 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: 140541952 vsize: 140541952 resident: 49885184 share: 31637504 rss: 49885184 rss_rlim: 4294967295
CPU usage: start_time: 1184694480 rtime: 752 utime: 701 stime: 51 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 -1208436176 (LWP 5479)]
[New Thread -1341305968 (LWP 5586)]
[New Thread -1299346544 (LWP 5525)]
[New Thread -1278100592 (LWP 5514)]
[New Thread -1226142832 (LWP 5504)]
[New Thread -1249703024 (LWP 5493)]
(no debugging symbols found)
0x00ea7402 in __kernel_vsyscall ()

+ Trace 148633

Thread 2 (Thread -1341305968 (LWP 5586))

  • #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 ??
  • #17 ??
  • #18 ??
  • #19 ??
  • #20 ??
    from /lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
    from /lib/libglib-2.0.so.0 


----------- .xsession-errors (3080 sec old) ---------------------
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
Network sensor: can not find eth1
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-18 10:09:23 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 ***