[Desktop-packages] [Bug 2016925] Re: Firefox window is visually corrupted after upgrading to Ubuntu 23.04
** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- 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/2016925 Title: Firefox window is visually corrupted after upgrading to Ubuntu 23.04 Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: New Bug description: After upgrading from Ubuntu 22.10 to Ubuntu 23.04, every time I open firefox the windows is heavily visually corrupted. It seems to work fine under the corruption, but it is completely unusuable. The tar version of Firefox works fine. In the attached screenshot you can see the snap version of Firefox (corrupted) and the tar version of Firefox (working fine). I tried uninstalling (with --purge) and reinstalling and refreshing firefox to no avail. All other applications, including 3D games, are working fine. I am using an AMD RX5500 with default mesa drivers. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: firefox 1:1snap1-0ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 18 18:04:26 2023 InstallationDate: Installed on 2020-11-04 (895 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SnapChanges: IDEstado Generado Listo Resumen 1215 Done2023-04-18T17:42:17-03:00 2023-04-18T17:44:05-03:00 Eliminar snap "firefox" 1216 Done2023-04-18T17:45:37-03:00 2023-04-18T17:47:25-03:00 Instalar snap "firefox" 1217 Done2023-04-18T17:48:16-03:00 2023-04-18T17:48:30-03:00 Eliminar snap "firefox" 1218 Done2023-04-18T17:48:39-03:00 2023-04-18T17:48:49-03:00 Instalar snap "firefox" SourcePackage: firefox UpgradeStatus: Upgraded to lunar on 2023-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2016925/+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 1862713] Re: Failed to verify signature archive-contents.sig
I had the same issue with emacs-nox, but I have installed it on Windows 10 inside of WSL2 with Ubuntu 18.04. I was able to workaround the issue with: gpg --homedir ~/.emacs.d/elpa/gnupg --keyserver hkps://keyserver.ubuntu.com:443 --receive-keys 066DAFCB81E42C40 After successfully importing the key, a package-refresh-contents worked fine. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1862713 Title: Failed to verify signature archive-contents.sig Status in emacs25 package in Ubuntu: Confirmed Bug description: After freshly installing the emacs25-nox package, the very first command I ran was > M-x list-packages Which immediately produced this error. Failed to verify signature archive-contents.sig: No public key for 066DAFCB81E42C40 created at 2020-02-10T16:05:02-0600 using RSA Command output: gpg: Signature made Mon 10 Feb 2020 04:05:02 PM CST gpg:using RSA key C433554766D3DDC64221BFAA066DAFCB81E42C40 gpg: Can't check signature: No public key I have no .emacs or .emacs.d configured - this is a 100% fresh "apt install" of emacs25-nox. I would expect Emacs packaged with Ubuntu to be bundled with a valid key! Also, none of the instructions on the internet actually work on getting this fixed! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: emacs25-nox 25.2+1-6 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 10 20:26:51 2020 InstallationDate: Installed on 2019-12-29 (43 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: emacs25 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1862713/+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 1288786] Re: pkexec does not launch graphical authentication
No, pkexec per default does not start a graphical application for security reasons. If you want to start a graphical application with pkexec, you need a policy in /usr/share/polkit-1/actions. But, nowadays, it mostly isn't necessary to start a graphical application with elevated privileges, because there are better alternatives. On *buntu 18.04, synaptic does have a policy => https://packages.ubuntu.com/bionic/amd64/synaptic/filelist You can start it with synaptic-pkexec. The same command is used in /usr/share/applications/synaptic.desktop If it does not work and you have a policy, please check, that the PolicyKit Authentication Agent is running (lxsession-default-apps in section autostart) and logout/login. I don't understand, how "su -l $other_user" is related to this bug report? -- 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/1288786 Title: pkexec does not launch graphical authentication Status in policykit-1 package in Ubuntu: Confirmed Bug description: Installed Trusty Tahr Lubuntu Beta1 version and added xubuntu desktop. In buth desktops, I tried to launch synaptic to install some packages. If I try to launch from menu, nothing seems to happen. From a terminal, I ran pkexec "/usr/sbin/synaptic" and saw that it asks for password in the terminal window, instead of popping up an authentication window like previous Ubuntu version did. That was why I saw no authentication request when launching from menu.. I have a workaround)launching from Terminal window), but this should be fixed before release. ralph@minnie:~$ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu Trusty Tahr (development branch)" ralph@minnie:~$ pkexec --version pkexec version 0.105 Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1288786/+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
