Bug 392969 – crash in Rhythmbox Music Player: closing

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 392969 - crash in Rhythmbox Music Player: closing


Summary:	crash in Rhythmbox Music Player: closing


Status:	RESOLVED INVALID

Product:	rhythmbox
Classification:	Other
Component:	general
Version:	0.9.7
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	RhythmBox Maintainers
QA Contact:	RhythmBox Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-01-05 00:58 UTC by Andrea V.
Modified:	2007-01-24 14:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Andrea V. 2007-01-05 00:58:40 UTC

What were you doing when the application crashed?
closing


Distribution: Fedora Core release 6 (Rawhide)
Gnome Release: 2.17.2 2006-11-07 (Red Hat, Inc)
BugBuddy Version: 2.17.3

System: Linux 2.6.19-1.2904.fc7 #0 SMP Tue Jan 2 00:25:46 EST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Enabled

Memory status: size: 109101056 vsize: 0 resident: 109101056 share: 0 rss: 29900800 rss_rlim: 0
CPU usage: start_time: 1167958497 rtime: 0 utime: 368 stime: 0 cutime:286 cstime: 0 timeout: 82 it_real_value: 0 frequency: 5

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 -1208621344 (LWP 20087)]
[New Thread -1256703088 (LWP 20094)]
(no debugging symbols found)
0x008f1402 in __kernel_vsyscall ()

+ Trace 99484

Thread 1 (Thread -1208621344 (LWP 20087))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 g_list_first
from /lib/libglib-2.0.so.0
#5 rb_podcast_manager_entry_downloaded
#6 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#7 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#8 g_main_context_check
from /lib/libglib-2.0.so.0
#9 g_main_loop_run
from /lib/libglib-2.0.so.0
#10 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#11 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
(rhythmbox:20087): Rhythmbox-WARNING **: Unable to stop mDNS browsing: Il servizion MDNS non è in esecuzione
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
warning: the debug information found in "/usr/lib/debug//usr/bin/rhythmbox.debug" does not match "/usr/bin/rhythmbox" (CRC mismatch).
warning: the debug information found in "/usr/lib/debug//usr/lib/libtotem-plparser.so.1.3.0.debug" does not match "/usr/lib/libtotem-plparser.so.1" (CRC mismatch).
** (nm-applet:9690): WARNING **: <WARN>  nma_dbus_init(): could not acquire its service.  dbus_bus_acquire_service() says: 'Connection ":1.22" is not allowed to own the service "org.freedesktop.Networ
--------------------------------------------------

Comment 1 Alex Lancaster 2007-01-05 08:19:55 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. Thanks in advance!

Comment 2 Andrea V. 2007-01-24 14:40:44 UTC

Sorry, I reported this bug but now I upgraded my system to FC6 (development) and now I am not able to reproduce it so I changed the status to INVALID (I think this is the status for bad bug reports).