[Desktop-packages] [Bug 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines
@Francis I've confirmed that the DUT has already used the latest ubuntu-drivers from proposed. Setting up ubuntu-drivers-common (1:0.9.0~0.20.04.8) ... But it doesn't seem to solve the issue. Please check following messages. + _run sudo ubuntu-drivers devices + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@10.102.153.239 sudo ubuntu-drivers devices WARNING:root:_pkg_get_support nvidia-driver-525: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535-open: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-525-server: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535-server-open: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-525-open: package has invalid Support PBheader, cannot determine support level WARNING:root:_pkg_get_support nvidia-driver-535-server: package has invalid Support PBheader, cannot determine support level == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd2191sv1028sd0949bc03sc00i00 vendor : NVIDIA Corporation model: TU116M [GeForce GTX 1660 Ti Mobile] driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-535 - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525-server - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-535-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-modules-nvidia-535-server-open-generic : Depends: linux-modules-nvidia-535-server-open-5.4.0-173-generic (= 5.4.0-173.191) but it is not going to be installed E: Unable to correct problems, you have held broken packages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2044973 Title: ubuntu-drivers install the wrong version of Nvidia driver on some machines Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: During the SRU testing, I found some of machines installed the wrong version of Nvidia driver. They shouldn't install nvidia-driver-535-server-open on a desktop. Please have a look, thanks. If you want to have more information, please let me know. + _run sudo ubuntu-drivers devices + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@10.102.154.51 sudo ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1FB8sv1028sd0906bc03sc02i00 vendor : NVIDIA Corporation model: TU117GLM [Quadro T2000 Mobile / Max-Q] driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-535 - distro non-free driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-525-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2044973/+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 2054769] Re: Boot animation and login screen use different display scales
Fix proposed: https://gitlab.freedesktop.org/plymouth/plymouth/-/merge_requests/307 -- 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/2054769 Title: Boot animation and login screen use different display scales Status in mutter package in Ubuntu: Won't Fix Status in plymouth package in Ubuntu: In Progress Bug description: Boot animation and login screen use different display scales, on some (not many) machines. For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale 2 for the boot screen while GNOME selects scale 1 for the login screen. This means the Ubuntu logo shrinks. I've tried a few laptops and so far it's only the Surface Laptop 4 that has the problem: 13.5" 2256x1504, 201 PPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054769/+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 2051838] Re: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send
Also have this issue (100% cpu usage by /usr/sbin/rsyslogd) with Firefox in Sway on Ubuntu 22.04. So far I've only noticed this after reloading the sway config (`swaymsg reload` or Mod+Shift+c). Fabien (afabien) wrote: > To avoid having disk full problems, I used the following workaround: > > I created a file /etc/rsyslog.d/10-no-gdm-wayland.conf > Containing the following lines: > :msg, contains, "Error: WaylandMessage::Write() too many files to send" ~ > :msg, contains, " :" ~ > > And then restarted rsyslog (as root): systemctl restart rsyslog.service This workaround didn't work for me, even after replacing the `~` with `stop`. -- 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/2051838 Title: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send Status in firefox package in Ubuntu: Confirmed Bug description: GDM, or more specifically is flooding systemd journal and /var/log/syslog via rsyslogd with gigabytes of the following messages: Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send I noticed the problem when I started to run out of disk because /var/log/syslog was consuming more than 400GiB. I noticed that rsyslogd starts to consume a lot of CPU trying to process such volume of messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051838/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.
** Description changed: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to - the end of the upgrade, I got an „Oh, no! [something, I do not remember] - and the system cannot recover. Call the system administrator” message - after a red FAILED in the terminal. The system administrator is myself, + the end of the upgrade, I got an „Oh, no! Something has gone wrong and + the system cannot recover. Call the system administrator” message after + a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half our to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: - default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 - 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 - 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown + default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 + 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 + 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: network-manager UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago) modified.conffile..etc.init.d.apport: [modified] mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00 nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.45.90 connected started full enabled enabled enabled missing enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.45.90 connected started full enabled enabled enabled missing enabled ** Tags added: network-manager -- 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/2055012 Title: When I upgraded from 22.04 to 24.04, DNS resolution went wrong. Status in network-manager package in Ubuntu: New Bug description: I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to the end of the upgrade, I got an „Oh, no! Something has gone wrong and the system cannot recover. Call the system administrator” message after a red FAILED in the terminal. The system administrator is myself, because my computer is a personal one. Hard reset, same error, Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish the update with dpkg. While dpkg was upgrading, it printed an error message for every WiFi connection: „[Failed] Failed to migrate [I do not remember, something with /etc/netplan]” It took at least one and a half our to find the solution on Ask Ubuntu. The problem was: /etc/resolv.conf became a broken link, along with systemd-resolve.service. I needed to remove both of them and write a new resolv.conf to fix the error. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: network-manager 1.45.90-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 08:21:02 2024 InstallationDate: Installed on 2023-07-05 (236 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) IpRoute: default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600 192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 600 192.168.122.0/24 dev
[Desktop-packages] [Bug 2055037] Re: My screen radomly starts flickering
There are lots of amdgpu errors in your system log, so let's start there. ** Tags added: amdgpu ** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (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/2055037 Title: My screen radomly starts flickering Status in linux-hwe-6.5 package in Ubuntu: Incomplete Bug description: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of error, a black screen with a few lines at the top. Selecting "Start linux mint in compatability mode" does boot to mint but then the trackpad does not work. I have included this reference to Linux Mint as I believe mint is based on Ubuntu. Many thanks, Nick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:33:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39ec] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [17aa:39ec] InstallationDate: Installed on 2024-02-24 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 81MT ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=e078d5fc-6eaf-4e92-9388-969fa8b6f6db ro 1915.enable_psr=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2021 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN27WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.27 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN27WW(V2.06):bd01/12/2021:br2.27:efr2.27:svnLENOVO:pn81MT:pvrLenovoV145-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2055037/+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 2055032] Re: SEG/11 in Wayland _st_theme_get_matched_properties()
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, processing it in order to get sufficient information for the developers failed (it does not generate an useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report. Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Tags added: jammy ** Description changed: Crashed after unlocking session from being away for a couple days. - Crash report ID is c81ddc34-d487-11ee-ba77-fa163e171f02 + Crash report ID is https://errors.ubuntu.com/oops/c81ddc34-d487-11ee- + ba77-fa163e171f02 ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/2055032 Title: SEG/11 in Wayland _st_theme_get_matched_properties() Status in gnome-shell package in Ubuntu: Invalid Bug description: Crashed after unlocking session from being away for a couple days. Crash report ID is https://errors.ubuntu.com/oops/c81ddc34-d487-11ee- ba77-fa163e171f02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2055032/+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 1861609] Re: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRI
** Tags added: bionic jammy mantic noble ** Summary changed: - Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper + Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] ** Description changed: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. - and call stack comes from DRIMoveBuffersHelper - WORKAROUND Select 'Ubuntu on Wayland' on the login screen. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1861609 Title: Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] Status in X.Org X server: New Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg crashed with assertion failure (usually in a VM): privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. WORKAROUND Select 'Ubuntu on Wayland' on the login screen. To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1861609/+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 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 ** This bug has been marked a duplicate of bug 1861609 Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in xorg-server package in Ubuntu: Confirmed Bug description: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. This actually seems to happen most frequently in VirtualBox. WORKAROUND: Select "Ubuntu on Wayland" from the login screen before logging in. --- It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
[Desktop-packages] [Bug 2055103] Re: /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 ** This bug has been marked a duplicate of bug 1861609 Xorg crashed with assertion failure (usually in a VM) at [privates.h:121/122: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2055103 Title: /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.1-3ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/e0bf19ca61a90032292ab167b4009523a9684945 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2055103/+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 2055103] [NEW] /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.1-3ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/e0bf19ca61a90032292ab167b4009523a9684945 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic jammy kinetic kylin-18.04 kylin-22.04 kylin-23.04 lunar mantic noble zesty -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2055103 Title: /usr/lib/xorg/Xorg:Xorg: ../../../../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in xorg-server package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding xorg-server. This problem was most recently seen with package version 2:1.20.1-3ubuntu2.1, the problem page at https://errors.ubuntu.com/problem/e0bf19ca61a90032292ab167b4009523a9684945 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2055103/+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 2054924] Re: color emoji are broken with fontconfig 2.15
The workaround detailed upstream works for me - removing /etc/fonts/conf.d/70-no-bitmaps.conf and re-generating your fonts cache. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/2054924 Title: color emoji are broken with fontconfig 2.15 Status in Fontconfig: Fix Released Status in fontconfig package in Ubuntu: Triaged Status in fonts-noto-color-emoji package in Ubuntu: Triaged Status in fontconfig package in Debian: New Bug description: The Noto Color Emoji font is no longer used to show emoji. Many emoji no longer show and the few that do are not in color. To manage notifications about this bug go to: https://bugs.launchpad.net/fontconfig/+bug/2054924/+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 2053207] Re: glib requires gobject-introspection >= 1.78.1-13
** Changed in: glib2.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2053207 Title: glib requires gobject-introspection >= 1.78.1-13 Status in glib2.0 package in Ubuntu: Fix Released Status in gobject-introspection package in Ubuntu: Fix Released Bug description: glib2.0 2.79.1-1 requires gobject-introspection >= 1.78.13 to migrate out of noble-proposed before or at the same as glib2.0. I'm filing this bug to explain why glib2.0 isn't migrating despite the excuses page saying "Will attempt migration" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2053207/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
This bug was fixed in the package ghostwriter - 23.08.5+ds-0ubuntu1 --- ghostwriter (23.08.5+ds-0ubuntu1) noble; urgency=medium * New upstream release (23.08.5) ghostwriter (23.08.4+ds-0ubuntu2) noble; urgency=medium * Add apparmor profile to fix userns. (LP: #2046844) -- Scarlett Moore Thu, 22 Feb 2024 09:31:12 -0700 ** Changed in: ghostwriter (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Released Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2054183] Re: nautilus not generating thumbnails anymore
the solution to not lose the configuration after the reboot : sudo nano /etc/rc.local The bash: #!/bin/bash # Votre commande ici sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 sudo chmod +x /etc/rc.local -- 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/2054183 Title: nautilus not generating thumbnails anymore Status in nautilus package in Ubuntu: Confirmed Bug description: After the upgrade to 24.04, nautilus is not generating thumbnails for new files. Old thumbnails are displayed ok. I cleaned out $HOME/.cache/thumbnails/ and found that only a subdirectory "fail" is being generated. It contains a subdirectory "gnome-thumbnail-factory" which in turn contains lots of PNG files: ece577c54f5ca98e1f7aaa5b4e932aa4.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ee638c64b1c285684412717bf120e295.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ef811735cfb8e69447b5d3a53f361c63.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0b3ab2f77c342daa3579bfcf9c72481.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced f0ddb101b8342e4b298b4c7121881422.png: PNG image data, 1 x 1, 8-bit/color RGBA, non-interlaced ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: nautilus 1:45.2.1-4ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu6 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Feb 17 08:49:55 2024 EcryptfsInUse: Yes InstallationDate: Installed on 2019-04-16 (1767 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nautilus UpgradeStatus: Upgraded to noble on 2024-02-14 (3 days ago) usr_lib_nautilus: file-roller 43.1-1 nautilus-extension-gnome-terminal 3.49.92-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2054183/+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 2055088] [NEW] debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie
Public bug reported: d/control is used on the official gtk desktops such as budgie. budgie-desktop for noble now uses budgie-session instead of gnome- session. software-properties needs an update to its dependency list ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: noble ** Tags added: noble -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/2055088 Title: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie Status in software-properties package in Ubuntu: New Bug description: d/control is used on the official gtk desktops such as budgie. budgie-desktop for noble now uses budgie-session instead of gnome- session. software-properties needs an update to its dependency list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055088/+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 2044973] Re: ubuntu-drivers install the wrong version of Nvidia driver on some machines
@kevinyew, @shanew, It looks like you are hitting this on focal. Can you please confirm? If so, can you please retest with the latest ubuntu-drivers from focal- proposed? This should be version 1:0.9.0~0.20.04.8. This appears to fix a bug (discussed in https://bugs.launchpad.net/ubuntu/+source/nvidia- graphics-drivers-515/+bug/1988836) which caused the -open drivers to be preferred. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/2044973 Title: ubuntu-drivers install the wrong version of Nvidia driver on some machines Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: During the SRU testing, I found some of machines installed the wrong version of Nvidia driver. They shouldn't install nvidia-driver-535-server-open on a desktop. Please have a look, thanks. If you want to have more information, please let me know. + _run sudo ubuntu-drivers devices + ssh -t -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null ubuntu@10.102.154.51 sudo ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd1FB8sv1028sd0906bc03sc02i00 vendor : NVIDIA Corporation model: TU117GLM [Quadro T2000 Mobile / Max-Q] driver : nvidia-driver-535-server - distro non-free driver : nvidia-driver-535 - distro non-free driver : nvidia-driver-418-server - distro non-free driver : nvidia-driver-525 - distro non-free driver : nvidia-driver-535-open - distro non-free driver : nvidia-driver-470 - distro non-free driver : nvidia-driver-450-server - distro non-free driver : nvidia-driver-535-server-open - distro non-free recommended driver : nvidia-driver-470-server - distro non-free driver : nvidia-driver-525-open - distro non-free driver : nvidia-driver-525-server - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2044973/+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 2049555] Re: [SOF - sof-bytcht rt5640, playback] fails after a while
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/2049555 Title: [SOF - sof-bytcht rt5640, playback] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: Playing music or watching videos for couple minutes, like on Youtube. Sound will be cracked with long beep. And player will be stopped. But if I reload the page, sound will be resumed again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Jan 16 22:44:25 2024 InstallationDate: Installed on 2024-01-14 (1 days ago) InstallationMedia: Xubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller - Intel HDMI/DP LPE Audio Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [SOF - sof-bytcht rt5640, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/20/2015 dmi.bios.release: 1.10 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Gummi CHT dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd11/20/2015:br1.10:svnAcer:pnAspireSW3-016P:pvrV1.10:rvnAcer:rnGummiCHT:rvrV1.10:cvnAcer:ct9:cvrChassisVersion:skuAspireSwitch10E_106E_1.10: dmi.product.family: CHT-CR dmi.product.name: Aspire SW3-016P dmi.product.sku: Aspire Switch 10 E_106E_1.10 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049555/+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 1961508] Re: Dock displaying over window after resuming from blank screen
The workaround from #71 worked almost perfectly out of the box, I've only seen 1-2 windows staying under the dock. I probably simply need bump the delay a bit from the default value. Thanks a lot @popov895. @ballogy, thanks for working on this with upstream! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1961508 Title: Dock displaying over window after resuming from blank screen Status in Dash to dock: Unknown Status in Mutter: New Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: In Progress Status in gnome-desktop package in Fedora: Confirmed Bug description: I have Blank Screen set to happen after 2 minutes of inactivity. When resuming from a Blank Screen (by moving the mouse or touching the keyboard), the Dock is displayed over the top of the current program. To get it back to normal I need to click "Restore Down" on the current programs window and then "Maximize" so that the Dock no longer overlaps it. (Note: I have Auto-hide dock turned off.) This only happens sometimes. I can't reproduce the bug it every time. - 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu - Ubuntu 21.10 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center - Not sure (I guess the Dock is part of the Gnome interface?) 3) What you expected to happen - Dock should not overlap the current program on resume from screen blank. 4) What happened instead - The Dock overlaps the current program on resume from screen blank. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2022-02-18 (24 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: gnome-shell-extension-ubuntu-dock PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 RelatedPackageVersions: mutter-common 40.5-1ubuntu3~21.10.1 Tags: wayland-session impish Uname: Linux 5.13.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2022-02-18 (328 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Package: mutter PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.19.0-28.29-generic 5.19.17 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 43.0-1ubuntu4 Tags: wayland-session third-party-packages kinetic Uname: Linux 5.19.0-28-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-25 (79 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1961508/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
** Merge proposal linked: https://code.launchpad.net/~p-pisati/britney/+git/hints-ubuntu/+merge/461043 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bubblewrap in Ubuntu. https://bugs.launchpad.net/bugs/2046844 Title: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP Status in akonadiconsole package in Ubuntu: Fix Released Status in akregator package in Ubuntu: Fix Released Status in angelfish package in Ubuntu: In Progress Status in apparmor package in Ubuntu: Fix Released Status in bubblewrap package in Ubuntu: Confirmed Status in cantor package in Ubuntu: Fix Released Status in devhelp package in Ubuntu: Fix Released Status in digikam package in Ubuntu: Fix Released Status in epiphany-browser package in Ubuntu: Fix Released Status in evolution package in Ubuntu: Fix Released Status in falkon package in Ubuntu: Fix Released Status in freecad package in Ubuntu: Confirmed Status in ghostwriter package in Ubuntu: Fix Committed Status in gnome-packagekit package in Ubuntu: Confirmed Status in goldendict-webengine package in Ubuntu: Confirmed Status in kalgebra package in Ubuntu: Fix Released Status in kchmviewer package in Ubuntu: Confirmed Status in kdeplasma-addons package in Ubuntu: Confirmed Status in kgeotag package in Ubuntu: Fix Released Status in kiwix package in Ubuntu: Confirmed Status in kmail package in Ubuntu: Fix Released Status in konqueror package in Ubuntu: Fix Released Status in kontact package in Ubuntu: Fix Released Status in marble package in Ubuntu: Fix Released Status in notepadqq package in Ubuntu: Confirmed Status in opam package in Ubuntu: Fix Released Status in pageedit package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in plasma-welcome package in Ubuntu: Fix Released Status in privacybrowser package in Ubuntu: Confirmed Status in qmapshack package in Ubuntu: Confirmed Status in qutebrowser package in Ubuntu: Confirmed Status in rssguard package in Ubuntu: Confirmed Status in steam package in Ubuntu: Fix Committed Status in supercollider package in Ubuntu: Confirmed Status in tellico package in Ubuntu: Fix Released Bug description: Hi, I run Ubuntu development branch 24.04 and I have a problem with Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get this error $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) $ epiphany bwrap: Creating new namespace failed: Permission denied ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch dbus-proxy: Le processus fils s’est terminé avec le code 1 Trappe pour point d'arrêt et de trace (core dumped) Thanks for your help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/akonadiconsole/+bug/2046844/+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 2055040] Re: Software rendering under Wayland mode
1. Confirmed. 2. I am not able to respond to this question since I have started to use the experimental snap for a while now. The intention was to get the smartcards over OpenSC to work as stated here: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1967632/comments/57 3. Done, please have a look at the attachment. ** Attachment added: "chr.log" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+attachment/5749490/+files/chr.log -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2023322]
Bug driver 470, Nvidia GTX 650 W dniu 26.02.2024 o 04:06, Craig pisze: > (In reply to Michael Catanzaro from comment #62) >> Hi Craig and Thomas (and Emil if you're still around): if you're still >> encountering problems with NVIDIA graphics, please report new a bug and >> leave a comment here linking to the new bug. > My problem was on legacy nvidia driver, and newer versions wouldn't even > start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect > there will be a fix for my old driver anyway. > https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 > ** Attachment added: "Zrzut ekranu z 2024-02-26 14-51-55.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749476/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-51-55.png ** Attachment added: "Zrzut ekranu z 2024-02-26 14-52-37.png" https://bugs.launchpad.net/bugs/2023322/+attachment/5749477/+files/Zrzut%20ekranu%20z%202024-02-26%0A%2014-52-37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning:
[Desktop-packages] [Bug 2045096] Re: Error in network definition: Invalid MAC address 'random'
** Changed in: netplan Status: In Progress => Fix Committed -- 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/2045096 Title: Error in network definition: Invalid MAC address 'random' Status in netplan: Fix Committed Status in netplan.io package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: netplan dose not understand the 'random' key word in 'Cloned MAC address' set by networkmanager. ``` /etc/netplan/90-NM-X.yaml:9:19: Error in network definition: Invalid MAC address 'random', must be XX:XX:XX:XX:XX:XX or XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX macaddress: "random" ^ ``` netplan Version 0.107-5ubuntu2 network-manager Version 1.44.2-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/2045096/+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 2055040] Re: Software rendering under Wayland mode
Correction: Command in 3 should be 'chromium --enable-logging=stderr --v=1 >chr.log 2>&1'. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
Thanks for clarifying. > If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script) 1. Just to confirm, this means that if you just launch the Chromium snap normally, the described behavior happens? Because, as you pointed out, --ozone-platform-hint=auto is a default flag in the launcher, so passing it via command line shouldn't affect the observed behavior. 2. Is the issue something new or was it this way ever since you started using the edge Chromium snap? 3. Can you attach the log generated from running 'chromium --enable- logging=stderr --v=1 2&>1 >chr.log'? ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Tags added: kivu ** Description changed: - Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the - --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as + Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) + with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium (edge channel) with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
The output is: > tracking: latest/edge Exactly, I had the impression that some interactive websites with animations ran particularly slow and the CPU fan began to become very noisy. htop revealed the CPU's load of nearly 100% due to the chromium processes. This was the reason that I have tried to retrieve the same websites on the Firefox browser (always with the official snap and Wayland as a compositing manager) where I hadn't any difficulty at all. So I have checked the chrome://gpu's output and noticed the cause. -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: Incomplete Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2055040] Re: Software rendering under Wayland mode
** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: Incomplete Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2051838] Re: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send
Same problem here. Any suggestions on how I may help fixing this? -- 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/2051838 Title: /usr/libexec/gdm-wayland-session: Error: WaylandMessage::Write() too many files to send Status in firefox package in Ubuntu: Confirmed Bug description: GDM, or more specifically is flooding systemd journal and /var/log/syslog via rsyslogd with gigabytes of the following messages: Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: Error: WaylandMessage::Write() too many files to send Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[283270]: : Jan 31 08:44:26 rivendell /usr/libexec/gdm-wayland-session[285102]: Error: WaylandMessage::Write() too many files to send I noticed the problem when I started to run out of disk because /var/log/syslog was consuming more than 400GiB. I noticed that rsyslogd starts to consume a lot of CPU trying to process such volume of messages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2051838/+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 2055040] [NEW] Software rendering under Wayland mode
What is 'snap info chromium|grep tracking'? > When omitting the parameter or setting it to "X11", HW rendering gets > correctly detected and activated. How did you determine that, was it in about:gpu? -- 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2054769] Re: Boot animation and login screen use different display scales
Turns out we don't need to change mutter at all. I just failed to understand its complicated scale selection rules. I've proposed a simplification to mutter anyway: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3616 but it's no longer required to fix this bug. ** Changed in: mutter (Ubuntu) Status: In Progress => Won't Fix -- 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/2054769 Title: Boot animation and login screen use different display scales Status in mutter package in Ubuntu: Won't Fix Status in plymouth package in Ubuntu: In Progress Bug description: Boot animation and login screen use different display scales, on some (not many) machines. For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale 2 for the boot screen while GNOME selects scale 1 for the login screen. This means the Ubuntu logo shrinks. I've tried a few laptops and so far it's only the Surface Laptop 4 that has the problem: 13.5" 2256x1504, 201 PPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054769/+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 2055040] [NEW] Software rendering under Wayland mode
Public bug reported: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. ** 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/2055040 Title: Software rendering under Wayland mode Status in chromium-browser package in Ubuntu: New Bug description: Under Wayland on Ubuntu 22.04 LTS, If I launch Chromium with the --ozone-platform-hint=wayland or --ozone-platform-hint=auto (as specified in the snap's starter script), the browser always ends up into slow SW rendering. When omitting the parameter or setting it to "X11", HW rendering gets correctly detected and activated. The platform consists of a Dell XPS 13 9360 with an Intel HD Graphics 620 chip running Mesa 23.2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2055040/+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 2023322]
(In reply to Michael Catanzaro from comment #62) > Hi Craig and Thomas (and Emil if you're still around): if you're still > encountering problems with NVIDIA graphics, please report new a bug and > leave a comment here linking to the new bug. My problem was on legacy nvidia driver, and newer versions wouldn't even start. But I now know a workaround (GSK_RENDERER=cairo) and don't expect there will be a fix for my old driver anyway. https://gitlab.gnome.org/GNOME/gtk/-/issues/5858 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yelp in Ubuntu. https://bugs.launchpad.net/bugs/2023322 Title: GTK internal browser does not render with Nvidia drivers Status in Webkit: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-online-accounts package in Ubuntu: Invalid Status in webkit2gtk package in Ubuntu: Fix Released Status in yelp package in Ubuntu: Invalid Status in webkit2gtk package in Debian: Fix Released Bug description: When I go into Settings > Online Accounts > Google, I get to the prompt for email address, once in a while it stops accepting input there. But often I can get to the password screen. Once I do, I can't type anything or paste anything. This is a fresh install of Ubuntu 23.04 and I have installed all updates. Nothing in /var/crash Jun 08 11:15:59 CCW-HAL systemd[3523]: vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time. Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 'closure->ref_count > 0' failed Jun 08 11:16:29 CCW-HAL systemd[3523]: Started app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell. Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Activating via systemd: service name='org.gnome.Terminal' unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 comm="/usr/bin/gnome-terminal.real" label="unconfined") Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service - GNOME Terminal Server... Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] Successfully activated service 'org.gnome.Terminal' Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service - GNOME Terminal Server. Jun 08 11:16:29 CCW-HAL systemd[3523]: Started vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 launched by gnome-terminal-server process 10931. Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child process exited with code 1 Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found default implementation dconf (DConfSettingsBackend) for ‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - kerberosGoaBackend: activated kerberos providerGLib-GIO: _g_io_module_get_default: Found default implementation gnutls (GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was dismissed Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0) Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report /etc/cron.hourly) Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed for user root Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 (core 2, socket 0) Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 0x55bd22ad9ab2. Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an override-redirect window and this is not correct according to the standard, so we'll fallback to the first non-override-redirect window 0x3a006dc. Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - Cleanup of Temporary Directories... Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully. Jun 08 11:17:42
[Desktop-packages] [Bug 2055037] [NEW] My screen radomly starts flickering
Public bug reported: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of error, a black screen with a few lines at the top. Selecting "Start linux mint in compatability mode" does boot to mint but then the trackpad does not work. I have included this reference to Linux Mint as I believe mint is based on Ubuntu. Many thanks, Nick. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:33:11 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Lenovo Stoney [Radeon R2/R3/R4/R5 Graphics] [17aa:39ec] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445 / 530/535 / 620/625 Mobile] [17aa:39ec] InstallationDate: Installed on 2024-02-24 (1 days ago) InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220) MachineType: LENOVO 81MT ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=e078d5fc-6eaf-4e92-9388-969fa8b6f6db ro 1915.enable_psr=0 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/12/2021 dmi.bios.release: 2.27 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN27WW(V2.06) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.27 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN27WW(V2.06):bd01/12/2021:br2.27:efr2.27:svnLENOVO:pn81MT:pvrLenovoV145-15AST:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- 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/2055037 Title: My screen radomly starts flickering Status in xorg package in Ubuntu: New Bug description: Hello, I recently installed Ubuntu 22.04.4 on a Lenovo V145-15AST laptop. Randomly, the screen will start flickering. I have found that pulling the power cable out sometimes solves the issue ! But even so, with the power cable out the screen can still start flickering. It's completely random, but very distracting. I am treating this as a bug as I have looked at the options in "Settings > Screen Display" and non of those seem to make any difference. Also I previously tried to install Linux Mint 21.3 and in that case, while booting from the usb stick, I got the welcome to linux mint menu which allows me various options and I select "Start Linux Mint" After that the spinning mint logo appears, then a small mouse pointer on a black screen then the screen goes into some sort of
[Desktop-packages] [Bug 2055010] Re: Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well
Sorry, there is a mistake in my bug report: the critical GTK error
occurs when I close gedit.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2055010
Title:
Gedit has an invalid regular expression, the error is not fatal, but
immediately occurs at its start, additionally, it has a critical level
GTK error as well
Status in gedit package in Ubuntu:
New
Bug description:
When the unstable sudo apt-get autoremove removed Gedit, I reinstalled
it (with the removed necessary Python packages). When I started it first time
from the terminal, I got the following message:
/usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py:212:
SyntaxWarning: invalid escape sequence '\-'
RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')
I was able to fix that with replacing \- to \\-, \[ to \\[ and \] to
\\], but an average user will have extreme computer rage from it and
s/he will shoot the computer. And, in addition, this problem probably
makes gedit less efficient.
The huger problem is:
„(gnome-text-editor:31580): Gtk-CRITICAL **: 07:40:03.163:
gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed”
Imagine it circa 1000 times.
I attached a quick-and-dirty patch to the first problem.
The additional necessary information has been included by apport.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.1-3 [modified:
usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py]
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 08:04:39 2024
InstallationDate: Installed on 2023-07-05 (236 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2055010/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1
** Changed in: policykit-1 (Ubuntu) Importance: Undecided => High -- 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/2054716 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 Status in policykit-1 package in Ubuntu: Confirmed Bug description: I was working on recreating bug 2054319 and did so by modifying my /etc/apt/sources.list file from jammy to noble and installing polkit and all its dependencies. bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic linux-headers-6.5.0-14-generic linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic linux-modules-extra-6.2.0-36-generic linux-modules-extra-6.5.0-14-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 locales systemd systemd-dev systemd-oomd systemd-resolved systemd-sysv systemd-timesyncd udev Suggested packages: glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container systemd-homed systemd-userdbd systemd-boot libqrencode4 libtss2-rc0 Recommended packages: libnss-nis libnss-nisplus The following NEW packages will be installed: libduktape207 libsystemd-shared systemd-dev systemd-resolved The following packages will be upgraded: gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 libsystemd0 libudev1 libzstd1 locales pkexec policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev 26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded. Need to get 34.9 MB of archives. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: polkitd 124-1 ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Feb 22 08:46:48 2024 ErrorMessage: installed polkitd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-11-02 (112 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.11 SourcePackage: policykit-1 Title: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054851] Re: [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference()
As a workaround, if anyone needs it, i can get into GUI using recovery mode (no driver loaded) -- 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/2054851 Title: [radeon] gnome-shell (and Xorg) crashes with SIGSEGV in radeon_bo_reference() Status in Mesa: New Status in mesa package in Ubuntu: Confirmed Bug description: Idont know ProblemType: Crash DistroRelease: Ubuntu 24.04 Package: gnome-shell 45.3-1ubuntu1 ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3 Uname: Linux 6.6.0-14-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Feb 23 10:38:05 2024 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2023-10-01 (146 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=es_CO.UTF-8 LANGUAGE=es_CO:es PATH=(custom, no user) SHELL=/bin/false XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 45.3-1ubuntu1 Signal: 11 SignalName: SIGSEGV SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so Title: gnome-shell crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2054851/+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 2055032] [NEW] SEG/11 in Wayland _st_theme_get_matched_properties()
Public bug reported: Crashed after unlocking session from being away for a couple days. Crash report ID is c81ddc34-d487-11ee-ba77-fa163e171f02 ** Affects: mutter (Ubuntu) Importance: Undecided Status: 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/2055032 Title: SEG/11 in Wayland _st_theme_get_matched_properties() Status in mutter package in Ubuntu: New Bug description: Crashed after unlocking session from being away for a couple days. Crash report ID is c81ddc34-d487-11ee-ba77-fa163e171f02 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055032/+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 2042859] Re: [snap] Firefox snap cannot use kerberos authentication
In bug #1970182 there is a workaround for the issue: adding something
similar to
default_ccache_name = FILE:/home/%{username}/krb5cc
under [libdefaults] will make the ticket store visible to firefox and,
thus, fix the authentication.
--
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/2042859
Title:
[snap] Firefox snap cannot use kerberos authentication
Status in firefox package in Ubuntu:
Confirmed
Bug description:
Applies to Ubuntu 22.04 and any other versions where firefox runs as snap:
firefox:
Installed: 1:1snap1-0ubuntu2
Candidate: 1:1snap1-0ubuntu2
Version table:
*** 1:1snap1-0ubuntu2 500
500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/statu
You can configure Firefox to use negotiate authentication with kerberos.
https://people.redhat.com/mikeb/negotiate/ on how to do this.
To use kerberos auth, Firefox needs to read kerberos ticket cache, default
to /tmp/krb5cc_${id -u}. Since Firefox runs as a snap in 22.04, and possibly
other versions, it cannot read this cache, and thus cannot use kerberized
authentication.
Firefox installed as native application works as expected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2042859/+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 2054769] Re: Boot animation and login screen use different display scales
** Changed in: plymouth (Ubuntu) Status: Opinion => In Progress -- 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/2054769 Title: Boot animation and login screen use different display scales Status in mutter package in Ubuntu: In Progress Status in plymouth package in Ubuntu: In Progress Bug description: Boot animation and login screen use different display scales, on some (not many) machines. For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale 2 for the boot screen while GNOME selects scale 1 for the login screen. This means the Ubuntu logo shrinks. I've tried a few laptops and so far it's only the Surface Laptop 4 that has the problem: 13.5" 2256x1504, 201 PPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054769/+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 2054890] Re: freezes on ubuntu 24.04
*** This bug is a duplicate of bug 2054851 *** https://bugs.launchpad.net/bugs/2054851 As a workaround, if anyone needs it, i can get into GUI using recovery mode -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2054890 Title: freezes on ubuntu 24.04 Status in xorg-server package in Ubuntu: Incomplete Bug description: i cannot start GUI, mouse cursor gets stuck when starting it, before reaching lightdm greeter display. The only way to restart is the REISUB keyboard sequence. xorg.0.log attached Ubuntu 24.04 LTS kernel 6.6.15 mainstream (not ubuntu specific) hardware: Acer E1-522 laptop AMD A6-5200 4-core CPU with AMD Radeon 8400HD GPU 16 GB DDR3 RAM Server does not close flawlessly but freezes system, other than the REISUB escape sequence --- ProblemType: Bug .tmp.unity_support_test.1: ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: 2023-12-31 00:30:04,259 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: noble DistroRelease: Ubuntu 24.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8400 / R3 Series] [1002:9830] (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Kabini [Radeon HD 8400 / R3 Series] [1025:076b] InstallationDate: Installed on 2014-03-28 (3621 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140323) MachineType: Acer Aspire E1-522 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.6.15-060615-generic root=UUID=90a6e034-b9b7-4179-9423-503011e8fcf5 ro recovery nomodeset dis_ucode_ldr Tags: noble ubuntu regression reproducible Uname: Linux 6.6.15-060615-generic x86_64 UpgradeStatus: Upgraded to noble on 2023-12-30 (56 days ago) UserGroups: adm audio boinc cdrom dip libvirt lpadmin plugdev sambashare sudo video wireshark _MarkForUpload: True dmi.bios.date: 11/19/2013 dmi.bios.release: 2.9 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.09 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Aspire E1-522 dmi.board.vendor: Acer dmi.board.version: V2.09 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.09 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.09:bd11/19/2013:br2.9:efr1.13:svnAcer:pnAspireE1-522:pvrV2.09:rvnAcer:rnAspireE1-522:rvrV2.09:cvnAcer:ct10:cvrV2.09:skuAspireE1-522_076B_2.09: dmi.product.family: Kabini dmi.product.name: Aspire E1-522 dmi.product.sku: Aspire E1-522_076B_2.09 dmi.product.version: V2.09 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu6 version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.1.9~kisak1~j version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 xserver.bootTime: Sun Feb 25 11:33:45 2024 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:21.1.11-2ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2054890/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
** Changed in: ubuntu-z-systems Status: Opinion => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2054887] Re: Grahpical bugs caused by unable to access libdrm
Looks like GPU indeed, can you confirm with --disable-gpu? What is 'snap list|grep ^gnome' and 'snap connections chromium'? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: New Bug description: The chromium snap package has a bunch of graphical glitches that makes the program unusable. This appears to be caused by the snap package being unable to access the libdrm directory. Below is the output I get when launching the program. I have confirmed I have libdrm installed and the amdgpu.ids file is present on my system. Using a normal version of Chromium (not a snap) works as expected so I believe there is an issue with the snap package. /usr/share/libdrm/amdgpu.ids: No such file or directory [6505:6505:0224/105129.482765:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented System and snap info Chromium Snap version: latest/stable:122.0.6261.57 Linux 6.5.0-21-generic #21~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 9 13:32:52 UTC 2 x86_64 x86_64 x86_64 GNU/Linux PRETTY_NAME="Ubuntu 22.04.4 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.4 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054887/+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 2055010] Re: Gedit has an invalid regular expression, the error is not fatal, but immediately occurs at its start, additionally, it has a critical level GTK error as well
The attachment "library.py" seems to be a patch. If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gedit in Ubuntu.
https://bugs.launchpad.net/bugs/2055010
Title:
Gedit has an invalid regular expression, the error is not fatal, but
immediately occurs at its start, additionally, it has a critical level
GTK error as well
Status in gedit package in Ubuntu:
New
Bug description:
When the unstable sudo apt-get autoremove removed Gedit, I reinstalled
it (with the removed necessary Python packages). When I started it first time
from the terminal, I got the following message:
/usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py:212:
SyntaxWarning: invalid escape sequence '\-'
RE_KEY = re.compile('^([a-zA-Z_][a-zA-Z0-9_.\-]*)(\[([a-zA-Z_@]+)\])?$')
I was able to fix that with replacing \- to \\-, \[ to \\[ and \] to
\\], but an average user will have extreme computer rage from it and
s/he will shoot the computer. And, in addition, this problem probably
makes gedit less efficient.
The huger problem is:
„(gnome-text-editor:31580): Gtk-CRITICAL **: 07:40:03.163:
gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed”
Imagine it circa 1000 times.
I attached a quick-and-dirty patch to the first problem.
The additional necessary information has been included by apport.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: gedit 46.1-3 [modified:
usr/lib/x86_64-linux-gnu/gedit/plugins/externaltools/library.py]
ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
Uname: Linux 6.6.0-14-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 08:04:39 2024
InstallationDate: Installed on 2023-07-05 (236 days ago)
InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=
SourcePackage: gedit
UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/2055010/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)
I've added a section to the release notes summing this up and linking back here and to some of the past links. ** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1833322 Title: Please consider no more having irqbalance enabled by default (per image/use-case/TBD) Status in cloud-images: New Status in Release Notes for Ubuntu: Fix Released Status in Ubuntu on IBM z Systems: Opinion Status in irqbalance package in Ubuntu: Opinion Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: as per https://github.com/pop-os/default-settings/issues/60 Distribution (run cat /etc/os-release): $ cat /etc/os-release NAME="Pop!_OS" VERSION="19.04" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Pop!_OS 19.04" VERSION_ID="19.04" HOME_URL="https://system76.com/pop; SUPPORT_URL="http://support.system76.com; BUG_REPORT_URL="https://github.com/pop-os/pop/issues; PRIVACY_POLICY_URL="https://system76.com/privacy; VERSION_CODENAME=disco UBUNTU_CODENAME=disco Related Application and/or Package Version (run apt policy $PACKAGE NAME): $ apt policy irqbalance irqbalance: Installed: 1.5.0-3ubuntu1 Candidate: 1.5.0-3ubuntu1 Version table: *** 1.5.0-3ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status $ apt rdepends irqbalance irqbalance Reverse Depends: Recommends: ubuntu-standard gce-compute-image-packages Issue/Bug Description: as per konkor/cpufreq#48 and http://konkor.github.io/cpufreq/faq/#irqbalance-detected irqbalance is technically not needed on desktop systems (supposedly it is mainly for servers), and may actually reduce performance and power savings. It appears to provide benefits only to server environments that have relatively-constant loading. If it is truly a server- oriented package, then it shouldn't be installed by default on a desktop/laptop system and shouldn't be included in desktop OS images. Steps to reproduce (if you know): This is potentially an issue with all default installs. Expected behavior: n/a Other Notes: I can safely remove it via "sudo apt purge irqbalance" without any apparent adverse side-effects. If someone is running a situation where they need it, then they always have the option of installing it from the repositories. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2054941] Re: Chromium does not print out, although printer is visible
** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2054941 Title: Chromium does not print out, although printer is visible Status in chromium-browser package in Ubuntu: New Status in cups package in Ubuntu: New Bug description: Firefox from snap prints OK, but not Chromium. Interesting thing is that printer is visible, but printout is never coming out from the printer, if it is printed from Chromium. I have this problem for longer time, maybe half a year or more. Here are some outputs which could be useful: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy $ uname -v #107-Ubuntu SMP Wed Feb 7 13:26:48 UTC 2024 $ cups.lpstat -p printer HP_LaserJet_Professional_M1132_MFP is idle. enabled since Sun Feb 25 21:20:34 2024 Could not create job on the system's CUPS daemon - No such file or directory $ lpstat -v device for HP_LaserJet_Professional_M1132_MFP: hp:/usb/HP_LaserJet_Professional_M1132_MFP?serial=0XXX $ cups.lpstat -p printer HP_LaserJet_Professional_M1132_MFP is idle. enabled since Sun Feb 25 21:23:45 2024 Could not create job on the system's CUPS daemon - No such file or directory $ snap list | grep cups cups 2.4.7-3 1024 latest/stable openprinting** - $ snap connections cups InterfacePlug Slot Notes avahi-controlcups:avahi-control:avahi-control - cups chromium:cups cups:cups - cups-control - cups:cups-control - cups-control cups:cups-host:cups-control - home cups:home :home - network cups:network :network - network-bind cups:network-bind :network-bind - network-manager-observe cups:network-manager-observe :network-manager-observe - raw-usb cups:raw-usb :raw-usb - system-files cups:etc-cups :system-files - $ ps aux | grep cups-proxyd root7618 0.0 0.1 241736 3300 ?Sl 19:59 0:01 cups-proxyd /var/snap/cups/common/run/cups.sock /var/run/cups/cups.sock -l --logdir /var/snap/cups/1024/var/log This is interesting part of log from /var/log/cups/error_log: E [25/Feb/2024:19:52:33 +0100] [Client 168] Returning IPP client-error-not-possible for CUPS-Create-Local-Printer (ipp://localhost/) from localhost. W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 502 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 503 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Notifier for subscription 505 (dbus://) went away, retrying! W [25/Feb/2024:20:55:05 +0100] Printer drivers are deprecated and will stop working in a future version of CUPS. See https://github.com/OpenPrinting/cups/issues/103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2054941/+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 2054769] Re: Boot animation and login screen use different display scales
It looks like plymouth's threshold for scale 200% is 192 DPI. And gnome- shell's threshold is 135 DPI. Since my laptop with the bug is 201 DPI it should be scale 200% for both mutter and plymouth. I think there's a simple math error in mutter though, leading to 100% being chosen instead of 200%. ** Changed in: plymouth (Ubuntu) Status: Triaged => Invalid ** Changed in: plymouth (Ubuntu) Status: Invalid => Opinion ** Changed in: mutter (Ubuntu) Status: Triaged => In Progress -- 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/2054769 Title: Boot animation and login screen use different display scales Status in mutter package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Opinion Bug description: Boot animation and login screen use different display scales, on some (not many) machines. For example on a Microsoft Surface Laptop 4, Plymouth seems to use scale 2 for the boot screen while GNOME selects scale 1 for the login screen. This means the Ubuntu logo shrinks. I've tried a few laptops and so far it's only the Surface Laptop 4 that has the problem: 13.5" 2256x1504, 201 PPI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054769/+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
