--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/956229
Title:
rhythmbox does not save added radio stations
To manage notifications about this bug go to:
Public bug reported:
Any radio stations added to rhythmbox are at first added to the table and are
playable, but upon exit, they are not written to the rhythmdb.xml file, so that
they are gone the next time rhythmbox is started.
On the terminal, I receive the error RhythmDB-WARNING **: Can't
Dear Vadim,
attached is the requested debug log.
Apparently something is also going wrong when the Ubuntu One plugin searches
for the Purchased Music folder and doesn't find it, but uninstalling that
plugin did not solve my own problem. I also tried to rename the rhythmdb.xml
file; in that
I tried both with emacs and gedit, and could edit and save the file normally;
and less correctly showed the line I had added.
The output you requested is:
-rw-rw-r-- 1 username username 4565471 Mar 16 12:40 rhythmdb.xml
I will try to purge rhythmbox (saving my db first, of course) and
I got it working again! Purging rhythmbox did not help; it still didn't keep
added radio stations. I then noticed that it hadn't deleted the
~/.local/share/rhythmbox directory, so I manually moved it. In the newly
generated directory, it was finally able to save radio stations in the empty
Public bug reported:
Since the update to 17.10 beta, my ubuntu-session crashes rather
frequently (though not always) when notifications appear. It happened,
e.g. when a new e-mail was received in Thunderbird, or when I clicked
the "play" button in the Spotify client.
It may be linked to the dual
I do have two rather huge (~30 MB) .crash files in that directory whose
filenames contain "gnome-shell", but they are already a week old. I
attaching the head of the first file (up to the core dump, which takes
the most space).
** Attachment added: "_usr_bin_gnome_shell.1000.crash_head"
I got another "crash" (or rather a lockup), again linked to Spotify
switching to a different song (-> notification). Unfortunately, apport-
retrace just gives me this: "ERROR: report file does not contain one of
the required fields: Package" I googled a bit and tried adding the
package gnome-shell
Ok, I might have just been too impatient, because the last few times the
session didn't drop me back on the login screen but just locked up. This
time, however, after a while it did drop me on the login screen and I
got a working .crash file. Reported a new bug (#1724159) with the
details!
--
I already tried that, but it gives me a message on the command line
saying "Gtk-Message: GtkDialog mapped without a transient parent. This
is discouraged.", along with a small window that says "Invalid problem
report" in the title and "Permission denied" in the window itself. No
success using sudo
Another addition: The Wayland session turns out to be affected as well,
but I wasn't able to figure out the precise reason why this is happening
yet.
I have a number of extensions installed, and I could -- for the moment
-- fix the problem by switching them all off, except the ubuntu-dock.
Then I
Public bug reported:
After locking the screen, unlocking it again does not return me to a
properly working gnome-shell. I can see the desktop background and the
top panel (which is responsive). However I cannot access the activities
overview, and the Ubuntu dock is missing.
One time I noticed
Addon: This seems to affect only the X11 version, the Wayland session
appears to lock and unlock just fine, so I'm switching to that for now.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
Actually, only about half of them were actually switched on -- the rest
I had tried at some point, but since there is no "remove" option in
Gnome Tweak they were still in the list. For now I had to roll back to
18.04 because of another problem, but I'll come back to 18.10 in a while
and check on
14 matches
Mail list logo
