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 477340 - crash in Rhythmbox Music Player: in short: - installed li...
crash in Rhythmbox Music Player: in short: - installed li...
Status: RESOLVED DUPLICATE of bug 469852
Product: rhythmbox
Classification: Other
Component: general
0.11.x
Other All
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-15 23:43 UTC by matthias
Modified: 2007-09-20 11:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description matthias 2007-09-15 23:43:59 UTC
Version: 0.11.2

What were you doing when the application crashed?
in short:
- installed libupnp(-devel) via yum ( from fedora repo, version 0:1.6.0-1.fc7 )
- had rhythmbox running and playing from a samba share via gnome-vfs
- enabled rhythmbox's upnp plugin 
-> bug buddy informs of crash

rhythmbox is version 0.11 rebuild from a srpm in rawhide 


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

System: Linux 2.6.22.5-76.fc7 #1 SMP Thu Aug 30 13:47:21 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Darkilouche
Icon Theme: Tango

Memory status: size: 267988992 vsize: 267988992 resident: 86097920 share: 44285952 rss: 86097920 rss_rlim: 4294967295
CPU usage: start_time: 1189890385 rtime: 44310 utime: 41959 stime: 2351 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208645920 (LWP 30519)]
[New Thread -1351828592 (LWP 32298)]
[New Thread -1331696752 (LWP 32297)]
[New Thread -1302738032 (LWP 32295)]
[New Thread -1416643696 (LWP 32294)]
[New Thread -1395663984 (LWP 32293)]
[New Thread -1406153840 (LWP 32292)]
[New Thread -1321206896 (LWP 30525)]
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208645920 (LWP 30519))

  • #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 __assert_fail
    from /lib/libc.so.6
  • #8 PyGILState_Release
    from /usr/lib/libpython2.5.so.1.0
  • #9 impl_activate
    at rb-python-plugin.c line 128
  • #10 rb_plugin_activate
    at rb-plugin.c line 153
  • #11 rb_plugins_engine_activate_plugin
    at rb-plugins-engine.c line 487
  • #12 plugin_manager_set_active
    at rb-plugin-manager.c line 284
  • #13 plugin_manager_toggle_active
    at rb-plugin-manager.c line 323
  • #14 active_toggled_cb
    at rb-plugin-manager.c line 149
  • #15 g_cclosure_marshal_VOID__STRING
    from /lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #17 ??
    from /lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #19 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #21 gtk_cell_renderer_activate
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #23 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #24 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 ??
    from /lib/libgobject-2.0.so.0
  • #27 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #28 ??
    from /lib/libgobject-2.0.so.0
  • #29 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #30 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #31 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #34 ??
    from /usr/lib/libgdk-x11-2.0.so.0
  • #35 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #36 ??
    from /lib/libglib-2.0.so.0
  • #37 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #38 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #39 main
    at main.c line 306
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** (gnome-system-monitor:32102): WARNING **: SELinux was found but is not enabled.
WARN  coherence                   Sep 16 01:31:47  Coherence UPnP framework version 0.4.0 starting... (coherence/base.py:156)
rhythmbox: Python/pystate.c:610: PyGILState_Release: Assertion `oldstate == PyGILState_UNLOCKED' failed.
warning: the debug information found in "/usr/lib/debug//usr/lib/gstreamer-0.10/libgstjack.so.debug" does not match "/usr/lib/gstreamer-0.10/libgstjack.so" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/gstreamer-0.10/libgstmad.so.debug" does not match "/usr/lib/gstreamer-0.10/libgstmad.so" (CRC mismatch).
Cannot access memory at address 0x7737
Cannot access memory at address 0x7737
--------------------------------------------------
Comment 1 Jonathan Matthew 2007-09-20 11:43:56 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 469852 ***