[Desktop-packages] [Bug 1901586] Re: [snap] CA Certificates from /usr/local/share/ca-certificates are not used
It is sad that snap developers have taken such intrusive decisions by creating yet another isolated certificate infrastructure. The Ubuntu system already has its own infrastructure in /etc/ssl/certs. So, now we have two (besides all the other built-in certificates in various tools and packages). In all honesty, why do snap developers think that their own /snap/core/current/etc/ssl/certs is so much better than the system's /etc/ssl/certs? And not only that, all documented procedures to deal with certificates (like update-ca-certificates) become useless. -- 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/1901586 Title: [snap] CA Certificates from /usr/local/share/ca-certificates are not used Status in chromium-browser package in Ubuntu: Confirmed Bug description: We have a company internal CA and placed its root CA certificate in /usr/local/share/ca-certificates and ran update-ca-certificates. This always worked for chromium based browsers. With chromium-browser as snap in Ubuntu 20.04 this seems to not work any more. Chromium reports invalid certificates as it cannot validate the chain any more. PLease make the snap version of Chromium use the certificates from the system (out of /etc/ssl/certs etc). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Oct 26 18:51:29 2020 InstallationDate: Installed on 2020-09-26 (30 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: chromium-browser 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/1901586/+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 1760849] Re: Login screen appears on only one monitor and it's not the one I want
Another problem with the workaround/fix is that it does NOT work when wayland is enabled for the login screen. You have to uncomment WaylandEnable=false in /etc/gdm3/custom.conf and then systemctl restart gdm. -- 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/1760849 Title: Login screen appears on only one monitor and it's not the one I want Status in GNOME Shell: New Status in gnome-control-center package in Ubuntu: Opinion Status in gnome-shell package in Ubuntu: Triaged Bug description: Upstream bugs: https://gitlab.gnome.org/GNOME/gdm/issues/168 https://gitlab.gnome.org/GNOME/gdm/issues/183 https://gitlab.gnome.org/GNOME/gdm/issues/195 https://gitlab.gnome.org/GNOME/gdm/issues/319 https://gitlab.gnome.org/GNOME/gdm/issues/372 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3867 The Ubuntu login screen is tiled on all displays, not mirrored, making it nearly impossible to login when using an external monitor if the laptop screen is not visible. There appears to be no available control to alter the display settings of the login screen. Prior to bionic, the controls followed the mouse onto different displays so you could login by giving the mouse a swipe to the right to get the controls to appear. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 3 22:13:53 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1760849/+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 1821415] Re: pkexec fails in a non-graphical environment
Can we raise the importance please? It is quite essential to let unprivileged users run certain commands, even if there is not GUI. Also, it is very confusing when everything is configured correctly, plus the password is correct, and then to get the message "Not authorized", "This incident has been reported." -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1821415 Title: pkexec fails in a non-graphical environment Status in PolicyKit: New Status in apport package in Ubuntu: Triaged Status in policykit-1 package in Ubuntu: Triaged Bug description: The plymouth apport source package hooks wants to gather log files as the root user and apport provides a policy kit policy for collecting that information. This works fine in a graphical environment but not in a non-graphical one. N.B. you first need to create a /var/log/plymouth-debug.log file for the plymouth apport package hook to actually trigger this. ubuntu@disco:~$ ubuntu-bug plymouth *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. .. AUTHENTICATING FOR com.ubuntu.apport.root-info === Authentication is required to collect system information for this problem report Authenticating as: Ubuntu (ubuntu) Password: polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie AUTHENTICATION FAILED === Error executing command as another user: Not authorized This incident has been reported. Subsequently, bug reports from servers will contain less information. To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/1821415/+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
