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 513339 - crash in Rhythmbox Music Player: Clicked on menu item Mus...
crash in Rhythmbox Music Player: Clicked on menu item Mus...
Status: RESOLVED INCOMPLETE
Product: rhythmbox
Classification: Other
Component: general
0.10.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-31 04:08 UTC by neil
Modified: 2008-02-20 07:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description neil 2008-01-31 04:08:55 UTC
Version: 0.10.1

What were you doing when the application crashed?
Clicked on menu item Music-Import Folder.


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

System: Linux 2.6.23.12-52.fc7 #1 SMP Tue Dec 18 21:18:02 EST 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: 97382400 vsize: 97382400 resident: 33443840 share: 22282240 rss: 33443840 rss_rlim: 4294967295
CPU usage: start_time: 1201734374 rtime: 75 utime: 62 stime: 13 cutime:14 cstime: 4 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 -1208350160 (LWP 3831)]
[New Thread -1220088944 (LWP 3837)]
[New Thread -1245709424 (LWP 3836)]
[New Thread -1233110128 (LWP 3835)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208350160 (LWP 3831))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #5 ??
    from /lib/libglib-2.0.so.0
  • #6 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #7 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (116 sec old) ---------------------
** Message: Missing plugin: gstreamer.net|0.10|totem|MPEG-1 Layer 3 (MP3) decoder|decoder-audio/mpeg, mpegversion=(int)1, layer=(int)3 (MPEG-1 Layer 3 (MP3) decoder)
** Message: Automatic missing codec installation not supported (helper script missing)
(bug-buddy:3604): GLib-GObject-WARNING **: invalid uninstantiatable type `GParamChar' in cast to `GObject'
(bug-buddy:3604): GLib-GObject-CRITICAL **: g_object_get_data: assertion `G_IS_OBJECT (object)' failed
(bug-buddy:3604): GLib-CRITICAL **: g_hash_table_destroy: assertion `hash_table->ref_count > 0' failed
(bug-buddy:3604): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x3200020 (02-janet.j)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** Message: don't know how to handle audio/mpeg, mpegversion=(int)1, layer=(int)3, rate=(int)44100, channels=(int)2, codec_data=(buffer)010002000000a10101007105
/usr/lib/python2.5/site-packages/pirut/Progress.py:87: GtkWarning: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
  self.pbar.set_fraction(fract)
--------------------------------------------------
Comment 1 Jonathan Matthew 2008-02-02 01:10:58 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
Comment 2 Jeff Cai 2008-02-20 07:20:21 UTC
*** Bug 516598 has been marked as a duplicate of this bug. ***