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 543343 - crash in Rhythmbox Music Player: Rhythmbox always crashes...
crash in Rhythmbox Music Player: Rhythmbox always crashes...
Status: RESOLVED DUPLICATE of bug 510236
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
: 544643 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-07-16 21:56 UTC by Anton Zinoviev
Modified: 2008-08-21 15:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Anton Zinoviev 2008-07-16 21:56:15 UTC
Version: 0.11.5

What were you doing when the application crashed?
Rhythmbox always crashes when I attach my flash memory (actualy a Nokia 770 device) to the computer.


Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-686 #1 SMP Fri Jun 27 03:23:20 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Yattacier3
Icon Theme: Neu

Memory status: size: 125136896 vsize: 125136896 resident: 37027840 share: 19066880 rss: 37027840 rss_rlim: 4294967295
CPU usage: start_time: 1216245224 rtime: 118 utime: 102 stime: 16 cutime:1 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb65509a0 (LWP 4640)]
[New Thread 0xb1b99b90 (LWP 4666)]
[New Thread 0xb239ab90 (LWP 4656)]
[New Thread 0xb2b9bb90 (LWP 4654)]
[New Thread 0xb339cb90 (LWP 4651)]
[New Thread 0xb3b9db90 (LWP 4650)]
[New Thread 0xb439eb90 (LWP 4649)]
[New Thread 0xb4bffb90 (LWP 4648)]
(no debugging symbols found)
0xb7f3a424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb65509a0 (LWP 4640))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 rhythmdb_entry_allocate
    from /usr/lib/librhythmbox-core.so.0
  • #7 rhythmdb_entry_new
    from /usr/lib/librhythmbox-core.so.0
  • #8 ??
    from /usr/lib/librhythmbox-core.so.0
  • #9 ??
  • #10 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(gbgoffice:3779): gtkmm-WARNING **: gtkmm: Attempt to call Gtk::manage() on a Gtk::Window, but a Gtk::Window has no parent container to manage its lifetime.
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
Предупреждение от мениджъра на прозорци: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1e0002c (Слуша)
Предупреждение от мениджъра на прозорци: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 Susana 2008-07-21 06:28:17 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 542936 ***
Comment 2 Anton Zinoviev 2008-07-21 13:22:21 UTC
I installed the package rhythmbox-dbg and the following is the new backtrace. Please tell me if I need to install the -dbg package for some library.

Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Fri Jun 27 04:49:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Yattacier3
Icon Theme: NoiaWarm

Memory status: size: 122531840 vsize: 122531840 resident: 43057152 share: 18808832 rss: 43057152 rss_rlim: 18446744073709551615
CPU usage: start_time: 1216646319 rtime: 314 utime: 294 stime: 20 cutime:18 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

[Thread debugging using libthread_db enabled]
[New Thread 0xf65869c0 (LWP 12044)]
[New Thread 0xf1efdb90 (LWP 12063)]
[New Thread 0xf26feb90 (LWP 12057)]
[New Thread 0xf2effb90 (LWP 12056)]
[New Thread 0xf38feb90 (LWP 12055)]
[New Thread 0xf4e29b90 (LWP 12054)]
[New Thread 0xf40ffb90 (LWP 12052)]
0xf7f39430 in __kernel_vsyscall ()

Thread 1 (Thread 0xf65869c0 (LWP 12044))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 rhythmdb_entry_allocate
    at rhythmdb.c line 1210
  • #7 rhythmdb_entry_new
    at rhythmdb.c line 1319
  • #8 rhythmdb_add_import_error_entry
    at rhythmdb.c line 1858
  • #9 rhythmdb_process_metadata_load_real
    at rhythmdb.c line 1898
  • #10 rhythmdb_process_one_event
    at rhythmdb.c line 2072
  • #11 rb_async_queue_watch_dispatch
    at rb-async-queue-watch.c line 61
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 ??
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 ??
  • #18 ??
  • #19 ??
    from /usr/lib/libglib-2.0.so.0
  • #20 ??
    from /usr/lib/libglib-2.0.so.0
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
    from /lib/i686/cmov/libc.so.6
  • #27 ??
    from /lib/i686/cmov/libpthread.so.0
  • #28 ??
    from /lib/i686/cmov/libpthread.so.0
  • #29 g_thread_self
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 main
    at main.c line 327
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
(rhythmbox:10873): Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && percentage <= 1.0' failed
(rhythmbox:10873): GLib-GObject-CRITICAL **: g_boxed_free: assertion `boxed != NULL' failed
(rhythmbox:10873): GLib-GObject-CRITICAL **: g_boxed_free: assertion `boxed != NULL' failed
(rhythmbox:10873): GLib-GObject-CRITICAL **: g_boxed_free: assertion `boxed != NULL' failed
(rhythmbox:10873): GLib-GObject-CRITICAL **: g_boxed_free: assertion `boxed != NULL' failed
Предупреждение от мениджъра на прозорци: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x300002c (Слуша)
Предупреждение от мениджъра на прозорци: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
closing
Предупреждение от мениджъра на прозорци: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x300002c (Слуша)
Предупреждение от мениджъра на прозорци: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 3 Anton Zinoviev 2008-07-21 13:37:38 UTC
I think I figured out how to find what packages to install. Here is a more complete backtrace.

Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-06-30 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25-2-amd64 #1 SMP Fri Jun 27 04:49:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Yattacier3
Icon Theme: NoiaWarm

