[Desktop-packages] [Bug 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
Jammy fix for bug 2055519 and bug 2055530 ** Patch added: "mutter_42.9-0ubuntu7.debdiff" https://bugs.launchpad.net/mutter/+bug/2055519/+attachment/5751422/+files/mutter_42.9-0ubuntu7.debdiff ** Changed in: mutter (Ubuntu Jammy) Status: Fix Committed => 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: [ Impact ] Mutter's test cases fail on jammy since Mesa got updated: mutter:cogl+cogl/conform / framebuffer-get-bits [ Test Plan ] Build mutter and run its tests (done automatically during packaging) [ Where problems could occur ] More tests fail. [ Other Info ] 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+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 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
Debdiff proposed in https://bugs.launchpad.net/mutter/+bug/2055519/comments/3 ** Changed in: mutter (Ubuntu Jammy) Status: Fix Committed => 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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: [ Impact ] Mutter failed to build, only once, on jammy amd64: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. [ Test Plan ] Build mutter. [ Where problems could occur ] More build failures or accidentally depending on meson features that don't exist in jammy. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+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 2036761] Re: [mantic] ppa-purge no longer purges what add-apt-repository adds
This bug was fixed in the package ppa-purge - 0.2.8+bzr63-0ubuntu2 --- ppa-purge (0.2.8+bzr63-0ubuntu2) noble; urgency=high * Add support for deb822 source format. (LP: #2036761) -- Ghadi Elie Rahme Fri, 02 Feb 2024 17:12:55 +0200 ** Changed in: ppa-purge (Ubuntu Noble) Status: Fix Committed => Fix Released -- 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/2036761 Title: [mantic] ppa-purge no longer purges what add-apt-repository adds Status in ppa-purge package in Ubuntu: Fix Released Status in software-properties package in Ubuntu: Confirmed Status in ppa-purge source package in Mantic: Triaged Status in software-properties source package in Mantic: Confirmed Status in ppa-purge source package in Noble: Fix Released Status in software-properties source package in Noble: Confirmed Bug description: Thank you @jbicha for the original bug report! [ Impact ] Currently ppa-purge fails to purge packages on distribution using the deb822 source format. Currently mantic and noble make use of this format and are affected by this issue. When running ppa-purge to remove a custom PPA, ppa-purge fails to disable the custom PPA since it cannot disable deb822 sources and leads to apt still querying the ppa when running: $ apt update In older versions of ubuntu, PPAs used the ".list" format which could be disabled by simply commenting out the "deb" line with a "#". This was the method that ppa-purge used to disable PPAs. This new patch allows ppa-purge to detect and disable deb822 source files by adding an "Enabled: no" field in each component section of the deb822 file. It also removes any line that starts with "Enabled:" to make sure the resulting file is clean. [ Test Plan ] The changes were tested on both mantic and noble in a lxc container using the oibaf mesa PPA (https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers) as the test PPA. The following steps were recorded in a noble lxc container. - First make sure that mesa-utils is installed in your environment: $ sudo apt update && sudo apt install mesa-utils - Add the oibaf PPA to your system using the following command: $ sudo add-apt-repository ppa:oibaf/graphics-drivers - Make sure that the mesa-utils packages were upgraded after adding the PPA: $ sudo apt update && sudo apt upgrade $ dpkg - l | grep mesa - output should be similar to the following: ii libegl-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the EGL API -- Mesa vendor library ii libgl1-mesa-dri:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 24.1~git2402280600.41722c~oibaf~n amd64free implementation of the OpenGL API -- GLX vendor library ii mesa-utils 9.0.0-2 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd649.0.0-2 amd64Miscellaneous Mesa utilities -- native applications ii mesa-vulkan-drivers:amd64 24.1~git2402280600.41722c~oibaf~n amd64Mesa Vulkan graphics drivers - Install and run ppa-purge: $ sudo apt install ppa-purge $ sudo ppa-purge ppa:oibaf/graphics-drivers - ppa-purge will report at the end that none of the oibaf packages need to be downgraded/removed: libglapi-mesa is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglapi-mesa set to manually installed. libglx-mesa0 is already the newest version (24.1~git2402280600.41722c~oibaf~n). libglx-mesa0 set to manually installed. mesa-vulkan-drivers is already the newest version (24.1~git2402280600.41722c~oibaf~n). mesa-vulkan-drivers set to manually installed. Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-amdgpu1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [all]) for 'libdrm-common' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-intel1' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-nouveau2' Selected version '2.4.120+git2402271331.1b4e04~oibaf~n' (Updated Open Graphics Drivers - since 2011!:24.04/noble [amd64]) for 'libdrm-radeon
[Desktop-packages] [Bug 2055521] Re: Xorg freeze
Hello, thanks for the bug report. I suggest taking your dmesg output (from CurrentDmesg.txt) to the virtualbox developers, it looks very unhappy. Thanks ** Information type changed from Private Security to Public -- 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/2055521 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: System is freeze after opening browsers 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 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 11:59:12 2024 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0ab0] Subsystem: Dell GP107M [GeForce MX350] [1028:0ab0] InstallationDate: Installed on 2023-12-11 (80 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6730 Microdia Integrated_Webcam_HD Bus 001 Device 004: ID 0bda:c829 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 3554:fc03 CX 2.4G Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 3511 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic root=UUID=400f7ddd-5dab-4879-8016-60995117717f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2023 dmi.bios.release: 1.26 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.26.0 dmi.board.name: 0YX04V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.26.0:bd12/19/2023:br1.26:svnDellInc.:pnInspiron153511:pvr:rvnDellInc.:rn0YX04V:rvrA00:cvnDellInc.:ct10:cvr:sku0AB0: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 3511 dmi.product.sku: 0AB0 dmi.sys.vendor: Dell Inc. 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/xorg/+bug/2055521/+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
Also would like to note that tuxedo-control-center, a third-party Electron app for Tuxedo Computers, is affected by this. -- 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: Fix Released 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 geary 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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP
Geary is seeded in Edubuntu as its main email client, so this is definitely something we'd like fixed. ** Also affects: geary (Ubuntu) Importance: Undecided Status: New ** Changed in: geary (Ubuntu) Status: New => Confirmed ** Changed in: geary (Ubuntu) Importance: Undecided => High -- 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: Fix Released 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 geary 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 2052925] Re: lpoptions -d as root
I've successfully tested this package on jammy using -proposed: ubuntu@jammy-vm:~$ lsb_release -rd Description:Ubuntu 22.04.3 LTS Release:22.04 ubuntu@jammy-vm:~$ ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.8 Candidate: 2.4.1op1-1ubuntu4.8 Version table: *** 2.4.1op1-1ubuntu4.8 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages ... root@jammy-vm:~# cat /root/.cups/lpoptions cat: /root/.cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color [...] root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /root/.cups/lpoptions: No such file or directory root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2052925 Title: lpoptions -d as root Status in cups package in Ubuntu: Fix Released Status in cups source package in Jammy: Fix Committed Bug description: Copied from https://github.com/OpenPrinting/cups/issues/454 Yair Yarom submitted Debian bug 1008053 and observed that running lpoptions as root does not update /etc/cups/lpoptions but /root/.cups/lpoptions. Running lpoptions as root (e.g. "lpoptions -d HP-OfficeJet") should update /etc/cups/lpoptions to be the defaults for all users. But instead it tries to update /root/.cups/lpoptions. This has been fixed upstream in cups, in debian sid, and mantic. Proposing to add this change in jammy and older (still supported) series as well. The fix is a one line change in https://github.com/OpenPrinting/cups/pull/456 Thanks. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ubuntu@jammy-vm:~$ lsb_release -rd Description: Ubuntu 22.04.3 LTS Release: 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ubuntu@jammy-vm:~$ apt-cache policy cups cups: Installed: 2.4.1op1-1ubuntu4.7 Candidate: 2.4.1op1-1ubuntu4.7 Version table: *** 2.4.1op1-1ubuntu4.7 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 2.4.1op1-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) What you expected to happen: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /etc/cups/lpoptions Default HP-Officejet-Pro-8710 root@jammy-vm:~# root@jammy-vm:~# cat /root/.cups/lpoptions cat: /etc/cups/lpoptions: No such file or directory root@jammy-vm:~# 4) What happened instead: root@jammy-vm:~# lpstat -p printer HP-Officejet-Pro-8710 is idle. enabled since Thu 01 Feb 2024 03:17:49 PM UTC root@jammy-vm:~# root@jammy-vm:~# lpoptions -d HP-Officejet-Pro-8710 copies=1 device-uri=lpd://10.20.135.153:515/PASSTHRU finishings=3 job-cancel-after=10800 job-hold-until=no-hold job-priority=50 job-sheets=none,none marker-change-time=0 number-up=1 print-color-mode=color printer-commands=none printer-info=HP-Officejet-Pro-8710 printer-is-accepting-jobs=true printer-is-shared=true printer-is-temporary=false printer-location printer-make-and-model='HP Officejet Pro 8710, hpcups 3.21.12' printer-state=3 printer-state-change-time=1706800669 printer-state-reasons=none printer-type=4124 printer-uri-supported=ipp://localhost/printers/HP-Officejet-Pro-8710 root@jammy-vm:~#
[Desktop-packages] [Bug 1218322] Re: Can't set keyboard layout change to alt+shift, ctrl+shift, etc.
Launchpad has imported 6 comments from the remote bug at https://bugzilla.altlinux.org/show_bug.cgi?id=29591. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2013-11-18T17:19:32+00:00 Norbert wrote: Description of problem: In previous GNOME versions (for example, in 3.4) I was able to set keyboard layout switching to Alt+Shift, Ctrl+Shift, both Shifts, etc. In AltLinux p7 I can't set it from gnome-control-center keyboard. This bug come from GNOME. Version-Release number of selected component (if applicable): gnome-control-center 3.8.6-alt0.M70P.1 How reproducible: Go to gnome-control-center keyboard and try to set Alt+Shift or Ctrl+Shift as layout switching keys. Steps to Reproduce: 1. Go to gnome-control-center keyboard (Shortcuts -> Typing) 2. Try to set Alt+Shift or Ctrl+Shift at 'Switch to next input source' 3. Get 'Disabled' in 'Switch to next input source'. If you set default Super+Space - it set and work normally, but it is not comfortable and universal for all users. This bug is very hot in Ubuntu 13.10 too (689 users are affected, see https://bugs.launchpad.net/bugs/1218322), but Canonical fixed it. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1218322/comments/365 On 2013-11-19T09:35:16+00:00 Aris-x wrote: Shortcuts -> Typing -> Modifiers-only switch to next source Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1218322/comments/367 On 2013-11-19T09:52:54+00:00 Norbert wrote: Спасибо, Юрий! Но сочетания Ctrl+Shift+C/V на русской раскладке в терминале и выделение текста по Ctrl+Shift+стрелки не работают если переключение поставлено на привычное Ctrl+Shift. Мне создать новый багрепорт здесь или писать сразу в апстрим? Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1218322/comments/369 On 2013-11-19T11:42:45+00:00 Aris-x wrote: Это у вас с одной стороны не работает, -- используйте другую. В апстрим написать можете, но проще приспособиться. Мне, например, правым Ctrl-ом удобно переключаться. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1218322/comments/371 On 2013-11-19T12:42:09+00:00 Norbert wrote: Спасибо! Действительно "другая сторона" работает. Но в апстрим я все- таки написал (https://bugzilla.gnome.org/show_bug.cgi?id=712667). Этот (29591) баг можем закрывать. Спасибо! Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1218322/comments/372 On 2024-02-29T18:28:11+00:00 Lav-7 wrote: (Ответ для Nikolay Strelkov на комментарий #2) > Спасибо, Юрий! > Но сочетания Ctrl+Shift+C/V на русской раскладке в терминале и выделение > текста по Ctrl+Shift+стрелки не работают если переключение поставлено на > привычное Ctrl+Shift. Мне создать новый багрепорт здесь или писать сразу в > апстрим? Есть задача и патч, исправляющий поведение (делает переключение раскладки при _отжатии_ клавиш): https://bugzilla.altlinux.org/34900 Также эта проблема не актуальна для wayland. Reply at: https://bugs.launchpad.net/ubuntu/+source/gnome-settings- daemon/+bug/1218322/comments/549 ** Changed in: gnome-control-center (ALT Linux) Status: Unknown => Invalid ** Changed in: gnome-control-center (ALT Linux) Importance: Unknown => Medium ** Bug watch added: bugzilla.gnome.org/ #712667 https://bugzilla.gnome.org/show_bug.cgi?id=712667 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1218322 Title: Can't set keyboard layout change to alt+shift, ctrl+shift, etc. Status in GNOME Settings Daemon: Unknown Status in System76: New Status in Ubuntu Flashback: New Status in Ubuntu GNOME: Fix Released Status in Ubuntu GNOME Flashback: New Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-control-center package in ALT Linux: Invalid Status in gnome-control-center package in Baltix: Confirmed Status in gnome-control-center package in Gentoo Linux: Unknown Status in gnome-control-center package in Mandriva: Unknown Bug description: [Impact] Can't set keyboard layout change to Ctrl+Shift, Caps Lock, Alt+Shift, etc. Shift, Caps Lock keys are just ignored in settings. [Test Case] - open
[Desktop-packages] [Bug 2055692] [NEW] crash: malloc(): corrupted top size
Public bug reported: The video player segfaults when being opened with any mp4 video: $ totem vid.mp4 malloc(): corrupted top size Abgebrochen (Speicherabzug geschrieben) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 14:16:46 2024 InstallationDate: Installed on 2021-08-27 (917 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: totem UpgradeStatus: Upgraded to mantic on 2023-11-03 (119 days ago) XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/2055692 Title: crash: malloc(): corrupted top size Status in totem package in Ubuntu: New Bug description: The video player segfaults when being opened with any mp4 video: $ totem vid.mp4 malloc(): corrupted top size Abgebrochen (Speicherabzug geschrieben) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: totem 43.0-2ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-21.21-generic 6.5.8 Uname: Linux 6.5.0-21-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Mar 1 14:16:46 2024 InstallationDate: Installed on 2021-08-27 (917 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: totem UpgradeStatus: Upgraded to mantic on 2023-11-03 (119 days ago) XorgLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/2055692/+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 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
** Tags added: fixed-in-mutter-45.0 fixed-upstream -- 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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Mutter failed to build, only once, on jammy amd64: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. [ Test Plan ] Build mutter. [ Where problems could occur ] More build failures or accidentally depending on meson features that don't exist in jammy. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
** Tags added: fixed-in-mutter-43.8 fixed-upstream -- 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Mutter's test cases fail on jammy since Mesa got updated: mutter:cogl+cogl/conform / framebuffer-get-bits [ Test Plan ] Build mutter and run its tests (done automatically during packaging) [ Where problems could occur ] More tests fail. [ Other Info ] 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+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 2055281] Re: Desktop freeze while navigating the Dash
The problem was exactly from the gsconnect. After removing it, I have no freeze any more. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2055281 Title: Desktop freeze while navigating the Dash Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I open the Dash menu and proceed to navigate through the software icons, after three or four transitions to the next page, the system freezes completely, rendering the keyboard unresponsive. While any ongoing music or video playback continues, I find myself unable to interact with the desktop environment or utilize the keyboard. Consequently, I resort to holding down the power button to forcibly halt the system. Simply pressing the power button typically results in no response, or if any, it's imperceptible due to the system freeze. Description: Ubuntu 22.04.4 LTS Kernel: 6.2.0-39-generic #40~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 16 10:53:04 UTC 2 x86_64 x86_64 x86_64 GNU/Linux I have switched to kernel 6.2 due to some bugs about audio hardware load while using kernel 6.5 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 15:02:38 2024 DisplayManager: gdm3 InstallationDate: Installed on 2023-07-23 (219 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) RelatedPackageVersions: mutter-common 42.9-0ubuntu5 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2055281/+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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
** Changed in: mutter Status: Unknown => Fix Released -- 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Mutter's test cases fail on jammy since Mesa got updated: mutter:cogl+cogl/conform / framebuffer-get-bits [ Test Plan ] Build mutter and run its tests (done automatically during packaging) [ Where problems could occur ] More tests fail. [ Other Info ] 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+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 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
Proposed fixes for the Jammy build failures: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/comments/11 No we didn't cause them :) -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [Impact] On systems equipped with reduced blanking panel, mirror mode can result to no image on external monitor. The reason is due to current fallback modes don't have pixelclock for reduced blanking, so inadequate refresh rate is used to mode set, and result with atomic commit failure. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3449 Add reduced blanking (RB) to fallback modes, so mutter can use RB mode to meet pixelclock requirement in order to pick the right refresh rate. [Test] Connect an external monitor to affected system. Use the monitor hotkey to switch to mirror mode or use GNOME control center to choose mirror mode. With the patch included, the issue is no longer observed. [Where problems could occur] The modelines of reduced blanking have reversed Hsync and Vsync flags, so if the driver doesn't handle those flags correctly, the atomic modeset/commit may fail. I haven't observe any issue on Intel/AMD/Nvidia GPU so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
** Description changed: - 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING + [ Impact ] + + Mutter's test cases fail on jammy since Mesa got updated: + + 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... -Test GL+GLSL GL3 ES2 - test_framebuffer_get_bits: ok FAIL n/a + Test GL+GLSL GL3 ES2 + test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): - File "/<>/src/tests/meta-dbus-runner.py", line 184, in - test_case.wrap_call(rest[1:]) - File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call - self.assertEqual(p.wait(), 0) - File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual - assertion_func(first, second, msg=msg) - File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual - raise self.failureException(msg) + File "/<>/src/tests/meta-dbus-runner.py", line 184, in + test_case.wrap_call(rest[1:]) + File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call + self.assertEqual(p.wait(), 0) + File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual + assertion_func(first, second, msg=msg) + File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual + raise self.failureException(msg) AssertionError: 134 != 0 ―― - 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 - + 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and - - 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING + 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... -Test GL+GLSL GL3 ES2 - test_framebuffer_get_bits: ok FAIL n/a + Test GL+GLSL GL3 ES2 + test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): - File "/<>/src/tests/meta-dbus-runner.py", line 184, in - test_case.wrap_call(rest[1:]) - File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call - self.assertEqual(p.wait(), 0) - File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual - assertion_func(first, second, msg=msg) - File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual - raise self.failureException(msg) + File "/<>/src/tests/meta-dbus-runner.py", line 184, in + test_case.wrap_call(rest[1:]) + File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call + self.assertEqual(p.wait(), 0) + File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual + assertion_func(first, second, msg=msg) + File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual + raise self.failureException(msg) AssertionError: 134 != 0 ―― - 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 + 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 + + [ Test Plan ] + + Build mutter and run its tests (done automatically during packaging)
[Desktop-packages] [Bug 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
** Description changed: + [ Impact ] + + Mutter failed to build, only once, on jammy amd64: + In file included from ../src/backends/meta-backend-private.h:39, - from ../src/backends/x11/meta-backend-x11.h:31, - from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, - from ../src/tests/meta-backend-test.h:23, - from ../src/tests/meta-backend-test.c:22: + from ../src/backends/x11/meta-backend-x11.h:31, + from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, + from ../src/tests/meta-backend-test.h:23, + from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory -41 | #include "meta/meta-enum-types.h" - | ^~~~ + 41 | #include "meta/meta-enum-types.h" + | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. + + [ Test Plan ] + + Build mutter. + + [ Where problems could occur ] + + More build failures or accidentally depending on meson features that + don't exist in jammy. + + [ Other Info ] ** Changed in: mutter (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: [ Impact ] Mutter failed to build, only once, on jammy amd64: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. [ Test Plan ] Build mutter. [ Where problems could occur ] More build failures or accidentally depending on meson features that don't exist in jammy. [ Other Info ] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+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 1959507] Re: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f)
I had this problem on my Ubuntu Noble. Attaching journalctl ** Attachment added: "jjj.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+attachment/5751113/+files/jjj.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1959507 Title: gnome-shell crashed in clutter_actor_get_real_resource_scale() with assertion failed: (guessed_scale >= 1.f) Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hi, I'm starting a VM Ubuntu 22.04 on QEMU/KVM and this alert appears. It seems to myself there is an issue between Wayland and spice-vdagent. Regards, Michel ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 09:52:12 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-01-28 (1 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 41.3-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: __pthread_kill_implementation (no_tid=0, signo=6, threadid=140083783699840) at pthread_kill.c:44 __pthread_kill_internal (signo=6, threadid=140083783699840) at pthread_kill.c:80 __GI___pthread_kill (threadid=140083783699840, signo=signo@entry=6) at pthread_kill.c:91 __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 __GI_abort () at abort.c:79 Title: gnome-shell crashed with SIGABRT in __pthread_kill_implementation() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507/+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 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Here's the fixes for jammy build failures in 42.9-0ubuntu6 ** Patch added: "mutter_42.9-0ubuntu7.debdiff" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2054510/+attachment/5751114/+files/mutter_42.9-0ubuntu7.debdiff -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 1048163] Re: Cannot switch off sticky edges between displays
** Also affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1048163 Title: Cannot switch off sticky edges between displays Status in One Hundred Papercuts: Confirmed Status in Unity: Confirmed Status in gnome-desktop package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Bug description: I switch Sticky edges off in Display but it persists even though the settings stays set as Off. It also makes it difficult to drag a window between monitor displays. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: gnome-control-center 1:3.4.2-0ubuntu14 ProcVersionSignature: Ubuntu 3.5.0-14.15-generic 3.5.3 Uname: Linux 3.5.0-14-generic x86_64 ApportVersion: 2.5.1-0ubuntu7 Architecture: amd64 Date: Sun Sep 9 18:49:00 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to quantal on 2012-07-27 (43 days ago) usr_lib_gnome-control-center: activity-log-manager-control-center 0.9.4-0ubuntu3 deja-dup23.90-0ubuntu1 gnome-control-center-signon 0.0.14-0ubuntu1 indicator-datetime 12.10.0-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1048163/+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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1)
https://salsa.debian.org/gnome- team/mutter/-/commit/9d01e79fa5c26356254df8392ccb5326c8e52637 ** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+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
** Changed in: gedit (Ubuntu)
Assignee: (unassigned) => Zalán Hári (zalanhari)
--
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 2055519] Re: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits
Upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/2848 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2848 https://gitlab.gnome.org/GNOME/mutter/-/issues/2848 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2848 Importance: Unknown Status: Unknown ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => High ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Summary changed: - Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits + Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) -- 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/2055519 Title: Mutter rebuilds on jammy fail test: mutter:cogl+cogl/conform / framebuffer-get-bits (due to Mesa >= 23.1.1) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: In Progress Bug description: 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> RUN_TESTS_QUIET=1 PATH=/usr/lib/s390x-linux-gnu:/<>/obj-s390x-linux-gnu/cogl/cogl:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games MALLOC_PERTURB_=176 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-s390x-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 2.35s exit status 1 and 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits RUNNING >>> MALLOC_PERTURB_=159 PATH=/<>/obj-aarch64-linux-gnu/cogl/cogl:/usr/lib/aarch64-linux-gnu:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games RUN_TESTS_QUIET=1 /<>/src/tests/meta-dbus-runner.py /<>/cogl/tests/run-tests.sh /<>/obj-aarch64-linux-gnu/cogl/tests/config.env cogl/tests/conform/test-conformance test_framebuffer_get_bits ― ✀ ― Starting D-Bus daemons (session & system)... Starting mocked services... Running test case... Test GL+GLSL GL3 ES2 test_framebuffer_get_bits: ok FAIL n/a Traceback (most recent call last): File "/<>/src/tests/meta-dbus-runner.py", line 184, in test_case.wrap_call(rest[1:]) File "/<>/src/tests/meta-dbus-runner.py", line 171, in wrap_call self.assertEqual(p.wait(), 0) File "/usr/lib/python3.10/unittest/case.py", line 845, in assertEqual assertion_func(first, second, msg=msg) File "/usr/lib/python3.10/unittest/case.py", line 838, in _baseAssertEqual raise self.failureException(msg) AssertionError: 134 != 0 ―― 27/113 mutter:cogl+cogl/conform / framebuffer-get-bits FAIL 0.83s exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2055519/+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 2036388] Re: Login screen grey background flickers
** Changed in: yaru Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2036388 Title: Login screen grey background flickers Status in Yaru Theme: Fix Released Status in gnome-shell package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: Fix Committed Bug description: Login screen grey background flickers on startup and again on login. It looks like it's trying to fade between two very similar shades of grey and there just aren't enough colours between them to fade smoothly. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/2036388/+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 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
https://salsa.debian.org/gnome- team/mutter/-/commit/65b84bfc8a351d39b777e3821559a69d229af68a ** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+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 2055530] Re: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
Looks like it was fixed in 45.0: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3000 ** Changed in: mutter (Ubuntu) Status: In Progress => Fix Released ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu Jammy) Status: New => 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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+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 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
** Description changed:
- Possible, proposed solutions
-
-
- Option 1: Please install from these channels and report back with
- success or failure.
-
- snap refresh --channel candidate/core22 firefox
-
- Option 2:
-
- chromium --ozone-platform=wayland
- MOZ_ENABLE_WAYLAND=1 firefox
-
- If nothing works, it is possible around the issue by disabling hardware
- acceleration.
-
- Original bug report
- ---
-
Snap packages which use hardware accelerated graphics are broken after
the last routine system upgrade via apt. My system is using AMD Radeon
RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers.
Two snap packages which are now unusable are Mozilla Firefox and
Chromium browsers. Both display animated speckled color garbage inside
their windows, overlayed with the correct image. Disabling hardware
acceleration in the settings for the snap version of Firefox fixed it.
Also, Firefox version installed from the original Mozilla tarball into
/opt/ works just fine with the acceleration enabled on the same system,
as well as glmark2 benchmark. Looks like the issue is only affecting
snap packages.
$ snap list firefox chromium
Name Version Rev Tracking Publisher Notes
chromium 109.0.5414.119 2295 latest/stable canonical✓ -
firefox 109.0.1-1 2311 latest/stable mozilla✓-
$ dpkg -l snapd|grep ^ii
ii snapd 2.58+22.10 amd64Daemon and tooling that enable
snap packages
$ dpkg -l mesa\* | grep ^ii
ii mesa-utils8.5.0-1 amd64Miscellaneous
Mesa utilities -- symlinks
ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous
Mesa utilities -- native applications
ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API
video acceleration drivers
ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video
acceleration drivers
ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan
graphics drivers
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.10
Release:22.10
Codename: kinetic
$ uname -a
Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4
12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: snap (not installed)
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Wed Feb 1 22:55:48 2023
InstallationDate: Installed on 2020-08-02 (913 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: snap
UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago)
---
ProblemType: Bug
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DRM.card0-DP-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ==
modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200
1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900
1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480
640x480 640x480 640x480
DRM.card0-DP-2:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-DP-3:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DiskUsage:
Filesystem Type Size Used Avail Use% Mounted on
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
tmpfs tmpfs 16G 0 16G 0% /dev/shm
/dev/nvme0n1p2 ext4 916G 222G 648G 26% /
DistroRelease: Ubuntu 22.10
InstallationDate: Installed on 2020-08-02 (914 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUS System Product Name
Package: chromium-browser 1:85.0.4183.83-0ubuntu2
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic
root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Snap.Changes: no changes found
Snap.ChromeDriverVersion: ChromeDriver 109.0.5414.119
(772095164c7d5d4e73160f858efed3b5e87eca83-refs/branch-heads/5414@{#1458})
Snap.ChromiumVersion:
[Desktop-packages] [Bug 2004532] Re: Hardware acceleration broken for amdgpu/mesa in snap
It looks like this regressed in Chromium (probably when Chromium switched to core22) judging by LP:2054887. The fix for the lack of /usr/share/libdrm/amdgpu.ids is currently released on beta and will be soon in other channels too. ** Changed in: chromium-browser (Ubuntu) Status: Fix Released => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2004532 Title: Hardware acceleration broken for amdgpu/mesa in snap Status in ubuntu-spotify-app: New Status in chromium-browser package in Ubuntu: Fix Committed Status in firefox package in Ubuntu: Fix Released Bug description: Snap packages which use hardware accelerated graphics are broken after the last routine system upgrade via apt. My system is using AMD Radeon RX 5500 XT graphics card from ASUS, with stock amdgpu kernel drivers. Two snap packages which are now unusable are Mozilla Firefox and Chromium browsers. Both display animated speckled color garbage inside their windows, overlayed with the correct image. Disabling hardware acceleration in the settings for the snap version of Firefox fixed it. Also, Firefox version installed from the original Mozilla tarball into /opt/ works just fine with the acceleration enabled on the same system, as well as glmark2 benchmark. Looks like the issue is only affecting snap packages. $ snap list firefox chromium Name Version Rev Tracking Publisher Notes chromium 109.0.5414.119 2295 latest/stable canonical✓ - firefox 109.0.1-1 2311 latest/stable mozilla✓- $ dpkg -l snapd|grep ^ii ii snapd 2.58+22.10 amd64Daemon and tooling that enable snap packages $ dpkg -l mesa\* | grep ^ii ii mesa-utils8.5.0-1 amd64Miscellaneous Mesa utilities -- symlinks ii mesa-utils-bin:amd64 8.5.0-1 amd64Miscellaneous Mesa utilities -- native applications ii mesa-va-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VA-API video acceleration drivers ii mesa-vdpau-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa VDPAU video acceleration drivers ii mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1 amd64Mesa Vulkan graphics drivers $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 22.10 Release:22.10 Codename: kinetic $ uname -a Linux xx 5.19.0-29-generic #30-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 4 12:14:09 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: snap (not installed) ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Feb 1 22:55:48 2023 InstallationDate: Installed on 2020-08-02 (913 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: snap UpgradeStatus: Upgraded to kinetic on 2023-02-02 (0 days ago) --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE DRM.card0-DP-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAebQd34yoBAAQcAQS1PCJ4nz4xrlBHrCcMUFQhCABxQIGAgcCpwNHAgQABAQEBTdAAoPBwPoAwIGUMWFQhAAAaKGgAoPBwPoAIkGUMWFQhAAAa/QAwPYeHOAEKICAgICAg/ABMRyBIRFIgNEsKICAgAfsCAxlxRJAEAwEjCQcHgwEAAOMFwADjBgUBAjqAGHE4LUBYLEUAWFQhAAAeVl4AoKCgKVAwIDUAWFQhAAAaKQ== modes: 3840x2160 3840x2160 3840x2160 3840x2160 3840x2160 2560x1440 1920x1200 1920x1080 1920x1080 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1440x900 1280x800 1152x864 1280x720 1280x720 1280x720 1024x768 800x600 720x480 720x480 640x480 640x480 640x480 DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DiskUsage: Filesystem Type Size Used Avail Use% Mounted on /dev/nvme0n1p2 ext4 916G 222G 648G 26% / tmpfs tmpfs 16G 0 16G 0% /dev/shm /dev/nvme0n1p2 ext4 916G 222G 648G 26% / DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2020-08-02 (914 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: ASUS System Product Name Package: chromium-browser 1:85.0.4183.83-0ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=1a37d538-d59f-477b-96f0-f949ce9b4553 ro quiet splash vt.handoff=7
[Desktop-packages] [Bug 2055530] [NEW] Mutter (sometimes) fails to build with [fatal error: meta/meta-enum-types.h: No such file or directory]
Public bug reported: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. ** Affects: mutter (Ubuntu) Importance: Medium Assignee: Daniel van Vugt (vanvugt) Status: In Progress ** Tags: jammy ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: New => In Progress ** Tags added: jammy -- 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/2055530 Title: Mutter (sometimes) fails to build with [fatal error: meta/meta-enum- types.h: No such file or directory] Status in mutter package in Ubuntu: In Progress Bug description: In file included from ../src/backends/meta-backend-private.h:39, from ../src/backends/x11/meta-backend-x11.h:31, from ../src/backends/x11/nested/meta-backend-x11-nested.h:25, from ../src/tests/meta-backend-test.h:23, from ../src/tests/meta-backend-test.c:22: ../src/backends/meta-monitor-manager-private.h:41:10: fatal error: meta/meta-enum-types.h: No such file or directory 41 | #include "meta/meta-enum-types.h" | ^~~~ compilation terminated. Seems like an old issue that you can hit at random in highly parallel builds. Because meta-enum-types.h is auto-generated its consumers need to declare stronger dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2055530/+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
Maybe it was perception error, because today I can confirm /usr/share/libdrm/amdgpu.ids is present in the beta snap. Could you please confirm the bug (or at least the error message) goes away by switching to it? sudo snap refresh --beta chromium ** Changed in: chromium-browser (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2054887 Title: Grahpical bugs caused by unable to access libdrm Status in chromium-browser package in Ubuntu: Fix Committed 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 1972545] Re: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- 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/1972545 Title: Ubuntu Dock does not show indicator for open Firefox (after snap refresh?) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: I am using the Firefox Snap on a fresh install of 22.04 (using defaults, as far as I know). Normally, Firefox shows an indicator in the Dock showing that it is running (the orange dot) and gives the ability to choose between open windows. At the moment, I have Firefox windows open, but nothing is shown in the Dock (as if it is closed). My suspicion is that the snap was refreshed while running and this confused Gnome Shell. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-ubuntu-dock 72~ubuntu5 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 9 13:31:40 2022 InstallationDate: Installed on 2022-04-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1972545/+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 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Verified fixed on Mantic using Mutter version 45.2-0ubuntu4. ** Description changed: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. - 3. Open Settings > About and verify Graphics = llvmpipe and Windowing System = X11. + 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. ** Tags removed: verification-needed-mantic ** Tags added: verification-done-mantic -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 2054510] Re: Incomplete screen redraws in virtual machines running Xorg
Oh I see the issue with 'meta-enum-types.h'. It's generated at build time and most likely someone forgot to declare dependencies on that. So at random times, depending on how parallel your build is, it might not be built before it gets included. -- 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/2054510 Title: Incomplete screen redraws in virtual machines running Xorg Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Mantic: Fix Committed Status in mutter source package in Noble: Fix Committed Bug description: [ Impact ] When using software rendering on Xorg (so usually just in VMs), some parts of app windows may fail to redraw. https://gitlab.gnome.org/GNOME/mutter/-/issues/2880 [ Test Plan ] 1. Set up a virtual machine without graphics acceleration. 2. Log into 'Ubuntu on Xorg'. 3. Open Settings > About and verify Graphics = llvmpipe (or "Software Rendering"), and Windowing System = X11. 4. sudo snap install chromium 5. Open Chromium and find a web page with lots of text. Plain text without any links and staying at the top of the page will work best because you don't want to trigger any scrolling. 6. Start selecting text with the mouse and while holding the button move the mouse up and down rapidly. Avoid triggering any page scrolling. 7. Release the mouse button in roughly the middle of the area of text that was selected. 8. Verify the remaining text selection is contiguous and not broken into multiple disconnected text selections (the bug). 9. Repeat steps 7 and 8 several times to be sure. [ Where problems could occur ] The fix adds a new synchronization point between the compositor and X server. This should be inconsequential, although there is a "sync ring" in mutter used for this, and if a mistake occurs there then other parts of the desktop could appear to stop responding in Xorg sessions. [ Other Info ] This is a regression that started in 3.37.3 due to https://gitlab.gnome.org/GNOME/mutter/-/commit/551101c65cda. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2054510/+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 2055528] Re: ftbfs with golang-1.22: missing crosscall_amd64 symbol
https://github.com/ubuntu/ubuntu-report/pull/61 ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2055528 Title: ftbfs with golang-1.22: missing crosscall_amd64 symbol Status in ubuntu-report package in Ubuntu: New Bug description: https://launchpadlibrarian.net/708934179/buildlog_ubuntu-noble- amd64.ubuntu-report_1.7.2_BUILDING.txt.gz dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libsysmetrics1/DEBIAN/symbols doesn't match completely debian/libsysmetrics1.symbols --- debian/libsysmetrics1.symbols (libsysmetrics1_1.7.2_amd64) +++ dpkg-gensymbolsKEGIqW 2024-01-12 08:59:34.126055379 + @@ -1,9 +1,9 @@ libsysmetrics.so.1 libsysmetrics1 #MINVER# (regex|optional)"_cgo.*" 1.0.0 - (arch=arm64 riscv64)crosscall1@Base 1.0.0 + crosscall1@Base 1.0.0 crosscall2@Base 1.0.0 (arch=i386)crosscall_386@Base 1.0.0 - (arch=amd64)crosscall_amd64@Base 1.0.0 +#MISSING: 1.7.2# (arch=amd64)crosscall_amd64@Base 1.0.0 (arch=armhf)crosscall_arm1@Base 1.0.0 (arch=ppc64el)crosscall_ppc64@Base 1.0.0 (arch=s390x)crosscall_s390x@Base 1.0.0 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2055528/+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 2055528] [NEW] ftbfs with golang-1.22: missing crosscall_amd64 symbol
Public bug reported: https://launchpadlibrarian.net/708934179/buildlog_ubuntu-noble- amd64.ubuntu-report_1.7.2_BUILDING.txt.gz dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libsysmetrics1/DEBIAN/symbols doesn't match completely debian/libsysmetrics1.symbols --- debian/libsysmetrics1.symbols (libsysmetrics1_1.7.2_amd64) +++ dpkg-gensymbolsKEGIqW 2024-01-12 08:59:34.126055379 + @@ -1,9 +1,9 @@ libsysmetrics.so.1 libsysmetrics1 #MINVER# (regex|optional)"_cgo.*" 1.0.0 - (arch=arm64 riscv64)crosscall1@Base 1.0.0 + crosscall1@Base 1.0.0 crosscall2@Base 1.0.0 (arch=i386)crosscall_386@Base 1.0.0 - (arch=amd64)crosscall_amd64@Base 1.0.0 +#MISSING: 1.7.2# (arch=amd64)crosscall_amd64@Base 1.0.0 (arch=armhf)crosscall_arm1@Base 1.0.0 (arch=ppc64el)crosscall_ppc64@Base 1.0.0 (arch=s390x)crosscall_s390x@Base 1.0.0 dh_makeshlibs: error: failing due to earlier errors ** Affects: ubuntu-report (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs ** Tags added: ftbfs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-report in Ubuntu. https://bugs.launchpad.net/bugs/2055528 Title: ftbfs with golang-1.22: missing crosscall_amd64 symbol Status in ubuntu-report package in Ubuntu: New Bug description: https://launchpadlibrarian.net/708934179/buildlog_ubuntu-noble- amd64.ubuntu-report_1.7.2_BUILDING.txt.gz dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libsysmetrics1/DEBIAN/symbols doesn't match completely debian/libsysmetrics1.symbols --- debian/libsysmetrics1.symbols (libsysmetrics1_1.7.2_amd64) +++ dpkg-gensymbolsKEGIqW 2024-01-12 08:59:34.126055379 + @@ -1,9 +1,9 @@ libsysmetrics.so.1 libsysmetrics1 #MINVER# (regex|optional)"_cgo.*" 1.0.0 - (arch=arm64 riscv64)crosscall1@Base 1.0.0 + crosscall1@Base 1.0.0 crosscall2@Base 1.0.0 (arch=i386)crosscall_386@Base 1.0.0 - (arch=amd64)crosscall_amd64@Base 1.0.0 +#MISSING: 1.7.2# (arch=amd64)crosscall_amd64@Base 1.0.0 (arch=armhf)crosscall_arm1@Base 1.0.0 (arch=ppc64el)crosscall_ppc64@Base 1.0.0 (arch=s390x)crosscall_s390x@Base 1.0.0 dh_makeshlibs: error: failing due to earlier errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/2055528/+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
