[Desktop-packages] [Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
Bug appears in 22.04. -- 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/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Confirmed Status in yaru-theme source package in Jammy: Confirmed Bug description: If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 1917705] Re: "profile will be deleted" at startup after chromium 89 update
@Olivier Tilloy Are there any plans to remedy this issue? Like releasing api keys to be used by distros? -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917705] Re: "profile will be deleted" at startup after chromium 89 update
For personal accounts nothing is lost from what I can see so far, all data is transferred to a blank profile. My god, though, this could surely have been handled better. Not even a banner inside chromium to let us know like what I think happened with Windows Xp. -- 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/1917705 Title: "profile will be deleted" at startup after chromium 89 update Status in chromium-browser package in Ubuntu: Won't Fix Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917705] Re: profile will be deleted
May I suggest dropping 89 on the stable channel for snappy? -- 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/1917705 Title: profile will be deleted Status in chromium-browser package in Ubuntu: Confirmed Bug description: After updating the chromium-browser snap from 1497 to 1506, Chromium refuses to work with profiles that are linked to Google accounts. Each of them is deleted whenever first opening it. And turning on profile synchronization does not work. See the attached file for a screenshot of the issue. Workaround: 1. Kill the current chromium process. 2. Revert the snap back to an older version. Warning 1: Running on an older version of Chromium comes at its own issues. Warning 2: Any already deleted profile will not be restored by going back to an older version of Chromium. You will have to create and link the profile again. This bug is severe and means that Chromium has become unusable in a professional environment. "We also need:" 1) The release of Ubuntu you are using $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal 2) The version of the package you are using $ snap list chromium Name VersionRev Tracking Publisher Notes chromium 89.0.4389.72 1506 latest/stable canonical* - 3) What you expected to happen Chromium works as usual, linked profiles work, new profiles can be linked to sync with Google accounts. 4) What happened instead Chromium cannot work with linked profiles. Existing profiles from older versions of Chromium that are linked to sync with a Google account are deleted upon start, and the feature of linking a profile to a Google account for syncing is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917705/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap ** Description changed: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. + + The current profile is named "Person 1". + + Ubuntu 20.04.2 LTS, fully updated + Chromium 89.0.4389.72 2021-03-03 (1506) snap -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. The current profile is named "Person 1". Ubuntu 20.04.2 LTS, fully updated Chromium 89.0.4389.72 2021-03-03 (1506) snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1917713] Re: [snap] Logged out of Chromium after latest update to 89
I run the command and it said: "Package chromium-browser not installed and no hook available, ignoring" I reviewed the linked bug and, though it is similar, the difference is that I still seem to have everything, whereas in the bug it is suggested data is lost. So could it be the same bug but with different symptoms? -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1917713] [NEW] [snap] Logged out of Chromium after latest update to 89
Public bug reported: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1917713 Title: [snap] Logged out of Chromium after latest update to 89 Status in chromium-browser package in Ubuntu: New Bug description: It seems I haven't lost anything, but on the top right corner it shows a person, as well as that I'm not logged in. What is happening? I'm worried I may lose something if I mess with it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1917713/+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 1900981] Re: Formatting USB flash drives doesn't ask for password
** Package changed: ubuntu => gnome-disk-utility (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1900981 Title: Formatting USB flash drives doesn't ask for password Status in gnome-disk-utility package in Ubuntu: New Bug description: Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1900981/+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 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Issue appears on 20.04, fresh install -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in GNOME Settings Daemon: Unknown Status in Ubuntu Flashback: New Status in Ubuntu GNOME: Fix Released Status in Ubuntu GNOME Flashback: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-control-center package in ALT Linux: Unknown Status in gnome-control-center package in Baltix: Confirmed Status in gnome-control-center package in Gentoo Linux: Unknown Status in gnome-control-center package in Mandriva: Unknown Bug description: [Impact] Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift, etc. Shift, Caps Lock keys are just ignored in settings. [Test Case] - open gnome-control-center's text input settings - click on the "next layout key" entry - try entering a combination of two modifier keys such as Ctrl+Shift -> the UI should reflect the new keys - add at least two input sources through gnome-control-center's text entry settings - press and release Ctrl+Shift -> the current input source should change [Regression Potential] That UI was not working before, it should only be an improvement (some key combos are not working as expected, that's another issue and shouldn't be mixed with this one) The input switching shortcut might capture other non-modifier shortcuts, but users will need to consider this when choosing their switching shortcut anyways. For users this bug affects, this represents a working solution for a critical bug. -- Test results for different keyboard layout change hotkeys may be viewed and added in the Google Docs table, created by Norbert (https://docs.google.com/spreadsheet/ccc?key=0Ao5e713Ig9g_dEJrX2NRYlpLWWVzSWxsVXU4ck9HYVE=sharing). You can use the tag keyboard-layout-switching-hotkeys to find related bugs. https://bugs.launchpad.net/ubuntu/+bugs?field.tag=keyboard-layout-switching-hotkeys For using layout switching hotkeys in Unity Greeter, see bug 1245137. For using layout switching hotkeys in GNOME lockscreen, see bug 1244548. For using layout switching hotkeys in GNOME FlashBack sessions, see bug 1687466 (at least ). -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20130829.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 Date: Thu Aug 29 14:21:54 2013 InstallationDate: Installed on 2013-07-31 (28 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130730) MarkForUpload: True ProcEnviron: LANGUAGE=ru_UA:ru PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_UA.UTF-8 SHELL=/bin/bash SourcePackage: indicator-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1218322/+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 1831039] Re: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
Sry man Yes, the OSK is not brought up automatically for non-Ubuntu apps when using Wayland. -- 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/1831039 Title: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in chromium-browser package in Ubuntu: Incomplete Status in firefox package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 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/chromium-browser/+bug/1831039/+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 1831039] Re: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
No, it works when using x11 in 20.04. -- 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/1831039 Title: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in chromium-browser package in Ubuntu: Incomplete Status in firefox package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 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/chromium-browser/+bug/1831039/+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 1831039] Re: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
Umm, yes, but on Wayland, it works in x11. -- 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/1831039 Title: The onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in chromium-browser package in Ubuntu: Incomplete Status in firefox package in Ubuntu: Incomplete Status in gnome-shell package in Ubuntu: Incomplete Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 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/chromium-browser/+bug/1831039/+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 1875124] Re: Lock screen hangs after entering password
Also if the PC went to sleep while it was idle (screen off), logging in will fail on resume. -- 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/1875124 Title: Lock screen hangs after entering password Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Running the newest release of ubuntu (20.04LTS). I entered my password to log in after the lock screen had engaged automatically and it accepted my password (greying out the buttons) but didn't log in. Five minutes later it still hadn't changed so I went to another TTY and killed the gnome-terminal process. X started up again, and allowed me to log in with no issues after that. Intentionally locking the screen did not trigger the bug. This could be a serious problem for anyone not already familiar with linux as this would force a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 20:28:57 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1875124/+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 1875124] Re: Lock screen hangs after entering password
I think I have a workaround, if the problem is the same as the one I'm facing. Press the user button on the bottom right where you enter your password, the lock screen changes colors , re enter the password and login will be successful. -- 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/1875124 Title: Lock screen hangs after entering password Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Running the newest release of ubuntu (20.04LTS). I entered my password to log in after the lock screen had engaged automatically and it accepted my password (greying out the buttons) but didn't log in. Five minutes later it still hadn't changed so I went to another TTY and killed the gnome-terminal process. X started up again, and allowed me to log in with no issues after that. Intentionally locking the screen did not trigger the bug. This could be a serious problem for anyone not already familiar with linux as this would force a reboot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 25 20:28:57 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1875124/+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 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps
Fixed for me and i'm on 2.42 Eoan. Dialog appears to choose the app to open. -- 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/1776873 Title: Whitelisted allowedURLschemes breaks some desktop apps Status in snapd: Triaged Status in chromium-browser package in Ubuntu: Confirmed Bug description: https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55 snapd has a hard-coded list of allowed URL schemes. Currently that is limited to "http", "https", "mailto", "snap". We have a number of applications in the store which are trying to use protocol handlers outside this scope and break when that's not possible. e.g. Telegram Desktop: tg:/ Github Desktop: git:/ IRCCloud Desktop: irc:/ These are the ones I know of, others may also be affected. Can we please at least expand the list to those that we know of, and perhaps research other popular protocol handlers? Ideally we wouldn't have a whitelist, because this delays our ability to land new applications with as-yet unknown url schemes. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776873/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
Download firefox from its website, just run it from it's unzipped directory -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Status in goopg package in Ubuntu: Confirmed Status in kdeconnect package in Ubuntu: Confirmed Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1616650] Re: snap refresh while command is running may cause issues
Suggestion: If there is an update, don't just update, show a notification if the app is running. After the user presses yes or something, the app closes (or they close it), the update happens and once it is finished you can open your app again. -- 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/1616650 Title: snap refresh while command is running may cause issues Status in snapd: In Progress Status in chromium-browser package in Ubuntu: Confirmed Bug description: In testing a desktop snap that saves state in $HOME on close, I noticed that if I snap refresh the snap while the command is running that it will try to save its state to the previous snap version's data directory. For the snap I was testing (a browser), this resulted in a very poor user experience (the browser on restart complained about an improper shutdown). What is happening is that: 1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something like /home/user/snap/foo/x1. The security policy correctly allows writes to SNAP_USER_DATA 2. on snap refresh to 'x2', the security policy for the snap is updated for the running process such that /home/user/snap/foo/x1 is readonly and /home/user/snap/foo/x2 is read/write 3. the command in '1's environment is not changed and HOME (as well as SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path 4. the command tries to shutdown gracefully and save state to the 'x1' HOME and security policy blocks it Snappy's design for rollbacks relies on the previous SNAP_DATA and SNAP_USER_DATA directories not being writable and IMHO we should not change the policy to make other snap version's data dirs writable. The design of the snappy state engine ensures (among other things) that there is only ever one security policy in place for the snap. In snappy 15.04 this problem was (intentionally) avoided because we used snap security policy that was versioned such that the new policy would not apply until the next app invocation. Gustavo and Zygmunt, you both advocated strongly for only one version of the policy on disk and loaded in the kernel and I recall bringing up this type of bug as a counter-argument, and if IIRC for daemons we said that snapd could simply restart them (makes perfect sense). Have you thought of the mechanism for restarting non-daemons? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+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 1864758] Re: "Show Details" For Snap Programs - Error
*** This bug is a duplicate of bug 1844699 *** https://bugs.launchpad.net/bugs/1844699 ** This bug is no longer a duplicate of bug 1857814 "Show details" option broken for Snap apps ** This bug has been marked a duplicate of bug 1844699 The snap plugin is not claiming the desktop id correctly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1864758 Title: "Show Details" For Snap Programs - Error Status in gnome-software package in Ubuntu: New Bug description: For Snap programs if you right click and "Show Details" in Gnome it will open Ubuntu Software and come up with an error message "Sorry! There are no details for that application" Expected outcome when clicking "Show Details" should be Ubuntu Software being opened to the program's page ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 25 15:27:09 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2019-10-23 (125 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=en_US.UTF-8 SourcePackage: gnome-software UpgradeStatus: Upgraded to focal on 2020-02-22 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1864758/+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 1857814] Re: "Show details" option broken for Snap apps
*** This bug is a duplicate of bug 1844699 *** https://bugs.launchpad.net/bugs/1844699 ** This bug has been marked a duplicate of bug 1844699 The snap plugin is not claiming the desktop id correctly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1857814 Title: "Show details" option broken for Snap apps Status in gnome-software package in Ubuntu: Confirmed Bug description: Gnome Software says "Unable to find 'vlc_vlc.desktop'" for VLC, for example. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1857814/+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 1851931] Re: eoan regression: OSK does not appear automatically when selecting some text fields
Unaffected: Terminal, Files, Gedit, Ubuntu Software, Calculator, Libreoffice writer Affected: Snap: VLC, Chromium, Firefox, Non-snap: Steam, Gsmartcontrol, Tor browser, Teamviewer, Anydesk -- 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/1851931 Title: eoan regression: OSK does not appear automatically when selecting some text fields Status in gnome-shell package in Ubuntu: Incomplete Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851931/+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 1616650] Re: snap refresh while command is running may cause issues
Solution(?): Check for snap updates when you start the PC and every 6 hours I guess. If chromium is updated, restart the system. Be careful, new tabs won't reappear or save as bookmarks, so you should restart and not have to deal with it. Of course, this bug needs more attention than it currently has by the developers. -- 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/1616650 Title: snap refresh while command is running may cause issues Status in snapd: In Progress Status in chromium-browser package in Ubuntu: New Bug description: In testing a desktop snap that saves state in $HOME on close, I noticed that if I snap refresh the snap while the command is running that it will try to save its state to the previous snap version's data directory. For the snap I was testing (a browser), this resulted in a very poor user experience (the browser on restart complained about an improper shutdown). What is happening is that: 1. on launch the snap's HOME is set to SNAP_USER_DATA, which is something like /home/user/snap/foo/x1. The security policy correctly allows writes to SNAP_USER_DATA 2. on snap refresh to 'x2', the security policy for the snap is updated for the running process such that /home/user/snap/foo/x1 is readonly and /home/user/snap/foo/x2 is read/write 3. the command in '1's environment is not changed and HOME (as well as SNAP_USER_DATA and SNAP_DATA) are all still using 'x1' in the path 4. the command tries to shutdown gracefully and save state to the 'x1' HOME and security policy blocks it Snappy's design for rollbacks relies on the previous SNAP_DATA and SNAP_USER_DATA directories not being writable and IMHO we should not change the policy to make other snap version's data dirs writable. The design of the snappy state engine ensures (among other things) that there is only ever one security policy in place for the snap. In snappy 15.04 this problem was (intentionally) avoided because we used snap security policy that was versioned such that the new policy would not apply until the next app invocation. Gustavo and Zygmunt, you both advocated strongly for only one version of the policy on disk and loaded in the kernel and I recall bringing up this type of bug as a counter-argument, and if IIRC for daemons we said that snapd could simply restart them (makes perfect sense). Have you thought of the mechanism for restarting non-daemons? To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1616650/+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 1851931] Re: [snap] eoan regression: OSK does not appear automatically when selecting some text fields
** No longer affects: chromium-browser (Ubuntu) ** Tags removed: snap ** Summary changed: - [snap] eoan regression: OSK does not appear automatically when selecting some text fields + eoan regression: OSK does not appear automatically when selecting some text fields -- 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/1851931 Title: eoan regression: OSK does not appear automatically when selecting some text fields Status in gnome-shell package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851931/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
*doesn't appear automatically -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
The OSK doesn't work on 19.10 on text fields other than Ubuntu's. I hope it works in 20.04... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1857814] Re: "Show details" option broken for Snap apps
It looks to be the same -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1857814 Title: "Show details" option broken for Snap apps Status in gnome-software package in Ubuntu: Confirmed Bug description: Gnome Software says "Unable to find 'vlc_vlc.desktop'" for VLC, for example. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1857814/+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 1862135] Re: [snap] Chromium 80 window border artifacts while using chromium's title bar and borders
Fixed in 80.0.3987.100 ** Changed in: chromium-browser (Ubuntu) Status: New => Fix Released -- 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/1862135 Title: [snap] Chromium 80 window border artifacts while using chromium's title bar and borders Status in chromium-browser package in Ubuntu: Fix Released Bug description: FIX: It can be fixed by switching to system title bar and borders and back to chromium's. I'm using Wayland, Ubuntu 19.10, Chromium 80.0.3987.87 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862135/+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 1862135] Re: [snap] Chromium 80 window border error while using chromium's title bar and borders
** Summary changed: - [snap] Chromium 80 bug while using chromium's title bar and borders + [snap] Chromium 80 window border error while using chromium's title bar and borders ** Summary changed: - [snap] Chromium 80 window border error while using chromium's title bar and borders + [snap] Chromium 80 window border artifacts while using chromium's 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/1862135 Title: [snap] Chromium 80 window border artifacts while using chromium's title bar and borders Status in chromium-browser package in Ubuntu: New Bug description: FIX: It can be fixed by switching to system title bar and borders and back to chromium's. I'm using Wayland, Ubuntu 19.10, Chromium 80.0.3987.87 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862135/+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 1862135] [NEW] [snap] Chromium 80 bug while using chromium's title bar and borders
Public bug reported: FIX: It can be fixed by switching to system title bar and borders and back to chromium's. I'm using Wayland, Ubuntu 19.10, Chromium 80.0.3987.87 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Description changed: - I'm using wayland, Ubuntu 19.10, Chromium 80.0.3987.87 + FIX: It can be fixed by switching to system title bar and borders and + back to chromium's. - It can be fixed by switching to system title bar and borders and back to - chromium's. + I'm using Wayland, Ubuntu 19.10, Chromium 80.0.3987.87 -- 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/1862135 Title: [snap] Chromium 80 bug while using chromium's title bar and borders Status in chromium-browser package in Ubuntu: New Bug description: FIX: It can be fixed by switching to system title bar and borders and back to chromium's. I'm using Wayland, Ubuntu 19.10, Chromium 80.0.3987.87 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1862135/+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 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
(I think) It makes development easier, you don't have to build it for every Ubuntu version in support, or any Linux OS, it contains specific libraries you know won't cause issues with the app. -- 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/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+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 1813441] Re: Can no longer drag and drop files between desktop and applications
Applies to 19.10 as well -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Never mind the however part, it is fixed. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
I can confirm that hdmi is not selected when monitor returns from sleep (I did something and the correct sound device would be selected at startup before updating from proposed). However, closing and reopening the monitor manually causes HDMI to be selected. I don't think that used to happen previously. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
How do I update only pulseaudio? I get: $ sudo apt upgrade pulseaudio/eoan-proposed Reading package lists... Done Building dependency tree Reading state information... Done Selected version '1:13.0-1ubuntu1.1' (Ubuntu:19.10/eoan-proposed [amd64]) for 'pulseaudio' Selected version '1:13.0-1ubuntu1.1' (Ubuntu:19.10/eoan-proposed [amd64]) for 'libpulse0' because of 'pulseaudio' Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pulseaudio : Depends: libpulse0 (= 1:13.0-1ubuntu1.1) but 1:13.0-1ubuntu1 is to be installed pulseaudio-module-bluetooth : Depends: pulseaudio (= 1:13.0-1ubuntu1) E: Broken packages -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
When will the fix be released? -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1857814] [NEW] "Show details" option broken for Snap apps
Public bug reported: Gnome Software says "Unable to find 'vlc_vlc.desktop'" for VLC, for example. Ubuntu 19.10 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: eoan ** Package changed: android (Ubuntu) => gnome-software (Ubuntu) ** Description changed: Gnome Software says "Unable to find 'vlc_vlc.desktop'" for VLC, for example. + + Ubuntu 19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1857814 Title: "Show details" option broken for Snap apps Status in gnome-software package in Ubuntu: New Bug description: Gnome Software says "Unable to find 'vlc_vlc.desktop'" for VLC, for example. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1857814/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
Release 'eoan-proposed' for 'pulseaudio' was not found -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This bug is so annoying if you have your screen turn off due to inactivity that I'm inclined to press 1. for a fix and 2. to write something about it in the known issues section for 19.10. -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1851931] Re: [snap] regression: OSK does not appear automatically when selecting some text fields
*It worked with the snap on Disco. I'm also not convinced this is related only to Chromium. I just tested in Firefox and it doesn't work there either. -- 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/1851931 Title: [snap] regression: OSK does not appear automatically when selecting some text fields Status in chromium-browser package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851931/+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 1851931] Re: [snap] regression: OSK does not appear automatically when selecting some text fields
It worked with the snap -- 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/1851931 Title: [snap] regression: OSK does not appear automatically when selecting some text fields Status in chromium-browser package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851931/+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 1851931] Re: On-screen keyboard does not appear automatically when selecting some text fields on Eoan
*** This bug is a duplicate of bug 1697641 *** https://bugs.launchpad.net/bugs/1697641 No it doesn't. It worked in disco. -- 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/1851931 Title: On-screen keyboard does not appear automatically when selecting some text fields on Eoan Status in chromium-browser package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851931/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
For me, HDMI audio is selected in the options but sound plays in the desired device. What is annoying is that I have to go to settings every time I need to adjust the volume because the top right menu adjusts HDMI audio. Am I having the same issue? -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Status in pulseaudio source package in Focal: Triaged Bug description: On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1851931] Re: On-screen keyboard does not appear automatically when selecting some text fields on Eoan
** Description changed: - I get this on Eoan, no OSK pop up for Chromium text fields on laptop. - Works on desktop. + I get this on Eoan, no OSK pop up for Chromium text fields, on laptop + and desktop. - On my laptop (Thinkpad L520) it doesn't work. Curiously, when swiping up - with mouse the OSK doesn't come up when Chromium is on the view, but it - comes up when on desktop. The OSK pops up fine on terminal, login field - and text editor. It also doesn't work on Chrome. + Curiously, when swiping up with mouse on the laptop the OSK doesn't come + up when Chromium is on the view, but it comes up when on desktop. The + OSK pops up fine on terminal, login field and text editor. It also + doesn't work on Chrome. ** Description changed: - I get this on Eoan, no OSK pop up for Chromium text fields, on laptop - and desktop. + I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop + and a desktop. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. ** Description changed: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. + The OSK pops up fine on terminal, login field and text editor. It also + doesn't work on Chrome. + Curiously, when swiping up with mouse on the laptop the OSK doesn't come - up when Chromium is on the view, but it comes up when on desktop. The - OSK pops up fine on terminal, login field and text editor. It also - doesn't work on Chrome. + up when Chromium is on the view, but it comes up when on desktop. -- 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/1851931 Title: On-screen keyboard does not appear automatically when selecting some text fields on Eoan Status in gnome-shell package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields, on a laptop and a desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. Curiously, when swiping up with mouse on the laptop the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851931/+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 1851931] [NEW] On-screen keyboard does not appear automatically when selecting some text fields on Eoan
Public bug reported: I get this on Eoan, no OSK pop up for Chromium text fields on laptop. Works on desktop. On my laptop (Thinkpad L520) it doesn't work. Curiously, when swiping up with mouse the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: eoan -- 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/1851931 Title: On-screen keyboard does not appear automatically when selecting some text fields on Eoan Status in gnome-shell package in Ubuntu: New Bug description: I get this on Eoan, no OSK pop up for Chromium text fields on laptop. Works on desktop. On my laptop (Thinkpad L520) it doesn't work. Curiously, when swiping up with mouse the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851931/+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 1806080] Re: [snap] Chromium snap crashes when trying to access fs
** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Released -- 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/1806080 Title: [snap] Chromium snap crashes when trying to access fs Status in chromium-browser package in Ubuntu: Fix Released Bug description: When I attempt to upload or save on certain pages it crashes the browser. Some examples below. Does not happen on Google Drive. Looks like it's trying to query the fs and dies when it can't. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial Kernel: 4.15.0-39-generic Chromium: Version 70.0.3538.110 (Official Build) snap (64-bit) # Right click on blank page "save as" Nov 30 16:31:00 $HOSTNAME kernel: [35208.515968] audit: type=1400 audit(1543595460.939:151): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=30734 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:04 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=32093 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:04 $HOSTNAME kernel: [35212.081247] audit: type=1107 audit(1543595464.507:152): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=31991 label="snap.chromium.chromium" peer_pid=24826 peer_label="unconfined" Nov 30 16:31:05 $HOSTNAME kernel: [35213.238692] audit: type=1400 audit(1543595465.663:153): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=31991 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 30 16:31:05 $HOSTNAME kernel: [35213.274048] audit: type=1400 audit(1543595465.699:154): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=31991 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Right click on blank page "save as" #2 Nov 30 16:31:08 $HOSTNAME kernel: [35216.557849] audit: type=1400 audit(1543595468.983:155): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=31991 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:13 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=32646 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:14 $HOSTNAME kernel: [35221.656759] audit: type=1107 audit(1543595474.083:156): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=32544 label="snap.chromium.chromium" peer_pid=24826 peer_label="unconfined" Nov 30 16:31:23 $HOSTNAME kernel: [35230.641856] audit: type=1400 audit(1543595483.067:157): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=32544 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 30 16:31:23 $HOSTNAME kernel: [35230.660955] audit: type=1400 audit(1543595483.087:158): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=32544 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Upload to Salesforce case #2 Nov 30 16:31:46 $HOSTNAME kernel: [35253.816946] audit: type=1400 audit(1543595506.243:159): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=32544 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:56 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=938 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:56 $HOSTNAME kernel: [35264.509009] audit: type=1107 audit(1543595516.935:160): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager"
[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
On my laptop (Thinkpad L520) it doesn't work. Curiously, when swiping up with mouse the OSK doesn't come up when Chromium is on the view, but it comes up when on desktop. The OSK pops up fine on terminal, login field and text editor. It also doesn't work on Chrome. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
I get this on Eoan, no OSK pop up for Chromium text fields on laptop. Works on desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+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 1806697] Re: Status of interface connections not properly updated in the UI
It works, disco gnome-software: Installed: 3.30.6-2ubuntu4.19.04.2 Candidate: 3.30.6-2ubuntu4.19.04.2 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Status in gnome-software source package in Eoan: Fix Released Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1806697] Re: Status of interface connections not properly updated in the UI
Fix release for disco when? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Won't Fix Status in gnome-software source package in Disco: Fix Committed Status in gnome-software source package in Eoan: Fix Released Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1822773] Re: Volume resets to 0 on startup
Tried startup without steam and chromium, issue still occurs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1822773 Title: Volume resets to 0 on startup Status in alsa-utils package in Ubuntu: New Bug description: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10, 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1822773/+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 1822773] Re: Volume resets to 0 on startup
What happens is, the sound in the login screen appears as 0, then in the desktop it goes to 100, then after a few seconds goes to 0. I have chromium and steam starting up on boot. Applies to Ubuntu 19.04. ** Description changed: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. - Ubuntu 18.10 + Ubuntu 18.10, 19.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-utils in Ubuntu. https://bugs.launchpad.net/bugs/1822773 Title: Volume resets to 0 on startup Status in alsa-utils package in Ubuntu: New Bug description: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10, 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1822773/+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 1837534] [NEW] Internet connection randomly stops working
Public bug reported: Ubuntu says I'm still connected. "nmcli device" says I'm connected. I have to turn off and on again my internet connection(menu in the top right -> name of connection menu -> Turn Off) to fix the issue. Ubuntu 19.10 ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: gnome-software (Ubuntu) => ubuntu ** Description changed: - Ubuntu says I'm still connected. nmcli device says I'm connected. I have - to turn off and on again my internet connection(menu in the top right -> - name of connection menu -> Turn Off) to fix the issue. + Ubuntu says I'm still connected. "nmcli device" says I'm connected. I + have to turn off and on again my internet connection(menu in the top + right -> name of connection menu -> Turn Off) to fix the issue. Ubuntu 19.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1837534 Title: Internet connection randomly stops working Status in Ubuntu: New Bug description: Ubuntu says I'm still connected. "nmcli device" says I'm connected. I have to turn off and on again my internet connection(menu in the top right -> name of connection menu -> Turn Off) to fix the issue. Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1837534/+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 1823035] Re: Buttons in Night Light menu in settings weird behaviour
Fixed in Ubuntu 19.04/Gnome 3.32.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1823035 Title: Buttons in Night Light menu in settings weird behaviour Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-25 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) 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-control-center/+bug/1823035/+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 1823035] Re: Buttons in Night Light menu in settings weird behaviour
I can't say those bugs are related to mine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1823035 Title: Buttons in Night Light menu in settings weird behaviour Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-25 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) 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-control-center/+bug/1823035/+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 1823035] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1823035/+attachment/5252798/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1823035 Title: Buttons in Night Light menu in settings weird behaviour Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-25 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) 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-control-center/+bug/1823035/+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 1823035] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1823035/+attachment/5252797/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1823035 Title: Buttons in Night Light menu in settings weird behaviour Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-25 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) 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-control-center/+bug/1823035/+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 1823035] Re: Buttons in Night Light menu in settings weird behaviour
apport information ** Tags added: apport-collected ** Description changed: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 + --- + ProblemType: Bug + ApportVersion: 2.20.10-0ubuntu13.2 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.10 + InstallationDate: Installed on 2018-10-25 (160 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 + Tags: cosmic + Uname: Linux 4.18.0-17-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1823035/+attachment/5252796/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1823035 Title: Buttons in Night Light menu in settings weird behaviour Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-10-25 (160 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Tags: cosmic Uname: Linux 4.18.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) 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-control-center/+bug/1823035/+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 1823035] Re: Buttons in Night Light menu in settings weird behaviour
I'm on Ubuntu 18.10 and gnome 3.30.1. The buttons are found in Settings->Devices->Displays->Night Light. -- 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/1823035 Title: Buttons in Night Light menu in settings weird behaviour Status in gnome-shell package in Ubuntu: Incomplete Bug description: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823035/+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 1823035] [NEW] Buttons in Night Light menu in settings weird behaviour
Public bug reported: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1823035 Title: Buttons in Night Light menu in settings weird behaviour Status in gnome-shell package in Ubuntu: New Bug description: When you press the pressed button (eg the sunset to sunrise button), it gets unpressed and nothing changes. Then, when you press that button again, the opposite button (manual) is pressed. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1823035/+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 1822773] [NEW] Volume resets to 0 on startup
Public bug reported: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1822773 Title: Volume resets to 0 on startup Status in gnome-settings-daemon package in Ubuntu: New Bug description: Steps to reproduce the problem 1. Set the volume to some value like 100 or 80% 2. Shutdown and start the system 3. Volume is set to 0%. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1822773/+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 1822593] [NEW] No option to disable devices low battery notifications
Public bug reported: You can find the battery levels of devices in Settings->Power. It would be nice if the notifications about the batteries could be disabled. I keep getting them, but my devices keep working for a long time (even when they themselves flash red due to low battery). Ubuntu 18.10 Gnome 3.30.1 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1822593 Title: No option to disable devices low battery notifications Status in gnome-settings-daemon package in Ubuntu: New Bug description: You can find the battery levels of devices in Settings->Power. It would be nice if the notifications about the batteries could be disabled. I keep getting them, but my devices keep working for a long time (even when they themselves flash red due to low battery). Ubuntu 18.10 Gnome 3.30.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1822593/+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 1822165] [NEW] Steam application links don't work in Chromium Snap
Public bug reported: Example of a link: steam://connect/164.132.201.196:27119 This link is supposed to open a window or start a game in the steam application, but steam is not doing anything. It works in non-snap Chromium (tested on a new installation and a chrome prompt appeared, maybe some setting in my snap version is preventing this?). Ubuntu 18.10 Chromium Version 73.0.3683.75 (Official Build) snap (64-bit) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- 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/1822165 Title: Steam application links don't work in Chromium Snap Status in chromium-browser package in Ubuntu: New Bug description: Example of a link: steam://connect/164.132.201.196:27119 This link is supposed to open a window or start a game in the steam application, but steam is not doing anything. It works in non-snap Chromium (tested on a new installation and a chrome prompt appeared, maybe some setting in my snap version is preventing this?). Ubuntu 18.10 Chromium Version 73.0.3683.75 (Official Build) snap (64-bit) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1822165/+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 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek
** Description changed: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. - Ubuntu 18.10 + Applies to Ubuntu 18.10 and 19.04 -- 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/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Bug description: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Applies to Ubuntu 18.10 and 19.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820523/+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 1820523] Re: OSK Enter, space and backspace keys don't work when typing in Greek
I opened Ubuntu 19.04 in a VM and selected The Try Ubuntu option. The bug is still present. This is the bug in gitlab gnome: https://gitlab.gnome.org/GNOME/gnome-shell/issues/1079 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1079 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1079 -- 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/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek Status in gnome-shell package in Ubuntu: Incomplete Bug description: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1820523/+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 1820523] Re: OSK Enter and backspace keys don't work
** Package changed: gnome-settings-daemon (Ubuntu) => gdm3 (Ubuntu) ** Summary changed: - OSK Enter and backspace keys don't work + OSK Enter and backspace keys don't work in some text fields ** Description changed: - The enter and backspace keys on the Ubuntu On-screen keyboard don't - work. They don't work on Chromium and the apps menu, but work in gedit. + The enter and backspace keys on the Ubuntu On-screen keyboard don't work + in some instances. They don't work on Chromium and the apps menu, but + work in gedit. Ubuntu 18.10 ** Description changed: The enter and backspace keys on the Ubuntu On-screen keyboard don't work - in some instances. They don't work on Chromium and the apps menu, but + in some instances. They don't work in Chromium and the apps menu, but work in gedit. Ubuntu 18.10 ** Description changed: The enter and backspace keys on the Ubuntu On-screen keyboard don't work in some instances. They don't work in Chromium and the apps menu, but work in gedit. + The problem occurs in a laptop. I tested it on a desktop and it works + fine. + Ubuntu 18.10 ** Summary changed: - OSK Enter and backspace keys don't work in some text fields + OSK Enter and backspace keys don't work when typing in Greek ** Description changed: The enter and backspace keys on the Ubuntu On-screen keyboard don't work - in some instances. They don't work in Chromium and the apps menu, but - work in gedit. - - The problem occurs in a laptop. I tested it on a desktop and it works - fine. + when typing in Greek. Ubuntu 18.10 ** Summary changed: - OSK Enter and backspace keys don't work when typing in Greek + OSK Enter, space and backspace keys don't work when typing in Greek ** Description changed: - The enter and backspace keys on the Ubuntu On-screen keyboard don't work - when typing in Greek. + The enter, space and backspace keys on the Ubuntu On-screen keyboard + don't work when typing in Greek. Ubuntu 18.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1820523 Title: OSK Enter, space and backspace keys don't work when typing in Greek Status in gdm3 package in Ubuntu: New Bug description: The enter, space and backspace keys on the Ubuntu On-screen keyboard don't work when typing in Greek. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1820523/+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 1820523] [NEW] OSK Enter and backspace keys don't work
Public bug reported: The enter and backspace keys on the Ubuntu On-screen keyboard don't work. They don't work on Chromium and the apps menu, but work in gedit. Ubuntu 18.10 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1820523 Title: OSK Enter and backspace keys don't work Status in gnome-settings-daemon package in Ubuntu: New Bug description: The enter and backspace keys on the Ubuntu On-screen keyboard don't work. They don't work on Chromium and the apps menu, but work in gedit. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1820523/+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 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
mirec You are not running the latest version of gnome-shell. The latest version is 3.30.2-0ubuntu1.18.10.1 -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+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
A computer that doesn't have any proposed packages installed also exhibits the language indicator bug, so it's probably not related to the packages for this issue. -- 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: Fix Committed Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: Fix Committed 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Is there a way to reliably reproduce the bug? Because, for me, it happens randomly. -- 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: Fix Committed Status in gnome-shell source package in Cosmic: Invalid Status in gnome-shell-extension-ubuntu-dock source package in Cosmic: Fix Committed 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 1812865] Re: Extracting an archive by right-clicking and selecting "Extract here" results in many extracted files to be 0 bytes
** Package changed: linphone (Ubuntu) => gdm3 (Ubuntu) ** Summary changed: - Extracting an archive by right-clicking and selecting "Extract here" results in many extracted files to be 0 bytes + Extracting an archive by right-clicking and selecting "Extract here" results in many extracted files to be 0 bytes in size -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1812865 Title: Extracting an archive by right-clicking and selecting "Extract here" results in many extracted files to be 0 bytes in size Status in gdm3 package in Ubuntu: New Bug description: Download the linux-x64 zip from here (https://github.com/JustArchiNET/ArchiSteamFarm/releases/tag/3.4.2.2) to test. Extracting works fine with the unzip command. I am not aware of this bug occurring with zips different from the one provided. Ubuntu 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1812865/+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
I've noticed the text on the keyboard layout indicator disappear too. -- 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: Fix Committed 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Don't forget to change the tags to verification-failed if the new package doesn't fix the issue. From what you said it's still present, at least for you. -- 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: Fix Committed 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Jesse Running "apt-cache policy " shows the version of the package installed -- 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: Fix Committed 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Yes, the problem existed before installing the package. I too experienced this sporadically. I assume installing dash-to-dock causes the issue to appear consistently. I experienced the issue without dash- to-dock installed. -- 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: Fix Committed 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
I installed dash-to-dock to test this. I locked the PC and unlocked it without an issue. The dock didn't appear in the lock screen. gnome-shell-extension-ubuntu-dock: Installed: 63ubuntu1.18.10.1 Candidate: 63ubuntu1.18.10.1 ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- 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: Fix Committed 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Eric I have this version and I experienced the issue 2 days ago. -- 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Dom Hudson But this (https://bugs.launchpad.net/ubuntu/cosmic/+source /gnome-shell-extension-ubuntu-dock/+bug/1769383/comments/48) says it is released on Ubuntu Disco. -- 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 1769383] Re: Ubuntu dock/launcher is shown on the lock screen
Is this fix released for Ubuntu 18.10? -- 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 1808204] Re: Glitches related to closing the screen due to inactivity
** Package changed: gdm (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1808204 Title: Glitches related to closing the screen due to inactivity Status in gdm3 package in Ubuntu: New Bug description: I can't replicate this issue. Its appearance seems random. Steps taken: 1. Have the screen close due to inactivity. 2. Open the screen by e.g. moving the mouse. 3. The login screen "banner" appears. This time, however, the application bar (and maybe even the top status and notifications bar) can be seen. 4. Press enter to remove the banner and reveal the desktop environment. 5. The desktop environment is not revealed and there is the characteristic pink reddish background of gnome in place of the banner(1st glitch). 6. Put your PC to sleep through the pause button in the menu in the top status bar. 7. Reopen your PC. 8. Press enter to reveal the desktop environment. 9. The desktop environment is revealed and is functional for the most part. However, the application bar acts really weird. For example, if you put the mouse cursor to the edge of the screen, you can't click the Show apps button (2nd glitch). 10. Press alt-F2, r and then enter to restart Gnome. This fixes the previous issue. Ubuntu 18.10 Gnome 3.30.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1808204/+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 1808204] [NEW] Glitches related to closing the screen due to inactivity
Public bug reported: I can't replicate this issue. Its appearance seems random. Steps taken: 1. Have the screen close due to inactivity. 2. Open the screen by e.g. moving the mouse. 3. The login screen "banner" appears. This time, however, the application bar (and maybe even the top status and notifications bar) can be seen. 4. Press enter to remove the banner and reveal the desktop environment. 5. The desktop environment is not revealed and there is the characteristic pink reddish background of gnome in place of the banner(1st glitch). 6. Put your PC to sleep through the pause button in the menu in the top status bar. 7. Reopen your PC. 8. Press enter to reveal the desktop environment. 9. The desktop environment is revealed and is functional for the most part. However, the application bar acts really weird. For example, if you put the mouse cursor to the edge of the screen, you can't click the Show apps button (2nd glitch). 10. Press alt-F2, r and then enter to restart Gnome. This fixes the previous issue. Ubuntu 18.10 Gnome 3.30.1 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-settings-daemon (Ubuntu) => gdm (Ubuntu) ** Description changed: I can't replicate this issue. Its appearance seems random. - Steps: + Steps taken: 1. Have the screen close due to inactivity. 2. Open the screen by e.g. moving the mouse. 3. The login screen "banner" appears. This time, however, the application bar (and maybe even the top status and notifications bar) can be seen. 4. Press enter to remove the banner and reveal the desktop environment. 5. The desktop environment is not revealed and there is the characteristic pink reddish background of gnome in place of the banner(1st glitch). 6. Put your PC to sleep through the pause button in the menu in the top status bar. 7. Reopen your PC. 8. Press enter to reveal the desktop environment. - 9. The application bar acts really weird. For example, if you put the mouse cursor to the edge of the screen, you can't click the Show apps button (2nd glitch). + 9. The desktop environment is revealed and is functional for the most part. However, the application bar acts really weird. For example, if you put the mouse cursor to the edge of the screen, you can't click the Show apps button (2nd glitch). 10. Press alt-F2, r and then enter to restart Gnome. This fixes the previous issue. Ubuntu 18.10 Gnome 3.30.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1808204 Title: Glitches related to closing the screen due to inactivity Status in gdm3 package in Ubuntu: New Bug description: I can't replicate this issue. Its appearance seems random. Steps taken: 1. Have the screen close due to inactivity. 2. Open the screen by e.g. moving the mouse. 3. The login screen "banner" appears. This time, however, the application bar (and maybe even the top status and notifications bar) can be seen. 4. Press enter to remove the banner and reveal the desktop environment. 5. The desktop environment is not revealed and there is the characteristic pink reddish background of gnome in place of the banner(1st glitch). 6. Put your PC to sleep through the pause button in the menu in the top status bar. 7. Reopen your PC. 8. Press enter to reveal the desktop environment. 9. The desktop environment is revealed and is functional for the most part. However, the application bar acts really weird. For example, if you put the mouse cursor to the edge of the screen, you can't click the Show apps button (2nd glitch). 10. Press alt-F2, r and then enter to restart Gnome. This fixes the previous issue. Ubuntu 18.10 Gnome 3.30.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1808204/+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 1806080] Re: [snap] Chromium snap crashes when trying to access fs
It works with version 71.0.3578.80 (538). It is currently available in the candidate channel. -- 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/1806080 Title: [snap] Chromium snap crashes when trying to access fs Status in chromium-browser package in Ubuntu: Confirmed Bug description: When I attempt to upload or save on certain pages it crashes the browser. Some examples below. Does not happen on Google Drive. Looks like it's trying to query the fs and dies when it can't. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.5 LTS Release: 16.04 Codename: xenial Kernel: 4.15.0-39-generic Chromium: Version 70.0.3538.110 (Official Build) snap (64-bit) # Right click on blank page "save as" Nov 30 16:31:00 $HOSTNAME kernel: [35208.515968] audit: type=1400 audit(1543595460.939:151): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=30734 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:04 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=32093 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:04 $HOSTNAME kernel: [35212.081247] audit: type=1107 audit(1543595464.507:152): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=31991 label="snap.chromium.chromium" peer_pid=24826 peer_label="unconfined" Nov 30 16:31:05 $HOSTNAME kernel: [35213.238692] audit: type=1400 audit(1543595465.663:153): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=31991 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 30 16:31:05 $HOSTNAME kernel: [35213.274048] audit: type=1400 audit(1543595465.699:154): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=31991 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Right click on blank page "save as" #2 Nov 30 16:31:08 $HOSTNAME kernel: [35216.557849] audit: type=1400 audit(1543595468.983:155): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=31991 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:13 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=32646 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:14 $HOSTNAME kernel: [35221.656759] audit: type=1107 audit(1543595474.083:156): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" mask="send" name="org.bluez" pid=32544 label="snap.chromium.chromium" peer_pid=24826 peer_label="unconfined" Nov 30 16:31:23 $HOSTNAME kernel: [35230.641856] audit: type=1400 audit(1543595483.067:157): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c99:0" pid=32544 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 Nov 30 16:31:23 $HOSTNAME kernel: [35230.660955] audit: type=1400 audit(1543595483.087:158): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/udev/data/c6:0" pid=32544 comm="TaskSchedulerFo" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Upload to Salesforce case #2 Nov 30 16:31:46 $HOSTNAME kernel: [35253.816946] audit: type=1400 audit(1543595506.243:159): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=32544 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 # Restart browser Nov 30 16:31:56 $HOSTNAME dbus[1899]: apparmor="DENIED" operation="dbus_method_call" bus="session" path="/org/freedesktop/secrets" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name="org.freedesktop.secrets" pid=938 label="snap.chromium.chromium" peer_pid=1823 peer_label="unconfined" Nov 30 16:31:56 $HOSTNAME kernel: [35264.509009] audit: type=1107 audit(1543595516.935:160): pid=1384 uid=106 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/" interface="org.freedesktop.DBus.ObjectManager"
[Desktop-packages] [Bug 1795142] Re: Allow for a custom period of inactivity before going to sleep to be selected
** Description changed: The times of inactivity you are allowed to set your computer to sleep after are predetermined. I would like to be able to define these times, preferably in minutes. I know I am probably able to change the value through text files and the command line, but Ubuntu should be as user- - friendly as it can be. Having to use a command line doesn't help with - that. + friendly as it can be. Having to use a command line for simple things + doesn't help with that. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 29 17:26:33 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1795142 Title: Allow for a custom period of inactivity before going to sleep to be selected Status in gnome-control-center package in Ubuntu: New Bug description: The times of inactivity you are allowed to set your computer to sleep after are predetermined. I would like to be able to define these times, preferably in minutes. I know I am probably able to change the value through text files and the command line, but Ubuntu should be as user-friendly as it can be. Having to use a command line for simple things doesn't help with that. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Sep 29 17:26:33 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1795142/+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 1806697] Re: Status of interface connections not properly updated in the UI
I did, however, manage to change one other permission(the home folder access) before changing the removable drives one. That's why I thought it was specific to the removable drives permission. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI Status in gnome-software package in Ubuntu: Confirmed Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1806697] Re: Status of interface connections not properly updated in the UI
I did, however, manage to change one other permission earlier. That's why I thought it was specific to this permission. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1806697 Title: Status of interface connections not properly updated in the UI Status in gnome-software package in Ubuntu: Confirmed Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1806697/+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 1806697] [NEW] Chromium snap "Removable storage devices" permission fails to enable
Public bug reported: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: chromium snap ** Summary changed: - Chromium snap Removable storage devices permission fails to enable + Chromium snap "Removable storage devices" permission fails to enable -- 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/1806697 Title: Chromium snap "Removable storage devices" permission fails to enable Status in chromium-browser package in Ubuntu: New Bug description: Steps to reproduce the problem: 1. Go to the Chromium snap store page by e.g. right clicking on its icon and selecting Show details and then the specific app. 2. Press the Permissions button. 3. Press/slide the Read/write files on removable storage devices slider. 4. Close the permissions and the store window. 5. Reopen the windows. 6. The permission should be enabled, but it isn't. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1806697/+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 1796499] Re: Keyboard calculator button not working
It's fixed. I'm using gnome-settings-daemon 3.30.1.2-1ubuntu3. ** Tags removed: verification-needed verification-needed-cosmic ** Tags added: verification-done verification-done-cosmic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1796499 Title: Keyboard calculator button not working Status in gnome-settings-daemon package in Ubuntu: Fix Committed Status in gnome-settings-daemon source package in Cosmic: Fix Committed Bug description: * Impact The calculator keybinding doesn't work with the gnome-calculator snap * Test case - go to gnome-control-center, keyboard and configure a keybinding to start the calculator (or use the default one which is the calculator key if you have a keyboard including one of those) - install gnome-calculator as a snap and remove the deb (should be the case on the default installation) - press the configured key -> the calculator should start * Regression potential The code allows trying 2 .desktop name, upstream renamed their in the 3.23 which was in zesty, they still include the fallback but Ubuntu hasn't been needed it since zesty, the patch changes to know about the current .deb name and about the snap one. If users had pinned an years old version of the calculator then their keybinding is going to stop working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796499/+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 1796499] Re: Keyboard calculator button not working
seb128 I don't understand what that means, but I am certain a solution is being worked on. I think the importance should be higher. As Flatron commented in the askubuntu question, "How could they possible break the Calculator ? Of all things that may be broken this one should always work on any OS, no matter what... Imagine being a new person to (Ubuntu) Linux and finding that your calculator simply does not work with no error". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1796499 Title: Keyboard calculator button not working Status in gnome-settings-daemon package in Ubuntu: In Progress Bug description: The calculator app doesn't open when the calculator button on the keyboard is pressed. I'm using a Logitech K520 keyboard. I found this: https://askubuntu.com/questions/1031673/cannot-open-calculator-app- from-keyboard-calculator-button An out-of-the-box solution would be nice though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 18:17:47 2018 InstallationDate: Installed on 2018-09-29 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796499/+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 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
The workaround worked. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
The bug ID is 435. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
@seb128 Sorry, I will remove it. ** Description changed: - "Started bpfilter" is located just under "Started Gnome Desktop - Manager". There is unusual Network activity during that time. The light - of the WiFi adapter is blinking a lot. + There is unusual Network activity during that time. The light of the + WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". ** Description changed: - There is unusual Network activity during that time. The light of the - WiFi adapter is blinking a lot. + The boot process hangs with the message "started bpfilter". There is + unusual Network activity during that time. The light of the WiFi adapter + is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". ** Description changed: - The boot process hangs with the message "started bpfilter". There is - unusual Network activity during that time. The light of the WiFi adapter - is blinking a lot. + The boot process hangs with the last message being "started bpfilter". + There is unusual Network activity during that time. The light of the + WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The
[Desktop-packages] [Bug 1798790] Re: Ubuntu 18.10 login screen never appears when using the Nvidia driver
** Attachment added: "prev_boot.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204440/+files/prev_boot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 login screen never appears when using the Nvidia driver Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798790] Re: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot
** Attachment added: "dpkgl.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204403/+files/dpkgl.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: "Started bpfilter" is located just under "Started Gnome Desktop Manager". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798790] Re: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot
@seb128 I'm just trying to explain where the two messages are in relation to each other in this command-like environment you are stuck in. Having one line before the other is not an issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: "Started bpfilter" is located just under "Started Gnome Desktop Manager". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798790] Re: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot
These commands were run in a normal boot of Ubuntu, without the Nvidia drivers. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204405/+files/lspcik.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: "Started bpfilter" is located just under "Started Gnome Desktop Manager". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798790] Re: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204402/+files/dmesg.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: "Started bpfilter" is located just under "Started Gnome Desktop Manager". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798790] Re: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot
** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+attachment/5204404/+files/journal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" - "Started Gnome Desktop Manager" during boot Status in gdm3 package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: "Started bpfilter" is located just under "Started Gnome Desktop Manager". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
Yes, it auto opens for the apps I mentioned it works. I think I'm using Wayland. Yes, I enabled the OSK in universal access. -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+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 1791551] Re: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X
After updating to 18.10, it seems the OSK works as intended in several apps like Chrome, Chromium, the cmd and gedit. Strangely, it doesn't automatically appear in the search box of file explorer. -- 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/1791551 Title: Activation of new on-screen keyboard in Gnome 3.28/3.30 is difficult to discover in Wayland and not possible in X Status in gnome-shell package in Ubuntu: Confirmed Bug description: The new OSK does not auto-activate reliably by selecting any text widget as the Gnome 3.28 release notes claim: "The new keyboard automatically activates when a text area is selected, ..." -- https://help.gnome.org/misc/release-notes/3.28/ This does not work with text widgets of alien toolkits (Chrome, Firefox, Qt, ...). Even in Gnome this does not work everywhere, for me (Cosmic, 3.30) it does only for the search boxes of Activity and Application menus, not anywhere else that I can find. Not even epiphany, gedit, or other first-class Gnome applications. It is the same in Ubuntu 18.04 according to Bug #1760399 (this report is also referenced as evidence further down). Does this need a separate bug report? Is it a bug in Gnome libraries, Gtk libraries, or in each individual application where it does not work who is using these libraries? Hence it is necessary to have a way for manual activation. This is possible in Wayland by swiping up from bottom of screen on a touch screen, but there is no UI hint for this and I banged my head bloody until I stumbled on the solution. In the default X session the swipe does not work and hence it cannot be manually activated at all. The Ubuntu help for 18.04.1 describes it incorrectly/incompletely and contributes to the confusion. Bug report: https://bugs.launchpad.net/ubuntu/+source/ubuntu-docs/+bug/1791548 I refer you to user confusion on the following links, note that the previously available answers on Askubuntu all provide incorrect or incomplete solutions: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760399 (I added a description in comment #10 earlier today) Askubuntu (I added new answers earlier today): https://askubuntu.com/questions/1057485/ubuntu-18-04-no-on-screen-keyboard/1073461#1073461 https://askubuntu.com/questions/1035622/screen-keyboard-not-showing-up-in-firefox-ubuntu-18-04/1073756#1073756 https://askubuntu.com/questions/1036983/cannot-consistently-bring-up-on-screen-keyboard/1073754#1073754 https://askubuntu.com/questions/1058176/how-to-make-ubuntu-18-04-on-screen-keyboard-work-with-google-chrome/1073743#1073743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.3-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 9 23:04:26 2018 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2185 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-04-08 (154 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791551/+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 1798790] [NEW] Ubuntu 18.10 hangs at "started bpfilter"
Public bug reported: "Started bpfilter" is located just under "Started Gnome Desktop Manager". I have found that uninstalling my Nvidia drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Package changed: xorg-server (Ubuntu) => gdm3 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu 18.10 hangs at "started bpfilter" Status in gdm3 package in Ubuntu: New Bug description: "Started bpfilter" is located just under "Started Gnome Desktop Manager". I have found that uninstalling my Nvidia drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+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 1798429] [NEW] Automatic selection of account in the login screen
Public bug reported: For example, if there is only one account, it should be selected automatically. I shouldn't have to press enter to select it and enter my password. An idea for multiple accounts would be to select the most frequently used. You could even show all the accounts when having one selected to enter its password. Description:Ubuntu 18.04.1 LTS Release:18.04 ** Affects: gnome-calculator (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1798429 Title: Automatic selection of account in the login screen Status in gnome-calculator package in Ubuntu: New Bug description: For example, if there is only one account, it should be selected automatically. I shouldn't have to press enter to select it and enter my password. An idea for multiple accounts would be to select the most frequently used. You could even show all the accounts when having one selected to enter its password. Description: Ubuntu 18.04.1 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1798429/+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 1796499] Re: Keyboard calculator button not working
** Description changed: The calculator app doesn't open when the calculator button on the - keyboard is pressed. I'm using a Logitech keyboard. I found this: + keyboard is pressed. I'm using a Logitech K520 keyboard. I found this: https://askubuntu.com/questions/1031673/cannot-open-calculator-app-from- keyboard-calculator-button An out-of-the-box solution would be nice though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 18:17:47 2018 InstallationDate: Installed on 2018-09-29 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1796499 Title: Keyboard calculator button not working Status in gnome-calculator package in Ubuntu: New Bug description: The calculator app doesn't open when the calculator button on the keyboard is pressed. I'm using a Logitech K520 keyboard. I found this: https://askubuntu.com/questions/1031673/cannot-open-calculator-app- from-keyboard-calculator-button An out-of-the-box solution would be nice though. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 6 18:17:47 2018 InstallationDate: Installed on 2018-09-29 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1796499/+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
