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 451036 - crash in Rhythmbox Music Player: I just loaded a new tra...
crash in Rhythmbox Music Player: I just loaded a new tra...
Status: RESOLVED DUPLICATE of bug 436456
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-25 20:02 UTC by yahn_ick
Modified: 2007-06-25 22:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description yahn_ick 2007-06-25 20:02:11 UTC
What were you doing when the application crashed?
I just loaded  a new track in jamendo, it was hardcore maybe my computer doesn' like that. oh and in the same time i've gone to firefox 2.0.4


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (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: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 366501888 vsize: 366501888 resident: 182542336 share: 21839872 rss: 182542336 rss_rlim: 4294967295
CPU usage: start_time: 1182799413 rtime: 27243 utime: 25905 stime: 1338 cutime:3 cstime: 1 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 -1208276432 (LWP 3607)]
[New Thread -1411867760 (LWP 19043)]
[New Thread -1401377904 (LWP 19042)]
[New Thread -1390888048 (LWP 19041)]
[New Thread -1345328240 (LWP 19040)]
[New Thread -1334838384 (LWP 19037)]
[New Thread -1322255472 (LWP 19036)]
[New Thread -1255597168 (LWP 19026)]
[New Thread -1276576880 (LWP 19025)]
[New Thread -1245107312 (LWP 3616)]
(no debugging symbols found)
0x00449402 in __kernel_vsyscall ()

Thread 1 (Thread -1208276432 (LWP 3607))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyErr_Occurred
    from /usr/lib/libpython2.5.so.1.0
  • #5 PyGC_Collect
    from /usr/lib/libpython2.5.so.1.0
  • #6 ??
  • #7 ??
    from /lib/libglib-2.0.so.0
  • #8 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #11 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (5768 sec old) ---------------------
Selected video codec: [ffdivx] vfm: ffmpeg (FFmpeg DivX ;-) (MS MPEG-4 v3))
==========================================================================
==========================================================================
Opening audio decoder: [mp3lib] MPEG layer-2, layer-3
AUDIO: 48000 Hz, 2 ch, s16le, 128.0 kbit/8.33% (ratio: 16000->192000)
Selected audio codec: [mp3] afm: mp3lib (mp3lib MPEG layer-2, layer-3)
==========================================================================
AO: [alsa] 48000Hz 2ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 512 x 384 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 512x384 => 512x384 Planar YV12 
A:   0.1 V:   0.0 A-V:  0.131 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.0 A-V:  0.113 ct:  0.001   2/  2 ??% ??% ??,?% 1 0              
A:   0.2 V:   0.1 A-V:  0.088 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-25 22:39:10 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 436456 ***