Bug 488444 – rhythmbox segfaults on exit

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 488444 - rhythmbox segfaults on exit


Summary:	rhythmbox segfaults on exit


Status:	RESOLVED DUPLICATE of bug 484988

Product:	libsoup
Classification:	Core
Component:	HTTP Transport
Version:	2.2.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	Dan Winship
QA Contact:	Dan Winship

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-19 22:27 UTC by Ritesh Khadgaray ( irc:ritz)
Modified:	2007-11-01 21:20 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Ritesh Khadgaray ( irc:ritz) 2007-10-19 22:27:47 UTC

Description:
  Unable to exit rhythmbox.

How reproducible:
  Always reproducible.

Step to reproduce:

  1. Open rb
  2. Open a podcast, and play the same
  3. Click on "Close" button, or use "Music->Quit"
  4. rb exits and opens up again.

Running fb from commandline shows a segv.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1208752352 (LWP 17990)]
(gdb) thread apply all bt

+ Trace 171554

Thread 1 (Thread -1208752352 (LWP 17990))

#0 ??
from /usr/lib/libgdk-x11-2.0.so.0
#1 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#2 ??
from /lib/libglib-2.0.so.0
#3 g_main_loop_run
from /lib/libglib-2.0.so.0
#4 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#5 main


Workaround:
  killall -9 rhythmbox.


Notes:
 Using rawhide updated as of today.

Comment 1 Christian Kirbach 2007-10-19 22:29:18 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 Ritesh Khadgaray ( irc:ritz) 2007-10-19 22:48:25 UTC

wow ! super fast reponse.

reported this bug with fedora
https://bugzilla.redhat.com/show_bug.cgi?id=343561

i suspect rb resfusing to die is to do with dbus-activation code. pasted below bt of rb's segfault.

(gdb) where

+ Trace 171563

#0 gdk_event_dispatch
at gdkevents-x11.c line 2356
#1 IA__g_main_context_dispatch
at gmain.c line 2061
#2 g_main_context_iterate
at gmain.c line 2694
#3 IA__g_main_loop_run
at gmain.c line 2898
#4 IA__gtk_main
at gtkmain.c line 1146
#5 main
#5 main

2351            (*_gdk_event_func) (event, _gdk_event_data);
2352          
2353          gdk_event_free (event);
2354        }
2355      
2356      GDK_THREADS_LEAVE ();
2357
2358      return TRUE;
2359    }
2360

Comment 3 Jonathan Matthew 2007-10-19 23:27:32 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 484988 ***

Comment 4 Ritesh Khadgaray ( irc:ritz) 2007-10-24 10:46:23 UTC

additionally, I moved all plugins out of tree

 $ mv /usr/lib/rhythmbox /tmp

started rb, and clicked on close. rb still segfaulted and opened up again :(

-------

w.r.t. bug, my bad, traced this to gstreamer-plugins-ugly package.
on removing a file, this issue was not seen anymore.


the issue was with rb-metadata segfaulting.

Oct 22 23:58:46 localhost kernel: rhythmbox-metad[8797]: segfault at 00000000
eip 00000000 esp b7355f6c error 4

(gdb) thread apply all bt

+ Trace 172499

Comment 5 Ritesh Khadgaray ( irc:ritz) 2007-10-24 10:50:02 UTC

i suspect this is a bug with gstreamer-ugly package.

Comment 6 Ritesh Khadgaray ( irc:ritz) 2007-11-01 21:17:34 UTC

i have hit another bug with gstreamer as confirmed by bastien. closing this as duplicate, and opening a new bug for gstreamer ugly plugin package.

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