[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
** Summary changed: - Rhythmnox ignores pulseaudio default sink and outputs sound on random device + rhythmbox ignores pulseaudio default sink and outputs sound on random device -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
"In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem" In addition, I created a brand new user on my system to reproduce the bug, but he could not see RAOP sinks. So I can't see if the bug is happening. Regarding this, all is greyed out in "paprefs" for the new user and my main user (see screenshot attached). The only difference is that "Make discoverable Apple AirTunes sound devices available locally" is pre-ticked for my main user, and pre-"unticked" for the new user. Maybe I should fill another bug report about this. ** Attachment added: "Screenshot from 2020-06-18 10-26-09.png" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+attachment/5384938/+files/Screenshot%20from%202020-06-18%2010-26-09.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
Thanks for the help. The workaround for paprefs did work for me. Regarding rhythmbox : I tried the gst-launch command line test a few times : it always outputs sound to my default sink, no problem here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: Incomplete Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
crvi : did you use RAOP sink as networks sinks ? I don't know if it matters, but my 2 networks sinks are both RAOP. Anyway, I have some more information : I can totally reproduce the problem with latest Fedora Live USB (Fedora-WS-Live-32-1-6), so it's not OS specific. I also tried Ubuntu 19.10 on live USB : the problem is not here. To be specific, in this situation : the 1st time I launch rhythmbox, it ignores my default sink. But with pavucontrol I can remap it to my local sink (my soundcard). Then I quit and relaunch rhythmbox : this time it remembers the last sink used and outputs sound on my local soundcard. My humble analysis : - it's probably an upstream problem - rhythmbox never took the default sink defined in pulseaudio into account - In version 3.4.3 and before, rhythmbox remembers last sink used and reconnects to it for next launch - this "save" function broke in 3.4.4 - specific conditions to trigger the problem are still to be defined, RAOP sinks may have a role -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
What's new : I can reproduce the problem on Ubuntu 20.04 live USB, so I'm sure the root cause is not a broken config on my side. To summarize : Ubuntu 20.04 / Fedora 32.1 are affected. (Ubuntu 19.10 is not) - Rhythmbox 3.4.4 fully affected (wrong sink at start + output is switched to a RAOP sink with each new song) - Spotify is mildly affected : wrong sink at start, but after that you can play new song normally - Rhytmbox 3.4.3 (in Ubuntu 19.10) is lightly affected : wrong sink on 1st launched, but the last sink used is saved for next launch - VLC, Totem, Firefox, Chromium are unaffected Requirements to trigger the bug : 1 (maybe 2) RAOP (aka Airplay / AirTunes) sinks available on local network in addition to local soundcard. Steps to reproduce : $ sudo apt install pulseaudio-module-raop $ sudo apt install paprefs If needed, fix paprefs (which is broken in 20.04) $ sudo ln -s /usr/lib/pulse-13.99.1/ /usr/lib/pulse-13.99 optional, to monitor sinks used by rhythmbox : $ sudo apt install pavucontrol && pavucontrol Launch paprefs and check "Make discoverable Apple AirTunes soud devices available locally" Launch Rhythmbox, play a track, correct the sink, play another track (next button or direct choice), correct the sink, etc. As the issue has been abruptly dismissed upstream : https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1797#note_844963 (I assume the guy knows his job), you are my only hope here ! I know it's my fault, I should have stayed in Ubuntu 19.10 and wait 20.04.1, but I felt harassed by the updater popup reminder :) No, seriously I needed rhythmbox 3.4.4, to support my new phone. So what should I do now ? I understand there is some kind of middleware between pulseaudio and rhythmbox : gstreamer ? Could it be the "culprit" ? If yes, should I report a bug here https://gstreamer.freedesktop.org/bugs/ or downstream ? Is it possible to downgrade gstreamer ? ** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1797 https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1797 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Hello, I'm landing here after tracking a bug : I could not output sound to my SRS-XB22 bluetooth speaker. I had in logs : `src/service.c:btd_service_connect() a2dp-sink profile connect failed for F8:DF:15:7F:ED:AA: Protocol not available` I found a workaround here https://askubuntu.com/questions/1172000/a2dp-sink-profile-connect-failed ``` $ pactl load-module module-bluetooth-policy $ pactl load-module module-bluetooth-discover ``` I did not understand why these commands were mandatory as I already have them in `/etc/pulse/default.pa` Then I checked my `~/.config/pulse/default.pa` and found this : ``` #!/usr/bin/pulseaudio -nF # # Work around for PA not allowing access to A2DP profiles in the user session # because GDM already has it open. # LP: #1703415 # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif ``` So here, we are : today, with - Ubuntu 20.10 - Pulseaudio 1:13.99.2-1ubuntu2.1 - BlueZ 5.55-0ubuntu1.1 => I do not reproduce the original bug. => Moreover, the now unnecessary workaround in `~/.config/pulse/default.pa` is preventing normal use for bluetooth devices. **Workaround for the workaround** : comment the lines in `~/.config/pulse/default.pa` ``` #!/usr/bin/pulseaudio -nF # # Work around for PA not allowing access to A2DP profiles in the user session # because GDM already has it open. # LP: #1703415 # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware #.ifexists module-bluetooth-policy.so # unload-module module-bluetooth-policy #.endif # #.ifexists module-bluetooth-discover.so # unload-module module-bluetooth-discover #.endif ``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Expired Status in PulseAudio: Unknown Status in gdm3 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 source package in Xenial: Triaged Status in pulseaudio source package in Xenial: Triaged Status in gdm3 source package in Zesty: Triaged Status in pulseaudio source package in Zesty: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
Sorry for not answering sooner, I've been quite busy. I already spent too much time reproducing the bug under differents OS and setups. Gnome does not want to help ? Fine, I switched to more reliable audio player. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1883902] [NEW] Rhythmnox ignores pulseaudio default sink and outputs sound on random device
Public bug reported: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. ** Affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 20.04 LTS rhythmbox: - Installed: 3.4.4-1ubuntu2 - Candidate: 3.4.4-1ubuntu2 + Installed: 3.4.4-1ubuntu2 + Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. - (Which can be defined in pavucontrol or set-default-sink + (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: Rhythmnox ignores pulseaudio default sink and outputs sound on random device Status in rhythmbox package in Ubuntu: New Bug description: Ubuntu 20.04 LTS rhythmbox: Installed: 3.4.4-1ubuntu2 Candidate: 3.4.4-1ubuntu2 What I expect to happen : When I launch rhythmbox, I expect it to use the default pulseaudio sink. (Which can be defined in pavucontrol or with set-default-sink in /etc/pulse/default.pa ). What happened instead : when I launch rhythmbox, it outputs sound to a random device (in my case : either a RAOP sink in my living-room, or another RAOP sink in my kitchen. Never my local soundcard) If I correct the output sink (with pavucontrol or pactl) the problem is fixed... until I quit and restart rhythmbox. I did not have this problem with Ubuntu 19.10 / Rhythmbox 3.4.3-2ubuntu1 In 20.04 : -> Spotify (snap store version 1.1.26.501.gbe11e53b-15) has the same problem -> others apps I tested (Firefox, Chromium, VLC, Totem) do not have the problem I already tried to delete $HOME/.config/pulse with no improvement. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1862455] [NEW] fails to modify cpu governor
Public bug reported: Description:Ubuntu 19.10 Release:19.10 gamemode: Installed: 1.5~git20190722.4ecac89-1build3 Candidate: 1.5~git20190722.4ecac89-1build3 Version table: 1.5~git20190722.4ecac89-1build3 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status What is expected to happen : The main feature of "gamemode" is to set cpu governor to "performance" on my core i5 2500K when I launch it with a game. What happened instead : CPU governor stays on "powersave" mode. gamemoded logs "Failed to update cpu governor policy". Workaround : As Ubuntu gamemode seems to be currently broken, you have to compile and install from git source : https://github.com/FeralInteractive/gamemode (Be careful to completely remove gamemode package 1st) And you can check it works as intended with this gnome extension https://extensions.gnome.org/extension/1852/gamemode/ (or $ watch "cpufreqctl --governor" on a terminal) ** Affects: gamemode (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gamemode in Ubuntu. https://bugs.launchpad.net/bugs/1862455 Title: fails to modify cpu governor Status in gamemode package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gamemode: Installed: 1.5~git20190722.4ecac89-1build3 Candidate: 1.5~git20190722.4ecac89-1build3 Version table: 1.5~git20190722.4ecac89-1build3 500 500 http://fr.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages 100 /var/lib/dpkg/status What is expected to happen : The main feature of "gamemode" is to set cpu governor to "performance" on my core i5 2500K when I launch it with a game. What happened instead : CPU governor stays on "powersave" mode. gamemoded logs "Failed to update cpu governor policy". Workaround : As Ubuntu gamemode seems to be currently broken, you have to compile and install from git source : https://github.com/FeralInteractive/gamemode (Be careful to completely remove gamemode package 1st) And you can check it works as intended with this gnome extension https://extensions.gnome.org/extension/1852/gamemode/ (or $ watch "cpufreqctl --governor" on a terminal) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gamemode/+bug/1862455/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] [NEW] Local mail is never checked
Public bug reported: Description:Ubuntu 19.10 Release:19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround ? : Putting MAIL=/var/mail/user in ~/.bashrc should work, but it seems the bash invoked by gnome-terminal does not even read ~/.bashrc So I have no idea. ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround ? : Putting MAIL=/var/mail/user in ~/.bashrc should work, but it seems the bash invoked by gnome-terminal does not even read ~/.bashrc So I have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
** Description changed: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: - Installed: 3.34.2-1ubuntu1 - Candidate: 3.34.2-1ubuntu1 + Installed: 3.34.2-1ubuntu1 + Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. - What happens instead : + What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. - Workaround ? : - Putting MAIL=/var/mail/user in ~/.bashrc should work, but it seems the bash invoked by gnome-terminal does not even read ~/.bashrc - So I have no idea. + Workaround : + Put + export MAIL=/var/mail/$USER + in ~/.bashrc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
Sorry, I didn't know where to open this. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
Anyway my workaround... does not really work. It only works if I receive a new mail while gnome-terminal is running : in this case I will have "You have new mail" at next command line prompt. If I receive new mail while gnome-terminal is not running, THEN I launch gnome-terminal : no notification. But you are right, I should move to askubuntu. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872053] Re: Local mail is never checked
Well, my approach was very simple : mail notification in terminal has worked for decades, I used in the 2000s, so why not use it again if it suits me ? It is not mandatory to "reinvent the wheel" for an old need. Anyway, I already tried to use /var/mail/$USER in my graphical email client (Thunderbird) : trust me it's very buggy. (Mail is only checked at start, sometimes "read-only", sometimes it becomes duplicated) But I will gladly examine any other graphical solution, provided it's (almost) as lightweight as the terminal one :) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1872053 Title: Local mail is never checked Status in gnome-terminal package in Ubuntu: New Bug description: Description: Ubuntu 19.10 Release: 19.10 gnome-terminal: Installed: 3.34.2-1ubuntu1 Candidate: 3.34.2-1ubuntu1 Context : In a typical daily use scenario, a Ubuntu user is not expected to use a console login with "Ctrl-Alt Fx". Instead it is expected to use gnome-terminal for command-line interaction. That being said : What I expect to happen when I launch gnome-terminal : I expect the bash shell started by gnome-terminal to check local mail (in /var/mail/$USER ) and reports accordingly "You have new mail" if there is new mail. What happens instead : gnome-terminal invokes bash with $MAIL variable not set. So mail is not checked, and the user is never informed about new local mail. Workaround : Put export MAIL=/var/mail/$USER in ~/.bashrc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1872053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1083237] Re: Ignore Steam files by default
Mokrates : you can't, it's hardcoded. (no jokes !) Because of Déjà Dup, I also lost data 1 year ago, and created a bug report : https://bugs.launchpad.net/deja-dup/+bug/1562357 But it's been completely ignored. My conclusion : "As deja-dup project seems more or less inactive, and can't be used as a reliable backup for steam users, I suggest everyone affected to use "Back in time". With this software : - backup settings can be changed - backup operation eats a lot less CPU, and is faster (for me) - data is easy to access, you don't even need the backup software" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1083237 Title: Ignore Steam files by default Status in Déjà Dup: Fix Released Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Precise: Fix Released Status in deja-dup source package in Quantal: Fix Released Bug description: [Impact] Steam is coming to Ubuntu (already in beta). Steam games are enormous, synchronized, and off-site. No need to back them up. Once users start playing Steam games, a user that enabled backups with Deja Dup's default settings will find that all of a sudden, many gigs of data are being backed up. Now, obviously this is a bit of a whack-a-mole problem. Many apps like Steam don't properly follow the XDG basedir spec and put cached data in ~/.cache so that Deja Dup and similar apps will ignore them. And we don't want to SRU a fix for every single non-compliant app. But Steam is a big one. It's both very popular and its data is very very large. I think it's worth an exception to avoid the pain and bug reports that will come when many people suddenly add multiple gigs of useless data to their backups. [Workaround] A user can simply add ~/Steam to the backup ignore list. But every single user that uses Steam will want to do that. It's a big burden to ask of each user individually. [Test Case] Try backing up your home directory with Steam installed. Notice that it will include ~/Steam. With this patch (from upstream), it will ignore ~/Steam instead. [Regression Potential] It's a very simple fix. I think regression potential is exceedingly tiny. [Fix Details] We add ~/.steam/root to the hidden default ignore list. ~/.steam/root points at ~/Steam (which will also be ignored) unless the user has manually changed it. To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1083237/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Hello, For the record I reproduce this bug on a fresh new install of Ubuntu 18.10. As it sounds like a 7-months-old critical security bug, I'm very interested in a reliable workaround. Should I remove gnome-shell-extension-ubuntu-dock, and install upstream Dash to dock from https://extensions.gnome.org/extension/307/dash-to- dock/ ? (I already had to remove gnome-shell-extension-appindicator to install the 'almost' bug free upstream app-indicator) Thanks for your help ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1769383 Title: Ubuntu dock/launcher is shown on the lock screen Status in gnome-shell package in Ubuntu: Invalid Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Bionic: In Progress Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: In Progress Status in gnome-shell source package in Disco: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Disco: Fix Released Bug description: [Impact] When entering the lock-screen mode, gnome-shell disables all the extensions. It can happen that under certain conditions ubuntu-dock re-enables itself, causing the ubuntu-dock to appear in the lock-screen, exposing sensitive information. One possible way to reproduce this is to enable dash-to-dock and ubuntu-dock at the same time. [Test Case] 1. Make sure ubuntu-dock is enabled 2. Enable dash-to-dock too 3. Lock the screen 4. Make sure the dock does not appear on the lock screen 5. Make sure there is no warning is the journal [Possible Regressions] Even if it's something we don't really support please make sure that you can use dash-to-dock without uninstalling ubuntu-dock. [Original Bug] After an update from ubuntu 16.04 to 18.04 the dock is aviable on the lockscreen after user login. I did not configure this knowingly. Also i can start every application which is available on the dock. Settings, virtual box, visualstudio code and so on. After the update to 18.04 i just configure the screen frequency to 144Hz and the night mode on. And attach the dock on bottom. I later undid these customizations back to configuration before, but the dock is stil aviable on lockscreen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat May 5 18:30:16 2018 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to bionic on 2018-05-01 (3 days ago) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-08 (27 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell-extension-ubuntu-dock 0.9.1 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-01 (4 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1769383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964274] [NEW] gnome-shell crashes after tracker-extract-3 reports "Not a JPEG file: starts with 0x89 0x50"
Public bug reported: System : Ubuntu 21.10 Kernel 5.13.0-35 Session : Wayland Each time I try to rip a CD with "abcde" gnome-shell crashes What I understand from the logs : Before the CD is ripped, abcde downloads a picture (from internet) as a cover of the CD. When tracker-extract discovers this picture something bad happens. Then gnome-shell crashes. After the crash (and re-login into Ubuntu) I can resume the ripping process as the picture has been cached by abcde, and tracker-extract does not interact again with it. Obviously the problem is back for each new CD. The problem appeared quite recently, probably less than 1 month ago. Logs : 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 comm="/usr/libexec/tracker-mi> 00:13:06 host systemd[3523]: Starting Tracker metadata extractor... 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' 00:13:06 host systemd[3523]: Started Tracker metadata extractor. 00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 0x50 00:13:14 host tracker-extract[11545]: Task for 'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: Could not get any metadata for uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg' 00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), message create_pool(nhi) 00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640) 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[4456]: Fatal server error: 00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[3640]: Connection to xwayland lost ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: gnome-shell tracker-extract -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1964274 Title: gnome-shell crashes after tracker-extract-3 reports "Not a JPEG file: starts with 0x89 0x50" Status in gnome-shell package in Ubuntu: New Bug description: System : Ubuntu 21.10 Kernel 5.13.0-35 Session : Wayland Each time I try to rip a CD with "abcde" gnome-shell crashes What I understand from the logs : Before the CD is ripped, abcde downloads a picture (from internet) as a cover of the CD. When tracker-extract discovers this picture something bad happens. Then gnome-shell crashes. After the crash (and re-login into Ubuntu) I can resume the ripping process as the picture has been cached by abcde, and tracker-extract does not interact again with it. Obviously the problem is back for each new CD. The problem appeared quite recently, probably less than 1 month ago. Logs : 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 comm="/usr/libexec/tracker-mi> 00:13:06 host systemd[3523]: Starting Tracker metadata extractor... 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' 00:13:06 host systemd[3523]: Started Tracker metadata extractor. 00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 0x50 00:13:14 host tracker-extract[11545]: Task for 'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: Could not get any metadata for uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg' 00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), message create_pool(nhi) 00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640) 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[4456]: Fatal server error: 00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[3640]: Connection to xwayland lost To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1964274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964274] Re: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool
Thanks, quick and good catch ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1964274 Title: Xwayland crashes with wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Committed Status in xwayland package in Ubuntu: Fix Released Bug description: System : Ubuntu 21.10 Kernel 5.13.0-35 Session : Wayland Each time I try to rip a CD with "abcde" gnome-shell crashes What I understand from the logs : Before the CD is ripped, abcde downloads a picture (from internet) as a cover of the CD. When tracker-extract discovers this picture something bad happens. Then gnome-shell crashes. After the crash (and re-login into Ubuntu) I can resume the ripping process as the picture has been cached by abcde, and tracker-extract does not interact again with it. Obviously the problem is back for each new CD. The problem appeared quite recently, probably less than 1 month ago. Logs : 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Activating via systemd: service name='org.freedesktop.Tracker3.Miner.Extract' unit='tracker-extract-3.service' requested by ':1.8' (uid=1000 pid=3573 comm="/usr/libexec/tracker-mi> 00:13:06 host systemd[3523]: Starting Tracker metadata extractor... 00:13:06 host dbus-daemon[3541]: [session uid=1000 pid=3541] Successfully activated service 'org.freedesktop.Tracker3.Miner.Extract' 00:13:06 host systemd[3523]: Started Tracker metadata extractor. 00:13:14 host tracker-extract-3[11545]: Not a JPEG file: starts with 0x89 0x50 00:13:14 host tracker-extract[11545]: Task for 'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' finished with error: Could not get any metadata for uri:'file:///home/user/Downloads/abcde.a80c7f0c/cover.jpg' and mime:'image/jpeg' 00:13:14 host gnome-shell[3640]: WL: file descriptor expected, object (6), message create_pool(nhi) 00:13:14 host gnome-shell[3640]: WL: error in client communication (pid 3640) 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[4456]: Fatal server error: 00:13:14 host gnome-shell[4456]: (EE) wl_display@1: error 1: invalid arguments for wl_shm@6.create_pool 00:13:14 host gnome-shell[4456]: (EE) 00:13:14 host gnome-shell[3640]: Connection to xwayland lost To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1964274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] [NEW] can't manually sort bookmarks anymore
Public bug reported: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: bookmarks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] Re: can't manually sort bookmarks anymore
Thank you for taking the time to study this bug report. "Drag and drop" is indeed the way I usually sort out my bookmarks. I know there is a "sort by name" option (I won't try it). I'm very sorry but I won't use any apport command, for classic privacy reasons. (But I can provide any logs, if it's "human-readable" and I can sanitize it by myself) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] Re: can't manually sort bookmarks anymore
If it may help : I created a new user on my system, and I reproduced the problem. I'll try to reproduce it from Ubuntu 21.10 "live USB" : right after the boot (if chromium is available) and with the latest chromium. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] Re: can't manually sort bookmarks anymore
Problem reproduced with a fresh Ubuntu 21.10 Live USB (booted with X, whereas I use wayland on a daily basis) : with both 2 snap versions of chromium available in Ubuntu store : 97.0.4692.71 (latest/stable) 98.0.4758.9 (latest/edge) My hardware is quite classic, so yes I'm probably not alone to suffer of this broken drag'n'drop : Ryzen 3600X Radeon RX 5700 XT 4K monitor (I tried to put it in 1080p, with no scaling : nothing changed) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: New Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] Re: can't manually sort bookmarks anymore
As a workaround, it's too bad we can't restore a bugfree version of chromium. Not for web browsing, just to sort out bookmarks. (And then we restore the latest one) The choice of versions available is *very* limited : $ snap info chromium channels: latest/stable:97.0.4692.71 2022-01-07 (1864) 154MB - latest/candidate: 97.0.4692.71 2022-01-07 (1864) 154MB - latest/beta: 97.0.4692.71 2022-01-07 (1864) 154MB - latest/edge: 98.0.4758.9 2021-12-17 (1860) 154MB - installed: 97.0.4692.71(1864) 154MB - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956888] Re: can't manually sort bookmarks anymore
I found a workaround : in Chromium, go to Settings / Appearance and disable "Use system title bar and borders" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1956888 Title: can't manually sort bookmarks anymore Status in chromium-browser package in Ubuntu: Confirmed Bug description: Ubuntu 21.10 Chromium is installed via snap. chromium97.0.4692.711864 latest/stable Since a few days (weeks ?) I can't anymore drag and drop my bookmarks in the bookmarks view (control + shift + O) nor directly in the bookmarks bar. Bookmarks folders have the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1956888/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948996] [NEW] (gnome-software) Application icons not showing in 200% scaling environment
Public bug reported:
Ubuntu 21.10 (existing or fresh install, same result)
Package : gnome-software 40.4-1build1
In Gnome Settings / Display : scaling is set to 200%.
Since I upgraded to Gnome 40.4 (with Ubuntu 21.10), gnome-software does
not display anymore most of applications icons when I scale the screen
to 200%.
Steps to reproduce the bug :
1.Boot on a fresh Ubuntu 21.10 USB Live environnement.
2.Install and launch gnome-software (check the "universe" repo first in
software-properties-gtk)
3.Notice that everything is fine, then quit gnome-software.
4. Use gnome settings / display to scale to 200% (or $ gsettings set
org.gnome.settings-daemon.plugins.xsettings overrides
"[{'Gdk/WindowScalingFactor', <2>}]" )
5. Launch again gnome-software. Notice most icons are missing. (see file
attached)
Bug IS NOT reproduced with Fedora 34 / Gnome 40.4
Bug IS NOT reproduced with Fedora 34 / Gnome 40.0
Bug IS NOT reproduced with Ubuntu 21.04
Bug is presumably not upstream, as discussed here
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1516
** Affects: gnome-software (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Screenshot_from_2021-10-24_15-28-13.png"
https://bugs.launchpad.net/bugs/1948996/+attachment/5536536/+files/Screenshot_from_2021-10-24_15-28-13.png
** Package changed: rhythmbox (Ubuntu) => gnome-software (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
https://bugs.launchpad.net/bugs/1948996
Title:
(gnome-software) Application icons not showing in 200% scaling
environment
Status in gnome-software package in Ubuntu:
New
Bug description:
Ubuntu 21.10 (existing or fresh install, same result)
Package : gnome-software 40.4-1build1
In Gnome Settings / Display : scaling is set to 200%.
Since I upgraded to Gnome 40.4 (with Ubuntu 21.10), gnome-software
does not display anymore most of applications icons when I scale the
screen to 200%.
Steps to reproduce the bug :
1.Boot on a fresh Ubuntu 21.10 USB Live environnement.
2.Install and launch gnome-software (check the "universe" repo first in
software-properties-gtk)
3.Notice that everything is fine, then quit gnome-software.
4. Use gnome settings / display to scale to 200% (or $ gsettings set
org.gnome.settings-daemon.plugins.xsettings overrides
"[{'Gdk/WindowScalingFactor', <2>}]" )
5. Launch again gnome-software. Notice most icons are missing. (see file
attached)
Bug IS NOT reproduced with Fedora 34 / Gnome 40.4
Bug IS NOT reproduced with Fedora 34 / Gnome 40.0
Bug IS NOT reproduced with Ubuntu 21.04
Bug is presumably not upstream, as discussed here
https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1516
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1948996/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
