User avatar
Scytale
Posts: 33
Joined: Sat Apr 08, 2017 7:01 am
Location: Marburg, Germany

[SOLVED] Rhythmbox crash: memory access error

Sun Aug 27, 2017 9:46 am

Hello there!

Rhytmbox is very unstable under Solus in comparison to previous used installations of Ubuntu 16.04 to 17.10. The following error does not appear there, as far as i know only under Solus:

I want to add a song to a playlist. I search for the song title, add it to the playlist, switch back to music tab and as soon as i delete the previous searched title name rhythmbox crashes. Reproducible, happens every time.

The output in the terminal is as following:
(rhythmbox:7347): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client

(rhythmbox:7347): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running

(rhythmbox:7347): libdmapsharing-WARNING **: Unable to initialize mDNS: Daemon läuft nicht

(rhythmbox:7347): libdmapsharing-WARNING **: Unable to notify network of media sharing: The avahi MDNS service is not running

(rhythmbox:7347): Gtk-WARNING **: Unable to parse accelerator '': ignored request to install 1 accelerators

(rhythmbox:7347): Gtk-WARNING **: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type b, target type NULL)

(rhythmbox:7347): Gtk-WARNING **: actionhelper: action app.play-shuffle can't be activated due to parameter type mismatch (parameter type b, target type NULL)

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x2680c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x26f4880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-CRITICAL **: gtk_tree_view_update_button_position: assertion 'column_el != NULL' failed

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x35ddc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x369e880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x24a2a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x25946c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-CRITICAL **: gtk_tree_view_update_button_position: assertion 'column_el != NULL' failed
Speicherzugriffsfehler
Speicherzugriffsfehler (german)= Memory Access Error
All messages above "Speicherzugriffsfehler" seems to be regular and appear during every run of rhytmbox.

Any ideas, why rhythmbox crash on my system?
Last edited by Scytale on Mon Aug 28, 2017 7:49 pm, edited 1 time in total.

sunnyflunk
Development Team
Posts: 2501
Joined: Sun Mar 13, 2016 11:35 pm

Re: Rhythmbox crash: memory access error

Mon Aug 28, 2017 1:32 am

Scytale wrote:
Sun Aug 27, 2017 9:46 am
Hello there!

Rhytmbox is very unstable under Solus in comparison to previous used installations of Ubuntu 16.04 to 17.10. The following error does not appear there, as far as i know only under Solus:

I want to add a song to a playlist. I search for the song title, add it to the playlist, switch back to music tab and as soon as i delete the previous searched title name rhythmbox crashes. Reproducible, happens every time.

The output in the terminal is as following:
(rhythmbox:7347): Gtk-WARNING **: Failed to register client: GDBus.Error:org.gnome.SessionManager.AlreadyRegistered: Unable to register client

(rhythmbox:7347): Rhythmbox-WARNING **: Unable to start mDNS browsing: MDNS service is not running

(rhythmbox:7347): libdmapsharing-WARNING **: Unable to initialize mDNS: Daemon läuft nicht

(rhythmbox:7347): libdmapsharing-WARNING **: Unable to notify network of media sharing: The avahi MDNS service is not running

(rhythmbox:7347): Gtk-WARNING **: Unable to parse accelerator '': ignored request to install 1 accelerators

(rhythmbox:7347): Gtk-WARNING **: actionhelper: action app.play-repeat can't be activated due to parameter type mismatch (parameter type b, target type NULL)

(rhythmbox:7347): Gtk-WARNING **: actionhelper: action app.play-shuffle can't be activated due to parameter type mismatch (parameter type b, target type NULL)

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x2680c00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x26f4880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-CRITICAL **: gtk_tree_view_update_button_position: assertion 'column_el != NULL' failed

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x35ddc00 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x369e880 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x24a2a40 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-WARNING **: Allocating size to GtkButton 0x25946c0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

(rhythmbox:7347): Gtk-CRITICAL **: gtk_tree_view_update_button_position: assertion 'column_el != NULL' failed
Speicherzugriffsfehler
Speicherzugriffsfehler (german)= Memory Access Error
All messages above "Speicherzugriffsfehler" seems to be regular and appear during every run of rhytmbox.

Any ideas, why rhythmbox crash on my system?
Can't reproduce:

Please do:

Code: Select all

sudo eopkg up
Run this once

Code: Select all

sudo eopkg up; sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall

User avatar
Scytale
Posts: 33
Joined: Sat Apr 08, 2017 7:01 am
Location: Marburg, Germany

Re: Rhythmbox crash: memory access error

Mon Aug 28, 2017 6:06 am

Can't reproduce:

Please do:

Code: Select all

sudo eopkg up
Run this once

Code: Select all

sudo eopkg up; sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
[/quote]

Code: Select all

sudo eopkg up; sudo eopkg check | grep Broken | awk '{print $4}' | xargs sudo eopkg it --reinstall
Depots-Upgrade wird durchgeführt
Depot wird aktualisiert: Solus
eopkg-index.xml.xz.sha1sum     (40.0  B)100%    848.91 KB/s [00:00:00] [vollständig]
Depot-Information von Solus ist aktuell.
Es gibt keine Pakete zu aktualisieren.
install (it): Install eopkg packages

Syntax: install <package_1> <package_2> ... <package_n>

