[Desktop-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2019212 Title: Backport packages for 22.04.3 HWE stack Status in mesa package in Ubuntu: Invalid Status in mesa source package in Jammy: Fix Committed Bug description: [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - new major release (23.0.4) [Test case] Install the new mesa on various hw configs, check that everything still works like before or better. [Where things could go wrong] This is a major update of Mesa, there could be regressions but we'll backport the final stable release of 23.0.x in order to minimize the chance for those. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 2021948] Re: New bugfix release 23.0.4
Hello Timo, or anyone else affected, Accepted mesa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/23.0.4-0ubuntu1~22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mesa (Ubuntu Jammy) Status: New => Fix Committed ** Tags added: verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2021948 Title: New bugfix release 23.0.4 Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Jammy: Fix Committed Status in mesa source package in Lunar: Fix Committed Bug description: [Impact] This is the last point-release of the 23.0.x-series, we should put it in lunar so latest bugfixes would get there, and in jammy for 22.04.3 image. We'll include an additional bugfix (a revert) to fix GPU hangs on some AMD gpu's running certain games. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2021948/+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 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
** Description changed: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test- example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test-example.com" Active Directory. Currently, 0.9.2 only changes '.' into '_2e', and this would change all special characters to use their hexadecimal representations, notably '-' becomes '_2d'. - There is plans from Foundations + Desktop to SRU 0.11.0 back to at least + There is plans from Foundations + Desktop to SRU 0.12.0 back to at least Jammy, documented in bug 2020682 which depends on golang 1.20 to be included in the jammy archive, documented in bug 2020658. However, this - fixup is required with high priority while the 0.11.0 release is being + fixup is required with high priority while the 0.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU - release to release of 0.11.0. + release to release of 0.12.0. [Testcase] Start a Windows Server VM, 2022 will be fine, and create an Active Directory with the domain "test-example.com". Launch a Focal, or Jammy, or Kinetic VM, and use SSSD to join the domain. Try to enable adsys: $ sudo apt install adsys $ adsysctl update ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test-example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name There are test packages in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf360012-test If you install the test package and retry to join the domain, it will succeed. [Where problems could occur] We are changing how domain names are being parsed and converted to valid dbus object path names. Domain names can only contain [0-9], [A-Z], [a-z], [.], and [-], so by adding '-' to being processed to its hexadecimal representation of '_2d', there should be limited scope of regressions. However, if a regression were to occur, then users may not be able to use adsys to apply group policy restrictions, and could run into issues accessing files, shares and networks. As mentioned in the impact section, this will be a temporary fix to 0.9.2 while 0.11.0 is being prepared to be released into the archive, which contains the full fix and testsuite coverage. This SRU should hopefully be short lived. [Other Info] The upstream merge request is: https://github.com/ubuntu/adsys/pull/498 This was fixed in 0.10.0 by the commit: commit 5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Author: Didier Roche Date: Tue Nov 15 11:10:51 2022 +0100 Subject: Fix special characters in domain conversion to dbus object path Link: https://github.com/ubuntu/adsys/commit/5752ba87347d7813dd56bc6a9ec6369ec56e5dc4 Now, there were some additional commits that added testsuite coverage: commit cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 Author: Didier Roche Date: Tue Nov 15 11:13:03 2022 +0100 Subject: Refresh golden file now that we properly handle the path. Link: https://github.com/ubuntu/adsys/commit/cd79b3f81441a3d9ab50f11bc8c3b5c7bf722540 commit 4571e39cd724a973270a586d2b18f653f0007de9 Author: Didier Roche Date: Tue Nov 15 11:14:35 2022 +0100 Subject: Use a better case to assert on ServerURL() failure being ignored. Link: https://github.com/ubuntu/adsys/commit/4571e39cd724a973270a586d2b18f653f0007de9 commit fdca6e462c26e1cbecdb8386f43515c1947d423d Author: Didier Roche Date: Tue Nov 15 11:16:21 2022 +0100 Subject: Add a separate case for special characters in domain name. Link: https://github.com/ubuntu/adsys/commit/fdca6e462c26e1cbecdb8386f43515c1947d423d These commits are not compatible with 0.9.2 due to testsuite harnesses and frameworks and test data files not being added until 0.10.0, and adding such commits is numerous, and contains too many changes for a SRU. Regrettably, the testsuite commits must be omitted. ** Description changed: [Impact] It is common that domain names contain the '-' character, as in "test- example.com", and adsys versions 0.9.2 and below cannot parse these correctly, leading to the error: ERRORgithub.com/ubuntu/adsys/cmd/adsysd/main.go:50 main.run() Error from server: error while updating policy: can't get policies for "test- example.com": failed to retrieve offline state from SSSD: dbus: invalid message: invalid path name when attempting to run adsys on a system attached to "test-example.com" Active Directory.
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Update debdiff based on the newly released ubuntu-drivers-
common-0.9.6.2~0.22.04.4
** Patch added: "jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5682424/+files/jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5.debdiff
** Patch removed: "force_install_NVIDIA_driver-jammy.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5676866/+files/force_install_NVIDIA_driver-jammy.debdiff
** Patch removed: "force_install_NVIDIA_driver-jammy_2.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5678569/+files/force_install_NVIDIA_driver-jammy_2.debdiff
** Patch removed: "force_install_NVIDIA_driver-jammy_3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5680578/+files/force_install_NVIDIA_driver-jammy_3.debdiff
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1990341
Title:
[SRU] Support to install nvidia driver by allowing list
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
Fix Released
Status in ubuntu-drivers-common source package in Jammy:
In Progress
Status in ubuntu-drivers-common source package in Lunar:
Fix Released
Bug description:
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to
OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA)
to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at
the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge
devices, it's time to have an official way to make the nvidia
installation consistent in unannounced (yet) nvidia devices to support
OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and
jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file
"/etc/custom_supported_gpus.json". And it won't generate automatically
which should not impact normal users
[ Other Info ]
* the patches are picked from
-
https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
-
https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
-
https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1990341/+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 1971984] Re: pcscd.socket is disabled after installation
** Changed in: pcsc-lite (Ubuntu Lunar) Status: Triaged => In Progress ** Changed in: pcsc-lite (Ubuntu Lunar) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: pcsc-lite (Ubuntu Kinetic) Status: Triaged => In Progress ** Changed in: pcsc-lite (Ubuntu Kinetic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: pcsc-lite (Ubuntu Jammy) Status: Triaged => In Progress ** Changed in: pcsc-lite (Ubuntu Jammy) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd.socket is disabled after installation Status in pcsc-lite package in Ubuntu: Fix Released Status in pcsc-lite source package in Jammy: In Progress Status in pcsc-lite source package in Kinetic: In Progress Status in pcsc-lite source package in Lunar: In Progress Status in pcsc-lite package in Debian: Fix Released Bug description: [ Impact ] The pscc-lite package provides an open source implementation of PC/SC, the de-facto standard to interface Personal Computers with Smart Cards/Readers. This bug is in the upstream debian packaging, and results in the pcscd.socket being disabled after installation. This prevents automatic startup of the associated pcscd.service, thus preventing automatic handling of Smart Cards/Readers w/out manual intervention to enable the socket (which doesn't persist across reboots). This is especially painful for users that require Smart Authentication for login. [ Test Plan ] Steps to reproduce: 1. If installed, remove and do a fresh install of the package pcscd (the sole version released for jammy is 1.9.5-3). 2. Verify that the pcscd.socket is disabled: $ systemctl status pcscd.socket ○ pcscd.socket - PC/SC Smart Card Daemon Activation Socket Loaded: loaded (/lib/systemd/system/pcscd.socket; disabled; vendor preset: enabled) Active: inactive (dead) Triggers: ● pcscd.service Listen: /run/pcscd/pcscd.comm (Stream) 3. [Optional] insert a Smart Card or Crypto Token (e.g. a Yubikey or Nitrokey) that's known to work on Ubuntu and verify that it fails to work. Repeating the same steps with a package built with the patch attached to comment #27 should ensure that the socket is enabled, and that interaction with a Smart Card or Crypto Token should work w/out manual intervention. [ Where problems could occur ] This is a back-ported change from upstream and is a result of a bug in dh_installsystemd (see comment #26). As such the risk is minimal. The only potential risk of failure I can come up with is a snap that stages the old version of the client library, as it would be looking in the wrong place for the socket. [ Other Info ] This bug was originally reported against Ubuntu Mate 22.04, however it applies to all derivatives of Ubuntu Desktop 22.04 LTS. Note - while there's some disagreement as to whether this bug occurs 100% of the time across all 22.04 installations, it's pretty clear from the upstream Debian bug and subsequent packaging fix that we should land this. As the upstream fix landed in 1.9.9-2 (which is already released in mantic) only the following releases are impacted by this bug: - jammy - kinetic - lunar To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+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 1998286] Re: Release mutter 42.9 to jammy
I successfully completed the wiki test case with mutter 42.9-0ubuntu1 on Ubuntu 22.04 LTS with the GNOME, GNOME Classic, Ubuntu and Ubuntu on Xorg sessions. I also successfully completed Extra Test Case 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/1998286 Title: Release mutter 42.9 to jammy Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.9/NEWS The overall GNOME project considers GNOME 42 to be end of life now and there are no more scheduled releases for mutter 42 after 42.9 This is basically a prerequisite for GNOME Shell 42.9 LP: #2023913 The current version of Mutter in Jammy is 42.5. Test Case - Complete the test case from https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter Extra Test Case 1 - This release also cherry-picks a patch to fix the prompt to enable accessibility features using keyboard shortcuts. 0. Install the updated mutter packages. Then log out and log back in. 1. Open the Settings app (gnome-control-center) 2. In the left sidebar, click Accessibility 3. In the typing section, lick Typing Assist 4. Turn on the first switch to enable turning accessibility features on and off using the keyboard 5. Close the Settings app 6. Press the Shift key 5 or 6 times in a row 7. You should see a system prompt about turning on Sticky Keys What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- Upstream assumes that people will be using matching versions of mutter and gnome-shell. To be cautious, I therefore bumped the dependency version in GNOME Shell 42.9 to require mutter >= 42.9 (even though GNOME Shell 42.9 appears to run ok with Mutter 42.5). I believe the only way to make the dependency relationship work the other way (not allow Mutter 42.9 with GNOME Shell 42.5) requires bumping the Breaks version but I don't think it's worth using Breaks unless necessary. This release will also enable AMD Xilinx/Mali support on Wayland. See https://ubuntu.com/download/amd-xilinx or private bug 1961563 or the 42.6 release notes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1998286/+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 1985089] Re: Resizing two edge tiled windows is laggy
The autopkgtest regressions have been resolved. See LP: #1998286 comment 10 for some comments about it. I installed mutter 42.9-0ubuntu1 on Ubuntu 22.04 LTS with about 6 GB of RAM. Before the update, my memory went from about 20% to 50% with the test case and stayed there. After the update, memory went up to about 35% with the test case. This is a significant improvement in used memory; therefore I consider this bugfix verified. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-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/1985089 Title: Resizing two edge tiled windows is laggy 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 42.9 includes a fix for tiled window resizing. Before the fix, window resizing could use very large amounts of memory and be laggy. Test Case - 0. Install the updated mutter packages. Log out then log back in. 1. Open System Monitor. Tile it to the Left. 2. Open a Terminal. Tile it to the right. 3. Click the Resources tab in System Monitor. 3. Right-click the System Monitor in the headerbar and click Resize. 4. Move your mouse left and right to resize the window. 5. The memory should not dramatically spike higher as seen in the System Monitor's Resources tab. What Could Go Wrong --- See the master mutter 42.9 bug LP: #1998286 Original Bug Report --- Just to report an issue that other people have reported to GNOME and in Reddit, that seems to also affect Ubuntu 22.04. If you snap 2 windows side-by-side in Wayland and then try to resize them, it's very slow and uses a lot of memory. Check here for more details: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2246 - https://old.reddit.com/r/gnome/comments/whjgel/resizing_two_tiled_windows_leaks_memory_and_is/ To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985089/+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 2025169] Re: pasdsp LIB dir incorrect
The attachment "pulseaudio_rules.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2025169 Title: pasdsp LIB dir incorrect Status in pulseaudio package in Ubuntu: New Bug description: /usr/bin/padsp script is generated with wrong LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" It must be generated like LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so" A patch is anexed thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025169/+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 2017333] Re: Some Area in Top right corner of the screen is not clickable.
*** This bug is a duplicate of bug 2012388 *** https://bugs.launchpad.net/bugs/2012388 hello this is cosmo head dev of PikaOS this effects all our users since 23.04 one thing interesting is issue is still present through anydesk and rdp and vnc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/2017333 Title: Some Area in Top right corner of the screen is not clickable. Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: https://www.reddit.com/r/Ubuntu/comments/12tyiwf/top_right_area_is_not_clickable_in_ubuntu_2304_i/ This link contains the visual representation and more details about the bug. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 22 12:10:32 2023 DistUpgraded: 2023-04-21 16:05:44,447 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] [103c:81ec] Subsystem: Hewlett-Packard Company Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / Radeon 520 Mobile] [103c:81ec] InstallationDate: Installed on 2022-04-01 (385 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:b008 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: HP HP Notebook ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=358a40b6-0ed5-4812-8281-fbd535f676fd ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) dmi.bios.date: 12/17/2019 dmi.bios.release: 15.48 dmi.bios.vendor: Insyde dmi.bios.version: F.48 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81EC dmi.board.vendor: HP dmi.board.version: 61.61 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 61.61 dmi.modalias: dmi:bvnInsyde:bvrF.48:bd12/17/2019:br15.48:efr61.61:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81EC:rvr61.61:cvnHP:ct10:cvrChassisVersion:skuW6T44PA#ACJ: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Notebook dmi.product.sku: W6T44PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 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/gnome-shell-extension-appindicator/+bug/2017333/+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 1966413] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1966413 Title: [SRU] --no-oem option is broken Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: New Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Won't Fix Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug description: [Impact] * ubuntu-drivers supports the --no-oem option, which is meant to filter-out the OEM metapackages when running on certified hardware. * When ubuntu-drivers is invoked with --no-oem as a global option (i.e., `ubuntu-drivers --no-oem list` or `ubuntu-drivers --no-oem install`, the script crashes with the following exception: NameError: name 'install_oem_meta' is not defined * When ubuntu-drivers is invoked with --no-oem as a sub-option of "install" (i.e., `ubuntu-drivers install --no-oem`), the script does not crash but the option is silently ignored - resulting in an OEM metapackage to be installed if we are running on certified hardware. This defeats the purpose of the option. * Today, the --no-oem option can be passed to ubuntu-drivers by ubiquity as a suboption of `ubuntu-drivers install`. By default, the option is not passed to ubuntu-drivers but the users can opt-in using preseeds. If they do, their decision is essentially ignored since the OEM metapackage will still be installed: https://git.launchpad.net/ubiquity/tree/scripts/simple-plugins#n20 * As part of the 23.10 cycle, subiquity will start replacing the functionality from ubiquity for OEM installs. At the moment, subiquity relies on the version of ubuntu-drivers-common from the system being installed. But going forward, we might have to ship ubuntu-drivers- common in the subiquity snap. This means we will fetch the deb from jammy-updates since subiquity is a core22-based snap. [Test plan] 1. We will compare the result of the following commands with and without the patch (both on certified and on un-certified hardware): * ubuntu-drivers --no-oem list -> crashes without the patch. Should not crash with the patch. The list returned should not include the OEM metapackage. * ubuntu-drivers --no-oem install -> crashes without the patch. Should not crash with the patch. The list of packages installed should not include the OEM metapackage. * ubuntu-drivers install --no-oem -> without the patch, the OEM metapackage gets installed on certified hardware. With the patch, it should not. 2. We will ensure ubiquity stills manages to install ubuntu on certified hardware. We will also ensure that the OEM metapackage does not get installed when it should not. [Where problems could occur] * When used as a global option, --no-oem currently makes the script crash unconditionally. Therefore, the change should be very low risk in that regard. * When used as a suboption of "install", the --no-oem option currently gets ignored silently. If people have been automating ubuntu deployment in one way or another and have used --no-oem, they might be surprised to notice that fewer packages get installed on their target system, after the option is fixed. This is theoretically a good thing, but might require some adjustments on their end. [Original description] $ ubuntu-drivers --no-oem install Traceback (most recent call last): File "/usr/bin/ubuntu-drivers", line 490, in greet() File "/usr/lib/python3/dist-packages/click/core.py", line 764, in __call__ return self.main(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 717, in main rv = self.invoke(ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 1134, in invoke Command.invoke(self, ctx) File "/usr/lib/python3/dist-packages/click/core.py", line 956, in invoke return ctx.invoke(self.callback, **ctx.params) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs) File "/usr/lib/python3/dist-packages/click/decorators.py", line 64, in new_func return ctx.invoke(f, obj, *args, **kwargs) File "/usr/lib/python3/dist-packages/click/core.py", line 555, in invoke return callback(*args, **kwargs)
[Desktop-packages] [Bug 2023675] Update Released
The verification of the Stable Release Update for gnome-video-effects has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-video-effects in Ubuntu. https://bugs.launchpad.net/bugs/2023675 Title: flip effect doesn't work on GStreamer 1.22 Status in GNOME Video Effects: Fix Released Status in gnome-video-effects package in Ubuntu: Fix Released Status in gnome-video-effects source package in Lunar: Fix Committed Status in gnome-video-effects package in Debian: Fix Released Bug description: Impact -- The Flip effect in the Cheese app doesn't work in Ubuntu 23.10. Test Case - 1. Install the updated gnome-video-effects packages 2. Open the Cheese app 3. Click the Effects button and verify that Flip is showing a reversed version of No Effect What Could Go Wrong --- This is a simple one-line patch. gnome-video-effects has only one reverse dependency in Ubuntu: cheese. Original Bug Report --- Distributor ID: Ubuntu Description: Ubuntu 23.04 Release: 23.04 Codename: lunar gnome-video-effects: Installed: 0.5.0-1ubuntu1 Candidate: 0.5.0-1ubuntu1 Version table: *** 0.5.0-1ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu lunar/main amd64 Packages 100 /var/lib/dpkg/status The file located in: /usr/share/gnome-video-effects/flip.effect is using the property "method" which is deprecated as you can see in GStreamer "https://gstreamer.freedesktop.org/documentation/videofilter/videoflip.html?gi- language=c" Deprecated version: PipelineDescription=videoflip method=horizontal- flip So the fix for this problem is to change the property to the new one, which is called video-direction, after this the effect will work correctly. Fix: PipelineDescription=videoflip video-direction=horiz The program that I used to test this effect was Cheese. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-video-effects/+bug/2023675/+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 1970921] Re: Drag and drop does not work
on ubuntu 23.04 draga drop for example from a zip file is not working anymore -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Triaged Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1970921/+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 2025169] [NEW] pasdsp LIB dir incorrect
Public bug reported: /usr/bin/padsp script is generated with wrong LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" It must be generated like LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so" A patch is anexed thanks ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Patch added: "pulseaudio_rules.diff" https://bugs.launchpad.net/bugs/2025169/+attachment/5682362/+files/pulseaudio_rules.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2025169 Title: pasdsp LIB dir incorrect Status in pulseaudio package in Ubuntu: New Bug description: /usr/bin/padsp script is generated with wrong LD_PRELOAD="/usr/\\$$LIB/pulseaudio/libpulsedsp.so" It must be generated like LD_PRELOAD="/usr/\$LIB/pulseaudio/libpulsedsp.so" A patch is anexed thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2025169/+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 878118] Re: please merge po files to upstream? source
When looking at the Git history of our (Czech) po file, it looks like that it was last imported from Ubuntu in 2015 and never updated: https://salsa.debian.org/pkgutopia-team/software- properties/-/commits/debian/master/po/cs.po ** Also affects: software-properties (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035019 Importance: Unknown Status: Unknown -- 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/878118 Title: please merge po files to upstream? source Status in software-properties package in Ubuntu: New Status in software-properties package in Debian: Unknown Bug description: I found software-properties in Rosetta is updated for translations but bzr(lp:ubuntu/software-properties, lp:ubuntu/oneiric/software- properties) and package source (https://launchpad.net/ubuntu/+archive/primary/+files/software- properties_0.81.13.dsc and https://translations.launchpad.net/software-properties) are not. Only https://translations.launchpad.net/ubuntu/oneiric/+source/software- properties/+pots/software-properties is to get newest translation... it's too complicated way. Debian tracks software-properties tarball version, however, it doesn't contain any updated po files. Please merge those and put it to tarball. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/878118/+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 2025150] [NEW] SRU: add two symbols for riscv64 to the symbols file
Public bug reported: This is seen with the planned backport of GCC 12.3 to lunar. It's already fixed in mantic [1]. The added symbols don't belong to the ABI, however the build fails because dh_makeshlibs is called with -c4, and two more template instantiations show up on riscv64. [ Impact ] Without the two added symbols, the build will fail with the updated GCC 12.3 as seen in mantic. [ Test plan ] The package builds. There are no code changes in this patch [ Where problems could occur ] The patch is small and doesn't touch code. [1] http://launchpadlibrarian.net/670755843/libcupsfilters_2.0~rc1-0ubuntu2_2.0~rc1-0ubuntu3.diff.gz ** Affects: libcupsfilters (Ubuntu) Importance: Undecided Status: New ** Affects: libcupsfilters (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libcupsfilters (Ubuntu Lunar) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcupsfilters in Ubuntu. https://bugs.launchpad.net/bugs/2025150 Title: SRU: add two symbols for riscv64 to the symbols file Status in libcupsfilters package in Ubuntu: New Status in libcupsfilters source package in Lunar: New Bug description: This is seen with the planned backport of GCC 12.3 to lunar. It's already fixed in mantic [1]. The added symbols don't belong to the ABI, however the build fails because dh_makeshlibs is called with -c4, and two more template instantiations show up on riscv64. [ Impact ] Without the two added symbols, the build will fail with the updated GCC 12.3 as seen in mantic. [ Test plan ] The package builds. There are no code changes in this patch [ Where problems could occur ] The patch is small and doesn't touch code. [1] http://launchpadlibrarian.net/670755843/libcupsfilters_2.0~rc1-0ubuntu2_2.0~rc1-0ubuntu3.diff.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcupsfilters/+bug/2025150/+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 1991022] Re: [SRU] Service activation via Systemd socket
I installed 0.11.1-1ubuntu3 from jammy-proposed and the snap[5] in a Jammy virtual machine, logged out, logged in, opened Pavucontrol, ran snap run --shell geheim XDG_RUNTIME_DIR=/run/user/1000 spd-say hi and verified that the volume indicator in Pavucontrol moved right after issuing the command. [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 ** 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 speech-dispatcher in Ubuntu. https://bugs.launchpad.net/bugs/1991022 Title: [SRU] Service activation via Systemd socket Status in speech-dispatcher package in Ubuntu: Fix Released Status in speech-dispatcher source package in Jammy: Fix Committed Status in speech-dispatcher source package in Kinetic: Fix Committed Status in speech-dispatcher source package in Lunar: Fix Committed Bug description: [Description] Systemd socket activation for Speech Dispatcher. - Creates the speech-dispatcher.socket; - Modifies the server so that it can detect it was automatically launched by that socket activation; and - Modifies the Autotools files accordingly. [Impact] Its relevance is described in [1], of which I quote the essential parts [my notes in brackets]: > Sandboxed applications [snaps] that use Speech Dispatcher currently bundle it inside of the sandbox, so that each application has its own "private" instance of Speech Dispatcher running. This works more or less, but it has the downside that speech dispatcher cannot coordinate simultaneous messages from multiple apps. When multiple sandboxed apps use Speech Dispatcher at the same time, the text reading overlaps. > > In order to solve this issue, I would really like to give sandboxed apps access to the Speech Dispatcher instance of the host. That can be done by implementing the action of the speech dispatcher service via a Systemd socket: > The only issue I see is having it auto launch. I think it would probably be a good step forward for speech-dispatcher to be auto launched by a systemd socket like other daemons already do on demand. That way the host speech-dispatcher with it's configuration would be used by all snaps, [Additional information] The changes are already merged upstream[21][22][23], but still not released. I have built and installed the package in Mantic and verified that running spd-say from inside a snap causes the host's dispatcher to spawn and emit sound — see 'Test case' for more details. This has also been verified in Jammy by Lissyx[31][32] and there is a merge proposal[4] for the Firefox snap that assumes the incorporation of this delta in speech-dispatcher. Note: Either the installed socket needs to be started manually to function correctly or the session must be restarted or the system needs to be rebooted. [Test case] Install the proposed speech-dispatcher and the snap[5] containing spd- say. Restart the user session so the new systemd unit gets activated. Then, snap run --shell geheim $ XDG_RUNTIME_DIR=/run/user/1000 spd-say hi should say "hi" through your loudspeakers. If you have no loudspeakers or if you are testing in a virtual machine, you can use Pavucontrol to verify that the dummy output device meter shows activity right after you issue the last command. [Regression potential] If the socket communication were not working (e.g. connection refused), then this would result in text-to-speech failing, even for a not sandboxed program. Do note, however, that if the socket were not available for whatever reason (e.g. the user didn't start it manually nor rebooted), then the sd_listen_fds(0) >= 1 test would be false and no regression would be observed, as then the program would fallback to its usual operation. [1] https://github.com/brailcom/speechd/issues/335 [21] https://github.com/brailcom/speechd/pull/763 [22] https://github.com/brailcom/speechd/pull/776 [23] https://github.com/brailcom/speechd/pull/817 [31] https://irclogs.ubuntu.com/2023/05/17/%23ubuntu-desktop.html [32] https://bugzilla.mozilla.org/show_bug.cgi?id=1729750#c23 [4] https://github.com/canonical/firefox-snap/pull/12 [5] https://launchpad.net/~nteodosio/+snap/test-speechd/+build/2103550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/speech-dispatcher/+bug/1991022/+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 1998060] Re: CVE-2022-37290: Pasted zip archive/invalid file causes NPD
As I don't see anything actionable right now, and there's been no movement since my last ping, I'll remove the ubuntu-sponsors subscription. Please re-add that in case any additional sponsoring is needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1998060 Title: CVE-2022-37290: Pasted zip archive/invalid file causes NPD Status in caja package in Ubuntu: New Status in nautilus package in Ubuntu: Fix Released Status in nemo package in Ubuntu: Fix Committed Status in caja source package in Focal: New Status in nautilus source package in Focal: Fix Released Status in nemo source package in Focal: New Status in caja source package in Jammy: New Status in nautilus source package in Jammy: Fix Released Status in nemo source package in Jammy: New Status in caja source package in Kinetic: New Status in nautilus source package in Kinetic: Fix Released Status in nemo source package in Kinetic: In Progress Status in caja source package in Lunar: New Status in nautilus source package in Lunar: Fix Released Status in nemo source package in Lunar: Fix Committed Bug description: A bug for the triage/patching of CVE-2022-37290. In get_basename() and g_file_get_basename(), when the file name cannot be parsed, NULL is returned; Nautilus does not check this and this results in a NPD and a crash. The issue on GNOME GitLab explains this pretty well: https://gitlab.gnome.org/GNOME/nautilus/-/issues/2376 And the code in question is also in Nemo and Caja. History of the code: The faulty code was introduced in Nautilus 2.20, before Nemo and Caja were forked; these file managers have the same issue and same code in the function. The simplest POC I found was running this via DBus, which I'm not 100% sure if I've altered correctly for Nemo and Caja, but regardless for Nautilus this results in a crash. ``` Nov 27 20:38:32 Joshua-2210Test nautilus[5433]: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449866] pool-org.gnome.[5439]: segfault at 0 ip 7f3058c6c570 sp 7f3051dfa968 error 4 in libglib-2.0.so.0.7400.0[7f3058c03000+8f000] Nov 27 20:38:32 Joshua-2210Test kernel: [ 825.449878] Code: 0f 85 bc fe ff ff e9 42 ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 f3 0f 1e fa 48 89 d1 48 85 f6 0f 89 b0 00 00 00 <0f> b6 07 84 c0 75 15 eb 27 0f 1f 80 00 00 00 00 0f b6 42 01 48 8d ``` Attached is the poc.py, made by Wu Chunming. ** Nemo ** Upstream, version 5.6.0: (more advanced/verbose) upstream patch: https://github.com/linuxmint/nemo/commit/b9953e61f61724f46740ac77317720549cdf6005 possible further problems: https://github.com/linuxmint/nemo/commit/33c37a82e88a8e6b289b3b0d2010ce0caece4bdb ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: nautilus 1:43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Nov 27 20:41:20 2022 GsettingsChanges: InstallationDate: Installed on 2022-09-18 (70 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220918) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.46.2-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1998060/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
A new fix is coming in triple-buffering 45: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1441#note_1777992 But I want it to mature a little, and even try proposing a backport upstream to main, before backporting to 44. -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2025135] Re: package firefox 91.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2025135 Title: package firefox 91.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: while upgrading ubuntu from ubuntu distribution, go this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kamalakannan979 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Jun 27 14:35:27 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2023-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.39 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 91.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-06-27 (0 days ago) dmi.bios.date: 03/05/2020 dmi.bios.release: 3.63 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN63WW(V3.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-15IIL dmi.ec.firmware.release: 3.63 dmi.modalias: dmi:bvnLENOVO:bvrCUCN63WW(V3.05):bd03/05/2020:br3.63:efr3.63:svnLENOVO:pn81WL:pvrLenovoIdeaPadS340-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-15IIL:skuLENOVO_MT_81WL_BU_idea_FM_IdeaPadS340-15IIL: dmi.product.family: IdeaPad S340-15IIL dmi.product.name: 81WL dmi.product.sku: LENOVO_MT_81WL_BU_idea_FM_IdeaPad S340-15IIL dmi.product.version: Lenovo IdeaPad S340-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2025135/+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 2025135] [NEW] package firefox 91.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1
Public bug reported: while upgrading ubuntu from ubuntu distribution, go this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kamalakannan979 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Jun 27 14:35:27 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2023-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.39 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 91.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-06-27 (0 days ago) dmi.bios.date: 03/05/2020 dmi.bios.release: 3.63 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN63WW(V3.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S340-15IIL dmi.ec.firmware.release: 3.63 dmi.modalias: dmi:bvnLENOVO:bvrCUCN63WW(V3.05):bd03/05/2020:br3.63:efr3.63:svnLENOVO:pn81WL:pvrLenovoIdeaPadS340-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-15IIL:skuLENOVO_MT_81WL_BU_idea_FM_IdeaPadS340-15IIL: dmi.product.family: IdeaPad S340-15IIL dmi.product.name: 81WL dmi.product.sku: LENOVO_MT_81WL_BU_idea_FM_IdeaPad S340-15IIL dmi.product.version: Lenovo IdeaPad S340-15IIL dmi.sys.vendor: LENOVO ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/2025135 Title: package firefox 91.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 Status in firefox package in Ubuntu: New Bug description: while upgrading ubuntu from ubuntu distribution, go this error ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 91.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kamalakannan979 F pulseaudio BuildID: 20210804193234 CasperMD5CheckResult: unknown Channel: Unavailable Date: Tue Jun 27 14:35:27 2023 ErrorMessage: new firefox package pre-installation script subprocess returned error exit status 1 ForcedLayersAccel: False InstallationDate: Installed on 2023-06-27 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IpRoute: default via 192.168.1.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.39 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 91.0+build2-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to jammy on 2023-06-27 (0 days ago) dmi.bios.date: 03/05/2020 dmi.bios.release: 3.63 dmi.bios.vendor: LENOVO dmi.bios.version: CUCN63WW(V3.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO
[Desktop-packages] [Bug 2024948] Re: librtaudio-dev has unresolvable dependencies on 22.04.2.
Thanks, closing then since it was an apt sources configuration issue and not a bug in the package ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/2024948 Title: librtaudio-dev has unresolvable dependencies on 22.04.2. Status in pulseaudio package in Ubuntu: Invalid Bug description: sudo apt install librtaudio-dev Reading package lists... Done Building dependency tree... Done Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: libpulse-dev : Depends: libpulse0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2.1 is to be installed Depends: libpulse-mainloop-glib0 (= 1:15.99.1+dfsg1-1ubuntu1) but 1:15.99.1+dfsg1-1ubuntu2.1 is to be installed E: Unable to correct problems, you have held broken packages. I have no held packages. I have seen chatter around a project that depends on librtaudio-dev suggesting it is a package maintenance issue but not sure myself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2024948/+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 2025118] Re: Adding a wireguard VPN from file hangs the dialog if...
Thank you for your bug report. Do you get any error dialog displayed before the hang? Are you sure it's due to the dot and not the length of the filename? Trying 'w.example.conf' it doesn't hang where it displays an error and hand renaming the same file 'wireguard.example.conf' https://gitlab.gnome.org/GNOME/gnome-control- center/-/merge_requests/1777 could perhaps help with the issue ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2025118 Title: Adding a wireguard VPN from file hangs the dialog if... Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When importing a wireguard configuration it consistently hangs up the dialog if the filename has more than one dot. I have several profiles like london.fast.conf pol.server.conf node.develop.aws.conf I tried all, all hangs up the dialog. When I remove the extra dots it works like charm. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Tue Jun 27 00:30:24 2023 InstallationDate: Installed on 2022-03-24 (460 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202) ProcEnviron: LANG=es_CU LANGUAGE=es_CU:es PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: Upgraded to lunar on 2023-04-04 (83 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2025118/+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
