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 568893 - crash in Rhythmbox Music Player: When I tried to launch R...
crash in Rhythmbox Music Player: When I tried to launch R...
Status: RESOLVED DUPLICATE of bug 512570
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-01-23 18:27 UTC by samuli.seppanen
Modified: 2009-01-23 23:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description samuli.seppanen 2009-01-23 18:27:33 UTC 
Version: 0.11.6

What were you doing when the application crashed?
When I tried to launch Rhythmbox, it segfaults. The same behavior occurs whether I use the precompile Debian packages or roll my own using apt-src.


Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-ver4 #1 SMP Sat Jan 17 23:41:14 EET 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: Crux

Memory status: size: 48304128 vsize: 48304128 resident: 22102016 share: 13287424 rss: 22102016 rss_rlim: 4294967295
CPU usage: start_time: 1232735115 rtime: 41 utime: 30 stime: 11 cutime:1 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb665c720 (LWP 3167)]
0xb80a1424 in __kernel_vsyscall ()

+ Trace 211800

Thread 1 (Thread 0xb665c720 (LWP 3167))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #6 <signal handler called>
  • #7 rb_python_module_load_with_gil
    at rb-python-module.c line 341
  • #8 IA__g_type_module_use
    at /tmp/buildd/glib2.0-2.16.6/gobject/gtypemodule.c line 190
  • #9 rb_plugins_engine_activate_plugin
    at rb-plugins-engine.c line 487
  • #10 rb_plugins_engine_load_cb
    at rb-plugins-engine.c line 316
  • #11 rb_uri_handle_recursively_cb
    at rb-file-helpers.c line 966
  • #12 directory_visit_internal
    at gnome-vfs-directory.c line 401
  • #13 directory_visit_internal
    at gnome-vfs-directory.c line 426
  • #14 gnome_vfs_directory_visit
    at gnome-vfs-directory.c line 542
  • #15 rb_uri_handle_recursively
    at rb-file-helpers.c line 995
  • #16 rb_plugins_engine_init
    at rb-plugins-engine.c line 326
  • #17 rb_shell_constructor
    at rb-shell.c line 1395
  • #18 IA__g_object_newv
    at /tmp/buildd/glib2.0-2.16.6/gobject/gobject.c line 937
  • #19 IA__g_object_new_valist
    at /tmp/buildd/glib2.0-2.16.6/gobject/gobject.c line 1027
  • #20 IA__g_object_new
    at /tmp/buildd/glib2.0-2.16.6/gobject/gobject.c line 795
  • #21 rb_shell_new
    at rb-shell.c line 983
  • #22 main
    at main.c line 275
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
seahorse nautilus module initialized
** Message: <info>  Yhteys langattomaan verkkoon "Qantar" on nyt muodostettu.
** 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)
Cannot access memory at address 0x1
Cannot access memory at address 0x1
--------------------------------------------------
Comment 1 Jonathan Matthew 2009-01-23 23:03:23 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.

Looking at some duplicates, it seems this is caused by rhythmbox using the wrong python library.  Output from 'ldd /usr/bin/rhythmbox' might be interesting.


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