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 452874 - crash in Rhythmbox Music Player: closing the app in the s...
crash in Rhythmbox Music Player: closing the app in the s...
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-01 15:52 UTC by Rui Gouveia
Modified: 2007-07-01 22:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Rui Gouveia 2007-07-01 15:52:13 UTC 
What were you doing when the application crashed?
closing the app in the systray.


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: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 127438848 vsize: 127438848 resident: 41959424 share: 25591808 rss: 41959424 rss_rlim: 4294967295
CPU usage: start_time: 1183305017 rtime: 329 utime: 304 stime: 25 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 -1208292816 (LWP 5923)]
[New Thread -1268413552 (LWP 5998)]
[New Thread -1279554672 (LWP 5950)]
[New Thread -1235604592 (LWP 5935)]
[New Thread -1257395312 (LWP 5932)]
(no debugging symbols found)
0x0083c402 in __kernel_vsyscall ()

+ Trace 145072

Thread 2 (Thread -1268413552 (LWP 5998))

  • #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 IA__g_logv
  • #8 IA__g_log
  • #9 g_mutex_free_posix_impl
    at gthread-posix.c line 171
  • #10 _gnome_vfs_job_destroy
    at gnome-vfs-job.c line 656
  • #11 thread_entry_point
    at gnome-vfs-job-queue.c line 76
  • #12 g_thread_pool_thread_proxy
    at gthreadpool.c line 265
  • #13 g_thread_create_proxy
    at gthread.c line 591
  • #14 start_thread
    from /lib/libpthread.so.0
  • #15 clone
    from /lib/libc.so.6 


----------- .xsession-errors (56475 sec old) ---------------------
==========================================================================
==========================================================================
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 - 720 x 480 (preferred colorspace: Planar YV12)
VDec: using Planar YV12 as output csp (no 0)
Movie-Aspect is 1.50:1 - prescaling to correct movie aspect.
VO: [xv] 720x480 => 720x480 Planar YV12 
A:   0.1 V:   0.0 A-V:  0.124 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.0 A-V:  0.103 ct: -0.000   2/  2 ??% ??% ??,?% 0 0              
A:   0.1 V:   0.1 A-V:  0.061 ct: -0.0
  =====  PAUSE  =====
A:   7.0 V:   6.8 A-V:  0.249 ct:  0.116 163/163  3%  2%  0.6% 1 0              
A:   7.0 V:   6.8 A-V:  0.212 ct:  0.116 164/164  3%  2%  0.6% 2 0              
A:   7.0 V:   6.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-07-01 22:32:46 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 ***