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 449908 - crash in Rhythmbox Music Player: J'ai cliqué sur la "croi...
crash in Rhythmbox Music Player: J'ai cliqué sur la "croi...
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-21 23:19 UTC by mathieu.bastide
Modified: 2007-06-22 14:23 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description mathieu.bastide 2007-06-21 23:19:40 UTC
What were you doing when the application crashed?
J'ai cliqué sur la "croix" pour fermer rhythmbox
I clicked on cross button in order to close rhythmbox


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: 141324288 vsize: 141324288 resident: 48418816 share: 26697728 rss: 48418816 rss_rlim: 4294967295
CPU usage: start_time: 1182467634 rtime: 1995 utime: 1833 stime: 162 cutime:14 cstime: 7 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 -1208772048 (LWP 14436)]
[New Thread -1340191856 (LWP 14468)]
[New Thread -1318876272 (LWP 14459)]
[New Thread -1230468208 (LWP 14451)]
[New Thread -1266029680 (LWP 14448)]
[New Thread -1255146608 (LWP 14444)]
(no debugging symbols found)
0x009b1402 in __kernel_vsyscall ()

Thread 2 (Thread -1340191856 (LWP 14468))

  • #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 (44037 sec old) ---------------------
Selected video codec: [ffdivx] vfm: ffmpeg (FFmpeg DivX ;-) (MS MPEG-4 v3))
==========================================================================
==========================================================================
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 11025 Hz, 1 ch, s16le, 10.2 kbit/5.76% (ratio: 1271->22050)
Selected audio codec: [ffwmav2] afm: ffmpeg (DivX audio v2 (FFmpeg))
==========================================================================
AO: [alsa] 48000Hz 1ch s16le (2 bytes per sample)
Starting playback...
VDec: vo config request - 320 x 240 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is undefined - no prescaling applied.
VO: [xv] 320x240 => 320x240 Planar YV12 
A:   5.2 V:   5.0 A-V:  0.180 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   5.3 V:   5.3 A-V: -0.046 ct: -0.005   2/  2 ??% ??% ??,?% 0 0              
A:   5.4 V:   5.4 A-V: -0.049 ct: -0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-06-22 14:23:43 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 ***