[Desktop-packages] [Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store
This bug was fixed in the package chromium-browser - 77.0.3865.120-0ubuntu2 --- chromium-browser (77.0.3865.120-0ubuntu2) focal; urgency=medium * debian/chromium-browser.preinst: revert a previous change which was causing upgrades from disco to eoan to install the snap but not connect the password-manager-service interface (LP: #1849160) * debian/control: update Vcs-Bzr URL to point to the branch for 20.04 (codename the Focal Fossa) -- Olivier Tilloy Tue, 22 Oct 2019 16:20:34 +0200 ** Changed in: chromium-browser (Ubuntu) Status: Fix Committed => 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/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: In Progress Bug description: [Impact] After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. [Test Case] Install chromium-browser in disco (19.04), save a few passwords for login forms. Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved passwords are still there. They can be inspected by browsing to chrome://settings/passwords. As an additional check, the output of `snap connections chromium | grep password` should look like this: password-manager-service chromium:password-manager-service :password-manager-service manual I.e. the interface should be marked as manually connected, even though the user hasn't explicitly connected it. [Regression Potential] Low. The change removes an assumption on upgrade paths that has become incorrect. Now the password-manager-service interface will always be connected on upgrade, which I think is sensible. Users who wish to disconnect the interface (unlikely use case) will also have to remove the chromium-browser transitional package, to prevent it from reconnecting the interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+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 1825940] Re: [graphics] Enable ICL
** Changed in: intel Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1825940 Title: [graphics] Enable ICL Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based on 18.04.3 graphics stack with linux-oem-osp1 kernel. [Test case] The usual desktop usage, graphics tests etc. [Regression potential] Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and it can't regress any currently running system. Mesa backports are limited to ICL, so they shouldn't regress earlier generations either. -- Original description: ICL graphics is not enabled in 19.04. if you want to use 19.04 on ICL platform, you need do like this Add kernel option i915.alpha_support=1 Target Release:19.10 Target Kernel: 5.2 Target Mesa: 19.1 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1825940/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions
Have seen it both with the internal laptop keyboard as well as an external USB keyboard -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1849415] Re: Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1849415 Title: Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: I tried to use the gnome magnifier after updating to 19.10 today. After enabling zoom from the control panel, I could no longer send mouse input anywhere other than the desktop. This made it impossible to turn zoom off using the mouse and it doesn't seem to be possible to turn off using keyboard navigation either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:20:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849415/+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 1849415] Re: Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions
Confirmed, but there are two workarounds: * Use Xorg instead (log into the "Ubuntu" session); or * Add zoom on/off controls to the top panel via: Settings > Universal Access > Always Show Universal Access Menu = ON -- 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/1849415 Title: Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: I tried to use the gnome magnifier after updating to 19.10 today. After enabling zoom from the control panel, I could no longer send mouse input anywhere other than the desktop. This made it impossible to turn zoom off using the mouse and it doesn't seem to be possible to turn off using keyboard navigation either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:20:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849415/+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 1849119] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exi
The relevant log file is DpkgTerminalLog.txt:
Preparing to unpack .../chromium-browser_77.0.3865.120-0ubuntu1~snap1_amd64.deb
...
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
error: snap "chromium" has "install-snap" change in progress
@Manisha: were you installing the chromium snap at the same time as you were
installing chromium-browser, by any chance?
** Summary changed:
- package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 10
+ package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: error: snap "chromium" has "install-snap" change in progress
** Tags added: 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/1849119
Title:
package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: error: snap "chromium" has "install-snap" change in
progress
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Showing system error
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
AptOrdering:
chromium-browser:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct 21 18:05:24 2019
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 10
InstallationDate: Installed on 2019-10-21 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu2
apt 1.9.4
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849119/+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 1849415] Re: Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions
** Summary changed: - Magnifier stuck on wayland + Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High -- 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/1849415 Title: Desktop zoom makes app windows unresponsive to the mouse in Wayland sessions Status in gnome-shell package in Ubuntu: Confirmed Bug description: I tried to use the gnome magnifier after updating to 19.10 today. After enabling zoom from the control panel, I could no longer send mouse input anywhere other than the desktop. This made it impossible to turn zoom off using the mouse and it doesn't seem to be possible to turn off using keyboard navigation either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:20:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849415/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice
Also, it looks like you're using a laptop keyboard. Is that right? ** Summary changed: - Keyboard shortcuts to launch apps sometimes launch twice + Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice in Wayland sessions Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1849415] [NEW] Magnifier stuck on wayland
Public bug reported: I tried to use the gnome magnifier after updating to 19.10 today. After enabling zoom from the control panel, I could no longer send mouse input anywhere other than the desktop. This made it impossible to turn zoom off using the mouse and it doesn't seem to be possible to turn off using keyboard navigation either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:20:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan wayland-session -- 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/1849415 Title: Magnifier stuck on wayland Status in gnome-shell package in Ubuntu: New Bug description: I tried to use the gnome magnifier after updating to 19.10 today. After enabling zoom from the control panel, I could no longer send mouse input anywhere other than the desktop. This made it impossible to turn zoom off using the mouse and it doesn't seem to be possible to turn off using keyboard navigation either. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 23 00:20:13 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-18 (127 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-10-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849415/+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 1292398] Re: Second screen position isn't saved from one session to another
@Daniel, just send the bug report to forum, As @Max said above, it really really annoying bug when using a laptop with an external monitor. When I using dual screen with my laptop on the left, external monitor on the right, I set that on Display setting. when I press Super + P to turn off whatever monitor and turn it on again ( by choosing join display ) the last monitor used ( not turn off ) will automatically show on the upper - left of another. -- 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/1292398 Title: Second screen position isn't saved from one session to another Status in elementary OS: Fix Released Status in GNOME Settings Daemon: Incomplete Status in GNOME Shell: Confirmed Status in Ubuntu GNOME: Confirmed Status in Ubuntu GNOME trusty series: Confirmed Status in Ubuntu GNOME xenial series: Confirmed Status in Ubuntu GNOME Flashback: Confirmed Status in Unity: New Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: (Noticed on Ubuntu 14.04 beta 1 GNOME) At work I have a second screen, which I prefer to virtually put on the left side of my laptop screen. Using gnome-control-center I can change the position of the second without problem. But when I disconnect the second screen (to work on another place) and then connect it again OR if I just power off the laptop and turn it on again, the second screen position is set back to the default right position. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gnome-control-center 1:3.6.3-0ubuntu53 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 14 08:50:00 2014 InstallationDate: Installed on 2014-03-01 (12 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140226) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_gnome-control-center: deja-dup 29.5-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1292398/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice
Initial testing does make it look like an Xorg session behaves better in this regard than a wayland session (using vanilla gnome sessions in both, fwiw) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Changed in: mutter (Ubuntu) Status: Incomplete => 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1840587] Re: Código de error: ssl_error_no_cypher_overlap
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1840587 Title: Código de error: ssl_error_no_cypher_overlap Status in firefox package in Ubuntu: Expired Bug description: Código de error: ssl_error_no_cypher_overlap - Google translates as: Error Code: ssl_error_no_cypher_overlap - ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: firefox 3.6.3+nobinonly-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-generic i686 Architecture: i386 CrashDB: ubuntu Date: Sun Aug 18 09:47:48 2019 FirefoxPackages: firefox 3.6.3+nobinonly-0ubuntu4 firefox-gnome-support 3.6.3+nobinonly-0ubuntu4 firefox-branding 3.6.3+nobinonly-0ubuntu4 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANG=es_CO.utf8 SHELL=/bin/bash SourcePackage: firefox ThirdParty: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1840587/+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 1827428] Re: Mouse cursor left frozen copy of itself
I am experiencing this after upgrading to 19.10 and enabling fractional scaling on wayland. The extra cursor appears at 125%/150% scaling and disappears at 100% scaling. -- 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/1827428 Title: Mouse cursor left frozen copy of itself Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: Mouse cursor left freezed copy of itself over all the windows after login after lock screen. Functionality is not broken. It's just not aesthetic. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 2 16:10:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8392] NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8392] InstallationDate: Installed on 2019-04-29 (2 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 04f2:b593 Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 17-an0xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=08661a81-0386-4b44-9d3e-17ad6fa2de96 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8392 dmi.board.vendor: HP dmi.board.version: 40.21 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.05:bd06/21/2017:svnHP:pnOMENbyHPLaptop17-an0xx:pvr:rvnHP:rn8392:rvr40.21:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 17-an0xx dmi.product.sku: 2FP35EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428/+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 184510] A change has been merged
Reviewed: https://reviews.mahara.org/10480 Committed: https://git.mahara.org/mahara/mahara/commit/045b1bea7beadcf7053b9f24adbf2749e57ed5e1 Submitter: Cecilia Vela Gurovic (cecili...@catalyst.net.nz) Branch:19.10_STABLE commit 045b1bea7beadcf7053b9f24adbf2749e57ed5e1 Author: Evonne Date: Wed Oct 23 15:46:30 2019 +1300 Bug 184510 Small raw theme changes - getting consistency with list-group - random responsive alignments behatnotneeded Change-Id: Ib95dd215c6a524d8075550779f8c12323279aaa1 (cherry picked from commit 4e60a70f5036a119a08374d82f192f17e10d8563) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 Status in onboard package in Ubuntu: Fix Released Bug description: Binary package hint: onboard hardy upgrade from wubi 7.04 install ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Jan 19 22:35:51 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/share/onboard/run-onboard.py InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: nvidia Package: onboard 0.87 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/onboard/run-onboard.py ProcCwd: /home/wx3200 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: onboard StacktraceTop: ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () Title: run-onboard.py crashed with SIGSEGV Uname: Linux ubuntu 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+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 184510] A patch has been submitted for review
Patch for "19.10_STABLE" branch: https://reviews.mahara.org/10480 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 Status in onboard package in Ubuntu: Fix Released Bug description: Binary package hint: onboard hardy upgrade from wubi 7.04 install ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Jan 19 22:35:51 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/share/onboard/run-onboard.py InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: nvidia Package: onboard 0.87 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/onboard/run-onboard.py ProcCwd: /home/wx3200 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: onboard StacktraceTop: ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () Title: run-onboard.py crashed with SIGSEGV Uname: Linux ubuntu 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+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 184510] A change has been merged
Reviewed: https://reviews.mahara.org/10467 Committed: https://git.mahara.org/mahara/mahara/commit/4e60a70f5036a119a08374d82f192f17e10d8563 Submitter: Robert Lyon (robe...@catalyst.net.nz) Branch:master commit 4e60a70f5036a119a08374d82f192f17e10d8563 Author: Evonne Date: Wed Oct 23 15:46:30 2019 +1300 Bug 184510 Small raw theme changes - getting consistency with list-group - random responsive alignments behatnotneeded Change-Id: Ib95dd215c6a524d8075550779f8c12323279aaa1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 Status in onboard package in Ubuntu: Fix Released Bug description: Binary package hint: onboard hardy upgrade from wubi 7.04 install ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Jan 19 22:35:51 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/share/onboard/run-onboard.py InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: nvidia Package: onboard 0.87 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/onboard/run-onboard.py ProcCwd: /home/wx3200 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: onboard StacktraceTop: ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () Title: run-onboard.py crashed with SIGSEGV Uname: Linux ubuntu 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+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 1844775] Re: HDR support for Ubuntu
For #15, Sorry for causing you confusion, just put related HDR patch of Gemini Lake for your reference. The patch for GLK were in i915 upstream. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc4=44b42ebfccfd9d6ef377a25e99ae0085b071e868 Gary -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844775 Title: HDR support for Ubuntu Status in ffmpeg package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in weston package in Ubuntu: Confirmed Bug description: This is a tracker bug for getting HDR support integrated in Ubuntu. Kernel i915: - 5.3 (Ice Lake) - plus at least https://patchwork.freedesktop.org/series/65656/ - gen4+ needs https://patchwork.freedesktop.org/series/63373/ - so anything beyond initial Ice Lake support will not be in 5.4 Mesa - needs current git master plus https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942 Mutter: https://gitlab.gnome.org/GNOME/mutter/merge_requests/804 Weston: https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 184510] A patch has been submitted for review
Patch for "master" branch: https://reviews.mahara.org/10467 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/184510 Title: Bug 81910 Status in onboard package in Ubuntu: Fix Released Bug description: Binary package hint: onboard hardy upgrade from wubi 7.04 install ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Sat Jan 19 22:35:51 2008 DistroRelease: Ubuntu 8.04 ExecutablePath: /usr/share/onboard/run-onboard.py InterpreterPath: /usr/bin/python2.5 NonfreeKernelModules: nvidia Package: onboard 0.87 PackageArchitecture: all ProcCmdline: /usr/bin/python /usr/share/onboard/run-onboard.py ProcCwd: /home/wx3200 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: onboard StacktraceTop: ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () from /usr/lib/python2.5/site-packages/virtkey.so ?? () ?? () Title: run-onboard.py crashed with SIGSEGV Uname: Linux ubuntu 2.6.24-3-generic #1 SMP Thu Jan 3 23:30:29 UTC 2008 i686 GNU/Linux UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/184510/+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 1846148] Re: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019
@hui.wang, Thanks a lot for the reply. 1) sudo hdajacksensetest -a Pin 0x12 (Internal Mic): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Not connected): present = Yes Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Left side): present = No 2) plug in 3) sudo hdajacksensetest -a Pin 0x12 (Internal Mic): present = No Pin 0x13 (Not connected): present = No Pin 0x14 (Internal Speaker): present = No Pin 0x18 (Not connected): present = No Pin 0x19 (Not connected): present = Yes Pin 0x1a (Not connected): present = No Pin 0x1b (Not connected): present = No Pin 0x1d (Not connected): present = No Pin 0x1e (Not connected): present = No Pin 0x21 (Black Headphone, Left side): present = Yes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846148 Title: Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound works okay but the internal mic doesn't work. When I plug in headset, the mic on headset also doens't work. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lilian 1689 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 12:27:10 2019 InstallationDate: Installed on 2019-09-21 (9 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: TIMI dmi.bios.version: RMRCM400P0100 dmi.board.name: TM1901 dmi.board.vendor: TIMI dmi.chassis.type: 10 dmi.chassis.vendor: TIMI dmi.modalias: dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr: dmi.product.family: Mi Laptop dmi.product.name: RedmiBook 14 dmi.product.sku: TM1901-24822 dmi.sys.vendor: TIMI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+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 1849405] Re: Repeated keypresses from bluetooth keyboard
Please try: * Logging into 'Ubuntu' instead of 'Ubuntu on Wayland'. That will mean key events are first handled by the 'Xorg' process and won't get delayed or lost by high CPU in the 'gnome-shell' process. * Moving away from wifi devices that might be using 2.4GHz frequencies, as they will interfere with Bluetooth and cause packet loss, and some resends. I don't know how unique the resends of lost packets are for Bluetooth keyboards... ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1849405 Title: Repeated keypresses from bluetooth keyboard Status in bluez package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g. around every 10-15mins) end up with repeated keypresses being made (e.g. apppt get update). This seems to happen when the machine is under slight stress, or when a new notification pops up in gnome, so it could be related to wayland possibly - but even if wayland or other processes are causing stress, I should imagine the bluetooth hid driver should not cause repeated key presses. Please let me know if you require further information about my environment, it's difficult to know where to begin with determining which process is the root cause of this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.2 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Wed Oct 23 09:38:20 2019 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Latitude 7480 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.1 dmi.board.name: 00F6D3 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.product.sku: 07A0 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:63:3F:E9:51:8C ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0 TX bytes:605292 acl:98 sco:0 commands:2484 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1849405/+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 1848086] Re: Keyboard shortcuts to launch apps sometimes launch twice
Can you please try logging into "Ubuntu" instead of "Ubuntu on Wayland"? The former will give you a Xorg session so that keyboard events are primarily handled in a different process to gnome-shell. It might help... ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1848086 Title: Keyboard shortcuts to launch apps sometimes launch twice Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Noticed that recently (past few days? since 3.34.1?) the key combinations that I have set to launch web browser or launch terminal end up launching two browsers or terminals instead of just one. Only happens ~50% of the time, but still pretty frequently. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.1-1ubuntu1 Uname: Linux 5.3.0-custom x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Oct 14 12:56:44 2019 InstallationDate: Installed on 2019-08-17 (58 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848086/+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 1849324] Re: Xorg logs spammed with failed page flip messages
** Tags added: amdgpu eoan ** Summary changed: - Xorg logs spammed with failed page flip messages + [amdgpu] Xorg logs spammed with failed page flip messages ** Also affects: xorg-server via https://bugs.freedesktop.org/show_bug.cgi?id=110417 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1849324 Title: [amdgpu] Xorg logs spammed with failed page flip messages Status in X.Org X server: Unknown Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1849324/+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 1848009] Re: Delay launching application launcher gets longer the more apps are open
I assume it's fixed-upstream if Marco says fixed-in-3.34.2 :) ** Tags added: fixed-upstream -- 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/1848009 Title: Delay launching application launcher gets longer the more apps are open Status in gnome-shell package in Ubuntu: In Progress Bug description: On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+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
We have configured PulseAudio in Ubuntu to prefer newly plugged in audio devices, which up until 19.04 was uncontroversial. The bug here is that the new version of PulseAudio thinks logging in with an HDMI/DisplayPort monitor already attached counts as newly plugged-in. If you need a workaround then see comment #3. Upstream is working on it so please keep an eye on: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749 -- 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 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 1844775] Re: HDR support for Ubuntu
That certainly looks HDR related. But if Ubuntu is to be able to use HDR then gnome-shell/mutter first should enable use of a deep colour framebuffer. Actually, for me, that's the only part I care about :) Can anyone confirm what the minimum Intel GPU required is for 10-bpc? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1844775 Title: HDR support for Ubuntu Status in ffmpeg package in Ubuntu: Fix Released Status in intel-media-driver package in Ubuntu: Fix Released Status in libva package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Status in weston package in Ubuntu: Confirmed Bug description: This is a tracker bug for getting HDR support integrated in Ubuntu. Kernel i915: - 5.3 (Ice Lake) - plus at least https://patchwork.freedesktop.org/series/65656/ - gen4+ needs https://patchwork.freedesktop.org/series/63373/ - so anything beyond initial Ice Lake support will not be in 5.4 Mesa - needs current git master plus https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942 Mutter: https://gitlab.gnome.org/GNOME/mutter/merge_requests/804 Weston: https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ffmpeg/+bug/1844775/+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 1842880] Re: Numlock state inverted: active at login, disabled on session
** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Fix Released -- 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/1842880 Title: Numlock state inverted: active at login, disabled on session Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: Hi, running Ubuntu 19.10 development version, I have a problem since a few days: Numlock behaviour is inverted. It is active and already enabled on the login screen, without the need to press the "Verr Num" Key to type numbers for the password. But just after the connexion and session start, it is inactive - I have to press the Key to make it available again. Normally it's the contrary! NumLock is disabled on login screen, and if activated at this moment, it remains active on the session... In Dconf editor, numlock-state is well 'on' and remember-numlock-state 'true'. Thanks in advance for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-06-16 (445 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) Package: gnome-settings-daemon 3.33.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Tags: eoan wayland-session Uname: Linux 5.2.0-15-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-06-10 (86 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-settings-daemon/+bug/1842880/+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 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
Hello, one of the potentially related upstream bug reports was closed (gnome#1607). I've grabbed the fix and built mutter with it at https://launchpad.net/~kisak/+archive/ubuntu/lp-1848852/ , but I don't have an Ubuntu 19.10 test box deployed yet. Can someone try it out and report back if it has an effect for this bug report? Note: Launchpad thinks it's older than the distro package so there might need some extra manipulation to try. -- 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/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: After upgrade to ubuntu 19.10, when I launch counter strike global offensive from steam the game is frozen. I can alt-tab and close the game. Tried in fluxbox window manager where the game works, changed fullscreen to windowed fullscreen in the options and tried on gnome again, now the desktop isn't responding after launching the game and I had to ctrl-alt-f3 to reboot my machine. Using a Radeon RX 580 video card. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+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 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell
Could this be somewhat related to https://gitlab.gnome.org/GNOME/gnome- shell/issues/1788 ? ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1788 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1788 -- 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/1848852 Title: Counter-Strike Global Offensive freezes in gnome-shell Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Bug description: After upgrade to ubuntu 19.10, when I launch counter strike global offensive from steam the game is frozen. I can alt-tab and close the game. Tried in fluxbox window manager where the game works, changed fullscreen to windowed fullscreen in the options and tried on gnome again, now the desktop isn't responding after launching the game and I had to ctrl-alt-f3 to reboot my machine. Using a Radeon RX 580 video card. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848852/+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 1849135] Re: Clicking Activities in the corner doesn't work in Xorg sessions
** Changed in: gnome-shell Status: Unknown => New -- 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/1849135 Title: Clicking Activities in the corner doesn't work in Xorg sessions Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭
Hi Steve, I can't reproduce it here (with a Swedish keyboard). Some questions to start with: * Which values do the environment variables have? env | grep -E 'XMOD|_IM' * Are you possibly on Wayland? * Can you reproduce it on a fresh 19.10 (or with a newly created user)? Assuming that you are on standard Ubuntu, using ibus-setup for adding/removing input sources is not the 'right' way - it's supposed to be done in Settings -> Region & Language (probably not significant for this issue, but still...). GNOME always starts IBus if it's installed (and it's installed by default on Ubuntu). ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 breaks the delete key, maps to ☭ Status in ibus package in Ubuntu: Incomplete Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+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 1848009] Re: Delay launching application launcher gets longer the more apps are open
** Tags added: fixed-in-3.34.2 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1848009 Title: Delay launching application launcher gets longer the more apps are open Status in gnome-shell package in Ubuntu: In Progress Bug description: On latest up to date daily image on my ThinkPad X220 / i7 / 16GB / 150GB SSD. If I launch a bunch of applications - possibly a slightly unreasonable number, but a lot anyway - with minimal CPU or memory in use, the button to launch applications in the bottom left takes progressively longer to run. Video showing it: https://www.youtube.com/watch?v=BRbFk-n9KzQ Steps to reproduce. Open application launcher Note a ~0.6s delay before the icons fly onto the screen Open GNOME Software Install all the editors picks Launch a bunch of applications Click the application launcher Note a 4s delay before icons fly onto the screen. Expectation Honestly, no delay at all, but it should be at least consistent with when no applications are running, so 0.6s delay as per the state when no apps are launched. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 13:02:04 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191012) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1848009/+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 1553669] Re: Annoying "call from" message when connecting Bose devices
This just started happening to me and I realized its after I used my headphones in a conference call. Selecting the headphone input in Sound Settings silently switched the output profile to HSP/HFD mode. The only "bug" here is that when the call ended and I turned off the microphone (selecting a different input device) it didn't restore A2DP output, so you have to do it manually. With that manual selection, "call from" is gone. -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+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 1849399] [NEW] ibus in 19.10 breaks the delete key, maps to ☭
Public bug reported: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". ** Affects: ibus (Ubuntu) Importance: High Status: New ** Changed in: ibus (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1849399 Title: ibus in 19.10 breaks the delete key, maps to ☭ Status in ibus package in Ubuntu: New Bug description: After upgrade to 19.10, I found that my Delete key was not working as a Delete key, but that instead if I hit Delete twice it would print the character ☭. Since others were not reporting this issue, I had a look around at my input config and remembered that I had ibus configured from a long time ago in order to support Chinese input. If I disable ibus (either by unsetting the environment variables; or by killing ibus-daemon), then the Delete key works again as expected. This is a regression in behavior since Ubuntu 19.04, where I had the same input setup on my desktop but the Delete key worked without problems. I'm also not sure how to disable ibus, now that I am in this situation; or if ibus is expected to always be running. The problem persists if I run ibus-setup and remove Chinese SunPinyin from the list of input methods, leaving only "English - English (US)". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1849399/+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 1848731] Re: Audio output device changes upon unlock/login
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1848731 Title: Audio output device changes upon unlock/login Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04. Locking/Suspending and logging in changes my audio output device. This did not happen in 19.04. How to reproduce When I lock my session with key combination "Win+L" and then unlock it again, the sound that's been playing through my headphones/speakers stops playing. When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is selected. When I select "Headphones - Built-in audio", sound continues playing. There is no related log output in dmesg. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848731/+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 1849157] Re: Default sound output device is never the expected one
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1849157 Title: Default sound output device is never the expected one Status in gnome-shell package in Ubuntu: Confirmed Bug description: According to this page: https://wiki.ubuntu.com/Sound#Primary_sound_output, "if you manually choose an output device in the “Sound” settings panel or a similar utility, that choice should be followed". Well, despite me having explicitly selected the headset as the output device, on every reboot it falls back to the HDMI device. The headset is always plugged in. I believe this is a regression. On Ubuntu 19.04 and previous versions, it respected my preferences about the sound device. It is reproducible on both Xorg and Wayland sessions. Specs: OS: Ubuntu 19.10 Eoan (GNOME, Ubuntu sessions) Motherboard: Gigabyte B360M GAMING HD CPU: Intel Core i3-8100 Graphics: AMD RX 560 (AMDGPU, open source) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 12:49:52 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-10-21 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1849157/+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 have 2 4K monitors, that do not even have speakers hooked up to them (but they apparently have Audio Controllers). Ubuntu 19.10 gnome- control-center chooses one of these speakerless monitors over my Laptop's built-in speakers on each reboot. It will not persist my preference. Screenshot: https://i.stack.imgur.com/kLYWy.png AskUbuntu: https://askubuntu.com/questions/1183052/ -- 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 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 1849162] Re: Lightning extension should be installed and enabled by default
Having it installed by default but disabled and an opt-in does makes sense indeed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1849162 Title: Lightning extension should be installed and enabled by default Status in thunderbird package in Ubuntu: Triaged Bug description: Upstream builds of thunderbird are now shipping lightning, and it is enabled by default. In contrast, lightning in Ubuntu is a separate binary package (xul- ext-lightning), and it’s neither installed by default nor even recommended by thunderbird. This results in confusion for users who don't know where to get lightning from. The extension should be bundled with the thunderbird package, i.e. installed and enabled by default (as was done for the wetransfer file link provider, see bug #1823361). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849162/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-session (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I'm also experiencing this bug with Nvidia GTX 1080 using the proprietary driver version 435.21. Issue persists with other driver versions as well. Currently using the same temporary fix as dehein mentioned, turning the automatic login off manually through editing the GDM config file. When fixing the issue this way via TTY I'm also seeing graphical corruption artifacts from the stuck Gnome session desktop that I cannot enter. When switching to the open source Nouveau drivers I can leave automatic login on without any issues, everything works fine. So in my case this issue seems to be tied to the Nvidia drivers. Also tried to search more online about this issue and most mentions seem to be from Nvidia users. I don't really have anything new to add as everything I thought of has already been reported here, but let me know if I can help in any way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati:
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu Eoan) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in gnome-shell source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1849273] Re: network connection fails to re-establish on resume from suspend
the log has 'wlan0: authentication with ... timed out' warnings, looks like rather a kernel/driver/wpasupplicant issue ** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1849273 Title: network connection fails to re-establish on resume from suspend Status in linux package in Ubuntu: New Bug description: The network connection doesn't reestablish on resume from suspend and the laptop has to be restarted. Restarting networking or network-manager doesn't make it reconnect either. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 09:28:30 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-03 (2239 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2018-01-26 (633 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connecting started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849273/+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 1849183] Re: Bluetooth devices doesn't get listed while turn off and then on
The log has those warnings 'Bluetooth: hci0: unexpected event for opcode 0x2005' It's more likely to be a kernel issue ** No longer affects: gnome-bluetooth (Ubuntu) ** No longer affects: gnome-control-center (Ubuntu) ** Package changed: bluez (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1849183 Title: Bluetooth devices doesn't get listed while turn off and then on Status in linux package in Ubuntu: New Bug description: When System Starts, first time Bluetooth devices(Say headphones) get connected smoothly. But after a point when headphones get disconnected, If I tried to reconnect Bluetooth settings don't list the devices. I turned it on/off multiple times but doesn't work. The only way that'd work after a system restart. Please can you check into this ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: raghuvar 1999 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 21 23:39:04 2019 InstallationDate: Installed on 2019-06-30 (113 days ago) InstallationMedia: PackageArchitecture: all ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 80XL dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849183/+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 1849367] Re: Kde battery indicator remaining time stucked
** Package changed: gnome-power-manager (Ubuntu) => kdelibs (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1849367 Title: Kde battery indicator remaining time stucked Status in kdelibs package in Ubuntu: New Bug description: I have the latest kubuntu 19.10 with kde 5.16.5. When I look the battery icon it show me the same reamining time no matter what is the percentage of energy remaining in the battery. I monitor dbus with this command "dbus-monitor --system sender=org.freedesktop.UPower" And I get this: dbus-monitor --system sender=org.freedesktop.UPower dbus-monitor: unable to enable new-style monitoring: org.freedesktop.DBus.Error.AccessDenied: "Rejected send message, 1 matched rules; type="method_call", sender=":1.1599" (uid=1000 pid=12348 comm="dbus-monitor --system sender=org.freedesktop.UPowe" label="unconfined") interface="org.freedesktop.DBus.Monitoring" member="BecomeMonitor" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)". Falling back to eavesdropping. signal time=1571765384.592371 sender=org.freedesktop.DBus -> destination=:1.1599 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.1599" signal time=1571765393.680203 sender=:1.681 -> destination=(null destination) serial=265 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.freedesktop.UPower.Device" array [ dict entry( string "UpdateTime" variant uint64 1571765393 ) dict entry( string "TimeToEmpty" variant int64 30127 ) dict entry( string "Voltage" variant double 8.056 ) dict entry( string "Percentage" variant double 74 ) dict entry( string "EnergyRate" variant double 5.358 ) dict entry( string "Energy" variant double 44.84 ) ] array [ ] signal time=1571765393.680667 sender=:1.681 -> destination=(null destination) serial=266 path=/org/freedesktop/UPower/devices/DisplayDevice; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.freedesktop.UPower.Device" array [ dict entry( string "UpdateTime" variant uint64 1571765393 ) dict entry( string "Percentage" variant double 74 ) dict entry( string "TimeToEmpty" variant int64 30127 ) dict entry( string "EnergyRate" variant double 5.358 ) dict entry( string "Energy" variant double 44.84 ) ] array [ ] So it seems that is receiving the good values but the battery indicator in the systray is not working at all. The only good value it gets is the total percentage of the battery. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdelibs/+bug/1849367/+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 1849119] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exi
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
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/1849119
Title:
package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 10
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Showing system error
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
AptOrdering:
chromium-browser:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Mon Oct 21 18:05:24 2019
ErrorMessage: new chromium-browser package pre-installation script subprocess
returned error exit status 10
InstallationDate: Installed on 2019-10-21 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu2
apt 1.9.4
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: new chromium-browser package pre-installation script
subprocess returned error exit status 10
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849119/+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 1844329] Re: Test bug for update-excuse-bionic
** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- 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/1844329 Title: Test bug for update-excuse-bionic Status in pulseaudio package in Ubuntu: Invalid Bug description: Feel free to close it tomorrow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1844329/+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 1849391] Re: Can't Persist Sound Output Selection Between Reboots
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 ** This bug has been marked a duplicate of bug 1847570 PulseAudio automatically switches to HDMI sound output on login -- 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/1849391 Title: Can't Persist Sound Output Selection Between Reboots Status in gnome-control-center package in Ubuntu: New Bug description: Each time I reboot Ubuntu 19.10, I have to open gnome-control-center and set the sound output device back to my Laptop's Built-in speakers. Otherwise, it will typically default to HDMI devices that don't even appear to have speakers. Which file are these settings saved to? I'm thinking that maybe that file is corrupted and that if I delete that file maybe Ubuntu 19.10 will start remembering my sound output preferences. I'm also open to other suggestions. Also submitted at AskUbuntu: https://askubuntu.com/questions/1183052/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:39:58 2019 InstallationDate: Installed on 2019-10-19 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1849391/+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 1849391] [NEW] Can't Persist Sound Output Selection Between Reboots
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Public bug reported: Each time I reboot Ubuntu 19.10, I have to open gnome-control-center and set the sound output device back to my Laptop's Built-in speakers. Otherwise, it will typically default to HDMI devices that don't even appear to have speakers. Which file are these settings saved to? I'm thinking that maybe that file is corrupted and that if I delete that file maybe Ubuntu 19.10 will start remembering my sound output preferences. I'm also open to other suggestions. Also submitted at AskUbuntu: https://askubuntu.com/questions/1183052/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:39:58 2019 InstallationDate: Installed on 2019-10-19 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Description changed: Each time I reboot Ubuntu 19.10, I have to open gnome-control-center and set the sound output device back to my Laptop's Built-in speakers. Otherwise, it will typically default to HDMI devices that don't even appear to have speakers. - Which file are these settings saved to? I'm think that maybe that file - is corrupted and that if I delete that file maybe Ubuntu 19.10 will + Which file are these settings saved to? I'm thinking that maybe that + file is corrupted and that if I delete that file maybe Ubuntu 19.10 will start remembering my sound output preferences. I'm also open to other suggestions. Also submitted at AskUbuntu: https://askubuntu.com/questions/1183052/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:39:58 2019 InstallationDate: Installed on 2019-10-19 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash 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/1849391 Title: Can't Persist Sound Output Selection Between Reboots Status in gnome-control-center package in Ubuntu: New Bug description: Each time I reboot Ubuntu 19.10, I have to open gnome-control-center and set the sound output device back to my Laptop's Built-in speakers. Otherwise, it will typically default to HDMI devices that don't even appear to have speakers. Which file are these settings saved to? I'm thinking that maybe that file is corrupted and that if I delete that file maybe Ubuntu 19.10 will start remembering my sound output preferences. I'm also open to other suggestions. Also submitted at AskUbuntu: https://askubuntu.com/questions/1183052/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 22 16:39:58 2019 InstallationDate: Installed on 2019-10-19 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1849391/+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 1848309] Re: "Automatic Date & Time" doesn't reflect the service status
It's a valid choice to want to replace the default time syncing by using ntpd, the issue there is that the graphical settings don't communicate much about what is happening ** Summary changed: - "Automatic Date & Time" is broken + "Automatic Date & Time" doesn't reflect the service status ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- 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/1848309 Title: "Automatic Date & Time" doesn't reflect the service status Status in gnome-control-center package in Ubuntu: Confirmed Bug description: In my always up-to-date Eoan the "Automatic Date & Time" adjustment is broken since around two months. 0 * * * * sudo ntpdate 0.ubuntu.pool.ntp.org >> /tmp/ntpsync ...is my crontab workaround to get proper time on Ubuntu Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+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 1846940]
*** Bug 128326 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1846940 Title: [upstream] Loop in libreoffice-calc when scrolling to top of spreadsheet Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Have a spreadsheet used in many past release of calc that is now failing. When opening this sheet and if not currently at the top of the sheet using the mouse wheel to move to the top (top line to the top of the window) soffice.bin goes to 100% cpu and stays there. Can't use the mouse wheel to move off of the top line. Can move off the top line by using the mouse and scroll bar. As soon as you are off the top line the loop in soffice.bin stops. This is the only sheet I can find that fails but it does fail on this laptop and also my desktop which is also running Ubuntu 19.10/libreoffice- calc-6.3.2.2. Adding failing spreadsheet file to this bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-calc 1:6.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 06:35:42 2019 InstallationDate: Installed on 2019-10-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+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 1846940]
(In reply to Julian Ragan from comment #28) > I have narrowed it down to the following: > If a form has more than one control and in the underlying sheet column width > in any one column is set to different than default, then all controls on the > form start (not always immediately) to refresh (redraw) in a continuous loop > affecting overall performance. > > Steps to reproduce the bug: > 1.Create new sheet > 2.Add two controls to the form > 3.Resize a few columns on the sheet > > If all columns have default width this bug will not manifest itself. > If there is one control on the form, this bug will not manifest itself. > > Reproducibility is a bit sketchy, since sometimes it starts to continuously > refresh immediately and sometimes it takes a few seconds to catch on. I have CALC workbook with only 1 control. It flickers so issue does occur with just 1 control -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1846940 Title: [upstream] Loop in libreoffice-calc when scrolling to top of spreadsheet Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Have a spreadsheet used in many past release of calc that is now failing. When opening this sheet and if not currently at the top of the sheet using the mouse wheel to move to the top (top line to the top of the window) soffice.bin goes to 100% cpu and stays there. Can't use the mouse wheel to move off of the top line. Can move off the top line by using the mouse and scroll bar. As soon as you are off the top line the loop in soffice.bin stops. This is the only sheet I can find that fails but it does fail on this laptop and also my desktop which is also running Ubuntu 19.10/libreoffice- calc-6.3.2.2. Adding failing spreadsheet file to this bug report. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libreoffice-calc 1:6.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 6 06:35:42 2019 InstallationDate: Installed on 2019-10-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191001.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1846940/+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 1848119] Re: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695]
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Won't Fix ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium -- 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/1848119 Title: gnome-shell infinite error loop when closing app in activities overview: Object St.Button (0x55aeadeca4a0), has been already deallocated ... [workspace.js:695] Status in GNOME Shell: Fix Released Status in gnome-shell package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-shell package in Fedora: Confirmed Bug description: Ubuntu 19.10 on Xorg gnome-shell 3.34.1-1ubuntu1 How to reproduce: 1) Open terminal and watch journalct -f 2) Open Files 3) Close Files in the activities overview 4) gnome-shell errors in journal non stop. Oct 14 23:25:38 titan gnome-shell[9919]: Object St.Button (0x55aeadeca4a0), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Oct 14 23:25:38 titan gnome-shell[9919]: == Stack trace for context 0x55aead0b5360 == Oct 14 23:25:38 titan gnome-shell[9919]: #0 55aeae6f3910 i resource:///org/gnome/shell/ui/workspace.js:695 (7f438c072c10 @ 15) Oct 14 23:25:38 titan gnome-shell[9919]: #1 7ffd96c5e360 b self-hosted:975 (7f438c12dee0 @ 392) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1848119/+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 1848958] Re: Suspend takes 3 minutes and screen is garbled after resume with nouveau driver after upgrade to 19.10
** Also affects: nouveau Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-nouveau in Ubuntu. https://bugs.launchpad.net/bugs/1848958 Title: Suspend takes 3 minutes and screen is garbled after resume with nouveau driver after upgrade to 19.10 Status in Nouveau Xorg driver: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: In Kubuntu 19.04 (kernel 5.0) suspend and resume was almost working on my machine, say 9 of 10 times it went well. The problematic suspends were mostly when there way an OpenGL app running. I was able to lived with that, the machine was able to achieve 30+days uptime. After upgrading to 19.10 the machine now behaves weird: 1. Suspend takes 3 minutes to complete. The screen blanks relatively fast as before, but the machine is up and running for another 3 minutes before finally entering sleep. 2. Resume is normal as before and does its job, however: - the screen is completely garbled. It looks like the video RAM content was lost. - the GPU seems to operate normally, the cursor is drawn correctly (see attached photo). 3. Restarting the X-server resolves the issue, i.e. the screen contains reasonable content 4. Text console is working correctly even without restarting the X-server 5. Tried running KDE with and without compositor, got the same results. I'd like to help fixing this or at least provide technical info that will lead to fixing this issue, please tell me what shall I try/test. Thank you. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xserver-xorg-video-nouveau 1:1.0.16-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Oct 20 23:18:53 2019 DistUpgraded: 2019-10-19 10:33:23,032 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation G94M [GeForce 9800M GS] [10de:062b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] G94M [GeForce 9800M GS] [1462:7220] InstallationDate: Installed on 2019-04-21 (182 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Micro-Star International GT627 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic root=UUID=bec74662-d895-4581-a6ea-6f92fea32635 ro resume=/dev/sda6 iommu=soft SourcePackage: xserver-xorg-video-nouveau UpgradeStatus: Upgraded to eoan on 2019-10-19 (1 days ago) dmi.bios.date: 04/07/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A1651IMS.10V dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-1651 dmi.board.vendor: MSI dmi.board.version: Ver 1.000 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA1651IMS.10V:bd04/07/2009:svnMicro-StarInternational:pnGT627:pvrVer1.000:rvnMSI:rnMS-1651:rvrVer1.000:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: GT627 dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: Ver 1.000 dmi.sys.vendor: Micro-Star International version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1848958/+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 1710931] Re: Ctrl+N shortcut does not work when desktop has focus
Status is "expired", but this is still here in late 2019 on Ubuntu 18.04.3 LTS. A behavioral work-around for me is to use Super+# to open the (pinned) Nautilus from the dock ... then use Ctrl+l to get to wherever I *really* want to go. But it's definitely a bug: as Marc Nijdam said, it's obviously due to some invalid `x-nautilus-desktop:///` argument which is passed to the Nautilus invocation. I don't know where in the labyrinth of Ubuntu/Nautilus/Debian/Gnome repositories this argument arises, but it would seem that a simple fix, valid for most users, would be simply to hard-code `$USER/Desktop\` instead. This would at least be better than the current state of affairs, which works for no one. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1710931 Title: Ctrl+N shortcut does not work when desktop has focus Status in Nautilus: Expired Status in nautilus package in Ubuntu: Triaged Bug description: When a Nautilus window is open, Ctrl+N opens a new window that shows the same folder as the focused Nautilus window. However, when the desktop is focused, the shortcut doesn't work - instead I see an error that x-nautilus-desktop:// is not supported. This functionality was previously reported as working in #307229. This is on Ubuntu 17.10 Artful Aardvark (fully patched as of today) with GNOME Files 3.24.2.1. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1710931/+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 1849371] Re: [snap] Cannot run headless chromium as user www-data
Thanks for the suggestion, and you're right, your summary is better. I tried the following (with various permutations). sudo su -l -s /bin/bash www-data mkdir /tmp/chromium-home HOME=/tmp/chromium-home /usr/bin/timeout 60 chromium-browser --no- sandbox --headless --disable-gpu --window-size=2048,1448 --screenshot='/tmp/dummy.pdf' --user-data-dir=/tmp/chromium-home 'http://localhost/...' and this complains in a different way: Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. Before the snap change was made, chromium would run headless without (I think) actually needing any writeable directory at all. -- 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/1849371 Title: [snap] Cannot run headless chromium as user www-data Status in chromium-browser package in Ubuntu: New Bug description: Since the move to snap, and upgrade to 19.10, I can no longer use headless-chromium to do automated conversions. The script, as currently run by Apache (user www-data) as a back-end server process is: /usr/bin/timeout 60 chromium-browser --no-sandbox --headless --disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf' 'http://localhost/[...]' 2>&1 2>&1 This returns error 1, with: dconf-CRITICAL **: 19:41:17.958: unable to create directory '/var/www/.cache/dconf': Permission denied. dconf will not work properly. WARNING: cannot create user data directory: cannot create "/var/www/snap/chromium/899": mkdir /var/www/snap: permission denied Sorry, home directories outside of /home are not currently supported. See https://forum.snapcraft.io/t/11209 for details. So... how are we supposed to use scripted Chrome for headless work, when the snaps don't support it? This is a major blocker for me, as it completely destroys my ability to do any development work, because the build-toolchain for selftests relies on the ability of chrome to operate headless. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: MATE DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g== modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480 720x480 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-2: enabled: enabled dpms: On status: connected edid-base64: AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU= modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-3: enabled: enabled dpms: On status: connected edid-base64: AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8= modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 640x480 720x400 Date: Tue Oct 22 19:48:51 2019 DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/sdb1 ext4 1.8T 491G 1.3T 29% /home tmpfs tmpfs 32G 927M 31G 3% /dev/shm /dev/sdb1 ext4 1.8T 491G 1.3T 29% /home InstallationDate: Installed on 2017-02-03 (991 days ago) InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro Snap.ChromeDriverVersion: ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded (failed to map segment from shared object): ignored. ChromeDriver 77.0.3865.120
[Desktop-packages] [Bug 1846882] Re: Thunderbird crashes when clicking on enigmail menu item while composing a message in a Unity session
I'm attaching a backtrace obtained by running `thunderbird -g` with
debug symbols installed.
** Attachment added: "backtrace.txt"
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1846882/+attachment/5299275/+files/backtrace.txt
** Changed in: thunderbird (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: thunderbird (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1846882
Title:
Thunderbird crashes when clicking on enigmail menu item while
composing a message in a Unity session
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Thunderbird 1:68.1.1+build1-0ubuntu1 On Ubuntu 19.10 fully updated.
When writing an email, upon clicking on Enigmail in the menu bar,
Thunderbird crashes.
I contacted Enigmail’s lead dev about the issue who wrote:
"…but even if the crash is initiated by Enigmail, the cause is
certainly in Thunderbird. Enigmail is purely JavaScript and XUL - and by
definition of the programming languages, these two cannot crash
Thunderbird."
I tried Thunderbird 68.1.1 from Mozilla’s site, and can’t
reproduce the problem with it.
Here is Thunderbird’s log upon crashing:
AdapterDeviceID: 0x1912
AdapterDriverVendor: mesa/i965
AdapterDriverVersion: 19.3.0.0
AdapterVendorID: 0x8086
Add-ons:
%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D:68.1.1,%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D:2.1.2,antidote7_linux_thunderbird_102%40druide.com:10.1.30,en-CA%40dictionaries.addons.mozilla.org:3.1.0,fr-dicollecte%40dictionaries.addons.mozilla.org:6.3.1webext,wetransfer%40extensions.thunderbird.net:2.0.0,thunderbird-compact-dark%40mozilla.org:1.0,google%40search.mozilla.org:1.0,bing%40search.mozilla.org:1.0,amazon%40search.mozilla.org:1.1,ddg%40search.mozilla.org:1.0,qwant%40search.mozilla.org:1.0,wikipedia%40search.mozilla.org:1.0,twitter%40search.mozilla.org:1.0,langpack-fr%40thunderbird.mozilla.org:68.0,wetransfer%40extensions.thunderbird.net:2.0.0
BuildID: 20191001201558
ContentSandboxCapabilities: 119
ContentSandboxCapable: 1
ContentSandboxLevel: 0
CrashTime: 1570225903
EventLoopNestingLevel: 1
FramePoisonBase: 9223372036600930304
FramePoisonSize: 4096
InstallTime: 1570020285
IsWayland: 0
Notes: Ubuntu Eoan Ermine (development
branch)FP(D00-L1000-W-T000) WR? WR- OMTP? OMTP+3
ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6}
ProductName: Thunderbird
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 383
StartupCrash: 0
StartupTime: 1570225565
ThreadIdNameMapping: 20357:"Gecko_IOThread",20358:"JS
Watchdog",20359:"JS Helper",20360:"JS Helper",20361:"JS
Helper",20362:"JS Helper",20363:"Link Monitor",20364:"Socket
Thread",20372:"Timer",20373:"Cache2
I/O",20375:"DataStorage",20376:"Cookie",20379:"GMPThread",20380:"Worker
Launcher",20381:"SoftwareVsyncThread",20382:"Compositor",20383:"ImgDecoder
#1",20384:"ImageIO",20390:"ImageBridgeChild",20391:"IPDL
Background",20392:"DOM Worker",20394:"HTML5
Parser",20397:"StyleThread#1",20396:"StyleThread#0",20398:"StyleThread#2",20401:"mozStorage
#1",20407:"localStorage DB",20408:"ImgDecoder #2",20410:"Cache
I/O",20411:"DNS Resolver #1",20412:"URL Classifier",20413:"Classifier
Update",20415:"QuotaManager IO",20426:"DNS Resolver #2",20427:"DNS
Resolver #3",20429:"ImgDecoder #3",20439:"mozStorage #3",20452:"DOM
Worker",20467:"mozStorage #5",20468:"mozStorage #6",20469:"mozStorage
#7",20479:"DOM Worker",20500:"mozStorage #8",27048:"StreamTrans #18",
Throttleable: 1
UptimeTS: 337.7284093
Vendor:
Version: 68.1.1
useragent_locale: fr
This is what I get when running Thunderbird from the console and after
the crash occurred:
1570277554871 addons.xpi WARNCan't get modified time of
/usr/lib/thunderbird/features/wetrans...@extensions.thunderbird.net
1570277554912 addons.xpi-utilsWARNupdateMetadata: Add-on
wetrans...@extensions.thunderbird.net is invalid: [Exception... "Component
returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)
[nsIFile.isFile]" nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)"
location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: get ::
line 235" data: no] Stack trace:
get()@resource://gre/modules/addons/XPIInstall.jsm:235
syncLoadManifest()@resource://gre/modules/addons/XPIInstall.jsm:745
updateMetadata()@resource://gre/modules/addons/XPIDatabase.jsm:2821
updateExistingAddon()@resource://gre/modules/addons/XPIDatabase.jsm:3036
processFileChanges()@resource://gre/modules/addons/XPIDatabase.jsm:3125
checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:2946
startup()@resource://gre/modules/addons/XPIProvider.jsm:2406
callProvider()@resource://gre/modules/AddonManager.jsm:213
[Desktop-packages] [Bug 1846882] Re: Thunderbird crashes when clicking on menu item
I had overlooked the fact that you're running a Unity session. I can now
reproduce the crash in a 19.10 VM with Unity.
** Changed in: thunderbird (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- Thunderbird crashes when clicking on menu item
+ Thunderbird crashes when clicking on enigmail menu item while composing a
message in a Unity session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to thunderbird in Ubuntu.
https://bugs.launchpad.net/bugs/1846882
Title:
Thunderbird crashes when clicking on enigmail menu item while
composing a message in a Unity session
Status in thunderbird package in Ubuntu:
Confirmed
Bug description:
Thunderbird 1:68.1.1+build1-0ubuntu1 On Ubuntu 19.10 fully updated.
When writing an email, upon clicking on Enigmail in the menu bar,
Thunderbird crashes.
I contacted Enigmail’s lead dev about the issue who wrote:
"…but even if the crash is initiated by Enigmail, the cause is
certainly in Thunderbird. Enigmail is purely JavaScript and XUL - and by
definition of the programming languages, these two cannot crash
Thunderbird."
I tried Thunderbird 68.1.1 from Mozilla’s site, and can’t
reproduce the problem with it.
Here is Thunderbird’s log upon crashing:
AdapterDeviceID: 0x1912
AdapterDriverVendor: mesa/i965
AdapterDriverVersion: 19.3.0.0
AdapterVendorID: 0x8086
Add-ons:
%7Be2fda1a4-762b-4020-b5ad-a41df1933103%7D:68.1.1,%7B847b3a00-7ab1-11d4-8f02-006008948af5%7D:2.1.2,antidote7_linux_thunderbird_102%40druide.com:10.1.30,en-CA%40dictionaries.addons.mozilla.org:3.1.0,fr-dicollecte%40dictionaries.addons.mozilla.org:6.3.1webext,wetransfer%40extensions.thunderbird.net:2.0.0,thunderbird-compact-dark%40mozilla.org:1.0,google%40search.mozilla.org:1.0,bing%40search.mozilla.org:1.0,amazon%40search.mozilla.org:1.1,ddg%40search.mozilla.org:1.0,qwant%40search.mozilla.org:1.0,wikipedia%40search.mozilla.org:1.0,twitter%40search.mozilla.org:1.0,langpack-fr%40thunderbird.mozilla.org:68.0,wetransfer%40extensions.thunderbird.net:2.0.0
BuildID: 20191001201558
ContentSandboxCapabilities: 119
ContentSandboxCapable: 1
ContentSandboxLevel: 0
CrashTime: 1570225903
EventLoopNestingLevel: 1
FramePoisonBase: 9223372036600930304
FramePoisonSize: 4096
InstallTime: 1570020285
IsWayland: 0
Notes: Ubuntu Eoan Ermine (development
branch)FP(D00-L1000-W-T000) WR? WR- OMTP? OMTP+3
ProductID: {3550f703-e582-4d05-9a08-453d09bdfdc6}
ProductName: Thunderbird
ReleaseChannel: release
SafeMode: 0
SecondsSinceLastCrash: 383
StartupCrash: 0
StartupTime: 1570225565
ThreadIdNameMapping: 20357:"Gecko_IOThread",20358:"JS
Watchdog",20359:"JS Helper",20360:"JS Helper",20361:"JS
Helper",20362:"JS Helper",20363:"Link Monitor",20364:"Socket
Thread",20372:"Timer",20373:"Cache2
I/O",20375:"DataStorage",20376:"Cookie",20379:"GMPThread",20380:"Worker
Launcher",20381:"SoftwareVsyncThread",20382:"Compositor",20383:"ImgDecoder
#1",20384:"ImageIO",20390:"ImageBridgeChild",20391:"IPDL
Background",20392:"DOM Worker",20394:"HTML5
Parser",20397:"StyleThread#1",20396:"StyleThread#0",20398:"StyleThread#2",20401:"mozStorage
#1",20407:"localStorage DB",20408:"ImgDecoder #2",20410:"Cache
I/O",20411:"DNS Resolver #1",20412:"URL Classifier",20413:"Classifier
Update",20415:"QuotaManager IO",20426:"DNS Resolver #2",20427:"DNS
Resolver #3",20429:"ImgDecoder #3",20439:"mozStorage #3",20452:"DOM
Worker",20467:"mozStorage #5",20468:"mozStorage #6",20469:"mozStorage
#7",20479:"DOM Worker",20500:"mozStorage #8",27048:"StreamTrans #18",
Throttleable: 1
UptimeTS: 337.7284093
Vendor:
Version: 68.1.1
useragent_locale: fr
This is what I get when running Thunderbird from the console and after
the crash occurred:
1570277554871 addons.xpi WARNCan't get modified time of
/usr/lib/thunderbird/features/wetrans...@extensions.thunderbird.net
1570277554912 addons.xpi-utilsWARNupdateMetadata: Add-on
wetrans...@extensions.thunderbird.net is invalid: [Exception... "Component
returned failure code: 0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)
[nsIFile.isFile]" nsresult: "0x80520006 (NS_ERROR_FILE_TARGET_DOES_NOT_EXIST)"
location: "JS frame :: resource://gre/modules/addons/XPIInstall.jsm :: get ::
line 235" data: no] Stack trace:
get()@resource://gre/modules/addons/XPIInstall.jsm:235
syncLoadManifest()@resource://gre/modules/addons/XPIInstall.jsm:745
updateMetadata()@resource://gre/modules/addons/XPIDatabase.jsm:2821
updateExistingAddon()@resource://gre/modules/addons/XPIDatabase.jsm:3036
processFileChanges()@resource://gre/modules/addons/XPIDatabase.jsm:3125
checkForChanges()@resource://gre/modules/addons/XPIProvider.jsm:2946
startup()@resource://gre/modules/addons/XPIProvider.jsm:2406
callProvider()@resource://gre/modules/AddonManager.jsm:213
_startProvider()@resource://gre/modules/AddonManager.jsm:649
[Desktop-packages] [Bug 1848309] Re: "Automatic Date & Time" is broken
purging and reinstalling `ntpdate` resolved the problem. IMO opinion the pkg manager should prevent the user from making breaking system integrity by miss-installing certain package. Ok, this might have happend in the eoan dev cycle where I have started to use eoan... but still future updates should have corrected this inconsistency. -- 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/1848309 Title: "Automatic Date & Time" is broken Status in gnome-control-center package in Ubuntu: Incomplete Bug description: In my always up-to-date Eoan the "Automatic Date & Time" adjustment is broken since around two months. 0 * * * * sudo ntpdate 0.ubuntu.pool.ntp.org >> /tmp/ntpsync ...is my crontab workaround to get proper time on Ubuntu Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+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 1849371] Re: headless chromium broken (as a consequence of snap)
Headless chromium as a snap works.
What doesn't work is running it as user www-data, which has $HOME set to
/var/www.
Try exporting HOME to something the snap can write to, or alternatively
run chromium with the --user-data-dir= argument.
Please share the results here. Thanks!
** Summary changed:
- headless chromium broken (as a consequence of snap)
+ Cannot run headless chromium as user www-data
** Summary changed:
- Cannot run headless chromium as user www-data
+ [snap] Cannot run headless chromium as user www-data
--
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/1849371
Title:
[snap] Cannot run headless chromium as user www-data
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since the move to snap, and upgrade to 19.10, I can no longer use
headless-chromium to do automated conversions.
The script, as currently run by Apache (user www-data) as a back-end
server process is:
/usr/bin/timeout 60 chromium-browser --no-sandbox --headless
--disable-gpu --window-size=2048,1448 --screenshot='dummy.pdf'
'http://localhost/[...]' 2>&1 2>&1
This returns error 1, with:
dconf-CRITICAL **: 19:41:17.958: unable to create directory
'/var/www/.cache/dconf': Permission denied. dconf will not work
properly.
WARNING: cannot create user data directory: cannot create
"/var/www/snap/chromium/899":
mkdir /var/www/snap: permission denied
Sorry, home directories outside of /home are not currently supported.
See https://forum.snapcraft.io/t/11209 for details.
So... how are we supposed to use scripted Chrome for headless work, when the
snaps don't support it?
This is a major blocker for me, as it completely destroys my ability to do
any development work, because the build-toolchain for selftests relies on the
ability of chrome to operate headless.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480
720x480 640x480 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-2:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480
640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480
640x480 640x480 640x480 720x400
Date: Tue Oct 22 19:48:51 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 ext4 1.8T 491G 1.3T 29% /home
tmpfs tmpfs 32G 927M 31G 3% /dev/shm
/dev/sdb1 ext4 1.8T 491G 1.3T 29% /home
InstallationDate: Installed on 2017-02-03 (991 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro
Snap.ChromeDriverVersion:
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be
preloaded (failed to map segment from shared object): ignored.
ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion:
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be
[Desktop-packages] [Bug 1806269] Re: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed
@Sebastian Oops! I usually add ~tj or ~lpXX but lost that change this time because whilst fighting with trying to combine the upstream, Debian, and Ubuntu git repos and use sbuild to test. It failed in all sorts of confusing ways so I simply made a non-git copy and ran 'dch -i' immediately without thinking. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1806269 Title: nm-connection-editor crashes when trying to modify connection without gnome-keyring installed Status in Network Manager Applet: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Bug description: * Impact the connection editor segfault when using without gnome-keyring * Test case uninstall gnome-keyring and try to edit a connection, it shouldn't segfault * Regression potential the fix changes an error handling case, it shouldn't impact normal use Thread 1 "nm-connection-e" received signal SIGSEGV, Segmentation fault. 0x77ba6b53 in modules_initialized (object=, res=0x56048a40, user_data=) at src/libnma/nma-cert-chooser-button.c:98 98 src/libnma/nma-cert-chooser-button.c: No such file or directory. This occurs when the package "gnome-keyring" is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-applet/+bug/1806269/+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 1842880] Re: Numlock state inverted: active at login, disabled on session
Hi, yes this bug seems resolved since a few days and 19.10 release : NumLock is still enabled on the login screen (which is fine), and this time well remains active after connexion, so no more problem for me ! -- 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/1842880 Title: Numlock state inverted: active at login, disabled on session Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Hi, running Ubuntu 19.10 development version, I have a problem since a few days: Numlock behaviour is inverted. It is active and already enabled on the login screen, without the need to press the "Verr Num" Key to type numbers for the password. But just after the connexion and session start, it is inactive - I have to press the Key to make it available again. Normally it's the contrary! NumLock is disabled on login screen, and if activated at this moment, it remains active on the session... In Dconf editor, numlock-state is well 'on' and remember-numlock-state 'true'. Thanks in advance for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-06-16 (445 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) Package: gnome-settings-daemon 3.33.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Tags: eoan wayland-session Uname: Linux 5.2.0-15-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-06-10 (86 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-settings-daemon/+bug/1842880/+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 942856] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
In Progress
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+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 942856] Proposed package removed from archive
The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/942856
Title:
NetworkManager does not support AES-encrypted private keys for WPA
802.1x authentication
Status in NetworkManager:
Confirmed
Status in network-manager package in Ubuntu:
Fix Released
Status in network-manager source package in Bionic:
In Progress
Bug description:
* Impact
Selecting AES-{192,256}-CBC keys to connect isn't working
* Test case
1. Start with a working (cleartext or DES-3) private key/cert for a network.
Set up a connection and verify that everything works.
2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in
working-key.pem -out aes-key.pem -aes256" (the output should have a line
starting with "DEK-Info: AES-256-CBC,")
3. Delete the settings for the test network and attempt to reconnect using
the new key.
That should work
* Regression potential
That's new code for an extra type of keys, it shouldn't impact
existing options
--
NetworkManager does not appear to support private keys encrypted with
AES. At the very least, it will not validate such a key in nm-util
when setting up a WPA 802.1x TLS wifi connection.
To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/942856/+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 1849371] [NEW] headless chromium broken (as a consequence of snap)
Public bug reported:
Since the move to snap, and upgrade to 19.10, I can no longer use
headless-chromium to do automated conversions.
The script, as currently run by Apache (user www-data) as a back-end
server process is:
/usr/bin/timeout 60 chromium-browser --no-sandbox --headless --disable-
gpu --window-size=2048,1448 --screenshot='dummy.pdf'
'http://localhost/[...]' 2>&1 2>&1
This returns error 1, with:
dconf-CRITICAL **: 19:41:17.958: unable to create directory
'/var/www/.cache/dconf': Permission denied. dconf will not work
properly.
WARNING: cannot create user data directory: cannot create
"/var/www/snap/chromium/899":
mkdir /var/www/snap: permission denied
Sorry, home directories outside of /home are not currently supported.
See https://forum.snapcraft.io/t/11209 for details.
So... how are we supposed to use scripted Chrome for headless work, when the
snaps don't support it?
This is a major blocker for me, as it completely destroys my ability to do any
development work, because the build-toolchain for selftests relies on the
ability of chrome to operate headless.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: MATE
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wBMLToINDAxMCsWAQOANCB4KgHxoldSnycKUFS/74BxT4EAgUCBgJUAlQ+pQLMAKDyAoHCwI0AwIDYABkQhAAAa/QA4Sx5REQAKICAgICAg/ABTTVMyNEE0NTAKICAg/wBINE1DQTEzMzYyCiAgAQkCAQQAAjqA0HI4LUAQLEWABkQhAAAeAR0AclHQHiBuKFUABkQhAAAeAR0AvFLQHiC4KFVABkQhAAAejArQkCBAMSAMQFUABkQhAAAYjArQiiDgLRAQPpYABkQhAAAY0g==
modes: 1920x1200 1920x1080 1600x1200 1680x1050 1280x1024 1280x1024 1440x900
1440x900 1280x960 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768
1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 720x576 720x480
720x480 640x480 640x480 640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-2:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAlpVNWODYxMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMTY4/ABMMjBDTQogICAgICAgAMU=
modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480
640x480 640x480 640x480 720x400
DRM.card0-HDMI-A-3:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAlpVNWNjIyMB0NAQOBKR//6uWVpVhMlyYeUFS/7wCBgKlAMVlFWWFZgZkBAQEBSD9AMGKwMkAAwAMAmDIRAAAe/QA4VR9cEQAKICAgICAg/wBCSEZGS0I2MzAwMjI2/ABMMjBDTQogICAgICAgAM8=
modes: 1600x1200 1280x1024 1280x1024 1280x1024 1024x768 1024x768 1024x768
1024x768 832x624 800x600 800x600 800x600 800x600 800x600 640x480 640x480
640x480 640x480 640x480 720x400
Date: Tue Oct 22 19:48:51 2019
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sdb1 ext4 1.8T 491G 1.3T 29% /home
tmpfs tmpfs 32G 927M 31G 3% /dev/shm
/dev/sdb1 ext4 1.8T 491G 1.3T 29% /home
InstallationDate: Installed on 2017-02-03 (991 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-generic
root=UUID=6ef42be7-d431-4d0d-bc57-79f7a96980ef ro
Snap.ChromeDriverVersion:
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded
(failed to map segment from shared object): ignored.
ChromeDriver 77.0.3865.120
(416d6d8013e9adb6dd33b0c12e7614ff403d1a94-refs/branch-heads/3865@{#884})
Snap.ChromiumVersion:
ERROR: ld.so: object 'libgtk3-nocsd.so.0' from LD_PRELOAD cannot be preloaded
(failed to map segment from shared object): ignored.
Chromium 77.0.3865.120 snap
SourcePackage: chromium-browser
UpgradeStatus: Upgraded to eoan on 2019-10-21 (0 days ago)
dmi.bios.date: 05/16/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3805
dmi.board.asset.tag: Default string
dmi.board.name: Z170 PRO GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd05/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
** Affects: chromium-browser
[Desktop-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently
Till Kamppeter (till-kamppeter) wrote on 2019-08-06: asking me to post the full log. I did on 8/08. Nothing has happened on this list for two months. Is there no solution to this problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1838836 Title: network-manager needs to be restarted frequently Status in network-manager package in Ubuntu: New Bug description: I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops working frequently and the network-manager service needs to be restarted. It will die on its own, but can be triggered by switching wifi 3 times (sometimes more, sometimes fewer)! When it is working, I have: ``` % usr/bin/sudo nmcli device DEVICE TYPE STATE CONNECTION wlp62s0 wifi connected ATT964 p2p-dev-wlp62s0 wifi-p2p disconnected -- enp59s0 ethernet unavailable -- lo loopback unmanaged -- % /usr/bin/sudo lshw -C network ...snip... *-network description: Wireless interface product: Wireless 8260 vendor: Intel Corporation physical id: 0 bus info: pci@:3e:00.0 logical name: wlp62s0 version: 3a serial: e4:b3:18:e3:11:e7 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:133 memory:dc20-dc201fff % /usr/bin/sudo lspci -vnnn | grep -A 9 Network 3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a) Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010] Flags: bus master, fast devsel, latency 0, IRQ 133 Memory at dc20 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7 Capabilities: [14c] Latency Tolerance Reporting ``` If I switch between my two wifi routers three times (sometimes more times) using the Select Network command on the taskbar, wifi stops working. Issuing the commands above yields the following differences: ``` % /usr/bin/sudo nmcli device DEVICE TYPE STATECONNECTION enp59s0 ethernet unavailable -- wlp62s0 wifi unavailable -- p2p-dev-wlp62s0 wifi-p2p unavailable -- lo loopback unmanaged % /usr/bin/sudo lshw -C network ...snip... *-network ...snip... configuration: broadcast=yes driver=iwlwifi driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no multicast=yes wireless=IEEE 802.11 ``` /var/log/syslog reports the following after failing to switch wifi networks: ``` Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): disconnecting for new activation request. Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5482] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5485] manager: NetworkManager state is now DISCONNECTING Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5548] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=21476 uid=1010 result="success" Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5550] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5562] dhcp4 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318 Jul 16 19:20:32 serval NetworkManager[617]: [1563330032.5572] dhcp6 (wlp62s0): state changed bound -> done Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING) Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0:
[Desktop-packages] [Bug 1849324] Re: Xorg logs spammed with failed page flip messages
that commit is in server-1.20-branch, and eoan has a git snapshot of it which includes that commit note that the source is not the modeset driver but 'AMDGPU', which means maybe this might help: https://bugs.freedesktop.org/show_bug.cgi?id=110417 ** Bug watch added: freedesktop.org Bugzilla #110417 https://bugs.freedesktop.org/show_bug.cgi?id=110417 ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1849324 Title: Xorg logs spammed with failed page flip messages Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1849324/+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 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs
jackd2 released version 1.9.13 which includes this fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to jackd2 in Ubuntu. https://bugs.launchpad.net/bugs/1833479 Title: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs Status in jackd2 package in Ubuntu: Confirmed Status in jackd2 package in Debian: Confirmed Bug description: After upgrading to Ubuntu 19.04, I started experiencing sporadic crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin is enabled by default in /etc/alsa/conf.d/50-jack.conf. The crashes are caused by a race condition when kodi's audio engine thread is enumerating the ALSA sound devices, and the udev thread is enumerating the udev devices triggered by the sound device add from turning the AVR on. When enumerating the ALSA jack plugin device, it tries to connect to connect to jackd. Since I don't have jackd installed, it fails to connect. libjack closes the socket on error, and then closes it again in it's cleanup code. Since it's closing the same file descriptor twice, it interacts with other threads that have potentially opened file descriptors, and causes the crash. This same bug could potentially affect other multi-threaded programs that enumerate ALSA devices. Fix committed upstream: https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jackd2/+bug/1833479/+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 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working
The response was “The MIC is bulit into the in mainboard of the unit.” Does that help? Happy to ask again if that still doesn’t answer your question. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1793410 Title: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working Status in alsa-driver package in Ubuntu: Confirmed Bug description: Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04 on it. Everything works except the internal microphone. I have also tested with an external microphone and this didn't work either. I have worked my way through all the suggested solutions I could find, including trying to reconfigure the pins using hdajacketask. In pavucontrol I have options for Internal Microphone and Microphone (unplugged) but the internal mic only captures static noise. The latest HD-Audio Codec-Specific Models has configurations for alc255-acer and alc256 for some other models, but setting options snd- hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve the issue with any of these. Some info - lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point- LP HD Audio (rev 21) cat /proc/asound/cards: 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xdf1a8000 irq 127 dmesg | grep snd: [3.944593] snd_hda_core: loading out-of-tree module taints kernel. [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0) [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0) [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, version 0.201808050301~ubuntu18.04.1 [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs: [4.013068] snd_hda_codec_realtek hdaudioC0D0: Mic=0x18 [4.013069] snd_hda_codec_realtek hdaudioC0D0: Internal Mic=0x12 info on node 12 from cat /proc/asound/card*/codec\#*: Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In Control: name="Internal Mic Boost Volume", index=0, device=0 ControlAmp: chs=3, dir=In, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0 Amp-In vals: [0x02 0x02] Pincap 0x0020: IN Pin Default 0x4000: [N/A] Line Out at Ext N/A Conn = Unknown, Color = Unknown DefAssociation = 0x0, Sequence = 0x0 Pin-ctls: 0x20: IN Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Let me know if you need any other information. James --- Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) _MarkForUpload: True dmi.bios.date: 06/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Erdinger_KL dmi.board.vendor: KBL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF315-52 dmi.product.version: V1.04 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793410/+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 1849367] [NEW] Kde battery indicator remaining time stucked
Public bug reported: I have the latest kubuntu 19.10 with kde 5.16.5. When I look the battery icon it show me the same reamining time no matter what is the percentage of energy remaining in the battery. I monitor dbus with this command "dbus-monitor --system sender=org.freedesktop.UPower" And I get this: dbus-monitor --system sender=org.freedesktop.UPower dbus-monitor: unable to enable new-style monitoring: org.freedesktop.DBus.Error.AccessDenied: "Rejected send message, 1 matched rules; type="method_call", sender=":1.1599" (uid=1000 pid=12348 comm="dbus-monitor --system sender=org.freedesktop.UPowe" label="unconfined") interface="org.freedesktop.DBus.Monitoring" member="BecomeMonitor" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)". Falling back to eavesdropping. signal time=1571765384.592371 sender=org.freedesktop.DBus -> destination=:1.1599 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.1599" signal time=1571765393.680203 sender=:1.681 -> destination=(null destination) serial=265 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.freedesktop.UPower.Device" array [ dict entry( string "UpdateTime" variant uint64 1571765393 ) dict entry( string "TimeToEmpty" variant int64 30127 ) dict entry( string "Voltage" variant double 8.056 ) dict entry( string "Percentage" variant double 74 ) dict entry( string "EnergyRate" variant double 5.358 ) dict entry( string "Energy" variant double 44.84 ) ] array [ ] signal time=1571765393.680667 sender=:1.681 -> destination=(null destination) serial=266 path=/org/freedesktop/UPower/devices/DisplayDevice; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.freedesktop.UPower.Device" array [ dict entry( string "UpdateTime" variant uint64 1571765393 ) dict entry( string "Percentage" variant double 74 ) dict entry( string "TimeToEmpty" variant int64 30127 ) dict entry( string "EnergyRate" variant double 5.358 ) dict entry( string "Energy" variant double 44.84 ) ] array [ ] So it seems that is receiving the good values but the battery indicator in the systray is not working at all. The only good value it gets is the total percentage of the battery. ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1849367 Title: Kde battery indicator remaining time stucked Status in gnome-power-manager package in Ubuntu: New Bug description: I have the latest kubuntu 19.10 with kde 5.16.5. When I look the battery icon it show me the same reamining time no matter what is the percentage of energy remaining in the battery. I monitor dbus with this command "dbus-monitor --system sender=org.freedesktop.UPower" And I get this: dbus-monitor --system sender=org.freedesktop.UPower dbus-monitor: unable to enable new-style monitoring: org.freedesktop.DBus.Error.AccessDenied: "Rejected send message, 1 matched rules; type="method_call", sender=":1.1599" (uid=1000 pid=12348 comm="dbus-monitor --system sender=org.freedesktop.UPowe" label="unconfined") interface="org.freedesktop.DBus.Monitoring" member="BecomeMonitor" error name="(unset)" requested_reply="0" destination="org.freedesktop.DBus" (bus)". Falling back to eavesdropping. signal time=1571765384.592371 sender=org.freedesktop.DBus -> destination=:1.1599 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired string ":1.1599" signal time=1571765393.680203 sender=:1.681 -> destination=(null destination) serial=265 path=/org/freedesktop/UPower/devices/battery_BAT0; interface=org.freedesktop.DBus.Properties; member=PropertiesChanged string "org.freedesktop.UPower.Device" array [ dict entry( string "UpdateTime" variant uint64 1571765393 ) dict entry( string "TimeToEmpty" variant int64 30127 ) dict entry( string "Voltage" variant double 8.056 ) dict entry( string "Percentage" variant double 74 ) dict entry( string "EnergyRate" variant
[Desktop-packages] [Bug 1842880] Re: Numlock state inverted: active at login, disabled on session
Could you check if that still an issue? Some issues are numlock got fixed before 19.10 ** Changed in: gnome-settings-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Incomplete -- 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/1842880 Title: Numlock state inverted: active at login, disabled on session Status in gnome-settings-daemon package in Ubuntu: Incomplete Bug description: Hi, running Ubuntu 19.10 development version, I have a problem since a few days: Numlock behaviour is inverted. It is active and already enabled on the login screen, without the need to press the "Verr Num" Key to type numbers for the password. But just after the connexion and session start, it is inactive - I have to press the Key to make it available again. Normally it's the contrary! NumLock is disabled on login screen, and if activated at this moment, it remains active on the session... In Dconf editor, numlock-state is well 'on' and remember-numlock-state 'true'. Thanks in advance for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-06-16 (445 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180611) Package: gnome-settings-daemon 3.33.90-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Tags: eoan wayland-session Uname: Linux 5.2.0-15-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-06-10 (86 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-settings-daemon/+bug/1842880/+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 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
Reading package lists ... Done Building a dependency tree Reading status information ... Done The gcc package is not available, but is listed in the dependency list of another package. This may mean that the package is missing, out of date, or available from sources not mentioned in sources.list -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, when I turn off the computer, it hangs on the logo. I can not turn off the computer using alt + SysRq + REISUO. The light on the system unit continues to light, and the fan runs. This is a problem with kernel 5.0, 5.3. There is no such problem with the 4.15 kernel. It happens that after 90 seconds it turns off. And with a new core, he writes that he will turn off after 90 seconds, but he will not turn off. Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq https://ibb.co/4JMGwvC sudo dmesg|grep ACPI|less - https://pastebin.com/PZxRGNyJ ProblemType: Bug DistroRelease: Ubuntu 18.04 Пакет: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 CurrentDesktop: XFCE Дата: Четверг 5 09:44:35 2019 Дата установки: установлено в 2019-08 -09 (26 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 (20190210) ProcEnviron: LANGUAGE = ru_UA: ru PATH = (пользовательский, нет пользователя) XDG_RUNTIME_ DIR = LANG = ru_UA.UTF -8 SHELL = / bin / bash SourcePackage: gvfs UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) --- Тип проблемы: ошибка ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 AudioDevicesInUse: КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID / dev / snd / controlC0: макс. 1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Установлен 2019-08-09 (37 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 (20190210) IwConfig: enp0s25 без беспроводных расширений. enp7s4 нет беспроводных расширений. нет никаких беспроводных расширений. Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower Пакет: Linux (не установлен) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень = UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1 ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18 RelatedPackageV ersions: linux- restricted- modules- 4.15.0- 62-родовое N / A linux- backports- modules- 4.15.0 - 62-типовой N / A linux-прошивка 1.173.9 RfKill: Теги: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: нет журнала обновления (возможно, новая установка) Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 26.10.2015 dmi. bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board. asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis. asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: rn2820h: rvr: cvnHewlett- Packard: ct6: cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dvtwelet dv00 от компании HP : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+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 1846290] Re: Ubuntu 19.10 incorrectly selects audio output source
*** This bug is a duplicate of bug 1847570 *** https://bugs.launchpad.net/bugs/1847570 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1846290 Title: Ubuntu 19.10 incorrectly selects audio output source Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have two monitors hooked up to an AMD RX570 via displayport. In the sound settings they appear as "Ellesmere HDMI Audio [Radeon RX 470/480/560/570/580/590]" and Ubuntu 19.10 selected one of them as the output device by default. My speakers are connected to a green mini- jack line out jack on the motherboard. Switching to line out gives me sound, and I have no other issues. Originally, I had upgraded to the beta from the command line in 19.04. I had not experienced this issue in 19.04, but upon first booting into 19.10, I had to switch output device back to line out. A fresh install of the beta iso gave the same result (one of my monitors connected to my video card was selected by default). Note that my monitors are Dell U2415s but they do have line out jacks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bick 1719 F pulseaudio /dev/snd/controlC0: bick 1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 2 00:19:28 2019 InstallationDate: Installed on 2019-10-02 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] - HDA ATI HDMI Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bick 1719 F pulseaudio /dev/snd/controlC0: bick 1719 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/12/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1820 dmi.board.asset.tag: Default string dmi.board.name: PRIME B450-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1820:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846290/+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 1848309] Re: "Automatic Date & Time" is broken
Oh, sorry, I read that the wrong way ConditionFileIsExecutable=!/usr/sbin/ntpd Which means systemd-timesyncd isn't doing syncing when ntp is installed Did you install ntpd? Does it work better if you uninstall it? -- 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/1848309 Title: "Automatic Date & Time" is broken Status in gnome-control-center package in Ubuntu: Incomplete Bug description: In my always up-to-date Eoan the "Automatic Date & Time" adjustment is broken since around two months. 0 * * * * sudo ntpdate 0.ubuntu.pool.ntp.org >> /tmp/ntpsync ...is my crontab workaround to get proper time on Ubuntu Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+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 1849346] [NEW] kerberos GSSAPI no longer works after deb->snap transition
Public bug reported: I configure AuthServerWhitelist as documented: https://cloud.google.com/docs/chrome- enterprise/policies/?policy=AuthServerWhitelist and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPEGNO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. ** 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/1849346 Title: kerberos GSSAPI no longer works after deb->snap transition Status in chromium-browser package in Ubuntu: New Bug description: I configure AuthServerWhitelist as documented: https://cloud.google.com/docs/chrome- enterprise/policies/?policy=AuthServerWhitelist and can see my whitelisted domains in chrome://policy/ but websites that used to work with SPEGNO/GSSAPI/kerberos no longer work. I'm guessing the snap needs some sort of permission to use the kerberos ticket cache (or the plumbing to do so doesn't exist...). I can confirm that Chrome has the desired behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849346/+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
Re: [Desktop-packages] [Bug 1848658] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió
Yes. It was a fresh install of Ubuntu 19.10. First was run apt update,
upgrade, installed aptitude, brasero, deborphan, gparted and
chromium-browser.
El mar., 22 oct. 2019 17:01, Olivier Tilloy
escribió:
> Luis, can you confirm this was a clean installation of 19.10, and one of
> the first things you did was to install chromium-browser ?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1848658
>
> Title:
> package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
> install/upgrade: el subproceso nuevo paquete chromium-browser script
> pre-installation devolvió el código de salida de error 10
>
> Status in chromium-browser package in Ubuntu:
> Confirmed
>
> Bug description:
> Packet crash apt install chromium-browser
>
> ProblemType: Package
> DistroRelease: Ubuntu 19.10
> Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
> ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
> Uname: Linux 5.3.0-18-generic x86_64
> NonfreeKernelModules: nvidia_modeset nvidia
> ApportVersion: 2.20.11-0ubuntu8
> AptOrdering:
>chromium-browser:amd64: Install
>NULL: ConfigurePending
> Architecture: amd64
> Date: Fri Oct 18 08:58:37 2019
> ErrorMessage: el subproceso nuevo paquete chromium-browser script
> pre-installation devolvió el código de salida de error 10
> InstallationDate: Installed on 2019-10-18 (0 days ago)
> InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
> Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal,
> 3.7.5-1
> PythonDetails: N/A
> RelatedPackageVersions:
>dpkg 1.19.7ubuntu2
>apt 1.9.4
> Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.90
> (58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830})
> Snap.ChromiumVersion:
>mkdir: cannot create directory '/run/user/0': Permission denied
>Chromium 77.0.3865.90 snap
> SourcePackage: chromium-browser
> Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
> install/upgrade: el subproceso nuevo paquete chromium-browser script
> pre-installation devolvió el código de salida de error 10
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848658/+subscriptions
>
--
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/1848658
Title:
package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: el subproceso nuevo paquete chromium-browser script
pre-installation devolvió el código de salida de error 10
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Packet crash apt install chromium-browser
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
AptOrdering:
chromium-browser:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Fri Oct 18 08:58:37 2019
ErrorMessage: el subproceso nuevo paquete chromium-browser script
pre-installation devolvió el código de salida de error 10
InstallationDate: Installed on 2019-10-18 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu2
apt 1.9.4
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.90
(58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 77.0.3865.90 snap
SourcePackage: chromium-browser
Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: el subproceso nuevo paquete chromium-browser script
pre-installation devolvió el código de salida de error 10
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848658/+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
Re: [Desktop-packages] [Bug 1849160] Re: after deb->snap transition, chromium no longer sees local password store
On Tue, Oct 22, 2019 at 01:50:07PM -, Olivier Tilloy wrote: > No, it's not connected. There have been similar reports, and I think I > understand what's going on. > I will SRU a fix to the chromium-browser package. In the meantime, I suggest > you run: > snap connect chromium:password-manager-service > (please confirm whether this fixes the problem) Ok, sure enough, running this command and restarting fixes the problem. Thanks! (Sorry, I tried to run this command before, but there seemed to be a whitespace issue in your comment #1 and it gave me an error instead.) -- 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/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Fix Committed Status in chromium-browser source package in Eoan: In Progress Bug description: [Impact] After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. [Test Case] Install chromium-browser in disco (19.04), save a few passwords for login forms. Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved passwords are still there. They can be inspected by browsing to chrome://settings/passwords. As an additional check, the output of `snap connections chromium | grep password` should look like this: password-manager-service chromium:password-manager-service :password-manager-service manual I.e. the interface should be marked as manually connected, even though the user hasn't explicitly connected it. [Regression Potential] Low. The change removes an assumption on upgrade paths that has become incorrect. Now the password-manager-service interface will always be connected on upgrade, which I think is sensible. Users who wish to disconnect the interface (unlikely use case) will also have to remove the chromium-browser transitional package, to prevent it from reconnecting the interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+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 1848753] Re: [snap] chromium times out connecting document portal with NFS home
> I suspect the chromium and password manager connection might have failed > due to headless custom made auto-update script that is run from cron.daily No, the connection to the password-manager-service interface wasn't even attempted, but that's a separate bug, which is being fixed (bug #1849160). > Should we continue solving the timeout problem in this issue? Yes, let's do that. What do you mean by a 12ms timeout, does the chromium window take 2 whole minutes to appear when you launch it? -- 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/1848753 Title: [snap] chromium times out connecting document portal with NFS home Status in snapd: New Status in chromium-browser package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: I have my /home folder shared via NFS from a local server one floor below in my house. The server runs Ubuntu 18.04. After starting a snapped version of chromium-browser in my Ubuntu 19.10 the document portal timeouts like this: XXX@koira:~$ chromium-browser 2019/10/18 18:51:27.986444 cmd_run.go:893: WARNING: cannot start document portal: Failed to activate service 'org.freedesktop.portal.Documents': timed out (service_start_timeout=12ms) After the timeout my chromium cannot seem to remember accounts or passwords. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1848753/+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 1848658] Re: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to install/upgrade: el subproceso nuevo paquete chromium-browser script pre-installation devolvió el c
Luis, can you confirm this was a clean installation of 19.10, and one of
the first things you did was to install chromium-browser ?
--
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/1848658
Title:
package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: el subproceso nuevo paquete chromium-browser script
pre-installation devolvió el código de salida de error 10
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
Packet crash apt install chromium-browser
ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: chromium-browser 77.0.3865.120-0ubuntu1~snap1
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
AptOrdering:
chromium-browser:amd64: Install
NULL: ConfigurePending
Architecture: amd64
Date: Fri Oct 18 08:58:37 2019
ErrorMessage: el subproceso nuevo paquete chromium-browser script
pre-installation devolvió el código de salida de error 10
InstallationDate: Installed on 2019-10-18 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
dpkg 1.19.7ubuntu2
apt 1.9.4
Snap.ChromeDriverVersion: ChromeDriver 77.0.3865.90
(58c425ba843df2918d9d4b409331972646c393dd-refs/branch-heads/3865@{#830})
Snap.ChromiumVersion:
mkdir: cannot create directory '/run/user/0': Permission denied
Chromium 77.0.3865.90 snap
SourcePackage: chromium-browser
Title: package chromium-browser 77.0.3865.120-0ubuntu1~snap1 failed to
install/upgrade: el subproceso nuevo paquete chromium-browser script
pre-installation devolvió el código de salida de error 10
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848658/+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 1849160] Re: after deb->snap transition, chromium no longer sees local password store
** Description changed: + [Impact] + After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login - Data being present and fully-populated. If I go into settings, I see + Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. + + + [Test Case] + + Install chromium-browser in disco (19.04), save a few passwords for login forms. + Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved passwords are still there. They can be inspected by browsing to chrome://settings/passwords. + As an additional check, the output of `snap connections chromium | grep password` should look like this: + + password-manager-service chromium:password-manager-service + :password-manager-service manual + + I.e. the interface should be marked as manually connected, even though + the user hasn't explicitly connected it. + + + [Regression Potential] + + Low. The change removes an assumption on upgrade paths that has become + incorrect. Now the password-manager-service interface will always be + connected on upgrade, which I think is sensible. Users who wish to + disconnect the interface (unlikely use case) will also have to remove + the chromium-browser transitional package, to prevent it from + reconnecting the interface. ** Also affects: chromium-browser (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: chromium-browser (Ubuntu Eoan) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu Eoan) Importance: Undecided => High ** Changed in: chromium-browser (Ubuntu Eoan) Status: New => In Progress ** Changed in: chromium-browser (Ubuntu Eoan) Status: In Progress => Fix Committed ** Changed in: chromium-browser (Ubuntu Eoan) Status: Fix Committed => In Progress -- 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/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Fix Committed Status in chromium-browser source package in Eoan: In Progress Bug description: [Impact] After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. [Test Case] Install chromium-browser in disco (19.04), save a few passwords for login forms. Dist-upgrade to eoan (19.10), launch chromium, and verify that the saved passwords are still there. They can be inspected by browsing to chrome://settings/passwords. As an additional check, the output of `snap connections chromium | grep password` should look like this: password-manager-service chromium:password-manager-service :password-manager-service manual I.e. the interface should be marked as manually connected, even though the user hasn't explicitly connected it. [Regression Potential] Low. The change removes an assumption on upgrade paths that has become incorrect. Now the password-manager-service interface will always be connected on upgrade, which I think is sensible. Users who wish to disconnect the interface (unlikely use case) will also have to remove the chromium-browser transitional package, to prevent it from reconnecting the interface. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+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 1849179] Re: canmount property switches to noauto in user's home dataset
Correct, with the new property, it works correctly. There is no way to get rid of the org.zsys one though, is there? Apparently there is no way to remove a user property in zfs. ** Changed in: zsys (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1849179 Title: canmount property switches to noauto in user's home dataset Status in zsys package in Ubuntu: Invalid Bug description: I can't be 100% sure about this, but I think anytime I have zsys installed and reboot, my user's dataset has its canmount property set to noauto. That property is set to off in the parent dataset USERDATA: $ zfs get canmount,mounted,mountpoint rpool/USERDATA NAMEPROPERTYVALUE SOURCE rpool/USERDATA canmountoff local rpool/USERDATA mounted no - rpool/USERDATA mountpoint / local In mine, it's on: $ zfs get canmount,mounted,mountpoint rpool/USERDATA/andreas_xk451a NAME PROPERTYVALUE SOURCE rpool/USERDATA/andreas_xk451a canmounton local rpool/USERDATA/andreas_xk451a mounted yes- rpool/USERDATA/andreas_xk451a mountpoint /home/andreas local I then install zsys 0.2.2: Get:1 http://br.archive.ubuntu.com/ubuntu eoan/universe amd64 zsys amd64 0.2.2 [1.303 kB] And reboot. When I login again, my home is gone, because the andreas_xk451a dataset is not mounted. Running zfs get again confirms that the canmount property changed back to noauto. NAME PROPERTYVALUE SOURCE rpool/USERDATA/andreas_xk451a canmountnoauto local rpool/USERDATA/andreas_xk451a mounted no - rpool/USERDATA/andreas_xk451a mountpoint /home/andreas local NAMEPROPERTYVALUE SOURCE rpool/USERDATA canmountoff local rpool/USERDATA mounted no - rpool/USERDATA mountpoint / local Since "noauto" isn't even the parent's setting, and the SOURCE of the property is marked as "local", something is doing it on purpose. My guess it's zsys, because after I remove it, this behavior stops. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1849179/+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 1849324] [NEW] Xorg logs spammed with failed page flip messages
Public bug reported: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The Xorg log file, currently 15 MB large" https://bugs.launchpad.net/bugs/1849324/+attachment/5299212/+files/Xorg.0.log ** Description changed: - This bug has already been discussed here: + Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. ** Description changed: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` - A fix has already been merged here: + A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1849324 Title: Xorg logs spammed with failed page flip messages Status in xorg package in Ubuntu: New Bug description: Please read this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1645553 I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source 2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these messages are still being spammed into my Xorg logs. ``` [ 6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable [ 6794.424] (EE) AMDGPU(0): present flip failed [ 6794.457] Failed to get FB for flip ``` A potential fix has already been merged here: https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193 Fedora users already have it. I haven't tested Fedora to see if that fixes my problem. If that fix is already in Ubuntu, I believe we're talking about a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1849324/+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 1849160] Re: after deb->snap transition, chromium no longer sees local password store
** Branch linked: lp:~chromium-team/chromium-browser/eoan-stable -- 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/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Fix Committed Bug description: After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+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 1849160] Re: after deb->snap transition, chromium no longer sees local password store
Fixed with https://bazaar.launchpad.net/~chromium-team/chromium-browser /eoan-stable/revision/1522. ** Changed in: chromium-browser (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: chromium-browser (Ubuntu) Status: Confirmed => Fix Committed -- 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/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Fix Committed Bug description: After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+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 1848621] Re: [snap] lost all passwords on 19.10 when chromium-browser deb was replaced by a snap
*** This bug is a duplicate of bug 1849160 *** https://bugs.launchpad.net/bugs/1849160 ** This bug has been marked a duplicate of bug 1849160 after deb->snap transition, chromium no longer sees local password store -- 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/1848621 Title: [snap] lost all passwords on 19.10 when chromium-browser deb was replaced by a snap Status in chromium-browser package in Ubuntu: Confirmed Bug description: After I've upgraded 19.04 to 19.10, chromium-browser deb was replaced by a snap package. When chromium is now started from a snap package, I no longer have any passwords which I had saved in deb version of chromium-browser. This is quite annoying; a workaround for now is to downgrade to chromium-browser deb from 19.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1848621/+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 1849160] Re: after deb->snap transition, chromium no longer sees local password store
No, it's not connected. There have been similar reports, and I think I understand what's going on. I will SRU a fix to the chromium-browser package. In the meantime, I suggest you run: snap connect chromium:password-manager-service (please confirm whether this fixes the problem) -- 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/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Confirmed Bug description: After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+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 1849160] Re: after deb->snap transition, chromium no longer sees local password store
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/1849160 Title: after deb->snap transition, chromium no longer sees local password store Status in chromium-browser package in Ubuntu: Confirmed Bug description: After upgrading to eoan and accepting the deb->snap transition for chromium, the passwords saved in my browser are no longer available to the app, despite ~/snap/chromium/current/.config/chromium/Default/Login Data being present and fully-populated. If I go into settings, I see Saved Passwords: Saved passwords will appear here. The data doesn't appear to be lost, since I have a copy in ~/snap as well as in ~/.config/chromium, but somehow they're inaccessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1849160/+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 1849321] [NEW] Build error on 5.3.0-19-generic; dkms says module installed fine
Public bug reported: Error reported during build, but dkms reports successful build. Dkms build appears to complete successfully despite error reports, so maybe only a cosmetic error during the build process? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-340 340.107-0ubuntu7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Tue Oct 22 09:47:38 2019 InstallationDate: Installed on 2019-10-11 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1849321 Title: Build error on 5.3.0-19-generic; dkms says module installed fine Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Error reported during build, but dkms reports successful build. Dkms build appears to complete successfully despite error reports, so maybe only a cosmetic error during the build process? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-340 340.107-0ubuntu7 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair wl ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 Date: Tue Oct 22 09:47:38 2019 InstallationDate: Installed on 2019-10-11 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20191010) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1849321/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Tags removed: rls-ee-incoming ** Tags added: rls-ee-tracking ** Tags removed: rls-ee-tracking ** Also affects: gnome-session (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gnome-shell (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Eoan) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: New Status in gnome-session source package in Eoan: New Status in gnome-shell source package in Eoan: New Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1849135] Re: Clicking Activities in the corner doesn't work in Xorg sessions
** Tags removed: rls-ee-incoming -- 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/1849135 Title: Clicking Activities in the corner doesn't work in Xorg sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Starting from Ubuntu 19.10, the top-left corner of the screen is unclickable. It's where the Activities button is. It is unresponsive to clicks to open the overlay, BUT it responds to clicks to close it. The unclickable spot is exactly one pixel large. Edit: At first it seemed to be reproducible only on Xorg sessions, but after using it for a while on Wayland, I am having the issue again. Specs: - Graphics: AMD RX 560 - CPU: Intel Core i3-8100 - Ubuntu 19.10 Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1849135/+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 1848309] Re: "Automatic Date & Time" is broken
alex@sun:~/$ dpkg -S /lib/systemd/system/systemd-timesyncd.service systemd: /lib/systemd/system/systemd-timesyncd.service alex@sun:~/$ dpkg -l systemd Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---= ii systemd242-7ubuntu3 amd64system and service manager alex@sun:~/$ ls -l /lib/systemd/system/systemd-timesyncd.service -rw-r--r-- 1 root root 1489 Oct 11 16:19 /lib/systemd/system/systemd-timesyncd.service -- 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/1848309 Title: "Automatic Date & Time" is broken Status in gnome-control-center package in Ubuntu: Incomplete Bug description: In my always up-to-date Eoan the "Automatic Date & Time" adjustment is broken since around two months. 0 * * * * sudo ntpdate 0.ubuntu.pool.ntp.org >> /tmp/ntpsync ...is my crontab workaround to get proper time on Ubuntu Eoan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1848309/+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 1849162] Re: Lightning extension should be installed and enabled by default
That makes sense. Maybe we could reconsider that decision? Quoting an e-mail from a thunderbird developer: « In the Thunderbird community there has been quite a few discussions lately on the problems with that packaging, especially regarding the Lightning calendar. Thunderbird upstream is shipping Lightning bundled and on by default, but apparently in Ubuntu an explicit install decision needs to be made by the user. This has caused major problems for users who couldn't figure out how to get lightning, or why it didn't show up in the first place. » People who have used upstream builds of thunderbird will expect lightning to be bundled. At the very least we can bundle it in the main thunderbird package, maybe not enabled by default? That would mostly fix the discoverability problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1849162 Title: Lightning extension should be installed and enabled by default Status in thunderbird package in Ubuntu: Triaged Bug description: Upstream builds of thunderbird are now shipping lightning, and it is enabled by default. In contrast, lightning in Ubuntu is a separate binary package (xul- ext-lightning), and it’s neither installed by default nor even recommended by thunderbird. This results in confusion for users who don't know where to get lightning from. The extension should be bundled with the thunderbird package, i.e. installed and enabled by default (as was done for the wetransfer file link provider, see bug #1823361). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849162/+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 1754671] Re: Full-tunnel VPN DNS leakage regression
Sorry for the late reply, I was on a conference last week. I installed the PPA now and tested with the reproducer of the initial posting. This works for me. Also the machine in general seems to work OK with this version of network-manager. Thank you very much Dariusz for packaging this version. So now the 1.10.14 should be removed from -proposed (to avoid need of an epoch), and the version from the PPA of Dariusz should get uploaded into -proposed, and then the reporters of the regressions in the 1.10.14 SRU informed (by comments in their bug reports) for the new SRU being verified. Could someone from the release team initiate the process by removing 1.10.14 from -proposed? Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1754671 Title: Full-tunnel VPN DNS leakage regression Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Status in network-manager source package in Bionic: In Progress Status in systemd source package in Bionic: Fix Released Status in network-manager source package in Cosmic: Fix Released Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] When using a VPN the DNS requests might still be sent to a DNS server outside the VPN when they should not [Test case] 1) Set up a VPN with split tunneling: a) Configure VPN normally (set up remote host, any ports and options needed for the VPN to work) b) Under the IPv4 tab: enable "Use this connection only for the resources on its network". c) Under the IPv6 tab: enable "Use this connection only for the resources on its network". 2) Connect to the VPN. 3) Run 'systemd-resolve --status'; note the DNS servers configured: a) For the VPN; under a separate link (probably tun0), note down the IP of the DNS server(s). Also note the name of the interface (link). b) For the "main" connection; under the link for your ethernet or wireless devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). Also note the name of the interface (link). 4) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 5) In a separate terminal, run 'sudo tcpdump -ni port 53'; let it run. 6) In yet another terminal, issue name resolution requests using dig: a) For a name known to be reachable via the public network: 'dig www.yahoo.com' b) For a name known to be reachable only via the VPN: 'dig ' 7) Check the output of each terminal running tcpdump. When requesting the public name, traffic can go through either. When requesting the "private" name (behind the VPN), traffic should only be going through the interface for the VPN. Additionally, ensure the IP receiving the requests for the VPN name is indeed the IP address noted above for the VPN's DNS server. If you see no traffic showing in tcpdump output when requesting a name, it may be because it is cached by systemd-resolved. Use a different name you have not tried before. [Regression potential] The code change the handling of DNS servers when using a VPN, we should check that name resolution still work whne using a VPN in different configurations - In 16.04 the NetworkManager package used to carry this patch: http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch It fixed the DNS setup so that when I'm on the VPN, I am not sending unencrypted DNS queries to the (potentially hostile) local nameservers. This patch disappeared in an update. I think it was present in 1.2.2-0ubuntu0.16.04.4 but was dropped some time later. This security bug exists upstream too: https://bugzilla.gnome.org/show_bug.cgi?id=746422 It's not a *regression* there though, as they didn't fix it yet (unfortunately!) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1754671/+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 1832426] Re: "Program" is not responding when debugging in gdb
I am also affected by this bug, currently using Ubuntu 19.10, and previously I had 19.04, both have the issue. It is really annoying because the window system becomes temporarily completely unresponsive and I am not even able to click on anything. -- 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/1832426 Title: "Program" is not responding when debugging in gdb Status in gnome-shell package in Ubuntu: Confirmed Bug description: I believe this is a regression for bug 1740869: is not responding window is constantly showing when debugging a program I'm debugging my c++ sdl2 program in gdb and when I hit a breakpoint this window shows up and I can't get it to stop asking me to close the program. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description: Ubuntu 19.04 Release: 19.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center gnome-shell: Installed: 3.32.1-1ubuntu1~19.04.1 Candidate: 3.32.1-1ubuntu1~19.04.1 Version table: *** 3.32.1-1ubuntu1~19.04.1 500 500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.32.0+git20190410-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 3) What you expected to happen When I hit a breakpoint in gdb, the program should stop. 4) What happened instead The program stops and ubuntu asks me if i want to kill the program. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell 3.32.1-1ubuntu1~19.04.1 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jun 11 22:03:44 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-06-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1832426/+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 1849162] Re: Lightning extension should be installed and enabled by default
One of the reason we didn't enable it before is because from earlier Ubuntu we always tried to avoid having several applications doing the same job and we already have gnome-calendar installed by default as a calendar. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1849162 Title: Lightning extension should be installed and enabled by default Status in thunderbird package in Ubuntu: Triaged Bug description: Upstream builds of thunderbird are now shipping lightning, and it is enabled by default. In contrast, lightning in Ubuntu is a separate binary package (xul- ext-lightning), and it’s neither installed by default nor even recommended by thunderbird. This results in confusion for users who don't know where to get lightning from. The extension should be bundled with the thunderbird package, i.e. installed and enabled by default (as was done for the wetransfer file link provider, see bug #1823361). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1849162/+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 1848942] Re: Freeze on opening font viewer
The whole desktop freezes - that's why I cannot run 'journalctl -b 0' command -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-font-viewer in Ubuntu. https://bugs.launchpad.net/bugs/1848942 Title: Freeze on opening font viewer Status in gnome-font-viewer package in Ubuntu: Incomplete Bug description: When I open gnome-font-viewer, after few seconds interface freezes and I only can move my cursor. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-font-viewer 3.34.0-1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 20 20:02:24 2019 InstallationDate: Installed on 2019-10-20 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-font-viewer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1848942/+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 1848156] Re: Update gnome-terminal to 3.34.1
*** This bug is a duplicate of bug 1849285 *** https://bugs.launchpad.net/bugs/1849285 ** This bug has been marked a duplicate of bug 1849285 [SRU] 3.34.2 -- 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/1848156 Title: Update gnome-terminal to 3.34.1 Status in gnome-terminal package in Ubuntu: Triaged Status in gnome-terminal source package in Eoan: Triaged Bug description: Please update to gnome-terminal 3.34.1 (or .2) for eoan. Or, at least, cherry-pick this trivial fix: https://gitlab.gnome.org/GNOME/gnome- terminal/commit/2cbc9e6b9be7f4d6b2d92b40e37ec687d36ce98d A change in GTK triggered a bug in Terminal causing a pretty bad user experience. A fullscreened terminal under Wayland doesn't retain its fullscreen status at certain operations, such as opening/closing a second tab, or zooming. Opening a second tab actually further grows the window as the tab bar appears, so that the bottom 1 or 2 text rows become invisible (out of screen). This issue was fixed in 3.34.1, along with two other minor issues and many translation updates. 3.34.2 brings another translation update only. Ubuntu usually aims to ship GNOME x.y.1. I assume there was no particular reason for not updating GNOME Terminal to .1 in this cycle, other than probably lack of time. I sincerely hope that the aforementioned UX regression convinces you to release a last minute fix for 19.10, or an update shortly afterwards. Thanks a lot! https://gitlab.gnome.org/GNOME/gnome-terminal/compare/3.34.0...3.34.2 There is a standing microrelease exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1848156/+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 1849285] Re: [SRU] 3.34.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- 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/1849285 Title: [SRU] 3.34.2 Status in gnome-terminal package in Ubuntu: Confirmed Status in gnome-terminal source package in Eoan: In Progress Bug description: [ Description ] We missed the release with this one, but we ought to catch up with upstream. [ QA ] Uploaded under the GNOME SRU policy exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Please test the terminal keeps working, including changing themes, multiple tabs and whatever else you can think of. [ Regression potential ] The substantive change is around full screen terminals not remaining full screen sometimes. So check that this keeps working and nothing else breaks regarding full screening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1849285/+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 1849285] Re: [SRU] 3.34.2
** Tags added: eoan upgrade-software-version -- 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/1849285 Title: [SRU] 3.34.2 Status in gnome-terminal package in Ubuntu: Confirmed Status in gnome-terminal source package in Eoan: In Progress Bug description: [ Description ] We missed the release with this one, but we ought to catch up with upstream. [ QA ] Uploaded under the GNOME SRU policy exception. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Please test the terminal keeps working, including changing themes, multiple tabs and whatever else you can think of. [ Regression potential ] The substantive change is around full screen terminals not remaining full screen sometimes. So check that this keeps working and nothing else breaks regarding full screening. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1849285/+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 1043336] Re: Swiss keyboard layout with Apple keyboard (period instead of comma)
For me executing echo 0 | sudo tee /sys/module/hid_apple/parameters/iso_layout Fixes the issue temporarily. Inserting this into /etc/modprobe.d/hid_apple.conf: options hid_apple iso_layout=0 Doesn't fix the issue after reboot: cat /sys/module/hid_apple/parameters/iso_layout 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/1043336 Title: Swiss keyboard layout with Apple keyboard (period instead of comma) Status in gnome-control-center package in Ubuntu: Confirmed Bug description: It is a known bug that two keys on an Apple keyboard are swapped. There is another bug which occurs on Swiss keyboards with an Apple model. In Switzerland people have a period instead of a comma on their numpad. Also there is something weird with the default mapping of the upper left key below "ESC". To correct this there is a workaround with xmodmap: keycode 91 = period period keycode 94 = section degree I think this is not the best solution so I report this as a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1043336/+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 1847551] Re: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions
** Merge proposal linked: https://code.launchpad.net/~vanvugt/ubuntu/+source/mutter/+git/mutter/+merge/374507 -- 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/1847551 Title: Mutter 3.34.1 broke Night Light, screen color profiles in Wayland sessions Status in Mutter: Fix Released Status in mutter package in Ubuntu: In Progress Bug description: Upgrading Mutter 3.34.0 to 3.34.1 has broken Night Light and screen color profile switching. The commit at fault is 104bdde746c9ceccd9e9ab09b22ef228b8f7026e “kms: Predict state changes when processing update” (which was intended to fix LP bug 1847044). Upstream issue: https://gitlab.gnome.org/GNOME/mutter/issues/851 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1847551/+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
