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 481746 - 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-09-30 01:44 UTC by sodoturcu
Modified: 2007-09-30 11:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description sodoturcu 2007-09-30 01:44:59 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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 136167424 vsize: 136167424 resident: 34373632 share: 18452480 rss: 34373632 rss_rlim: 4294967295
CPU usage: start_time: 1191116552 rtime: 283 utime: 257 stime: 26 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 -1208387024 (LWP 10386)]
[New Thread -1319806064 (LWP 10408)]
[New Thread -1288336496 (LWP 10403)]
[New Thread -1277580400 (LWP 10399)]
[New Thread -1245717616 (LWP 10393)]
[New Thread -1234076784 (LWP 10390)]
(no debugging symbols found)
0x001e7402 in __kernel_vsyscall ()

+ Trace 166519

Thread 3 (Thread -1288336496 (LWP 10403))

  • #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 ?? 






Comment 1


Jonathan Matthew





          2007-09-30 11:16:02 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 ***