rhythmbox crashed with SIGSEGV in sem_post()

[Michael Blennerhassett]

Possible Workaround:

Try disabling all the python based plugins:
* Context Pane
* Cover art search
* IM status
* Magnatune store
* Python console
* Send tracks
* Song lyrics
* Ubuntu One
* Zeitgeist

Crashed while clicking 'next'

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: rhythmbox 2.99.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
Uname: Linux 3.9.0-6-generic x86_64
ApportVersion: 2.10.2-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Sat Jun 22 11:12:40 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2012-09-09 (285 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120905.2)
MarkForUpload: True
ProcCmdline: rhythmbox
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f76731561e0 <sem_post>: mov (%rdi),%eax
 PC (0x7f76731561e0) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
 Stack memory exhausted (SP below stack segment)
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0
 PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in sem_post()
UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 sem_post () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_post.S:33
 PyThread_release_lock () from /tmp/apport_sandbox_uP17lo/usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
 g_datalist_clear (datalist=0x0) at /build/buildd/glib2.0-2.37.1/./glib/gdataset.c:277
 g_object_finalize (object=0x7f761802d070) at /build/buildd/glib2.0-2.37.1/./gobject/gobject.c:1019
 g_object_unref (_object=0x7f761802d070) at /build/buildd/glib2.0-2.37.1/./gobject/gobject.c:3189

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[terry_gardener (terry-gardener)]

Rhythmbox closes itself down after couple of minutes when listening to music. I have had to to use audacious at the moment since Rhythmbox doesn't work.

[terry_gardener (terry-gardener)]

Rhythmbox works with manjaro in gnome 3.8.4

[terry_gardener (terry-gardener)]

just done some more testing to find it crashes for me. it is when the song end and rhythmbox tries to goto the next track. it turns darks and then crashes and closes. if you click next (or use the next button on remote) before the track ends it goes to the next track.

it also seems to send to many notifications and i get multiple nutofications on the desktop telling me the song title. it tells you and then it disappears and tells you again and again for about 3-5 times.

[terry_gardener (terry-gardener)]

i have done further tests with regard to this and i have established that it is the plugin zeitgeist that is causing the crashing. the way i tested this was i disabled all plugins and tested it. then reactivated each plugin one by one.

terminal output when i ran rhythmbox from terminal.
rhythmbox

(rhythmbox:2440): GLib-GObject-CRITICAL **: Custom constructor for class SoupServer returned NULL (which is invalid). Unable to remove object from construction_objects list, so memory was probably just leaked. Please use GInitable instead.

(rhythmbox:2440): Gtk-CRITICAL **: gtk_tree_model_get_iter_first: assertion 'GTK_IS_TREE_MODEL (tree_model)' failed

(rhythmbox:2440): Gtk-CRITICAL **: gtk_combo_box_set_active_iter: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed

(rhythmbox:2440): Gtk-CRITICAL **: gtk_list_store_clear: assertion 'GTK_IS_LIST_STORE (list_store)' failed

(rhythmbox:2440): Gtk-CRITICAL **: gtk_widget_set_sensitive: assertion 'GTK_IS_WIDGET (widget)' failed

(rhythmbox:2440): Gtk-CRITICAL **: gtk_combo_box_set_active: assertion 'GTK_IS_COMBO_BOX (combo_box)' failed

(rhythmbox:2440): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed

(rhythmbox:2440): Gtk-CRITICAL **: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed /usr/lib/rhythmbox/plugins/rbzeitgeist/rbzeitgeist.py:114: PyGIDeprecationWarning: idle_add is deprecated; use GLib.idle_add instead GObject.idle_add(self.send_to_zeitgeist, db, entry, event_type) /usr/lib/rhythmbox/plugins/rbzeitgeist/rbzeitgeist.py:94: PyGIDeprecationWarning: idle_add is deprecated; use GLib.idle_add instead GObject.idle_add(self.reset_manual_switch) Segmentation fault (core dumped)

[Jonathan Hyry (jon-3)]

I am having this problem as well, exactly as described by terry_gardener, above. I have attached a GDB backtrace and execution log with all debugging symbols installed so nothing is missing.

This is still an issue in Saucy currently, though it must not be for very many people. Wondering why this affects such a small user base?

Please let me know if there is any other information I can provide to assist in fixing this issue.

Jon

[Jonathan Hyry (jon-3)]

I have also just confirmed that turning off the zeitgeist plugin relieves this bug. There must be an issue with that plugin specifically.

[rithik g (gkrithi)]

Is this still a problem ?

[Artyom Kazak (artyom-kazak)]

I don't use either rhythmbox or Ubuntu anymore, so I can't say.

On 1 Nov 2017 11:55 p.m., "rithik g" <email address hidden> wrote:

> Is this still a problem ?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1199159).
> https://bugs.launchpad.net/bugs/1193525
>
> Title:
> rhythmbox crashed with SIGSEGV in sem_post()
>
> Status in Rhythmbox:
> Expired
> Status in rhythmbox package in Ubuntu:
> Confirmed
>
> Bug description:
> Possible Workaround:
>
> Try disabling all the python based plugins:
> * Context Pane
> * Cover art search
> * IM status
> * Magnatune store
> * Python console
> * Send tracks
> * Song lyrics
> * Ubuntu One
> * Zeitgeist
>
> Crashed while clicking 'next'
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.10
> Package: rhythmbox 2.99.1-0ubuntu1
> ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6
> Uname: Linux 3.9.0-6-generic x86_64
> ApportVersion: 2.10.2-0ubuntu2
> Architecture: amd64
> CrashCounter: 1
> Date: Sat Jun 22 11:12:40 2013
> ExecutablePath: /usr/bin/rhythmbox
> InstallationDate: Installed on 2012-09-09 (285 days ago)
> InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64
> (20120905.2)
> MarkForUpload: True
> ProcCmdline: rhythmbox
> ProcEnviron:
> XDG_RUNTIME_DIR=<set>
> SHELL=/bin/bash
> LANGUAGE=en_AU:en
> PATH=(custom, no user)
> LANG=en_AU.UTF-8
> SegvAnalysis:
> Segfault happened at: 0x7f76731561e0 <sem_post>: mov (%rdi),%eax
> PC (0x7f76731561e0) ok
> source "(%rdi)" (0x00000000) not located in a known VMA region (needed
> readable region)!
> destination "%eax" ok
> Stack memory exhausted (SP below stack segment)
> SegvReason: reading NULL VMA
> Signal: 11
> SourcePackage: rhythmbox
> StacktraceTop:
> sem_post () from /lib/x86_64-linux-gnu/libpthread.so.0
> PyThread_release_lock () from /usr/lib/x86_64-linux-gnu/
> libpython2.7.so.1.0
> g_datalist_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
> Title: rhythmbox crashed with SIGSEGV in sem_post()
> UpgradeStatus: Upgraded to saucy on 2013-05-25 (27 days ago)
> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/rhythmbox/+bug/1193525/+subscriptions
>

[Paul White (paulw2u)]

Upstream report closed "RESOLVED INCOMPLETE" as information was not provided
Only the 13.10 release seems to have been affected which is now EOL
None of the 82 users affected by the bug replied to comment #12 so the issue
must have been fixed a long time ago.