Memory status: size: 236695552 vsize: 236695552 resident: 55635968 share: 22069248 rss: 55635968 rss_rlim: 18446744073709551615
CPU usage: start_time: 1216646975 rtime: 2241 utime: 2080 stime: 161 cutime:10 cstime: 7 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/rhythmbox'

[Thread debugging using libthread_db enabled]
[New Thread 0xf657e9c0 (LWP 4126)]
[New Thread 0xeb2f9b90 (LWP 4567)]
[New Thread 0xebafab90 (LWP 4566)]
[New Thread 0xec2fbb90 (LWP 4565)]
[New Thread 0xecafcb90 (LWP 4564)]
[New Thread 0xedafeb90 (LWP 4562)]
[New Thread 0xefef9b90 (LWP 4556)]
[New Thread 0xf0efbb90 (LWP 4555)]
[New Thread 0xee2ffb90 (LWP 4423)]
[New Thread 0xf16fcb90 (LWP 4418)]
[New Thread 0xf1efdb90 (LWP 4199)]
[New Thread 0xf26feb90 (LWP 4198)]
[New Thread 0xf40ffb90 (LWP 4197)]
[New Thread 0xf2effb90 (LWP 4196)]
[New Thread 0xef6f8b90 (LWP 4189)]
[New Thread 0xeeef7b90 (LWP 4157)]
[New Thread 0xf5f19b90 (LWP 4133)]
0xf7f31430 in __kernel_vsyscall ()

Thread 1 (Thread 0xf657e9c0 (LWP 4126))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 rhythmdb_entry_allocate
    at rhythmdb.c line 1210
  • #7 rhythmdb_entry_new
    at rhythmdb.c line 1319
  • #8 rhythmdb_add_import_error_entry
    at rhythmdb.c line 1858
  • #9 rhythmdb_process_metadata_load_real
    at rhythmdb.c line 1898
  • #10 rhythmdb_process_one_event
    at rhythmdb.c line 2072
  • #11 rb_async_queue_watch_dispatch
    at rb-async-queue-watch.c line 61
  • #12 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #13 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #14 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #15 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main
    at main.c line 327
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------

libWildMidi(WildMidi_Init:3707): ERROR Library not Initialized
Rhythmbox-Message: Missing plugin: gstreamer|0.10|rhythmbox-metadata|Декодер audio/midi|decoder-audio/midi (ignoring)
Rhythmbox-Message: All missing plugins are blacklisted, doing nothing
Rhythmbox-Message: Missing plugin: gstreamer|0.10|rhythmbox-metadata|Декодер application/x-ms-dos-executable|decoder-application/x-ms-dos-executable
no application found
Rhythmbox-Message: No installation candidate for missing plugins found.
Rhythmbox-Message: Missing plugin: gstreamer|0.10|rhythmbox-metadata|Декодер application/x-rar|decoder-application/x-rar
no application found
Rhythmbox-Message: No installation candidate for missing plugins found.
(rhythmbox:4126): GLib-GObject-CRITICAL **: g_type_class_add_private: assertion `private_size > 0' failed
(rhythmbox:4126): GLib-GObject-CRITICAL **: g_boxed_free: assertion `boxed != NULL' failed
Cannot access memory at address 0x0
Cannot access memory at address 0x0
--------------------------------------------------
Comment 4 André Klapper 2008-07-21 21:52:43 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 542936 ***
Comment 5 Susana 2008-07-21 23:10:11 UTC
Hi Anton,

Thank you for the better trace. :)

This is a duplicate of bug 510236 which is already fixed. It should be solved in the next software version. You may want to check for a software upgrade.
Comment 6 Anton Zinoviev 2008-07-22 20:35:31 UTC
The fix of bug 510236 is noted inside the changelog of the version of Rhythmbox I use (0.11.5 - 2008-03-07 while the fix of 510236 was on 2008-01-27). Because of this I think that either bug 543343 is not a duplicate of 510236 or both bugs are still not fixed.
Comment 7 Anton Zinoviev 2008-07-22 20:50:45 UTC
On the other hand I can confirm that if all files on the memory-card of my device are mp3 then Rhythmbox doesn't crash. Please tell me if my reasoning in my previous comment is wrong and I should test a newer version of Rhythmbox.
Comment 8 Anton Zinoviev 2008-07-25 12:30:13 UTC
*** Bug 544643 has been marked as a duplicate of this bug. ***
Comment 9 André Klapper 2008-08-21 15:00:20 UTC
I have reopened bug 510236.

*** This bug has been marked as a duplicate of 510236 ***