[Desktop-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack
** Changed in: mesa-amber (Ubuntu Jammy) Status: New => In Progress -- 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-amber package in Ubuntu: Invalid Status in mesa source package in Jammy: Fix Committed Status in mesa-amber source package in Jammy: In Progress 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) mesa-amber - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no changes to the classic dri drivers - drops old i915 driver, while mesa provides the more modern i915_dri.so called i915g - fixes installation (LP: #2006744) and image build [Test case] mesa: Install the new mesa on various hw configs, check that everything still works like before or better. mesa-amber: no need to test anything besides checking that the packages can be installed next to mesa and image build is fixed [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 2020588] Re: add nice-dcv support
Incomplete because this feature request can never be actioned in Ubuntu until the feature exists in upstream gnome-shell first. ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Incomplete -- 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/2020588 Title: add nice-dcv support Status in gnome-shell package in Ubuntu: Incomplete Bug description: Please backport nice-dcv support for gnome-shell in Focal. Work has been done to enable this in gitlab - https://gitlab.gnome.org/abono/gnome- shell/-/commits/wip/abono/ubuntu-20-04-gnome-3-36-9-backports To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2020588/+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 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind
This is probably a bug in mutter but before we can report it upstream it would be best to try and reproduce the bug without having the unsupported extension 'wint...@nowsci.com' installed. So please remove that extension and check the bug still occurs. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2026194 Title: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind Status in gnome-shell package in Ubuntu: Incomplete Bug description: Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 12:05:46 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-19 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 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/2026194/+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 1525451] Re: Ubuntu GNOME 16.04 daily wont boot in virtualbox
Thank you for reporting this bug to Ubuntu. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it anymore. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1525451 Title: Ubuntu GNOME 16.04 daily wont boot in virtualbox Status in Ubuntu GNOME: Confirmed Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Current images don't boot using virtualbox 5. [25.023] (WW) xf86OpenConsole: VT_ACTIVATE failed: Input/output error [25.030] (EE) Fatal server error: [25.030] (EE) xf86OpenConsole: Switching VT failed [25.030] (EE) [25.031] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [25.032] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [25.032] (EE) [25.034] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [25.034] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [25.034] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [25.034] (EE) Server terminated with error (1). Closing log file. ProblemType: BugDistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CasperVersion: 1.366 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Dec 12 00:58:31 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151211) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity Renderer: SoftwareSourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.65-3 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151019-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Dec 12 00:54:53 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1525451/+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 1525451] Re: Ubuntu GNOME 16.04 daily wont boot in virtualbox
Also reported in bug 2026120 ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1525451 Title: Ubuntu GNOME 16.04 daily wont boot in virtualbox Status in Ubuntu GNOME: Confirmed Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Won't Fix Bug description: Current images don't boot using virtualbox 5. [25.023] (WW) xf86OpenConsole: VT_ACTIVATE failed: Input/output error [25.030] (EE) Fatal server error: [25.030] (EE) xf86OpenConsole: Switching VT failed [25.030] (EE) [25.031] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [25.032] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [25.032] (EE) [25.034] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [25.034] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [25.034] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [25.034] (EE) Server terminated with error (1). Closing log file. ProblemType: BugDistroRelease: Ubuntu 16.04 Package: xserver-xorg 1:7.7+12ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CasperVersion: 1.366 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Dec 12 00:58:31 2015 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller]) LiveMediaBuild: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151211) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity Renderer: SoftwareSourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.65-3 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.7-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.7-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20151019-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sat Dec 12 00:54:53 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.17.3-2ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1525451/+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 2026120] Re: xf86CloseConsole: KDSETMODE failed: Input/output error
Which Nvidia driver do you have installed? ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2026120 Title: xf86CloseConsole: KDSETMODE failed: Input/output error Status in xorg-server package in Ubuntu: Incomplete Bug description: On every reboot the following messages are shown in the journal: /usr/libexec/gdm-x-session[14875]: (II) NVIDIA(GPU-0): Deleting GPU-0 /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error This is consistent on every reboot on several machines (including a cloud VM and metal). I was able to observe it on mantic and on jammy. Is this a result of the GPU being deleted prematurely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2026120/+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 2026120] Re: xf86CloseConsole: KDSETMODE failed: Input/output error
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2026120 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Tags added: nvidia ** Tags added: jammy mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2026120 Title: xf86CloseConsole: KDSETMODE failed: Input/output error Status in xorg-server package in Ubuntu: Incomplete Bug description: On every reboot the following messages are shown in the journal: /usr/libexec/gdm-x-session[14875]: (II) NVIDIA(GPU-0): Deleting GPU-0 /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error This is consistent on every reboot on several machines (including a cloud VM and metal). I was able to observe it on mantic and on jammy. Is this a result of the GPU being deleted prematurely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2026120/+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 2026200] Re: Snap update broke launching and printing on 20.04 Ubuntu.
You mention snap update in the title. What specific snap are you referring to, Chromium, Cups or Snapd? The output of "snap changes" could be useful. If you roll it back with "snap revert ", does it work again? > Launching chrome from menu shortcut that is managed by the snap works > and it using this location /snap/bin/chromium > > Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome > Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Indeed, you should let the snap manage the shortcut, as the one you used in 20.04 invokes the binary directly, out of the snap sandbox. Do you get issues with that in place? Please attach the output of snap connections chromium snap connections cups ** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** Changed in: cups (Ubuntu) Status: New => Incomplete ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: Incomplete Status in cups package in Ubuntu: Incomplete Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2026200/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New -- 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/1922414 Title: ssh-agent fails to start (has_option: command not found) Status in Light Display Manager: New Status in gdm3 package in Ubuntu: Fix Released Status in lightdm package in Ubuntu: New Status in xorg package in Ubuntu: Confirmed Bug description: Hi, I have been using ssh-agent for years and since I upgraded my system to Ubuntu 21.04/groovy, ssh-agent fails to start. Here is the error message: # journalctl | grep ssh-agent [...] Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: /etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not found ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: x11-common 1:7.7+22ubuntu1 Uname: Linux 5.11.11-05-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Sat Apr 3 09:02:46 2021 Dependencies: lsb-base 11.1.0ubuntu2 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1] MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2020 dmi.bios.release: 7.3 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.03RTR dmi.board.name: NS50MU dmi.board.vendor: TUXEDO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.2 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: TUXEDO InfinityBook S 15 Gen6 dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: TUXEDO version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1933186] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
Confirmed multiple reports of the crash still happening in GNOME 44 so we don't have a reliable fix coming. ** Changed in: mutter (Ubuntu Kinetic) Status: Fix Committed => Won't Fix ** Changed in: mutter (Ubuntu Jammy) Status: Fix Committed => Incomplete ** Changed in: mutter (Ubuntu) Status: Fix Released => Confirmed ** Changed in: mutter (Ubuntu Lunar) Status: Fix Released => Confirmed ** No longer affects: mutter (Ubuntu Jammy) ** No longer affects: mutter (Ubuntu Kinetic) ** No longer affects: mutter (Ubuntu Lunar) ** Tags removed: bionic fixed-in-mutter-42.7 fixed-in-mutter-43.2 fixed-in-mutter-44 fixed-upstream ** Tags added: lunar -- 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/1933186 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in Mutter: Fix Released Status in mutter package in Ubuntu: Confirmed Status in mutter package in Fedora: Unknown Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.4-1ubuntu3, the problem page at https://errors.ubuntu.com/problem/7ae33f650c2de2c5580905f0c63e5b6c35fb46c6 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1933186/+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 2015473] Re: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from met
*** This bug is a duplicate of bug 1933186 *** https://bugs.launchpad.net/bugs/1933186 ** This bug has been marked a duplicate of bug 1933186 gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() -- 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/2015473 Title: gnome-shell crashed with SIGSEGV in meta_window_place() from place_window_if_needed() from meta_window_constrain() from meta_window_move_resize_internal() from meta_window_force_placement() Status in gnome-shell package in Ubuntu: New Bug description: Closing lid on Fujitsu LIFEBOOK U Series crashed the gnome shell. Ubuntu 23.04 Beta ProblemType: Crash DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.0-2ubuntu3 ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6 Uname: Linux 6.2.0-19-generic x86_64 ApportVersion: 2.26.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 6 14:02:41 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-04-05 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 44.0-2ubuntu3 Signal: 11 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-12.so.0 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ffi_call () from /lib/x86_64-linux-gnu/libffi.so.8 Title: gnome-shell crashed with SIGSEGV in ffi_call() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015473/+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 2026230] Re: error when setting up after upgrading
** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2026230 Title: error when setting up after upgrading Status in network-manager package in Ubuntu: New Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2026230/+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 2026230] Re: error when setting up after upgrading
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/2026230 Title: error when setting up after upgrading Status in network-manager package in Ubuntu: New Bug description: I received an error from apport about a programme not working. I collected the data to submit. Hope this helps. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: network-manager 1.42.6-2ubuntu1 Uname: Linux 6.2.0-24-generic x86_64 Architecture: amd64 Date: Wed Jul 5 23:11:14 2023 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1687429583 ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) Signal: 6 SourcePackage: network-manager UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2026230/+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 2026228] [NEW] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
Public bug reported: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] [Other info] ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2026228/+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 2025651] Re: default Japanese font in snap apps is ugly
I tried on mantic: * Refreshed gnome-42-2204 to latest/candidate * Opened FF But that didn't recreate ~/snap/firefox/current/.config/fontconfig/fonts.conf . Is a later release of the FF snap needed too? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: Fix Committed Status in language-selector package in Ubuntu: Invalid Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 1899809] Re: Unncessarily restrictive dependency on libcurl4-gnutls-dev
This bug was fixed in the package raptor2 - 2.0.16-2 --- raptor2 (2.0.16-2) unstable; urgency=medium * QA upload. * Move from experimental to unstable. * Add libcurl-ssl-dev as alternative to libcurl4-gnutls-dev. LP: #1899809 * Add libicu-dev as BD. * Enable all tests but do not run them in parallel. -- Håvard F. Aasen Mon, 03 Jul 2023 08:56:32 +0200 ** Changed in: raptor2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to raptor2 in Ubuntu. https://bugs.launchpad.net/bugs/1899809 Title: Unncessarily restrictive dependency on libcurl4-gnutls-dev Status in raptor2 package in Ubuntu: Fix Released Bug description: Package raptor2 has currently a 'hard' dependency on libcurl4-gnutls-dev which prevents a usage when libcurl-openssl-dev has to be installed, e.g., when using libignition-fuel-tools1-dev The problem can easily be fixed by updating the dependency from libcurl4-openssl-dev to libcurl4-gnutls-dev | libcurl-ssl-dev This leaves the choice of libcurl's ssl backend to the user - similar to other packages like libgdal-dev (see https://packages.ubuntu.com/bionic/libgdal-dev). I am currently on working on Ubuntu 18.04.4 LTS -- libraptor-2.0.14-1build1 but dependencies have not been updated for Ubuntu 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/raptor2/+bug/1899809/+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 2025651] Re: default Japanese font in snap apps is ugly
There is a new build of gnome-42-2204 in the candidate channel now if someone wants to give it a try and confirm if it indeed fixes the issue (if you try on firefox you need a core22 based version, which is the default in lunar) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: Fix Committed Status in language-selector package in Ubuntu: Invalid Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests
** Changed in: mesa (Ubuntu) Status: In Progress => Fix Committed -- 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/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: New Status in mesa package in Ubuntu: Fix Committed Status in mesa package in Debian: New Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2026200] [NEW] Snap update broke launching and printing on 20.04 Ubuntu.
Public bug reported: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2026200 Title: Snap update broke launching and printing on 20.04 Ubuntu. Status in chromium-browser package in Ubuntu: New Bug description: Two deployed ubuntu images, 20.04 and 22.04. Both images are fully updated. Issue appears to only impact 20.04. chrome snap version 2529 Launching chrome from menu shortcut that is managed by the snap works and it using this location /snap/bin/chromium Launching chrome from desktop shortcut that I manage on 20.04 fails - /snap/chromium/current/usr/lib/chromium-browser/chrome Updating the desktop shortcut with this location on 20.04 works - /snap/bin/chromium Try and print from the browser, print dialog in chrome does not list any system printers, only shows PDF. Doing the same on 22.04 image, I get a list of printers. CLI I run cups.lstat -v which works on 22.04, does not work on 20.04. 20.04 I get an error "cannot stat /var/lib/snapd/seccomp/bpf/snap.cups.lpstat.bin: No such file or directory" I've run these tests on multiple 20.04 and 22.04 machines and I'm getting 100% failure rate on 20.04. I get this error when running chrome from cli from this path on 20.04 /snap/chromium/current/usr/lib/chromium-browser which points to 2529 snap image. /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/current/usr/lib/chromium-browser/chrome) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) /snap/chromium/current/usr/lib/chromium-browser/chrome: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by /snap/chromium/2529/usr/lib/chromium-browser/libffmpeg.so) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+so
[Desktop-packages] [Bug 2024248] Re: Update gnome-remote-desktop to 42.9
** Summary changed: - Update gnome-remote-desktop to 42.8 + Update gnome-remote-desktop to 42.9 ** Description changed: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: - https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.8 + https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.9 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024248 Title: Update gnome-remote-desktop to 42.9 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series It backports fixes for some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 22.04 LTS release: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/42.7...42.9 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Other Info -- The previous 22.04 LTS SRU, 42.7-0ubuntu1, got stuck in phased updates. We worked with upstream to do a new 42 release in hopes that this update along with the SRU for mutter 42.9 (LP: #1998286) will significantly improve the error rate. 42.7-0ubuntu1 was included in Ubuntu Desktop 22.04.2 so many users already have that version from the original install or got it before phasing was halted. https://ubuntu-archive-team.ubuntu.com/phased-updates.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024248/+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 2026197] [NEW] Update mozjs102 to 102.13.0
Public bug reported: Impact -- mozjs102 is the SpiderMonkey JavaScript engine from Firefox ESR. It is used by gjs to power GNOME Shell and some GNOME apps. There are new Firefox 102 ESR releases monthly until the end of August. https://whattrainisitnow.com/calendar/ Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/mfsa2023-23/ and found two CVEs CVE-2023-37202: Potential use-after-free from compartment mismatch in SpiderMonkey CVE-2023-37211 Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Additionally, mozjs102 has build tests. mozjs102 does not have autopkgtests of its own but it triggers the gjs autopkgtests. Security Sponsoring --- sudo apt install git-buildpackage mkdir tarballs; cd ../tarballs pull-lp-source mozjs102 mantic # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/lunar gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs git checkout ubuntu/102/kinetic gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs Initial Testing Done I built the package locally. I installed the library package on Ubuntu 23.04 and successfully completed the Test Case. Other Info -- It is believed that the only thing using mozjs102 in Ubuntu 22.04 LTS is actually cjs in Linux Mint 21.2 (in Beta testing). It has been proposed to switch Ubuntu's gjs to use it there also but that is currently on hold (benefit/risk analysis). See LP: #1993214 ** Affects: mozjs102 (Ubuntu) Importance: Undecided Status: Fix Committed ** Tags: jammy kinetic lunar upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs102 in Ubuntu. https://bugs.launchpad.net/bugs/2026197 Title: Update mozjs102 to 102.13.0 Status in mozjs102 package in Ubuntu: Fix Committed Bug description: Impact -- mozjs102 is the SpiderMonkey JavaScript engine from Firefox ESR. It is used by gjs to power GNOME Shell and some GNOME apps. There are new Firefox 102 ESR releases monthly until the end of August. https://whattrainisitnow.com/calendar/ Security Impact --- I looked through https://github.com/mozilla/gecko-dev/commits/esr102/js and searched for referenced bug numbers in https://www.mozilla.org/en-US/security/advisories/mfsa2023-23/ and found two CVEs CVE-2023-37202: Potential use-after-free from compartment mismatch in SpiderMonkey CVE-2023-37211 Test Case - https://wiki.ubuntu.com/DesktopTeam/TestPlans/gjs Additionally, mozjs102 has build tests. mozjs102 does not have autopkgtests of its own but it triggers the gjs autopkgtests. Security Sponsoring --- sudo apt install git-buildpackage mkdir tarballs; cd ../tarballs pull-lp-source mozjs102 mantic # That avoids needing to recreate the original tarball from pristine-tar which takes a while. Also, running lintian takes a while. cd .. gbp clone https://salsa.debian.org/gnome-team/mozjs cd mozjs git checkout ubuntu/102/lunar gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs git checkout ubuntu/102/kinetic gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs git checkout ubuntu/102/jammy gbp buildpackage --git-builder="debuild --no-lintian -S -nc" --git-tarball-dir=../tarballs Initial Testing Done I built the package locally. I installed the library package on Ubuntu 23.04 and successfully completed the Test Case. Other Info -- It is believed that the only thing using mozjs102 in Ubuntu 22.04 LTS is actually cjs in Linux Mint 21.2 (in Beta testing). It has been proposed to switch Ubuntu's gjs to use it there also but that is currently on hold (benefit/risk analysis). See LP: #1993214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs102/+bug/2026197/+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 2025980] Re: can not configure keyboard and mouse separately
also FYI: solaar detects my mouse properly -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2025980 Title: can not configure keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is ran out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! (and no keyboard) thus, I can not configure these devices separately, to get 1 keyboard and 1 mouse, but only can see 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2025980/+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 2019477] Re: Sliders temporary hide when hovered
Sliders are properly rendered also when hovered. ❯ apt-cache policy yaru-theme-gtk yaru-theme-gtk: Installed: 22.04.5 Candidate: 22.04.5 Version table: *** 22.04.5 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages ** Package changed: gnome-shell-extension-ubuntu-dock (Ubuntu) => yaru- theme (Ubuntu) ** 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2019477 Title: Sliders temporary hide when hovered Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] The slider temporary hide when hovered (see https://github.com/ubuntu/yaru/pull/3634) [ Test case ] 1. Install gtk3-widget-factory from gtk-3-examples package 2. Run the Widgets Factory application, go to "Page 3" 3. Hover the transparency slider in the right-bottom side of the window 4. The item should not be hidden [ Regression potential ] Sliders are not properly themed during hover To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/2019477/+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 2024248] Re: Update gnome-remote-desktop to 42.8
Sadly this new version has a new crash:
Core was generated by `/usr/libexec/gnome-remote-desktop-daemon'.
Program terminated with signal SIGABRT, Aborted.
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140478263563840)
at ./nptl/pthread_kill.c:44
44 ./nptl/pthread_kill.c: No such file or directory.
[Current thread is 1 (Thread 0x7fc3a4ff9640 (LWP 412662))]
(gdb) bt
#0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140478263563840)
at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=6, threadid=140478263563840) at
./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=140478263563840, signo=signo@entry=6) at
./nptl/pthread_kill.c:89
#3 0x7fc3c4ef2476 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
#4 0x7fc3c4ed87f3 in __GI_abort () at ./stdlib/abort.c:79
#5 0x7fc3c5a34b57 in g_assertion_message
(domain=, file=, line=,
func=0x564671390620 <__func__.4.lto_priv.6>
"maybe_release_pipewire_buffer_lock", message=) at
../../../glib/gtestutils.c:3253
#6 0x7fc3c5a8e70f in g_assertion_message_expr
(domain=domain@entry=0x0, file=file@entry=0x56467138fd98
"../src/grd-rdp-pipewire-stream.c", line=line@entry=194,
func=func@entry=0x564671390620 <__func__.4.lto_priv.6>
"maybe_release_pipewire_buffer_lock", expr=expr@entry=0x0) at
../../../glib/gtestutils.c:3279
#7 0x564671374c00 in maybe_release_pipewire_buffer_lock
(stream=, stream=0x56467361d280, buffer=0x0) at
../src/grd-rdp-pipewire-stream.c:194
#8 on_frame_ready (stream=0x56467361d280, frame=0x0, success=,
user_data=0x0)
at ../src/grd-rdp-pipewire-stream.c:1055
#9 0x7fc3c5788195 in impl_node_process_input (object=0x56467364ff90) at
../src/pipewire/stream.c:953
#10 0x7fc3c5760ab9 in process_node (data=0x564672f78b00) at
../src/pipewire/impl-node.c:1089
#11 0x7fc3c576649c in node_on_fd_events (source=) at
../src/pipewire/impl-node.c:1147
#12 0x7fc3b813fe33 in () at
/usr/lib/x86_64-linux-gnu/spa-0.2/support/libspa-support.so
#13 0x7fc3c5743226 in do_loop (user_data=0x564673611750) at
../src/pipewire/data-loop.c:81
#14 0x7fc3c4f44b43 in start_thread (arg=) at
./nptl/pthread_create.c:442
#15 0x7fc3c4fd6a00 in clone3 () at
../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
(gdb) f 7
#7 0x564671374c00 in maybe_release_pipewire_buffer_lock
(stream=0x56467361d280, stream=0x56467361d280,
buffer=0x0) at ../src/grd-rdp-pipewire-stream.c:194
194 ../src/grd-rdp-pipewire-stream.c: No such file or directory.
(gdb) print stream
$1 = 0x56467361d280
(gdb) print *stream
$2 = {parent = {g_type_instance = {g_class = 0x564673615810 [g_type: None]},
ref_count = 1, qdata = 0x0},
session_rdp = 0x564672f68050, rdp_surface = 0x7fc37c011050, pipewire_source =
0x564672eb7b10,
pipewire_context = 0x564673633570, pipewire_core = 0x564672f7b140,
pipewire_core_listener = {link = {
next = 0x56467364ff98, prev = 0x564672f7b1e8}, cb = {funcs =
0x56467139dde0 ,
data = 0x56467361d280}, removed = 0x0, priv = 0x0}, buffer_pool =
0x5646736061e0,
render_source = 0x564672e97980, frame_mutex = {p = 0x0, i = {0, 0}},
pending_frame = 0x0,
pipewire_stream = 0x56467364ff90, pipewire_stream_listener = {link = {next =
0x56467364fff8,
prev = 0x56467364fff8}, cb = {funcs = 0x56467139da60 ,
data = 0x56467361d280},
removed = 0x7fc3c577ffb0 , priv = 0x56467364ff90},
pipewire_buffers = 0x7fc3b4003520 = {
[0x564673650430] = 0x5646736462b0, [0x564673650408] = 0x564673646290,
[0x5646736503e0] = 0x564673646270,
[0x5646736503b8] = 0x564673646250, [0x564673650390] = 0x56467360e070,
[0x564673650368] = 0x564673611680,
[0x564673650458] = 0x5646736462d0, [0x564673650340] = 0x564673609fb0},
src_node_id = 43, spa_format = {
format = SPA_VIDEO_FORMAT_BGRx, modifier = 0, size = {width = 1920, height
= 1080}, framerate = {num = 0,
denom = 1}, max_framerate = {num = 30, denom = 1}, views = 0,
interlace_mode = SPA_VIDEO_INTERLACE_MODE_PROGRESSIVE, pixel_aspect_ratio =
{num = 0, denom = 0},
multiview_mode = SPA_VIDEO_MULTIVIEW_MODE_MONO, multiview_flags =
SPA_VIDEO_MULTIVIEW_FLAGS_NONE,
chroma_site = SPA_VIDEO_CHROMA_SITE_UNKNOWN, color_range =
SPA_VIDEO_COLOR_RANGE_UNKNOWN,
color_matrix = SPA_VIDEO_COLOR_MATRIX_UNKNOWN, transfer_function =
SPA_VIDEO_TRANSFER_UNKNOWN,
color_primaries = SPA_VIDEO_COLOR_PRIMARIES_UNKNOWN}}
(gdb) print stream->pipewire_buffers
$3 = 0x7fc3b4003520 = {[0x564673650430] = 0x5646736462b0, [0x564673650408] =
0x564673646290,
[0x5646736503e0] = 0x564673646270, [0x5646736503b8] = 0x564673646250,
[0x564673650390] = 0x56467360e070,
[0x564673650368] = 0x564673611680, [0x564673650458] = 0x5646736462d0,
[0x564673650340] = 0x564673609fb0}
Threaded trace: https://dpaste.com/DJP6YT6XX
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-failed verification-failed-jammy
--
You received this bug notification bec
[Desktop-packages] [Bug 1966167] Re: Ubuntu Dock icons not clickable at the edge of the screen
marco-ThinkPad-X1-Carbon-7th ~ 5s 18:22:50 ❯ apt-cache policy gnome-shell-extension-ubuntu-dock gnome-shell-extension-ubuntu-dock: Installed: 72~ubuntu5.22.04.2.1 Candidate: 72~ubuntu5.22.04.2.1 Version table: *** 72~ubuntu5.22.04.2.1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy-updates/main i386 Packages 100 /var/lib/dpkg/status 72~ubuntu5 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages marco-ThinkPad-X1-Carbon-7th ~ 18:23:27 ❯ apt-cache policy yaru-theme-gnome-shell yaru-theme-gnome-shell: Installed: 22.04.5 Candidate: 22.04.5 Version table: *** 22.04.5 400 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 400 http://archive.ubuntu.com/ubuntu jammy-proposed/main i386 Packages 100 /var/lib/dpkg/status 22.04.4 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages The fix is confirmed ** 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 gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1966167 Title: Ubuntu Dock icons not clickable at the edge of the screen Status in Dash to dock: New Status in Yaru Theme: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Fix Committed Status in yaru-theme source package in Jammy: Fix Committed Bug description: [ Impact ] If you go to the bottom left corner of the dock and click, the All Apps button doesn't get triggered or highlighted. Check attached video for details. [ Test case ] For verifying yaru-theme, in the Ubuntu session: 1. Move the pointer to the edge of the screen where the AppIcons button is visible (bottom-left corner by default) 2. The button should be highlighted and clicking it should open the applications grid [ Regression potential ] - The dock margins are wrong or icons are not clickable in their edges - There's no not-reactive space between the activity button and the first icon --- Ubuntu 21.10. Live mode. 1920x1080 screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1966167/+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 2025980] Re: can not setup keyboard and mouse separately
** Description changed: - I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. - battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. + I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. + battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is ran out of power, when I get 'low keyboard battery' message. - trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! - thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. + trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! + thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 - - output of 'upower -d': + output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 - native-path: hidpp_battery_0 - model:K800 - serial: b2-69-6e-91 - power supply: no - updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) - has history: yes - has statistics: yes - keyboard - present: yes - rechargeable:yes - state: discharging - warning-level: low - battery-level: low - percentage: 10% (should be ignored) - icon-name: 'battery-caution-symbolic' + native-path: hidpp_battery_0 + model:K800 + serial: b2-69-6e-91 + power supply: no + updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) + has history: yes + has statistics: yes + keyboard + present: yes + rechargeable:yes + state: discharging + warning-level: low + battery-level: low + percentage: 10% (should be ignored) + icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 - native-path: hidpp_battery_1 - model:Performance MX - serial: 04-81-33-3a - power supply: no - updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) - has history: yes - has statistics: yes - keyboard - present: yes - rechargeable:yes - state: discharging - warning-level: none - battery-level: high - percentage: 70% (should be ignored) - icon-name: 'battery-good-symbolic' + native-path: hidpp_battery_1 + model:Performance MX + serial: 04-81-33-3a + power supply: no + updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) + has history: yes + has statistics: yes + keyboard + present: yes + rechargeable:yes + state: discharging + warning-level: none + battery-level: high + percentage: 70% (should be ignored) + icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice - power supply: no - updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) - has history: no - has statistics: no - unknown - warning-level: none - percentage: 0% - icon-name: 'battery-missing-symbolic' + power supply: no + updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) + has history: no + has statistics: no + unknown + warning-level: none + percentage: 0% + icon-name: 'battery-missing-symbolic' Daemon: - daemon-version: 0.99.20 - on-battery: no - lid-is-closed: no - lid-is-present: no - critical-action: HybridSleep - + daemon-version: 0.99.20 + on-battery: no + lid-is-closed: no + lid-is-present: no + critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* - ID_INPUT_MOUSE=1 - ID_INPUT=1 + ID_INPUT_MOUSE=1 + ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* - ID_INPUT_KEYBOARD=1 - ID_INPUT=1 + ID_INPUT_KEYBOARD=1 + ID_INPUT=1 ** Summary changed: - can not setup keyboard and mouse separately + can not configure keyboard and mouse separa
[Desktop-packages] [Bug 2026194] Re: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind
As mentioned in OP, here is the screenshot showing context of entire desktop, with bright green hiding personal information. ** Attachment added: "Screenshot showing context of entire desktop" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026194/+attachment/5684056/+files/Screenshot%20from%202023-07-05%2011-53-20.png -- 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/2026194 Title: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind Status in gnome-shell package in Ubuntu: New Bug description: Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 12:05:46 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-19 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 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/2026194/+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 2026194] [NEW] When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind
Public bug reported: Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 12:05:46 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-19 (289 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=screen-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Screencast demo of the issue" https://bugs.launchpad.net/bugs/2026194/+attachment/5684050/+files/Screencast%20from%202023-07-05%2011-50-40.webm -- 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/2026194 Title: When clicking on some maximized or tiled windows, focus on roughly the lower quarter falls to the window behind Status in gnome-shell package in Ubuntu: New Bug description: Initially I thought this was an issue with IntelliJ and filed a bug there: https://youtrack.jetbrains.com/issue/IDEA-323780/Maximizing-the-the-window-sometimes-causes-clicks-on-a-lower-fraction-to-pass-through-to-the-window-behind But when I had the same issue with GIMP, I realized it's an Ubuntu or GNOME issue instead. I am assuming this is a gnome-shell problem. Every once in a while, when I maximize or tile (Win+Right) the IntelliJ window, a bottom fraction of the window (somewhere around a quarter) becomes impossible to interact with, with the mouse. Clicking in that lower area will give focus to the thing behind IntelliJ, and if it's a window, raise it to the foreground. if I restore the window so that it is not maximized, the entire window is interactive with the mouse once again. This also happened with GIMP. The attached "Screencast" is a recording. I had to crop it to hide personal information. The attached screenshot shows the state of my screen so you have context, with a bright green color used to replace personal information. For the first 10s of the recording, I simply moused over to show how the cursor changes around a quarter from the bottom of the screen. For the next 10s, I left click, then move, then left click, then move, until focus changes to Sublime, the window behind IntelliJ. For the remainder of the video I show that right-clicking and mousing over works fine on the top three quarters, until I reach the bottom again, and then the right click is sent to Sublime. Ubuntu 23.04 gnome-shell version 44.2-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: p
[Desktop-packages] [Bug 2007913] Re: HDMI Output sound has disappeared after Ubuntu update
I see that this looks like a kernel problem. One of my computers was without sound in the last 5 months, so I had to use a small screen laptop to watch movies or listen audio, but I lost patience in the process. Is there any GUI centric Linux distro, which fixes this problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/2007913 Title: HDMI Output sound has disappeared after Ubuntu update Status in alsa-driver package in Ubuntu: Confirmed Bug description: After months using the HDMI output without problems, it has stopped working after a system update two days ago. HDMI output is not listed in the list of available output devices. Same computer works with this sound output perfectly when booting with Windows or an older installation of Ubuntu (18.04). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Feb 21 08:12:58 2023 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-30 (296 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ca_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: M01EWR120 dmi.board.asset.tag: OEM Default string000 dmi.board.name: OEM Default string000 dmi.board.vendor: OEM Default string000 dmi.board.version: OEM Default string000 dmi.chassis.asset.tag: OEM Default string000 dmi.chassis.type: 10 dmi.chassis.vendor: OEM Default string000 dmi.chassis.version: OEM Default string000 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrM01EWR120:bd10/20/2021:br5.13:efr1.2:svnCHUWIInnovationAndTechnology(ShenZhen)co.,Ltd:pnCoreBox:pvrOEMDefaultstring000:rvnOEMDefaultstring000:rnOEMDefaultstring000:rvrOEMDefaultstring000:cvnOEMDefaultstring000:ct10:cvrOEMDefaultstring000:skuOEMDefaultstring000: dmi.product.family: OEM Default string000 dmi.product.name: CoreBox dmi.product.sku: OEM Default string000 dmi.product.version: OEM Default string000 dmi.sys.vendor: CHUWI Innovation And Technology(ShenZhen)co.,Ltd mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-05-15T20:34:56.735127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2007913/+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 2004649] Re: Regression bug with mesa backport and ogre rendering
could you check if the backport from lunar in jammy-proposed fixes this? ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu Jammy) Status: New => Incomplete -- 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/2004649 Title: Regression bug with mesa backport and ogre rendering Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Jammy: Incomplete Bug description: We found a breaking change with https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1991761 when running an application that relies on ogre 1.9 for rendering inside a Docker container based on the ubuntu:jammy image. We could confirm that the upgrade causing this was as follows, because the issue goes away when downgrading versions: [UPGRADE] libegl-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgbm-dev:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgbm1:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libgl1-mesa-dri:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libglapi-mesa:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 [UPGRADE] libglx-mesa0:amd64 22.0.1-1ubuntu2 -> 22.2.5-0ubuntu0.1~22.04.1 For completeness, the full stack trace is: Stack trace (most recent call last) in thread 18237: #25 Object "[0x]", at 0x, in #24 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba75089ff, in #23 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7476b42, in #22 Object "/lib/x86_64-linux-gnu/libstdc++.so.6", at 0x7f2ba3a4d2b2, in #21 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456b2bf, in ignition::gazebo::v6::systems::SensorsPrivate::RenderThread() #20 Object "/usr/lib/x86_64-linux-gnu/ign-gazebo-6/plugins/libignition-gazebo-sensors-system.so", at 0x7f2b6456aba6, in ignition::gazebo::v6::systems::SensorsPrivate::RunOnce() #19 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db113e, in ignition::sensors::v6::Manager::RunOnce(std::chrono::duration > const&, bool) #18 Object "/opt/underlay_ws/install/lib/libignition-sensors6.so.6", at 0x7f2b76db95b5, in ignition::sensors::v6::Sensor::Update(std::chrono::duration > const&, bool) #17 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rgbd_camera.so.6", at 0x7f2b6436a020, in ignition::sensors::v6::RgbdCameraSensor::Update(std::chrono::duration > const&) #16 Object "/opt/underlay_ws/install/lib/libignition-sensors6-rendering.so.6", at 0x7f2b64282a6d, in ignition::sensors::v6::RenderingSensor::Render() #15 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c6adc85, in ignition::rendering::v6::OgreDepthCamera::PostRender() #14 Object "/usr/lib/x86_64-linux-gnu/ign-rendering-6/engine-plugins/libignition-rendering-ogre.so", at 0x7f2b5c71d743, in ignition::rendering::v6::OgreRenderTexture::Buffer(float*) #13 Object "/lib/x86_64-linux-gnu/libOgreMain.so.1.9.0", at 0x7f2b5c32c90a, in Ogre::RenderTexture::copyContentsToMemory(Ogre::PixelBox const&, Ogre::RenderTarget::FrameBuffer) #12 Object "/usr/lib/x86_64-linux-gnu/OGRE-1.9.0/RenderSystem_GL.so", at 0x7f2aeac67a85, in Ogre::GLTextureBuffer::download(Ogre::PixelBox const&) #11 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26225cdd, in #10 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262246ae, in #9 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b262244b0, in #8 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26082975, in #7 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26224a86, in #6 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b260800a8, in #5 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b260a3f19, in #4 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b26c77f37, in #3 Object "/usr/lib/x86_64-linux-gnu/dri/iris_dri.so", at 0x7f2b25fa88b6, in #2 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba740a7f2, in abort #1 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7424475, in raise #0 Object "/lib/x86_64-linux-gnu/libc.so.6", at 0x7f2ba7478a7c, in pthread_kill Aborted (Signal sent by tkill() 17739 0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2004649/+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 2019212] Re: Backport packages for 22.04.3 HWE stack
** Description changed: [Impact] The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3 mesa - new major release (23.0.4) + mesa-amber + - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no + changes to the classic dri drivers + - drops old i915 driver, while mesa provides the more modern i915_dri.so called + i915g + - fixes installation (LP: #2006744) and image build + [Test case] + mesa: Install the new mesa on various hw configs, check that everything still works like before or better. + + mesa-amber: + no need to test anything besides checking that the packages can be installed next to mesa and image build is fixed [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. ** Changed in: mesa-amber (Ubuntu) Status: New => Invalid -- 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-amber package in Ubuntu: Invalid Status in mesa source package in Jammy: Fix Committed Status in mesa-amber source package in Jammy: New 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) mesa-amber - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no changes to the classic dri drivers - drops old i915 driver, while mesa provides the more modern i915_dri.so called i915g - fixes installation (LP: #2006744) and image build [Test case] mesa: Install the new mesa on various hw configs, check that everything still works like before or better. mesa-amber: no need to test anything besides checking that the packages can be installed next to mesa and image build is fixed [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 2025980] Re: can not setup keyboard and mouse separately
probably it's due to the single path for both devices?.. udevadm info /dev/input/event3 P: /devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3 M: event3 R: 3 U: input D: c 13:67 N: input/event3 L: 0 S: input/by-id/usb-Logitech_USB_Receiver-if02-event-kbd S: input/by-path/pci-:00:14.0-usb-0:6:1.2-event-kbd E: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:2010.0007/input/input18/event3 E: DEVNAME=/dev/input/event3 E: MAJOR=13 E: MINOR=67 E: SUBSYSTEM=input E: USEC_INITIALIZED=4130304 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_BUS=usb E: ID_MODEL=USB_Receiver E: ID_MODEL_ENC=USB\x20Receiver E: ID_MODEL_ID=c52b E: ID_SERIAL=Logitech_USB_Receiver E: ID_VENDOR=Logitech E: ID_VENDOR_ENC=Logitech E: ID_VENDOR_ID=046d E: ID_REVISION=1210 E: ID_TYPE=hid E: ID_USB_MODEL=USB_Receiver E: ID_USB_MODEL_ENC=USB\x20Receiver E: ID_USB_MODEL_ID=c52b E: ID_USB_SERIAL=Logitech_USB_Receiver E: ID_USB_VENDOR=Logitech E: ID_USB_VENDOR_ENC=Logitech E: ID_USB_VENDOR_ID=046d E: ID_USB_REVISION=1210 E: ID_USB_TYPE=hid E: ID_USB_INTERFACES=:030101:030102:03: E: ID_USB_INTERFACE_NUM=02 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:6:1.2 E: ID_PATH_TAG=pci-_00_14_0-usb-0_6_1_2 E: XKBMODEL=pc105 E: XKBLAYOUT=us,rud E: XKBVARIANT=dvorak, E: XKBOPTIONS=grp:shift_caps_toggle E: KMAP=/etc/console/boottime.kmap.gz E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=3/46d/2010:usb-:00:14.0-6 E: DEVLINKS=/dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-kbd /dev/input/by-path/pci-:00:14.0-usb-0:6:1.2-event-kbd E: TAGS=:power-switch: E: CURRENT_TAGS=:power-switch: udevadm info /dev/input/event4 P: /devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:101A.0008/input/input19/event4 M: event4 R: 4 U: input D: c 13:68 N: input/event4 L: 0 S: input/by-path/pci-:00:14.0-usb-0:6:1.2-event-mouse S: input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse E: DEVPATH=/devices/pci:00/:00:14.0/usb3/3-6/3-6:1.2/0003:046D:C52B.0004/0003:046D:101A.0008/input/input19/event4 E: DEVNAME=/dev/input/event4 E: MAJOR=13 E: MINOR=68 E: SUBSYSTEM=input E: USEC_INITIALIZED=4122172 E: ID_INPUT=1 E: ID_INPUT_MOUSE=1 E: ID_BUS=usb E: ID_MODEL=USB_Receiver E: ID_MODEL_ENC=USB\x20Receiver E: ID_MODEL_ID=c52b E: ID_SERIAL=Logitech_USB_Receiver E: ID_VENDOR=Logitech E: ID_VENDOR_ENC=Logitech E: ID_VENDOR_ID=046d E: ID_REVISION=1210 E: ID_TYPE=hid E: ID_USB_MODEL=USB_Receiver E: ID_USB_MODEL_ENC=USB\x20Receiver E: ID_USB_MODEL_ID=c52b E: ID_USB_SERIAL=Logitech_USB_Receiver E: ID_USB_VENDOR=Logitech E: ID_USB_VENDOR_ENC=Logitech E: ID_USB_VENDOR_ID=046d E: ID_USB_REVISION=1210 E: ID_USB_TYPE=hid E: ID_USB_INTERFACES=:030101:030102:03: E: ID_USB_INTERFACE_NUM=02 E: ID_USB_DRIVER=usbhid E: ID_PATH=pci-:00:14.0-usb-0:6:1.2 E: ID_PATH_TAG=pci-_00_14_0-usb-0_6_1_2 E: MOUSE_DPI=1000@166 E: LIBINPUT_DEVICE_GROUP=3/46d/101a:usb-:00:14.0-6 E: DEVLINKS=/dev/input/by-path/pci-:00:14.0-usb-0:6:1.2-event-mouse /dev/input/by-id/usb-Logitech_USB_Receiver-if02-event-mouse -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed
[Desktop-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack
** Also affects: mesa-amber (Ubuntu) Importance: Undecided Status: New -- 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-amber package in Ubuntu: New Status in mesa source package in Jammy: Fix Committed Status in mesa-amber source package in Jammy: New 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 2020834] Re: Properly convert DNS names with '-' characters to valid dbus object paths
I've tested Focal and it works well with adsys from -proposed: https://pastebin.ubuntu.com/p/6RBcBpZq2T/ And also does Jammy: https://pastebin.ubuntu.com/p/pqvgSkkmcQ/ I'm having issues with Kinetic. When I install adsys, I'm no longer able to login to the instance, I'm getting the following errors when trying to login: https://pastebin.ubuntu.com/p/hh9SHB3ZXx/ It works if I purge the adsys package. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adsys in Ubuntu. https://bugs.launchpad.net/bugs/2020834 Title: Properly convert DNS names with '-' characters to valid dbus object paths Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: Fix Committed Status in adsys source package in Jammy: Fix Committed Status in adsys source package in Kinetic: Fix Committed Bug description: [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.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.12.0 release is being prepared, and the SRU will hopefully bridge a few weeks between SRU 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.12.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 man
[Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
@Federico: Thanks for testing and reporting that observation! I can't reproduce it (on mantic), though. Dead keys work as expected for me, also with the keyboard layout you mentioned. Are you sure that the issue is related to the proposed ibus version? Does the issue go away if you downgrade to the released version? Are you testing on lunar or mantic? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+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 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests
** Changed in: mesa (Debian) Status: Unknown => New -- 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/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: New Status in mesa package in Ubuntu: In Progress Status in mesa package in Debian: New Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2025980] Re: can not setup keyboard and mouse separately
device models are listed in the log above: model: K800 (this is keyboard) model: Performance MX (mouse) their product codes are 046D:2010 and 046D:101A it really seems similar to the issue #215, but that fix didn't help me. I cloned git version of upower, compiled and installed. now I see: UPower client version 1.90.1 UPower daemon version 1.90.1 unfortunalely, the problem still persists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2025980/+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 2025982] Re: Warning 'failed to get driver name for fd 0' fails gtk tests
** Changed in: mesa Status: Unknown => New -- 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/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: New Status in mesa package in Ubuntu: In Progress Status in mesa package in Debian: Unknown Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2024197] Update Released
The verification of the Stable Release Update for gnome-remote-desktop 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-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024197 Title: Update gnome-remote-desktop to 44.2 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 44 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 23.04 release, 44.0: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/44.0...44.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024197/+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 2024197] Re: Update gnome-remote-desktop to 44.2
This bug was fixed in the package gnome-remote-desktop - 44.2-0ubuntu1 --- gnome-remote-desktop (44.2-0ubuntu1) lunar; urgency=medium * New upstream release (LP: #2024197) * debian/upstream/metadata: trivial fix for format error -- Jeremy Bícha Fri, 16 Jun 2023 09:58:47 -0400 ** Changed in: gnome-remote-desktop (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/2024197 Title: Update gnome-remote-desktop to 44.2 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Lunar: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 44 series It fixes some crashes reported to errors.ubuntu.com Changes since the current Ubuntu 23.04 release, 44.0: https://gitlab.gnome.org/GNOME/gnome-remote-desktop/-/compare/44.0...44.2 Test Cases -- Complete all the test cases from https://wiki.ubuntu.com/DesktopTeam/TestPlans/RemoteDesktop except for the "New Audio Forwarding Feature" test case. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/2024197/+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 2026120] [NEW] xf86CloseConsole: KDSETMODE failed: Input/output error
Public bug reported: On every reboot the following messages are shown in the journal: /usr/libexec/gdm-x-session[14875]: (II) NVIDIA(GPU-0): Deleting GPU-0 /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error This is consistent on every reboot on several machines (including a cloud VM and metal). I was able to observe it on mantic and on jammy. Is this a result of the GPU being deleted prematurely? ** Affects: xorg-server (Ubuntu) Importance: Low Status: New ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2026120 Title: xf86CloseConsole: KDSETMODE failed: Input/output error Status in xorg-server package in Ubuntu: New Bug description: On every reboot the following messages are shown in the journal: /usr/libexec/gdm-x-session[14875]: (II) NVIDIA(GPU-0): Deleting GPU-0 /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: KDSETMODE failed: Input/output error /usr/libexec/gdm-x-session[14875]: (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error This is consistent on every reboot on several machines (including a cloud VM and metal). I was able to observe it on mantic and on jammy. Is this a result of the GPU being deleted prematurely? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/2026120/+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 2025916] Re: command-chain ... not found
No. As I wrote, since this is my main laptop, I didn't do anything. I don't know anything about snap nor snapd. I had no 'intention'. I do a apt update && apt upgrade && snap refresh (One after the other!) on a daily base. That's all. grep "remove " /var/log/dpkg.log shows nothing. The file was started on July 1st. My mistake, eventually, to fail to make clear that I did not want install/reinstall chromium; and I issued only one single additional command: the one given by ricsipontaz in https://forum.snapcraft.io/t/snap-problem-on-ubuntu-20-10-21-04-dev/21512/7 on how to solve this problem. I did not have to reinstall the apps, contrary to him. -- 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/2025916 Title: command-chain ... not found Status in chromium-browser package in Ubuntu: Incomplete Bug description: (I'm not familiar with snap, was migrated to it by *buntu for chromium-browser) Received the usual, well-know notification of having to snap refresh, some time given ... Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with $ chromium-browser Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Using Firefox, after some Google I found and tried $ sudo apt install snap --reinstall ... The following NEW packages will be installed: snap And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+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 1983778] Re: Major security issue in Ubuntu Desktop default config - Removable Media
** Changed in: gsettings-desktop-schemas Status: New => Fix Released -- 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/1983778 Title: Major security issue in Ubuntu Desktop default config - Removable Media Status in GSettings Desktop Schemas: Fix Released Status in gnome-control-center package in Ubuntu: Confirmed Bug description: There is a MAJOR SECURITY VULNERABILITY in Ubuntu Desktop since release 18.04 ! Recently I used Ubuntu 22.04 LTS and noticed that the issue still exist! I don’t know the reason for it, but default values for “Removable Media” are VERY Risky! It will automatically run the software which is attached to the removable media. Why? Why has Ubuntu still didn’t disable that option? The following is the default configuration (the “bad” configuration): https://imgur.com/XXXQlV2 The following is the configuration which Ubuntu should be having (it is the fix to the problem): https://imgur.com/a/0JeM6ve Please change the default configurations for Ubuntu! To manage notifications about this bug go to: https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1983778/+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 2026010] [NEW] super + alt + s starts screen reader and uses 100% of one CPU core forever, even after disabling the screen reader
Public bug reported: I have Ubuntu 22.04 clean install + updates (installed yesterday). I have used super + alt + s to get screen reader working on this article: https://snapcraft.io/blog/snaps-how-we-got-here At the time I was either in Firefox or in Edge browser installed through deb downloaded from Microsoft, I am not sure. When I pressed the shortcut the voice said "screen reader on" and it started reading. Then I disabled it by using my mouse and clicking in the system tray on accessibility icon and the option to disable it. When I disabled it the voice DID NOT say "screen reader off" but instead orca process started using 100% of one CPU core and it remained like that until reboot. Killing orca process was not possible via system monitor in GUI. After reboot I cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: orca 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 11:43:15 2023 InstallationDate: Installed on 2023-07-02 (2 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: orca UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: orca (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to orca in Ubuntu. https://bugs.launchpad.net/bugs/2026010 Title: super + alt + s starts screen reader and uses 100% of one CPU core forever, even after disabling the screen reader Status in orca package in Ubuntu: New Bug description: I have Ubuntu 22.04 clean install + updates (installed yesterday). I have used super + alt + s to get screen reader working on this article: https://snapcraft.io/blog/snaps-how-we-got-here At the time I was either in Firefox or in Edge browser installed through deb downloaded from Microsoft, I am not sure. When I pressed the shortcut the voice said "screen reader on" and it started reading. Then I disabled it by using my mouse and clicking in the system tray on accessibility icon and the option to disable it. When I disabled it the voice DID NOT say "screen reader off" but instead orca process started using 100% of one CPU core and it remained like that until reboot. Killing orca process was not possible via system monitor in GUI. After reboot I cannot reproduce the issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: orca 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 5 11:43:15 2023 InstallationDate: Installed on 2023-07-02 (2 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) PackageArchitecture: all SourcePackage: orca UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/orca/+bug/2026010/+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 1985066] Re: cannot refresh snap "firefox": snap "firefox" has running apps (firefox)
> The dangerously misleading "All snaps up to date." message is still printed on "snap refresh". I can confirm that. Today, `sudo snap refresh` wrote "All snaps up to date." but `sudo snap refresh firefox` wrote "error: cannot refresh "firefox": snap "firefox" has running apps (firefox) [...]" because NOT all snaps are up to date. -- 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/1985066 Title: cannot refresh snap "firefox": snap "firefox" has running apps (firefox) Status in firefox package in Ubuntu: Confirmed Bug description: Firefox installed via 22.04 snap does not seem to update properly. There is a log line (or error printout on manual execution), but it does not really point me to the actual bug. I already know firefox is running for some other user - that machine is never up and not running firefox - but I do not see how that matters. # snap list firefox Name VersionRev Tracking Publisher Notes firefox 103.0.1-1 1635 latest/stable mozilla✓ - # snap info firefox | grep latest/stable tracking: latest/stable latest/stable:103.0.2-12022-08-09 (1670) 171MB - # sudo snap refresh firefox error: cannot refresh "firefox": snap "firefox" has running apps (firefox), pids: 19113,19246,19268,19361,19524,19529,19588,19874,20047,20075,20105,20127 # firefox --version Mozilla Firefox 103.0.1 (expected: 103.0.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1985066/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10
On 04/07/23 08:23, Gunnar Hjalmarsson wrote: > My first upload to the PPA proved to not be complete. Corrected now. > (Wait for the builds to finish and the packages to be published before > updating). I have installed the new proposed version, but I have a regression with deadkeys: pressing altgr+', then e used to insert the letter é, now it doesn't anymore. My keyboard layout is us_intl_altgr. Thanks for your work! Federico -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1996652 Title: Nautilus search is slow and jumbles keyboard input on 22.10 Status in ibus: New Status in ibus package in Ubuntu: Confirmed Bug description: Since my upgrade to 22.10, I've found the search box in Nautilus (files) essentially unusable. It is notably sluggish to launch and browse in general. But most detrimental to the usability is this: The characters do not appear in real time as I type. When they do appear, they are sometimes jumbled or in reverse (consistently reproducible). As I type in the file search box, the circular cursor spins intermittently, then the UI catches up and it's not what I typed. For example, I just typed "umbrella" into the search box, and Nautilus searched for: "umballer" Off-the-cuff test #2, searched for "Ubuntu" and I ended up with "Ubunut" ... you can't make this up. :-) Test #3, typed Launchpad, ended up with a search for "Laudaphcn". Keyboard input everywhere else on the system is otherwise normal and snappy. No pun intended, really. FWIW Nautilus files preferences are as default (Search in subfolders, Show thumbnails, File count == This computer only). $ apt-cache policy nautilus nautilus: Installed: 1:43.0-1ubuntu1 Candidate: 1:43.0-1ubuntu1 Version table: *** 1:43.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -r 5.19.0-23-generic $ lsb_release -rd Description:Ubuntu 22.10 Release:22.10 $ snap list Name Version RevTracking Publisher Notes bare 1.0 5 latest/stable canonical✓ base core 16-2.57.2 13886 latest/stable canonical✓ core core18 20221027 2620 latest/stable canonical✓ base core20 20221027 1695 latest/stable canonical✓ base gnome-3-34-18040+git.3556cb3 77 latest/stable/… canonical✓ - gnome-3-38-20040+git.6f39565 119latest/stable canonical✓ - google-cloud-sdk 409.0.0 298latest/stable google-cloud-sdk✓ classic gtk-common-themes 0.1-81-g442e511 1535 latest/stable/… canonical✓ - snap-store 41.3-64-g512c0ff 599latest/stable/… canonical✓ - snapd 2.57.417336 latest/stable canonical✓ snapd snapd-desktop-integration 0.1 14 latest/stable/… canonical✓ - Side question: Since this system has transitioned across several upgrades from 20.04 to 22.10, do I really need all of these core* and gnome* snaps? To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1996652/+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 2025651] Re: default Japanese font in snap apps is ugly
The fix has been merged, we will need a rebuild of the gnome-42-2204 snap next to have it working ** Changed in: language-selector (Ubuntu) Status: New => Invalid ** Changed in: snappy Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to language-selector in Ubuntu. https://bugs.launchpad.net/bugs/2025651 Title: default Japanese font in snap apps is ugly Status in Snappy: Fix Committed Status in language-selector package in Ubuntu: Invalid Bug description: Japanese fonts in snap packages such as Firefox use glyphs from Chinese fonts. non-snap packages are fine. This is derived from the following ticket: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2017076 How to reproduce: 1. Install lunar or mantic with Japanese language pack 2. Enable Japanese locale 3. Start Firefox 4. Type or Copy "刃" to address field and type enter 5. Check glyph of "刃" Expected result: The following Japanese glyph is displayed: https://glyphwiki.org/wiki/u5203 Actual result: The following Chinese? glyph is displayed: https://glyphwiki.org/wiki/zihai-018904 Others: * Ubuntu 22.04 LTS not affected, works fine. * Fixed if you remove fonts-droid-fallback package. To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/2025651/+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 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
Do we need evince to be reuploaded for jammy there since the previous upload was rejected by Steve? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Fix Released Status in evince package in Ubuntu: Fix Released Status in apparmor source package in Jammy: Fix Committed Status in evince source package in Jammy: In Progress Status in apparmor source package in Lunar: Fix Committed Status in evince source package in Lunar: Fix Committed Status in evince package in Debian: Confirmed Bug description: [Impact] * Users cannot open a hyperlink in a PDF opened with evince when the default browser is a snap. * The fix creates a snap_browsers abstraction on AppArmor which can be used in a transition for when the browser is executed. The snap_browsers abstraction provides the minimal amount of permissions required to execute a browser provided through snaps. This is a workaround since AppArmor currently does not provide mediation/filtering on enhanced environment variables. [Test Plan] * Make sure the default browser is provided through the snap store. * Open a PDF that contains a hyperlink using evince and click on the URL. * The browser should open the requested URL. [Where problems could occur] * If the browser or snap core update to have new requirements for opening a browser, then the current policy could become obsolete and will need to be updated again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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 2025687] Re: URL Links in Document Viewer Does not Open in Firefox
Thanks, it could be solved with the same fix than bug #1794064 which is pending review for 22.04 but the apparmor denial message is different in your log so maybe not, we will have to check once the fix for the other issue is available ** Changed in: evince (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2025687 Title: URL Links in Document Viewer Does not Open in Firefox Status in evince package in Ubuntu: New Bug description: 1. Description: Ubuntu 22.04.2 LTS Release: 22.04 2. evince: Installed: 42.3-0ubuntu3 Candidate: 42.3-0ubuntu3 Version table: *** 42.3-0ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.1-3 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. I expect the URL link in the PDF to open in my Firefox web browser when I click on it. I have to manually copy the link from the PDF document and paste it to the Firefox web browser. 4. Nothing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu3 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 3 21:27:55 2023 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2022-11-03 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2025687/+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 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap
And also the bug was reported against 'evince' which is a pdf reader but the description doesn't seem to have anything to do with pdf... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2003649 Title: Illegal block number passed to ext2fs_test_block_bitmap Status in evince package in Ubuntu: Invalid Bug description: Hello I am trying to understand how the three commands testb, icheck and ncheck of the debugfs command work. My goal is to use them to find all the sectors allocated to a file. For this, I created a test set consisting of a 100% full EXT4 partition containing only one file. Here are the features: mount /dev/sda9 /mnt/TEST df --block-size=512 -text4 | grep TEST /dev/sda94245641392 0 100% /mnt/TEST So I think there are only 1064 (42456-41392) unused sectors. To check it, I make this script: rm -v testb.in for ((k=1;k<42457;k++));do echo testb $k >>testb.in done debugfs -f testb.in /dev/sda9 > testb.out 2>err then I control head -2 testb.out; tail -2 testb.out ; head -2 err; tail -1 err debugfs: testb 1 Block 1 marked in use debugfs: testb 42456 Block 42456 not in use debugfs 1.46.5 (30-Dec-2021) Illegal block number passed to ext2fs_test_block_bitmap #6656 for block bitmap for /dev/sda9 Illegal block number passed to ext2fs_test_block_bitmap #42456 for block bitmap for /dev/sda9 I can only find this reported incident: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1487787 grep "Illegal block number passed to ext2fs_test_block_bitmap" err | wc -l 35801 i.e. 84% rejection. The rest of the treatment will not be good grep "marked in use" testb.out | wc -l 6522 grep "not in use" testb.out | wc -l 35934 I don't know if it's because of a missing option, misuse or malfunction of the command. thank you for looking into the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 22 16:18:03 2023 InstallationDate: Installed on 2022-02-16 (339 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-19 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+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 2000626] Re: cp command loop when using ntfs3 package
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. If you would prefer live chat support, you can find an IRC support channel for your flavor of Ubuntu here: https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. And also the bug was reported against 'evince' which is a pdf reader but the description doesn't seem to have anything to do with pdf... ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2000626 Title: cp command loop when using ntfs3 package Status in evince package in Ubuntu: Invalid Bug description: Hello. I'm on ubuntu 22.04, I saw that ntfs3 is supposed to correctly write to an NTFS partition. I inform you that this is not the case. Here is my quick test First try on EFI computer: I remove the NTFS-3G package to be sure not to use it. When I detect that the cp command is no longer responding, I kill the process. Nothing is happening. I shut down the computer. During the shutdown phase, I am informed twice that the cp command is running. On reboot, I cannot access the partition. But I succeed in read-only mode. I run another normal ubuntu which tells me that I have to use windows to do an chkdsk But windows refuse to start, I duplicate by the dd command the NTFS partition in a larger NTFS partition stored in an external disk. Then I delete the NTFS partition from the internal disk. Then I repare windows. After restarting windows, I find that its disk space manager cannot access to the duplicate partition on external disk. There's no answer. So no letter to do the CHKDSK command. I decide to be more methodical in order to open a discussion and make a script to see a little what is happening. Second try on LEGACY computer: I make a script based on cp command. I try it on a normal NTFS partition in NTFS-3G. It ends perfectly well. I restart it on the same partition mounted in NTF3 He blocks. I make on another disk two partitions of identical size. I launch on one. It hangs almost in the same place. I launch on the other. It hangs in exactly the same place. This makes me open the bug. I can provide you with some information. @b:~$ sudo df -ah |egrep "Taille|root" Sys. de fichiers Taille Utilisé Dispo Uti% Monté sur /dev/sdb6 99G 28G 71G 29% /media/root/TestNTFS /dev/sdd10 60G 30G 31G 50% /media/root/TestNTFS1 /dev/sdd11 60G 30G 31G 50% /media/root/TestNTFS2 a@b:~$ First disk root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 14 3 18 Second disk root@b:~# mount -v -t ntfs3 /dev/sdd10 /$Rep mount: /media/root/TestNTFS1: /dev/sdd10 déjà monté sur /media/root/TestNTFS1. root@b:~# root@b:~# Na=0 Nb=25 time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 root@b:~# dd if=/dev/zero of=FIC count=1 bs=1K Rep=/media/root/TestNTFS2 mkdir $Rep mount -v -t ntfs3 /dev/sdd11 /$Rep Na=0 Nb=25 1+0 enregistrements lus 1+0 enregistrements écrits 1024 octets (1,0 kB, 1,0 KiB) copiés, 0,000783991 s, 1,3 MB/s mount : /dev/sdd11 monté sur /media/root/TestNTFS2. root@b:~# root@b:~# time for (( I=$Na; I < $Nb; I++ )); do for (( J=$Na; J < $Nb; J++ )); do for (( K=$Na; K < $Nb; K++ )); do echo -n -e avancement $I $J $K "\r \a"; for (( L=$Na; L < $Nb; L++ )); do mkdir -p $Rep/$I/$J/$K/$L ; for (( M=$Na; M < $Nb; M++ )); do cp FIC $Rep/$I/$J/$K/$L/$M; done; done; done; done; done avancement 15 3 10 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 Uname: Linux 5.15.0-56-generic x86_64 NonfreeKernelModules: zfs zunicode zav
[Desktop-packages] [Bug 2025961] Re: udisksctl mount some partitions in read mode for the user.
Thank you for your bug report. I'm pretty sure I've read that description before, did you also post about that issue and where? Also could you report the problem directly to upstream on https://github.com/storaged-project/udisks/issues ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2025961 Title: udisksctl mount some partitions in read mode for the user. Status in udisks2 package in Ubuntu: New Bug description: Good morning. Under ubuntu 23.04, I created four different partitions (ext4, ntfs, ext3, exfat). When I plug in the usb key, all four partitions are automatically mounted by the UDISKSCTL application which says it works for me. i am the user "a". journalctl -b -g Quest juin 19 19:21:53 a udisksd[1343]: Mounted /dev/sdd4 at /media/a/Question4 on behalf of uid 1000 juin 19 19:21:54 a udisksd[1343]: Mounted /dev/sdd3 at /media/a/Question3 on behalf of uid 1000 juin 19 19:21:54 a udisksd[1343]: Mounted /dev/sdd1 at /media/a/Question1 on behalf of uid 1000 juin 19 19:21:54 a udisksd[1343]: Mounted /dev/sdd2 at /media/a/Question2 on behalf of uid 1000 But I see that I am banned from writing for two of them. ls -ls /media/a | grep Quest 4 drwxr-xr-x 3 root root 4096 juin 19 19:02 Question1 4 drwxrwxrwx 1 a a 4096 juin 19 19:20 Question2 4 drwxr-xr-x 3 root root 4096 juin 19 19:03 Question3 32 drwxr-xr-x 2 a a 32768 juin 19 19:21 Question4 I thought that this version will finally properly address the problem that has existed for too long. I consider this to be a malfunction and not smart security. I summarize the problem. When an external disk contains an ext4 partition, the user is not allowed to write to this partition. He must do a command 'sudo chown/chmod ' It is not normal. This situation has lasted long enough. Do what is necessary so that the write mount of a USB medium is transparent to the user. It will do a lot of people a lot of good. Good day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2025961/+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 2003649] Re: Illegal block number passed to ext2fs_test_block_bitmap
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. If you would prefer live chat support, you can find an IRC support channel for your flavor of Ubuntu here: https://wiki.ubuntu.com/IRC/ChannelList. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: evince (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/2003649 Title: Illegal block number passed to ext2fs_test_block_bitmap Status in evince package in Ubuntu: Invalid Bug description: Hello I am trying to understand how the three commands testb, icheck and ncheck of the debugfs command work. My goal is to use them to find all the sectors allocated to a file. For this, I created a test set consisting of a 100% full EXT4 partition containing only one file. Here are the features: mount /dev/sda9 /mnt/TEST df --block-size=512 -text4 | grep TEST /dev/sda94245641392 0 100% /mnt/TEST So I think there are only 1064 (42456-41392) unused sectors. To check it, I make this script: rm -v testb.in for ((k=1;k<42457;k++));do echo testb $k >>testb.in done debugfs -f testb.in /dev/sda9 > testb.out 2>err then I control head -2 testb.out; tail -2 testb.out ; head -2 err; tail -1 err debugfs: testb 1 Block 1 marked in use debugfs: testb 42456 Block 42456 not in use debugfs 1.46.5 (30-Dec-2021) Illegal block number passed to ext2fs_test_block_bitmap #6656 for block bitmap for /dev/sda9 Illegal block number passed to ext2fs_test_block_bitmap #42456 for block bitmap for /dev/sda9 I can only find this reported incident: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1487787 grep "Illegal block number passed to ext2fs_test_block_bitmap" err | wc -l 35801 i.e. 84% rejection. The rest of the treatment will not be good grep "marked in use" testb.out | wc -l 6522 grep "not in use" testb.out | wc -l 35934 I don't know if it's because of a missing option, misuse or malfunction of the command. thank you for looking into the problem. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Jan 22 16:18:03 2023 InstallationDate: Installed on 2022-02-16 (339 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-08-19 (156 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/2003649/+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 2024949] Re: The update notification bubble is not working
it won't be fixed ** Changed in: gnome-software (Ubuntu) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/2024949 Title: The update notification bubble is not working Status in gnome-software package in Ubuntu: Invalid Bug description: The crux of the problem: The gnome-software notification bubble is not working. In theory, it should be shown when the system starts, but it does not start. Although the setting is enabled. the behavior is relevant: it just doesn't show up. koljab@koljab-NEO-M114:~$ cat /etc/os-release NAME="Green Linux" VERSION="21.2 (Victoria)" ID=linuxmint ID_LIKE="ubuntu debian" PRETTY_NAME="Green Linux 21.2 Cinnamon 64-bit" VERSION_ID="21" HOME_URL="https://greenlinux.ru/"; SUPPORT_URL="https://forum.linuxmint.su/"; BUG_REPORT_URL="http://linuxmint-troubleshooting-guide.readthedocs.io/ru/latest/"; PRIVACY_POLICY_URL="https://greenlinux.ru/"; VERSION_CODENAME=victoria UBUNTU_CODENAME=jammy koljab@koljab-NEO-M114:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2024949/+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 2025980] Re: can not setup keyboard and mouse separately
Thank you for your bug report. Which mouse model do you have? It looks similar to https://gitlab.freedesktop.org/upower/upower/-/issues/215 ** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #215 https://gitlab.freedesktop.org/upower/upower/-/issues/215 ** Changed in: upower (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/2025980/+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 2025982] [NEW] Warning 'failed to get driver name for fd 0' fails gtk tests
Public bug reported: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 ** Affects: mesa Importance: Unknown Status: Unknown ** Affects: mesa (Ubuntu) Importance: High Assignee: Timo Aaltonen (tjaalton) Status: In Progress ** Affects: mesa (Debian) Importance: Unknown Status: Unknown ** Tags: update-excuse ** Changed in: mesa (Ubuntu) Status: New => In Progress ** Changed in: mesa (Ubuntu) Importance: Undecided => High ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9199 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #1039922 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 ** Also affects: mesa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 Importance: Unknown Status: Unknown -- 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/2025982 Title: Warning 'failed to get driver name for fd 0' fails gtk tests Status in Mesa: Unknown Status in mesa package in Ubuntu: In Progress Status in mesa package in Debian: Unknown Bug description: The new version displays that warning which makes the gtk autopkgtest red Upstream https://gitlab.freedesktop.org/mesa/mesa/-/issues/9199 Debian https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039922 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2025982/+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 2025980] [NEW] can not setup keyboard and mouse separately
Public bug reported: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: no updated: Wed 05 Jul 2023 10:48:37 (548 seconds ago) has history: no has statistics: no unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' Daemon: daemon-version: 0.99.20 on-battery: no lid-is-closed: no lid-is-present: no critical-action: HybridSleep modaliases in 61-input-id-local.hwdb: id-input:modalias:input:b0003v046Dp101Ae0111* ID_INPUT_MOUSE=1 ID_INPUT=1 id-input:modalias:input:b0003v046Dp2010e0111* ID_INPUT_KEYBOARD=1 ID_INPUT=1 ** Affects: upower (Ubuntu) Importance: Undecided Status: New ** Tags: battery modalias ** Tags removed: modaliases ** Tags added: modalias -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/2025980 Title: can not setup keyboard and mouse separately Status in upower package in Ubuntu: New Bug description: I have Logitech wireless keyboard and wireless mouse, coonnected to the same Unifying receiver. battery level of these devices is reported correctly, but both are listed in power settings as a keyboard, making me a bit confusing, which device is run out of power, when I get 'low keyboard battery' message. trying to set correct device type via modaliases for mouse changes nothing, but when I change my keyboard to 'a mouse', I get two mice in power settings! thus, I can not setup these devices separately, to get 1 keyboard and 1 mouse, but only 2 keyboards or 2 mice. ubuntu unity 23.04 UPower client version 0.99.20 UPower daemon version 0.99.20 output of 'upower -d': Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_0 native-path: hidpp_battery_0 model:K800 serial: b2-69-6e-91 power supply: no updated: Wed 05 Jul 2023 10:57:43 (2 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: low battery-level: low percentage: 10% (should be ignored) icon-name: 'battery-caution-symbolic' Device: /org/freedesktop/UPower/devices/battery_hidpp_battery_1 native-path: hidpp_battery_1 model:Performance MX serial: 04-81-33-3a power supply: no updated: Wed 05 Jul 2023 10:57:37 (8 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: discharging warning-level: none battery-level: high percentage: 70% (should be ignored) icon-name: 'battery-good-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply:
[Desktop-packages] [Bug 1563184] Re: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process"
Is this still a problem? If yes, does the --disable-gpu flag help? -- 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/1563184 Title: Chromium-browser armhf crashes with "InitializeSandbox() called with multiple threads in process gpu-process" Status in chromium-browser package in Ubuntu: Confirmed Status in chromium-browser package in Arch Linux: Confirmed Bug description: crashes on startup with [2457:2457:0322/182419:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process Segmentation fault System ODROID XU3 armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1563184/+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 2025916] Re: command-chain ... not found
I think you had removed the gnome-42-2204 and this caused the interface not to connect. > sudo apt install snap --reinstall > sudo apt install snap --reinstall chromium You conflated snap[1] and snapd[2] in those instances. If your intention was to reinstall Chromium (and not snapd), then you could have used either of apt install --reinstall chromium snap remove chromium && snap install chromium [1] https://packages.ubuntu.com/mantic/snap [2] https://packages.ubuntu.com/mantic/snapd ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/2025916 Title: command-chain ... not found Status in chromium-browser package in Ubuntu: Incomplete Bug description: (I'm not familiar with snap, was migrated to it by *buntu for chromium-browser) Received the usual, well-know notification of having to snap refresh, some time given ... Closed chromium and issue the usual 'sudo snap refresh'. It went through, without any error indication. Restarting chromium failed, on the command line with $ chromium-browser Content snap command-chain for /snap/chromium/2529/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected Using Firefox, after some Google I found and tried $ sudo apt install snap --reinstall ... The following NEW packages will be installed: snap And, no, I did not uninstall it. This is my work laptop, and I do only the basic and necessary system administration on it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025916/+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 2025961] Re: udisksctl mount some partitions in read mode for the user.
I think that anyone capable of using a computer has the right to write to a USB key regardless of its formatting. You don't have to be a genius with superpowers! enfants@p:/media/enfants$ ls -als total 127 4 drwxr-x---+ 25 rootroot 4096 juil. 5 09:11 . 4 drwxr-xr-x 11 rootroot 4096 juil. 5 09:10 .. 16 drwxr-xr-x 1 rootroot0 juil. 5 08:32 btrfs 4 drwxr-xr-x 2 enfants enfants 4096 juil. 5 09:11 exfat 4 drwxr-xr-x 3 rootroot 4096 juil. 5 08:32 ext2 4 drwxr-xr-x 3 rootroot 4096 juil. 5 08:32 ext3 4 drwxr-xr-x 3 rootroot 4096 juil. 5 08:32 ext4 4 drwxr-xr-x 2 rootroot 4096 juil. 5 08:32 f2fs 16 drwxr-xr-x 2 enfants enfants 16384 janv. 1 1970 FAT16 1 drwxr-xr-x 2 enfants enfants 512 janv. 1 1970 FAT32 1 drwxr-xr-x 4 enfants enfants 512 janv. 1 1970 FAT-DEUXUSB 0 drwxr-xr-x 1 enfants enfants 3 juil. 5 09:11 hfsplus 1 drwxr-xr-x 2 rootroot 4096 juil. 5 08:34 nilfs2 4 drwxrwxrwx 1 enfants enfants 4096 juil. 5 08:34 ntfs 0 drwxr-xr-x 4 rootroot 80 juil. 5 09:11 reiserfs 0 drwxr-xr-x 2 rootroot6 juil. 5 08:35 xfs enfants@p:/media/enfants$ cd ext4 enfants@p:/media/enfants/ext4$ sudo mkdir titi enfants n'apparaît pas dans le fichier sudoers. Cet incident sera signalé. enfants@p:/media/enfants/ext4$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2025961 Title: udisksctl mount some partitions in read mode for the user. Status in udisks2 package in Ubuntu: New Bug description: Good morning. Under ubuntu 23.04, I created four different partitions (ext4, ntfs, ext3, exfat). When I plug in the usb key, all four partitions are automatically mounted by the UDISKSCTL application which says it works for me. i am the user "a". journalctl -b -g Quest juin 19 19:21:53 a udisksd[1343]: Mounted /dev/sdd4 at /media/a/Question4 on behalf of uid 1000 juin 19 19:21:54 a udisksd[1343]: Mounted /dev/sdd3 at /media/a/Question3 on behalf of uid 1000 juin 19 19:21:54 a udisksd[1343]: Mounted /dev/sdd1 at /media/a/Question1 on behalf of uid 1000 juin 19 19:21:54 a udisksd[1343]: Mounted /dev/sdd2 at /media/a/Question2 on behalf of uid 1000 But I see that I am banned from writing for two of them. ls -ls /media/a | grep Quest 4 drwxr-xr-x 3 root root 4096 juin 19 19:02 Question1 4 drwxrwxrwx 1 a a 4096 juin 19 19:20 Question2 4 drwxr-xr-x 3 root root 4096 juin 19 19:03 Question3 32 drwxr-xr-x 2 a a 32768 juin 19 19:21 Question4 I thought that this version will finally properly address the problem that has existed for too long. I consider this to be a malfunction and not smart security. I summarize the problem. When an external disk contains an ext4 partition, the user is not allowed to write to this partition. He must do a command 'sudo chown/chmod ' It is not normal. This situation has lasted long enough. Do what is necessary so that the write mount of a USB medium is transparent to the user. It will do a lot of people a lot of good. Good day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/2025961/+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 2023623] Re: [SRU] Disable pressure for Precision5680 2nd source touchpad
This bug was fixed in the package libinput - 1.22.1-1ubuntu0.1 --- libinput (1.22.1-1ubuntu0.1) lunar; urgency=medium * Disable pressure for Precision5680 2nd source touchpad (LP: #2023623) - d/p/0001-quirks-Dell-Mayabay-Pressure-Pad.patch -- Kai-Chuan Hsieh Thu, 15 Jun 2023 11:39:41 +0800 ** Changed in: libinput (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2023623 Title: [SRU] Disable pressure for Precision5680 2nd source touchpad Status in OEM Priority Project: New Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Jammy: Fix Released Status in libinput source package in Lunar: Fix Released Bug description: [ Impact ] * libinput will detect contact size by pressure if the touchpad report pressure event, and it has threshold need to be tuned, however, the tuning might need be done every time if the touchpad firmware update. To relieve the workload, touchpad vendor decide to disable pressure event for libinput in upstream. * It will disable pressure event for i2c touchpad vid 0x06cb pid 0xcfa0 [ Test Plan ] * on Dell precision 5680 with touchpad vid:0x06cb pid:0xcfa0 * check left/right button * check 2 fingers scrolling * check 1 finger drag and drop * check 2 fingers drag and drop [ Where problems could occur ] * The quirk match the PID VID only, it won't impact other touchpad [ Other Info ] * https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/869 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023623/+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
Good! Marking it as fixed then, thank you again for reporting back. ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Fix Released -- 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 chromium-browser package in Ubuntu: Fix Released Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: 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 (20200
[Desktop-packages] [Bug 2023623] Re: [SRU] Disable pressure for Precision5680 2nd source touchpad
This bug was fixed in the package libinput - 1.20.0-1ubuntu0.3 --- libinput (1.20.0-1ubuntu0.3) jammy; urgency=medium * Disable pressure for Precision5680 2nd source touchpad (LP: #2023623) - d/p/0001-quirks-Dell-Mayabay-Pressure-Pad.patch -- Kai-Chuan Hsieh Tue, 13 Jun 2023 13:59:01 +0800 ** Changed in: libinput (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/2023623 Title: [SRU] Disable pressure for Precision5680 2nd source touchpad Status in OEM Priority Project: New Status in libinput package in Ubuntu: Fix Released Status in libinput source package in Jammy: Fix Released Status in libinput source package in Lunar: Fix Released Bug description: [ Impact ] * libinput will detect contact size by pressure if the touchpad report pressure event, and it has threshold need to be tuned, however, the tuning might need be done every time if the touchpad firmware update. To relieve the workload, touchpad vendor decide to disable pressure event for libinput in upstream. * It will disable pressure event for i2c touchpad vid 0x06cb pid 0xcfa0 [ Test Plan ] * on Dell precision 5680 with touchpad vid:0x06cb pid:0xcfa0 * check left/right button * check 2 fingers scrolling * check 1 finger drag and drop * check 2 fingers drag and drop [ Where problems could occur ] * The quirk match the PID VID only, it won't impact other touchpad [ Other Info ] * https://gitlab.freedesktop.org/libinput/libinput/-/merge_requests/869 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2023623/+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 1992688] Update Released
The verification of the Stable Release Update for ubuntu-meta 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-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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 1992688] Re: firefox deb not installed
This bug was fixed in the package ubuntu-meta - 1.481.1 --- ubuntu-meta (1.481.1) jammy; urgency=medium * Refreshed dependencies * Added firefox to desktop-minimal-recommends [amd64 arm64 armhf], desktop-recommends [amd64 arm64 armhf] as it provides dpkg alternatives for x-www-browser and gnome-www-browser. (LP: #1992688) -- Brian Murray Thu, 27 Apr 2023 01:17:57 -0700 ** Changed in: ubuntu-meta (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1992688 Title: firefox deb not installed Status in firefox package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Fix Released Status in firefox source package in Jammy: Invalid Status in ubuntu-meta source package in Jammy: Fix Released Bug description: Impact -- Applications which use x-www-browser to launch a browser will not work on a freshly installed Ubuntu 22.04 system as the firefox deb (which provides x-www-browser) is not installed. Test Plan - 1) Install Ubuntu 22.04.2 using an amd64 desktop iso image 2) Open a terminal 3) Run x-www-browser www.ubuntu.com 4) Observe a command not found message which recommends installing firefox Installing of a daily build of Ubuntu 22.04 with -proposed enabled and ubuntu-desktop version 1.481.1 will not exhibit the above problem. Where problems could occur -- Other Info -- I tested an upgrade from Ubuntu 20.04 to Ubuntu 22.04 and the firefox deb was not removed during the upgrade process so upgrades are a non-issue. Original Description Bug 1964036 leads me to believe that the firefox deb provides some important functionality (the firefox favourite icon in the gnome shell dock) but there is nothing that would require the deb to be installed (it is not seeded nor has an rdep) and the package description indicates that it can be safely removed. Is there some important functionality that it provides? ProblemType: BugDistroRelease: Ubuntu 22.10 Package: ubuntu-release-upgrader-core 1:22.10.8 ProcVersionSignature: User Name 5.19.0-19.19-generic 5.19.7 Uname: Linux 5.19.0-19-generic x86_64 ApportVersion: 2.23.1-0ubuntu2 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Oct 12 11:30:46 2022 InstallationDate: Installed on 2022-04-27 (167 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to kinetic on 2022-10-12 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1992688/+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