Man kann Dateinamen,URI's oder Paketnamen verwenden. Falls man einen
Paketnamen angegeben hat, sollte er in einem Depot auch vorhanden sein.

Man kann statt einem Paketnamen auch einen Komponentennamen angeben.
Dieser wird zu einem Paketnamen erweitert.


Optionen:
 --version                    : Programmversion anzeigen und beenden
 -h [--help]                  : Diesen Hilfetext anzeigen und beenden

 Optionen von install:
  --ignore-dependency         : Information der Abhängigkeiten nicht auswerten
  --ignore-comar              : Comar Konfigurations-Agent umgehen
  --ignore-safety             : Sicherheitsschalter umgehen
  -n [--dry-run]              : Keine Aktion ausführen sondern nur anzeigen was
                                in der Aktion geschehen würde
  --reinstall                 : Bereits installierte Pakete erneut installieren.
  --ignore-check              : Überspringe Distributions- und Architektur-
                                Überprüfung
  --ignore-file-conflicts     : Datei-Konflikte ignorieren
  --ignore-package-conflicts  : Paket-Konflikte ignorieren
  -c [--component] arg        : Pakete von Komponenten und rekursiven
                                Abhängigkeiten installieren
  -r [--repository] arg       : Name des Komponenten-Depots
  -f [--fetch-only]           : Upgrades abrufen aber nicht installieren.
  -x [--exclude] arg          : Bei der Installation von Paketen, Pakete und
                                Komponenten ignorieren, bei denen der Basisname
                                mit der Maske übereinstimmt.
  --exclude-from arg          : Bei der Installation von Paketen, Pakete und
                                Komponenten ignorieren, bei denen der Basisname
                                mit irgendeiner der Masken in der Datei
                                übereinstimmt.

 Allgemeine Optionen:
  -D [--destdir] arg          : Ändere für die eopkg-Befehle das System-
                                Root(wurzel)-Verzeichnis
  -y [--yes-all]              : Alle JA/Nein-Abfragen mit ja annehmen
  -u [--username] arg         
  -p [--password] arg         
  -L [--bandwidth-limit] arg  : Bandbreitenverwendung unter festgelegten KB's
                                halten
  -v [--verbose]              : Detaillerte Ausgabe
  -d [--debug]                : Debugger-Informationen anzeigen
  -N [--no-color]             : eopkg-Ausgaben ohne farbliche Darstellungen
                                anzeigen
still crashes

User avatar
Justin
Development Team
Posts: 3375
Joined: Mon Jul 28, 2014 10:42 am
Location: Adelaide, Australia
Contact: Website Google+ Twitter

Re: Rhythmbox crash: memory access error

Mon Aug 28, 2017 6:48 am

Seems to have been an issue with it running those commands as it didn't do what it was supposed to, can you please show the output of:

Code: Select all

sudo eopkg check | grep Broken | awk '{print $4}'

User avatar
Scytale
Posts: 33
Joined: Sat Apr 08, 2017 7:01 am
Location: Marburg, Germany

Re: Rhythmbox crash: memory access error

Mon Aug 28, 2017 6:12 pm

Justin wrote:
Mon Aug 28, 2017 6:48 am
Seems to have been an issue with it running those commands as it didn't do what it was supposed to, can you please show the output of:

Code: Select all

sudo eopkg check | grep Broken | awk '{print $4}'
Gives me no output which i guess is a good sign?

WinterWren
Posts: 2
Joined: Mon Aug 28, 2017 6:34 pm

Re: Rhythmbox crash: memory access error

Mon Aug 28, 2017 6:44 pm

Is the package "rhythmbox-alternate-toolbar" installed on your system? I have the same problem, and no idea how to solve it. But I removed the package and now Rhythmbox seems to work.

Edit: There seems to be an earlier thread about a similar problem: viewtopic.php?f=10&t=8194

User avatar
Scytale
Posts: 33
Joined: Sat Apr 08, 2017 7:01 am
Location: Marburg, Germany

Re: Rhythmbox crash: memory access error

Mon Aug 28, 2017 7:49 pm

WinterWren wrote:
Mon Aug 28, 2017 6:44 pm
Is the package "rhythmbox-alternate-toolbar" installed on your system? I have the same problem, and no idea how to solve it. But I removed the package and now Rhythmbox seems to work.

Edit: There seems to be an earlier thread about a similar problem: viewtopic.php?f=10&t=8194
You are my hero for today. Removing rhytmbox-alternative-toolbar solved all crashes.

Also thx to Justin for taking the time.

I don't know why i didn't found the your mentioned thread as i used the search function for rhythmbox. Well i guess everybody has a noob day

WinterWren
Posts: 2
Joined: Mon Aug 28, 2017 6:34 pm

Re: Rhythmbox crash: memory access error

Mon Aug 28, 2017 8:51 pm

Scytale wrote:
Mon Aug 28, 2017 7:49 pm
You are my hero for today. Removing rhytmbox-alternative-toolbar solved all crashes.

Also thx to Justin for taking the time.

I don't know why i didn't found the your mentioned thread as i used the search function for rhythmbox. Well i guess everybody has a noob day
Don't worry. I just mentioned the earlier thread because they seemed to have found a workaround that might be worth trying if you absolutely need the alternate toolbar.
Glad I could help though :)

Return to “Multimedia”