[Desktop-packages] [Bug 1978777] Re: [Intel 9560] wifi connection does not work properly
** Summary changed: - NOt able to Install any updates + [Intel 9560] wifi connection does not work properly ** Package changed: xorg (Ubuntu) => linux-hwe-5.4 (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1978777 Title: [Intel 9560] wifi connection does not work properly Status in linux-hwe-5.4 package in Ubuntu: New Bug description: I am not able to say much, since I don't know how to describe the problem. Yet I can mention that whenever I am trying to download the files like whatever is required to upgrade the software, the wifi connection does not work properly(Mobile Data, usually). I have checked if there is an error in the Wifi module by running the same, within Windows 11 updates, which worked normally as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 11:44:08 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.4.0-104-generic, x86_64: installed nvidia, 470.103.01, 5.4.0-107-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] InstallationDate: Installed on 2020-10-26 (596 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 3938:1032 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=aafecb7f-435a-43bb-a2ed-eabab507c6ad ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.vendor: Insyde dmi.bios.version: F.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FC dmi.board.vendor: HP dmi.board.version: 42.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.50:bd08/18/2021:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FC:rvr42.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 7LH02PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1978777/+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 1976204] Re: Screen freeze
I think a dongle is fine. I just wanted to avoid getting stuck on unrelated bugs that docking stations might trigger. -- 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/1976204 Title: Screen freeze Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+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 1978707] Re: Dragging windows cause gnome-shell to hangs up temporarily
** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/1978707 Title: Dragging windows cause gnome-shell to hangs up temporarily Status in Ubuntu: Incomplete Bug description: Ubuntu 22.04, upgraded from previous versions, AMD Ryzen 7 5700G integrated video card, Wayland session. Steps to reproduce: 1. Open an app window. I used Chromium, but can also reproduce with nautilus or even gnome-settings. 2. Move it constantly. Expected behavior: Window moves. Actual behavior: Whole gnome-shell session hangs up for a several seconds with a lot of "Stack trace for context" errors in the logs. I attached a demo video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 19:59:38 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1978707/+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 1976567] Re: Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor
I just encountered the bug again. When I turned on the monitor the login screen is at 1024x768 and the system log shows it is using Wayland: Jun 15 14:03:49 nine gnome-shell[1225]: Running GNOME Shell (using mutter 42.1) as a Wayland display server Although the monitor was plugged in when the system booted, the kernel failed to get a working connection: Jun 15 14:03:50 nine kernel: i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful That's _after_ the login screen had started. So the bug is occurring when the kernel can detect a monitor (hence bug 1919400 doesn't happen) but can't establish a reliable display signal. For me, the fix was just to log in as usual. Then the correct screen resolution is detected and used. If the problem persists for you after logging in then it's a sign you probably need to replug or replace the monitor data cable. I don't see any real bug here unless it's the kernel failing to train when it shouldn't fail. ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => Opinion ** No longer affects: mutter (Ubuntu) ** Summary changed: - Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor + [i915] Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor -- 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/1976567 Title: [i915] Desktop resolution was set incorrectly (1024x768) until I booted up the PC AFTER turning on the monitor Status in linux package in Ubuntu: Opinion Bug description: Whenever I boot up my PC, I turn on the monitor as well. When this happens, the Intel Mesa graphics loads, and my screen ends up being small with large pixelated icons. The resolution was capped at 1024x768. Only after I reboot my PC multiple times without changing the display settings did the resolution increase to 1680x1050, the correct resolution. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 1 21:07:53 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0589] InstallationDate: Installed on 2022-05-22 (10 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Gateway DX4860 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/01/2011 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02-A1 dmi.board.name: IPISB-VR dmi.board.vendor: Gateway dmi.board.version: 1.01 dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku: dmi.product.family: Gateway Desktop dmi.product.name: DX4860 dmi.sys.vendor: Gateway version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1976567/+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 1978777] [NEW] NOt able to Install any updates
Public bug reported: I am not able to say much, since I don't know how to describe the problem. Yet I can mention that whenever I am trying to download the files like whatever is required to upgrade the software, the wifi connection does not work properly(Mobile Data, usually). I have checked if there is an error in the Wifi module by running the same, within Windows 11 updates, which worked normally as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 11:44:08 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.4.0-104-generic, x86_64: installed nvidia, 470.103.01, 5.4.0-107-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] InstallationDate: Installed on 2020-10-26 (596 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b627 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 3938:1032 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Laptop 15-dk0xxx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-107-generic root=UUID=aafecb7f-435a-43bb-a2ed-eabab507c6ad ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/18/2021 dmi.bios.vendor: Insyde dmi.bios.version: F.50 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85FC dmi.board.vendor: HP dmi.board.version: 42.47 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.50:bd08/18/2021:svnHP:pnHPPavilionGamingLaptop15-dk0xxx:pvrType1ProductConfigId:rvnHP:rn85FC:rvr42.47:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-dk0xxx dmi.product.sku: 7LH02PA#ACJ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1978777 Title: NOt able to Install any updates Status in xorg package in Ubuntu: New Bug description: I am not able to say much, since I don't know how to describe the problem. Yet I can mention that whenever I am trying to download the files like whatever is required to upgrade the software, the wifi connection does not work properly(Mobile Data, usually). I have checked if there is an error in the Wifi module by running the same, within Windows 11 updates, which worked normally as expected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-generic 5.4.174 Uname: Linux 5.4.0-107-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jun 15 11:44:08 2022 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.4.0-104-generic, x86_64: installed nvidia, 470.103.01, 5.4.0-107-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:85fc] InstallationDate: Installed on 20
[Desktop-packages] [Bug 1976204] Re: Screen freeze
@vanvugt, Sure, but we don't have type-c monitor in Lab. I'm using a type-c to HDMI dongle. -- 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/1976204 Title: Screen freeze Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: In Progress Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1976204] Re: Screen freeze
Per comment #18 please also avoid using a dock in testing. We would like to minimize the number of variables. -- 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/1976204 Title: Screen freeze Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+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 1976204] Re: Screen freeze
Thanks for creating bug 1978764. The freeze does not appear to be one that is visible in stack traces so my next theory is a KMS/DRM screen update failure. To investigate that please try these separately: * Disable atomic KMS in /etc/environment: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and reboot. * Follow the instructions in comment #19 so we can see all the interaction with the kernel DRM functions at the time of the freeze. -- 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/1976204 Title: Screen freeze Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: New Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about thi
[Desktop-packages] [Bug 1978774] [NEW] nm-openvpn-dialog.ui > missing option translatable=yes
Public bug reported: I found it network-manager-openvpn version 1.8.12 properties/nm-openvpn-dialog.ui line 130 missing option translatable ="yes original : No need fix : No https://ibb.co/zngnZqv ** Affects: network-manager-openvpn (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1978774 Title: nm-openvpn-dialog.ui > missing option translatable=yes Status in network-manager-openvpn package in Ubuntu: New Bug description: I found it network-manager-openvpn version 1.8.12 properties/nm-openvpn-dialog.ui line 130 missing option translatable ="yes original : No need fix : No https://ibb.co/zngnZqv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1978774/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
FYI I have sent a MR to the upstream AppArmor project to remove this dbus deny rule from the exo-open abstraction: https://gitlab.com/apparmor/apparmor/-/merge_requests/884 -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in apparmor package in Ubuntu: New Status in evince package in Ubuntu: In Progress Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1978765] [NEW] App doesn't open via desktop executor
Public bug reported: > lsb_release -rd Description:Ubuntu 22.04 LTS Release:22.04 > apt-cache policy gnome-text-editor gnome-text-editor: Installed: 42.1-0ubuntu1 Candidate: 42.1-0ubuntu1 Version table: *** 42.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 100 /var/lib/dpkg/status 42.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages I installed the app via `sudo apt install gnome-text-editor` but I'm unable to open it with the [ilia desktop executor](https://github.com/regolith-linux/ilia). I can open the new `gnome-console` app just fine with `ilia`. I can also open `gnome-text- editor` from the terminal with `gtk-launch org.gnome.TextEditor` and it fires right up. I do see the the following output though: > gtk-launch org.gnome.TextEditor Gtk-Message: 16:01:19.175: Failed to load module "xapp-gtk3-module" I'd be happy to help debug, I just need some pointers. Thanks for making a great app! ** Affects: gnome-text-editor (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1978765 Title: App doesn't open via desktop executor Status in gnome-text-editor package in Ubuntu: New Bug description: > lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 > apt-cache policy gnome-text-editor gnome-text-editor: Installed: 42.1-0ubuntu1 Candidate: 42.1-0ubuntu1 Version table: *** 42.1-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 100 /var/lib/dpkg/status 42.0-2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages I installed the app via `sudo apt install gnome-text-editor` but I'm unable to open it with the [ilia desktop executor](https://github.com/regolith-linux/ilia). I can open the new `gnome-console` app just fine with `ilia`. I can also open `gnome- text-editor` from the terminal with `gtk-launch org.gnome.TextEditor` and it fires right up. I do see the the following output though: > gtk-launch org.gnome.TextEditor Gtk-Message: 16:01:19.175: Failed to load module "xapp-gtk3-module" I'd be happy to help debug, I just need some pointers. Thanks for making a great app! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1978765/+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 1949291] Re: LibreOffice has started displaying a donation nag
Sebastien, I am tired of the bias developers tend to show. Bug trackers are notoriously difficult to use for normal users, let alone those who speak English. There is clearly annoyance if you got even one report. -- Adolfo f...@libreoffice.org -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1949291 Title: LibreOffice has started displaying a donation nag Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Triaged Bug description: I just opened up a spreadsheet (technically a CSV file, but who's counting), to discover LibreOffice displaying an eye-catching blue "Your donations support our worldwide community." banner just below the toolbars and about a toolbar and a half tall. This irritating nag is apparently supposed to display every 90 to 180 days with no in-application means to disable it permanently, and there's apparently also a "Help us make LibreOffice even better!" banner that can appear too. According to this blog post... https://www.remembertheusers.com/2019/11/0580-libreoffice-nag- notices.html ...it is not responsive to configuration overrides within the user profile and the only apparent solution that doesn't require patching the source and rebuilding is to create a file containing the following markup in `$BASEDIR/share/registry` (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu package): http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:oor="http://openoffice.org/2001/registry";> http://openoffice.org/2004/installation"; oor:name="Setup" oor:package="org.openoffice"> 0 0 Regardless of how it's achieved, I think it's tasteless, irritating, and probably doesn't give a very good image to any office customers Ubuntu may have downstream for random employees to be receiving nag banners like that in IT-installed software. Please consider patching it out or otherwise ensuring it never triggers in distro-provided builds of LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Oct 31 04:32:03 2021 SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1949291/+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 1949969] Re: Libreoffice SNAP 7.2.1 and 7.2.2 no file format selection based on manually entered extension
** Tags added: snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1949969 Title: Libreoffice SNAP 7.2.1 and 7.2.2 no file format selection based on manually entered extension Status in libreoffice package in Ubuntu: New Bug description: When saving a file, if you enter the extension manually, no auto file format selection is made. Tested on LO SNAP 7.2.1 and 7.2.2 System: Distributor ID: Neon Description:KDE neon User - Plasma 25th Anniversary Edition Release:20.04 Codename: focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1949969/+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 1978488] Re: LibreOffice Writer lags freezes high CPU 22.04 LTS
** Changed in: libreoffice (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1978488 Title: LibreOffice Writer lags freezes high CPU 22.04 LTS Status in Ubuntu MATE: Confirmed Status in libreoffice package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-470 package in Ubuntu: New Status in nvidia-graphics-drivers-510 package in Ubuntu: New Bug description: Upgraded to 22.04 LTS (20.04 no issues). Using Nvidia 4xx series driver. 48GB RAM, dual 1080ti gpu, i7 cpu. LibreOffice Writer constantly lags, losing function, freezes (does not crash) with any type of writer document (odt or xslx). New single page or existing multi-page documents, doesn't matter, same issue after a minute or two. Hates text selection, mouse-wheel scrolling is a tell- tale sign. New Writer windows opened during lag are black. CPU usage in htop is very high for soffice.bin, ~60 - 80%. Must pkill the soffice.bin and use file recover but lag freeze up will occur again soon after opening. I experience the issue with all three installation methods: snap, distro command-line install, or using the LibreOffice ppa "fresh". I've tried changing OpenCL settings, disabling all extensions, disable smooth scrolling, disabling java, have purged install/reinstall and limiting to single window. I have the Marco ppa installed (ppa:ubuntu- mate-dev/marco). Doesn't seem to matter or what mate-tweak option is selected. LO using Yaru or other theme; doesn't matter same effect. Terminal does not show me any helpful errors when Writer is called directly from command line, at least I can easily identify. Guessing this is upstream of MATE and a libreoffice thing; a few similar issues around the web but no good workaround. I can update my exact specs and kernel later as required. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-03-27 (1174 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) Package: nvidia-graphics-drivers-510 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Tags: third-party-packages jammy Uname: Linux 5.15.0-37-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2022-06-03 (10 days ago) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1978488/+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 1978757] lspci.txt
apport information ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1978757/+attachment/5597305/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Can't playback preview on Intel IPU6 camera platform Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 1978757] lsusb.txt
apport information ** Attachment added: "lsusb.txt" https://bugs.launchpad.net/bugs/1978757/+attachment/5597306/+files/lsusb.txt ** Description changed: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. - --- + And https://webcamtests.com/ can work successfully. + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: - cheese41.1-1build1 - cheese-common 41.1-1build1 + cheese41.1-1build1 + cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. ** Tags added: originate-from-1973667 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Can't playback preview on Intel IPU6 camera platform Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSi
[Desktop-packages] [Bug 1978757] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1978757/+attachment/5597304/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Can't playback preview on Intel IPU6 camera platform Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 1978757] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1978757/+attachment/5597303/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Can't playback preview on Intel IPU6 camera platform Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 1978757] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1978757/+attachment/5597302/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Can't playback preview on Intel IPU6 camera platform Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 1978757] CheeseDebug.txt.gz
apport information ** Attachment added: "CheeseDebug.txt.gz" https://bugs.launchpad.net/bugs/1978757/+attachment/5597300/+files/CheeseDebug.txt.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Can't playback preview on Intel IPU6 camera platform Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 1978757] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1978757/+attachment/5597301/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1978757 Title: Can't playback preview on Intel IPU6 camera platform Status in OEM Priority Project: New Status in cheese package in Ubuntu: New Bug description: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1978757/+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 1978757] [NEW] Can't playback preview on Intel IPU6 camera platform
Public bug reported: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. And https://webcamtests.com/ can work successfully. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-14 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 MachineType: Dell Inc. XPS 9320 Package: cheese 41.1-1build1 [origin: unknown] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: jammy third-party-packages wayland-session gstreamer-error Uname: Linux 5.15.0-36-generic x86_64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/06/2022 dmi.bios.release: 89.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 89.4.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr89.4.1:bd06/06/2022:br89.4:svnDellInc.:pnXPS9320:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0AF3: dmi.product.family: XPS dmi.product.name: XPS 9320 dmi.product.sku: 0AF3 dmi.sys.vendor: Dell Inc. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: cheese (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected gstreamer-error jammy oem-priority originate-from-1973667 somerville third-party-packages wayland-session ** Tags added: oem-priority ** Tags added: apport-collected gstreamer-error jammy third-party- packages wayland-session ** Description changed: Cheese can't playback preview on Intel IPU6 camera platform. (cheese:6772): cheese-WARNING **: 10:26:06.389: Internal data stream error.: ../libs/gst/base/gstbasesrc.c(3127): gst_base_src_loop (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstPipeWireSrc:pipewiresrc1: streaming stopped, reason not-negotiated (-4) Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed Unsupported modifier, resource creation failed. XXX: resource creation failed On focal the gst-launch line is v4l2src, but it is changed to pipewiresrc on jammy. I tried command $ gst-launch-1.0 v4l2src ! glimagesink It can have camera image in the opened window. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X18 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-06-14 (0 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220425-25 + MachineType: Dell Inc. XPS 9320 + Package: cheese 41.1-1build1 [origin: unknown] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-36.37-generic 5.15.35 + RelatedPackageVersions: + cheese41.1-1build1 + cheese-common 41.1-1build1 + Tags: jammy third-party-packages wayland-session gstreamer-error + Uname: Linux 5.15.0-36-generic x86_64 + UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGro
[Desktop-packages] [Bug 1977875] Re: Ubuntu Desktop boot hangs absent zeroconf packets and after avahi-daemon purge
Thanks for the bug report. Please: 1. Reproduce the hang again. 2. Reboot into recovery mode. You need to be quick to press Esc at the right time at the end of the BIOS screen. 3. Run: journalctl -b-1 > prevboot1.txt journalctl -b-2 > prevboot2.txt journalctl -b-3 > prevboot3.txt 4. Attach the resulting text files here. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/1977875 Title: Ubuntu Desktop boot hangs absent zeroconf packets and after avahi- daemon purge Status in Ubuntu: Incomplete Bug description: Our install procedures customarily airgap machines during installation, purge unnecessary and irrelevant packages such as avahi- daemon, ufw, netplan.io, ModemManager, network-manager, fprintd, etc., configure networking via systemd-networkd, and enable an iptables firewall to be in place before the network is up, all before exposing any machine to a network for further configuration. The iptables rules drop all zeroconf and broadcast traffic for obvious security reasons. The kernel is typically configured to forward packets, so these DROP rules are in the mangle table's PREROUTING chain, to scrub them before reaching the filter table's INPUT or FORWARD chains. Presumably, this also scrubs such traffic to the loopback interface. INPUT, OUTPUT, and FORWARD rules ACCEPT suitable traffic before a default DROP rule in each case. We have found the Ubuntu desktop 22.04 boot process to be especially fragile. System boot hangs every time, typically presenting as either an ordering cycle or a failure of partition mounts, which may be related. Occasionally, we note that dmesg.service and networkd- dispatcher.service fail by reason of time-out. Often, the last message in tty1 is Reached target Host and Network Name Lookups. Over the course of weeks, we have debugged our install scripts and packet filtering and although the modality is unclear, the cause is an absence of zeroconf network traffic or the purge of the avahi-daemon package. Curiously, none of this configuration has any effect and the boot process proceeds normally and as expected so long as a machine's Ethernet cables are unplugged. Once connected, attempts to upgrade a system (# apt update && apt upgrade) themselves hang, the machine reboots successfully, and then after dpkg --reconfigure -a, the attempted reboot hangs as before. Ubuntu desktop 20.04 machines do not exhibit this behavior. The expectation is that local processes would utilize d-bus or, if ip traffic somehow was necessary for local interprocess communication, that those processes would rely on name resolution other than broadcast traffic. Alternatively, the expectation is that the necessity of deliberately opening this security vulnerability would be well and conspicuously documented, including identifying the processes, ports, protocols, sources, destinations, interfaces, sockets, and any IP or MAC address so that the traffic can be suitably filtered. Persisting avahi-daemon and zeroconf is a non-starter. Release: Ubuntu desktop 22.04 LTS Version: gnome-shell 42.0-2ubuntu1 Expected behavior: Boot to gdm3 login prompt. Actual behavior: Consistent boot hang. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jun 7 10:00:18 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-05-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1977875/+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 1978700] Re: Update gnome-text-editor to 42.2
This bug was fixed in the package gnome-text-editor - 42.2-1 --- gnome-text-editor (42.2-1) unstable; urgency=medium * Team upload * New upstream release (LP: #1978700) -- Nathan Pratta Teodosio Mon, 13 Jun 2022 14:33:42 -0300 ** Changed in: gnome-text-editor (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1978700 Title: Update gnome-text-editor to 42.2 Status in gnome-text-editor package in Ubuntu: Fix Released Status in gnome-text-editor source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the GNOME 42 series: https://gitlab.gnome.org/GNOME/gnome-text-editor/-/blob/42.2/NEWS Test Case - Install the new gnome-text-editor Verify that the app still opens a variety of files. What Could Go Wrong --- This app is not included by default in any Ubuntu flavor. This app should fall under the GNOME microrelease exception since it is a part of core GNOME since GNOME 42. It's not been formally added to the discourse wiki yet. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1978700/+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 1978707] Re: Dragging windows cause gnome-shell to hangs up temporarily
Thanks for the bug report. In most cases we find that third-party extensions are to blame, and you seem to have a lot enabled: 'focu...@armonge.info', 'donotdist...@kylecorry31.github.io', 'alt-tab- raise-first-win...@system76.com', 'always-show-workspa...@system76.com', 'batteryicon...@kylecorry31.github.io', 'pop-shop-deta...@system76.com', 'pop-suspend-but...@system76.com', 'system76-po...@system76.com', 'hidesystemacti...@pratap.fastmail.fm', 'task- wid...@juozasmiskinis.gitlab.io', 'cast-to-tv-desktop- ad...@rafostar.github.com', 'cast-to...@rafostar.github.com', 'cast-to- tv-links-ad...@rafostar.github.com', 'dash-to-pl...@hardpixel.eu', 'coverflowalt...@palatis.blogspot.com', 'vit...@corecoding.com', 'arcm...@arcmenu.com', 'remove-dropdown-arr...@mpdeimos.com', 'dash-to- d...@micxgx.gmail.com', 'kit...@fopdoodle.net', 'startup- meas...@marco.trevi.me' Please start by removing all of them by: cd ~/.local/share/gnome-shell rm -rf extensions and then log in again. Does the bug still occur? ** 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/1978707 Title: Dragging windows cause gnome-shell to hangs up temporarily Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04, upgraded from previous versions, AMD Ryzen 7 5700G integrated video card, Wayland session. Steps to reproduce: 1. Open an app window. I used Chromium, but can also reproduce with nautilus or even gnome-settings. 2. Move it constantly. Expected behavior: Window moves. Actual behavior: Whole gnome-shell session hangs up for a several seconds with a lot of "Stack trace for context" errors in the logs. I attached a demo video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 19:59:38 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978707/+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 1978746] [NEW] Had to restart Modem Manager to establish Mobile broadband connection from hotswap
Public bug reported: [Description] After hot-swapping sim 1 and sim 2, modem manager restart is needed to be able to establish cellular connection. [Expected result] After hot-swapping sim 1 and sim 2, cellular connection could be established after selecting the appropriate APN profile. [Actual result] After hot-swapping sim 1 and sim 2, cellular connection cannot be established after selecting the appropriate APN profile [Steps to reproduce] 1. Assuming that cellular connection was already established using sim 1, remove sim 1 from the sim card slot while the system is still booted on. 2. Insert sim 2 in the sim card slot. 3. Check that the sim card is already recognize by running "mmcli -m " to check if the sim card information is reflected. 4. From the mobile broadband GUI, select the appropriate APN profile for sim 2. Notice that cellular connection cannot be established ==> PROBLEM [Workaround] 1. Run "sudo systemctl restart ModemManager" to restart Modem Manager 2. Select the appropriate APN profile to establish cellular connection Ubuntu release version: Ubuntu 20.04.4 LTS Kernel version: 5.15.0-33-generic (hwe-kernel) ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1978746 Title: Had to restart Modem Manager to establish Mobile broadband connection from hotswap Status in modemmanager package in Ubuntu: New Bug description: [Description] After hot-swapping sim 1 and sim 2, modem manager restart is needed to be able to establish cellular connection. [Expected result] After hot-swapping sim 1 and sim 2, cellular connection could be established after selecting the appropriate APN profile. [Actual result] After hot-swapping sim 1 and sim 2, cellular connection cannot be established after selecting the appropriate APN profile [Steps to reproduce] 1. Assuming that cellular connection was already established using sim 1, remove sim 1 from the sim card slot while the system is still booted on. 2. Insert sim 2 in the sim card slot. 3. Check that the sim card is already recognize by running "mmcli -m " to check if the sim card information is reflected. 4. From the mobile broadband GUI, select the appropriate APN profile for sim 2. Notice that cellular connection cannot be established ==> PROBLEM [Workaround] 1. Run "sudo systemctl restart ModemManager" to restart Modem Manager 2. Select the appropriate APN profile to establish cellular connection Ubuntu release version: Ubuntu 20.04.4 LTS Kernel version: 5.15.0-33-generic (hwe-kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978746/+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 1961458] Re: chown of script directory and contents
Brian, sorry, the bug is open now. Thanks ** Information type changed from Private Security to Public Security -- 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/1961458 Title: chown of script directory and contents Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Bug description: [Impact] Potential security issues in ApplyPolicy due to race when scripts are enabled. [Test Plan] 1. Attach your machine to Ubuntu Advantage to get script support. 2. Add a script to one GPO for user login/logout 3. Login as an user, starting a new user session (no session should be currently running for that given user). 4. Check the permissions are following what is described from the discussion below. [Where problems could occur] Script support was added recently, and it needs Ubuntu Advantage enablement to be activated. However, to this day, there is still no official ubuntu-advantage-desktop-daemon packaged on focal. ./internal/policies/scripts/scripts.go ApplyPolicy() unsafe owner changes: Changing the scripts directory owner allows any user processes to create symbolic links within, and then they can take ownership of any file on writable mounts. If the files must be owned by the user, the best way is to switch to the user's uid before creating the files. fchown(2) of the file descriptor before closing it should also work. I lose track of what's happening around the "Running machine startup scripts" -- it looks to me like adsys is also *executing* the scripts that were moments ago given to the user to modify. It is not safe for root to run user-owned files. Does the user *have* to own the directory and scripts? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1961458/+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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: Fix Released Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: - Impact software-properties-gtk hit an exception when dealing some drivers - Test Case On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and try to install libcamhal-ipu6ep0 using software-properties-gtk https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 should not include reports on the new version - Regression potential The change make the driver code ignore one extra type of error, it shouldn't impact on any of the already working cases. Ensure that drivers that were hitting the error correctly install now [racb] It's possible that we accidentally catch and hide a real error due to an unrelated TypeError exception being raised inside the try block. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1325931] Re: [upstream] Can't select non-standard paper sizes for Printing
The bug still seems to be present with this version: Version: 7.3.3.2 / LibreOffice Community Build ID: 30(Build:2) CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-US Ubuntu package version: 1:7.3.3~rc2-0ubuntu0.20.04.1~lo1 Calc: threaded -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1325931 Title: [upstream] Can't select non-standard paper sizes for Printing Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Problem description: I was trying to print a small compliments slip on a card that was 140mm x 100mm. I set the page size under Format -> Page -> Size to user defined, and then entered the width of 14.00cm and height of 10.00cm correctly. However, when I came to try to print it, it would not print correctly. The print dialog box showed the dimensions of A6 (140mm x 105mm) and I couldn't find any way to change this. I tried to print it anyway, but it came out wrong. To prove that the problem is in LibreOffice and probably not related to the driver, I exported the file to a PDF, and was able to print it by setting up a Custom Paper size in the printer settings dialog - an option which LibreOffice doesn't seem to have. Steps to reproduce: 1. Create a new Document 2. From the menu, do Format -> Page 3. From the Format dropdown, select User 4. Enter a size that is not a standard paper size 5. Click OK 6. Attempt to print the document Current behavior: No matter what combinations of options I tried, I was unable to change the Printer paper size to the correct size. If I go ahead and click Print, the output is wrong (output not aligned correctly on the page). Expected behavior: Paper size could be set by the selected Page size, or provide some way to change the printer paper size. Operating System: Ubuntu Version: 4.2.3.3 release ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libreoffice 1:4.2.3~rc3-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-27.50-generic 3.13.11 Uname: Linux 3.13.0-27-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 3 12:04:40 2014 SourcePackage: libreoffice UpgradeStatus: Upgraded to trusty on 2014-05-07 (26 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1325931/+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 1973734] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted pulseaudio into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.14 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1973734 Title: FTBFS on riscv64 in focal Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973734/+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 1973734] Re: FTBFS on riscv64 in focal
Rather than having everybody install the new version of pulseaudio let's tag the bug block-proposed-focal. ** Tags added: block-proposed-focal ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1973734 Title: FTBFS on riscv64 in focal Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Committed Bug description: [Impact] * FTBFS on riscv64 in focal in unittest of volume test * Disable that unit test, as later releases do not run unittests on riscv64, and it's better to have up to date pulseaudio on riscv64 (with many security fixes), even if it doesn't completely correctly work. [Test Plan] * autopkgtests pass * riscv64 build is successful [Where problems could occur] * volume-test probably indicates that one can't set volume correctly on riscv64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1973734/+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 1973816] Re: Deja Dup's Google support will break in September 2022 for versions < 43.3
Hello Michael, or anyone else affected, Accepted deja-dup into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/deja-dup/40.7-0ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Description changed: * Impact The method Deja-Dup is using to authentificate to google account will stop working in september. * Test case Configure deja-dup to do backups on a google drive account. After confirming the authorization through the web browser it should be possible to start the backup. Check on the webview that the files are correctly added. - Restore some data and unsure that's working. + Restore some data and ensure that's working. * Regression potential The codepath is used for oauth authentification and integration with the system mimetype. Check that the webbrowser auth workflow works as expected, testing deb and snap based browsers -- Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows-safer.html Here's the upstream bug about switching to a new oauth flow: https://gitlab.gnome.org/World/deja-dup/-/issues/222 I've released version 43.3 with a new oauth workflow. This basically switches us from redirecting the oauth page to a local http://localhost:/ page being served by deja-dup and instead has the browser launch a custom URI like 'com.googlecontent.xxx:/oauth2redirect?code=yyy', which then launches deja-dup and gives it the correct oauth token. The key differences for packagers is just to note that now deja-dup will register itself as a handler for those weird URI schemes (they are specific to deja-dup, as they include its client ids for the service). I think this deserves a backport to all supported releases. I can whip up a patch for you in a bit, just wanted to get this registered as an issue. To be a bit more specific about what will break: - Existing users that have already granted deja-dup access to Google will continue to work without any issue. - In August, users will see a warning on the oauth screen. - And then in September, any new attempt to connect deja-dup to Google will not work. ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1973816 Title: Deja Dup's Google support will break in September 2022 for versions < 43.3 Status in deja-dup package in Ubuntu: Fix Released Status in deja-dup source package in Focal: Fix Committed Status in deja-dup source package in Jammy: Fix Released Status in deja-dup package in Debian: New Bug description: * Impact The method Deja-Dup is using to authentificate to google account will stop working in september. * Test case Configure deja-dup to do backups on a google drive account. After confirming the authorization through the web browser it should be possible to start the backup. Check on the webview that the files are correctly added. Restore some data and ensure that's working. * Regression potential The codepath is used for oauth authentification and integration with the system mimetype. Check that the webbrowser auth workflow works as expected, testing deb and snap based browsers -- Hello! I'm the maintainer of Deja Dup. I was recently made aware that Google is removing an oauth workflow that Deja Dup uses, in September. Here's their blog post about it: https://developers.googleblog.com/2022/02/making-oauth-flows- safer.html Here's the upstream bug ab
[Desktop-packages] [Bug 1978017] Re: Broken keyboard navigation in the Power Off dialog if launched via app search
Disabling the Desktop Icons NG extension also fixes the issue for me. -- 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/1978017 Title: Broken keyboard navigation in the Power Off dialog if launched via app search Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Bug description: The "power off" dialog in gnome shell does not have focus when launched from the launcher ui (meta key + search) and it is therefore impossible to select either "cancel" or "power off" using keyboard navigation. If, on the other hand, the dialog is launched from the indicator area in the top right corner, the dialog has focus and keyboard navigation works as expected. See the attached screencast for a visual demonstration. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978017/+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 1975638] Re: Broken background portal autostart in 1.14.3
** Also affects: xdg-desktop-portal (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1975638 Title: Broken background portal autostart in 1.14.3 Status in xdg-desktop-portal package in Ubuntu: Fix Committed Status in xdg-desktop-portal source package in Jammy: New Bug description: - Impact With 1.14.3 the background portal creates a broken autostart file (it sends an incorrectly quoted app ID to implementations). This means apps like EasyEffects or Pika Backup cannot rely on the background portal to create a working autostart file. Please update to xdg- desktop-portal 1.14.4 https://github.com/flatpak/xdg-desktop- portal/releases/tag/1.14.4 which fixes this issue. - Test Case 1. Install ASHPD Demo https://flathub.org/apps/details/com.belmoussaoui.ashpd.demo from Flathub 2. Within the app make a background portal request with auto start enabled (you must accept the prompt from GNOME Shell) 3. Note the contents of ~/.config/autostart/com.belmoussaoui.ashpd.demo.desktop is a desktop file, however the exec key’s value has an app id with quotes, making it invalid. 4. After logging out and in or restarting, the app will not already be running, even though it previously asked the portal API for it to be auto started. The same steps can be repeated with EasyEffects from Flathub instead of ASHPD Demo, note the EasyEffects switch is named "Start Service at Login" within EasyEffects' preferences menu. When the bug is fixed, the created desktop file for auto start is valid and the app will start after login. - Regression potential The update is a new minor version including the fix for that bug and translation updates (which are going to be imported by launchpad but not part of the deb on Ubuntu) The codepath change is specific to flatpak commandline parsing so check that flatpaks still start correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1975638/+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 1935000] Re: Generation of Error Message in gsd-backlight-helper Leading to An Information Disclosure Vulnerability
The fix is in the current Ubuntu version now
** Changed in: gnome-settings-daemon (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-settings-daemon (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1935000
Title:
Generation of Error Message in gsd-backlight-helper Leading to An
Information Disclosure Vulnerability
Status in gnome-settings-daemon package in Ubuntu:
Fix Released
Bug description:
Hi,
I found a information disclosure vulnerability in the PolicyKit action
`org.gnome.settings-daemon.plugins.power.backlight-helper`
```shell
user@ubuntu:~$ pkaction --verbose --action-id
org.gnome.settings-daemon.plugins.power.backlight-helper
org.gnome.settings-daemon.plugins.power.backlight-helper:
description: Modify the laptop brightness
message: Authentication is required to modify the laptop
brightness
vendor:GNOME Settings Daemon
vendor_url:http://git.gnome.org/browse/gnome-settings-daemon
icon: battery
implicit any: no
implicit inactive: no
implicit active: yes
annotation:org.freedesktop.policykit.exec.path ->
/usr/libexec/gsd-backlight-helper
```
As above shows, an unprivileged attacker can execute
`/usr/libexec/gsd-backlight-helper` as root without authentication in
an active session.
This binary needs two arguments. The first argument is the backlight
directory and attackers can supply a full path to any arbitrary file.
According to the error message, an unprivileged user can check for the
existence of any files on the system as root. The following is an
example:
```bash
$ id
uid=1000(user) gid=1000(user) groups=1000(user)
$ pkexec /usr/libexec/gsd-backlight-helper /root/.bashrc 111
Error: Could not find the specified backlight "/root/.bashrc"
$ pkexec /usr/libexec/gsd-backlight-helper /root/not_exist 111
Error: Could not canonicalize given path (2: No such file or directory)
# some unprivileged user should set the $SHELL environment to run pkexec
$ id ; echo $SHELL
uid=65534(nobody) gid=65534(nogroup) groups=65534(nogroup)
/usr/sbin/nologin
$ pkexec /usr/libexec/gsd-backlight-helper /root/.bashrc 111
The value for the SHELL variable was not found the /etc/shells file
This incident has been reported.
$ SHELL=/bin/sh pkexec /usr/libexec/gsd-backlight-helper /root/.bashrc 111
Error: Could not find the specified backlight "/root/.bashrc"
$ SHELL=/bin/sh pkexec /usr/libexec/gsd-backlight-helper /root/not_exist 111
Error: Could not canonicalize given path (2: No such file or directory)
```
I paste the vulnerable code below(https://github.com/GNOME/gnome-
settings-daemon/blob/master/plugins/power/gsd-backlight-
helper.c#L88-L93). When the attackers-controlled file doesn't exist,
`realpath` will return `NULL`, thus results in a different error
message when the file exists.
```C
device = realpath (argv[1], NULL);
if (device == NULL) {
fprintf (stderr, "Error: Could not canonicalize given path (%d:
%s)\n", errno, strerror (errno));
result = GSD_BACKLIGHT_HELPER_EXIT_CODE_FAILED;
goto done;
}
```
Here is my test environment:
```shell
user@ubuntu:~$ lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04
user@ubuntu:~$ apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
Installed: 3.36.1-0ubuntu1
Candidate: 3.36.1-0ubuntu1
Version table:
*** 3.36.1-0ubuntu1 500
500 http://mirrors.ustc.edu.cn/ubuntu focal-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.36.0-1ubuntu2 500
500 http://mirrors.ustc.edu.cn/ubuntu focal/main amd64 Packages
```
Best Regards,
Aobo Wang
Chaitin Tech.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1935000/+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 1978486] Re: Right clicks on file icons select a different file
Thanks, unsure how that got set, I don't think this option default was never set to true in Ubuntu but perhaps some configuration UI changed it? In any case closing the report now ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: Invalid Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
This bug was fixed in the package software-properties - 0.99.22.2 --- software-properties (0.99.22.2) jammy; urgency=medium * softwareproperties/gtk/SoftwarePropertiesGtk.py: Don't crash if the driver package does not have a matching modules package Fixes LP: #1969460 -- Alberto Milone Tue, 31 May 2022 11:39:13 +0200 ** Changed in: software-properties (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: Fix Committed Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Jammy: Fix Released Bug description: - Impact software-properties-gtk hit an exception when dealing some drivers - Test Case On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and try to install libcamhal-ipu6ep0 using software-properties-gtk https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57 should not include reports on the new version - Regression potential The change make the driver code ignore one extra type of error, it shouldn't impact on any of the already working cases. Ensure that drivers that were hitting the error correctly install now [racb] It's possible that we accidentally catch and hide a real error due to an unrelated TypeError exception being raised inside the try block. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1978731] Re: verbosity cannot be increased (“debug” option broken)
** Changed in: ppp (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1978731 Title: verbosity cannot be increased (“debug” option broken) Status in ppp package in Ubuntu: New Bug description: When the “debug” option is uncommented in /etc/ppp/options as well as the “-detach” option, the ppp logging is no more verbose than without those options. They seem to take no effect. This is the output I see either way: /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== I know that some people get more verbosity because I see posts showing more verbosity, like the output in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489243 At first I thought I was encountering this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639368 But I think that bug is different because Beraldo Costa Leal gets just one line of output (not even the standard output). In any case, these bugs are similar and should perhaps be examined at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1978731/+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 1975945] Re: Update gnome-control-center to 41.7
This bug was fixed in the package gnome-control-center - 1:41.7-0ubuntu0.22.04.1 --- gnome-control-center (1:41.7-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream bugfix release (LP: #1975945) * Drop 6 patches applied in new release -- Jeremy Bicha Fri, 27 May 2022 09:37:05 -0400 ** Changed in: gnome-control-center (Ubuntu Jammy) Status: Fix Committed => 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/1975945 Title: Update gnome-control-center to 41.7 Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Released Bug description: Impact -- There was a new bugfix release in the stable 41 series. https://gitlab.gnome.org/GNOME/gnome-control-center/-/compare/41.4...41.7 6 of these commits were already in Ubuntu 22.04 LTS. New changes: - Translation updates (because of Ubuntu language packs, this has no effect until the next language pack update, which is a few months away) - info-overview: Allow changing "Device Name" by pressing "Enter" - wwan: Remove duplicate line from .desktop - keyboard: Avoid segfault due to no "data" for `custom_shortcut_add_row` - network: Fix saving passwords for non-wifi connections - info-overview: Remove trailing space after CPU name Test Case 1 --- Install the update. Make sure that gnome-control-center continues to run well. Test Case 2 --- Install gnome-session Log out. Click your name on the login screen. Click the gear in the bottom right corner and choose GNOME. Finish logging in. Make sure that gnome-control-center continues to run well. This test case is because some of our Ubuntu customizations only show in the Ubuntu session, not other sessions like vanilla GNOME. Test Case 3 --- Open gnome-control-center Click the last item in the left sidebar named About Click Device Name. Type in a different name for your computer. Press Enter. The Rename Device dialog should close and your new computer name should take effect. What Could Go Wrong --- gnome-control-center is used by Ubuntu Desktop and Ubuntu Budgie. It is a critical app for viewing and changing a huge variety of settings for these desktops. gnome-control-center is part of GNOME Core and has a microrelease exception for Ubuntu stable release updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1975945/+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 1975945] Update Released
The verification of the Stable Release Update for gnome-control-center 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1975945 Title: Update gnome-control-center to 41.7 Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Released Bug description: Impact -- There was a new bugfix release in the stable 41 series. https://gitlab.gnome.org/GNOME/gnome-control-center/-/compare/41.4...41.7 6 of these commits were already in Ubuntu 22.04 LTS. New changes: - Translation updates (because of Ubuntu language packs, this has no effect until the next language pack update, which is a few months away) - info-overview: Allow changing "Device Name" by pressing "Enter" - wwan: Remove duplicate line from .desktop - keyboard: Avoid segfault due to no "data" for `custom_shortcut_add_row` - network: Fix saving passwords for non-wifi connections - info-overview: Remove trailing space after CPU name Test Case 1 --- Install the update. Make sure that gnome-control-center continues to run well. Test Case 2 --- Install gnome-session Log out. Click your name on the login screen. Click the gear in the bottom right corner and choose GNOME. Finish logging in. Make sure that gnome-control-center continues to run well. This test case is because some of our Ubuntu customizations only show in the Ubuntu session, not other sessions like vanilla GNOME. Test Case 3 --- Open gnome-control-center Click the last item in the left sidebar named About Click Device Name. Type in a different name for your computer. Press Enter. The Rename Device dialog should close and your new computer name should take effect. What Could Go Wrong --- gnome-control-center is used by Ubuntu Desktop and Ubuntu Budgie. It is a critical app for viewing and changing a huge variety of settings for these desktops. gnome-control-center is part of GNOME Core and has a microrelease exception for Ubuntu stable release updates. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1975945/+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 1976120] Update Released
The verification of the Stable Release Update for nautilus 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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1976120 Title: Update nautilus to 42.2 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 42 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/42.2/NEWS Test Case 1 --- Install the update Ensure that Nautilus still works well Test Case 2 --- Navigate to a folder. In the path bar. Right click on the parent folder and choose Open in New Window nautilus should open a new window with crashing. https://gitlab.gnome.org/GNOME/nautilus/-/issues/2208 Test Case 3 Optional Click the ☰ menu and choose Preferences. Set Performances > Count Number of Files in Folders to "On this computer only" (that is the default) Connect to a remote server (sshfs, smbfs, Google Drive etc.) Nautilus should not be showing you the count of items in those folders. https://gitlab.gnome.org/GNOME/nautilus/-/issues/2035 What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1976120/+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 1976120] Re: Update nautilus to 42.2
This bug was fixed in the package nautilus - 1:42.2-0ubuntu1 --- nautilus (1:42.2-0ubuntu1) jammy; urgency=medium * New upstream release (LP: #1976120) -- Jeremy Bicha Fri, 27 May 2022 15:54:54 -0400 ** Changed in: nautilus (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1976120 Title: Update nautilus to 42.2 Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Jammy: Fix Released Bug description: Impact -- This is a new stable release in the GNOME 42 series https://gitlab.gnome.org/GNOME/nautilus/-/blob/42.2/NEWS Test Case 1 --- Install the update Ensure that Nautilus still works well Test Case 2 --- Navigate to a folder. In the path bar. Right click on the parent folder and choose Open in New Window nautilus should open a new window with crashing. https://gitlab.gnome.org/GNOME/nautilus/-/issues/2208 Test Case 3 Optional Click the ☰ menu and choose Preferences. Set Performances > Count Number of Files in Folders to "On this computer only" (that is the default) Connect to a remote server (sshfs, smbfs, Google Drive etc.) Nautilus should not be showing you the count of items in those folders. https://gitlab.gnome.org/GNOME/nautilus/-/issues/2035 What Could Go Wrong --- nautilus is the default GUI file browser for Ubuntu Desktop. Other desktop flavors use other file browsers. As a component of GNOME core, there is a micro-release exception for nautilus https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1976120/+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 1973745] Re: adsys windows admx/adml lts only does not include 22.04
This bug was fixed in the package adsys - 0.8.5~22.04 --- adsys (0.8.5~22.04) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). -- Didier Roche Mon, 16 May 2022 14:09:36 +0200 ** Changed in: adsys (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1973745 Title: adsys windows admx/adml lts only does not include 22.04 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Due to some misunterpretation in how the launchpad API works when listing lts only, 22.04 was not included there by the admx/adml files generated by CI. Consequently, when those files are deployed on Windows AD server with LTS only templates, this one is not listed. [Test Plan] * Deploy the admx/adml generated for "LTS Only" use cases on an AD server * Open any GPO rule like changing the background * Ensure there is an "Override for 22.04" entry. [Where problems could occur] Those files are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973745/+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 1973745] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973745 Title: adsys windows admx/adml lts only does not include 22.04 Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Due to some misunterpretation in how the launchpad API works when listing lts only, 22.04 was not included there by the admx/adml files generated by CI. Consequently, when those files are deployed on Windows AD server with LTS only templates, this one is not listed. [Test Plan] * Deploy the admx/adml generated for "LTS Only" use cases on an AD server * Open any GPO rule like changing the background * Ensure there is an "Override for 22.04" entry. [Where problems could occur] Those files are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973745/+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 1973748] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973748 Title: Updating any gsettings key makes user dconf database unreadable Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Changing any gsettings key in AD resulted in user databases under /etc/dconf, owned by root, with 0600 as permissions. This change was done late in the cycle after passing some permissions checkers to harden the binaries. However, in that case, the user databases needs to be readable by the users so that they can apply those values, so we need to align with ibus profile and makes them 644. [Test case] * Change a gsettings key under AD, like picture-uri one. * Login on the Ubuntu laptop connected with AD by adsys * The background should now be changed to the set value. [Where problems could occur] This code is located in the dconf policy application manager and restricted to it. The negative impact in case of a new bug will be seen by gsettings key not being applied as it is already nowdays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973748/+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 1973748] Re: Updating any gsettings key makes user dconf database unreadable
This bug was fixed in the package adsys - 0.8.5~22.04 --- adsys (0.8.5~22.04) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). -- Didier Roche Mon, 16 May 2022 14:09:36 +0200 ** Changed in: adsys (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1973748 Title: Updating any gsettings key makes user dconf database unreadable Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Changing any gsettings key in AD resulted in user databases under /etc/dconf, owned by root, with 0600 as permissions. This change was done late in the cycle after passing some permissions checkers to harden the binaries. However, in that case, the user databases needs to be readable by the users so that they can apply those values, so we need to align with ibus profile and makes them 644. [Test case] * Change a gsettings key under AD, like picture-uri one. * Login on the Ubuntu laptop connected with AD by adsys * The background should now be changed to the set value. [Where problems could occur] This code is located in the dconf policy application manager and restricted to it. The negative impact in case of a new bug will be seen by gsettings key not being applied as it is already nowdays. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973748/+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 1973751] Re: Machines or Users scripts are not executed
This bug was fixed in the package adsys - 0.8.5~22.04 --- adsys (0.8.5~22.04) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). -- Didier Roche Mon, 16 May 2022 14:09:36 +0200 ** Changed in: adsys (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1973751 Title: Machines or Users scripts are not executed Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Machine and user scripts are not executed on startup/shutdown/login/logoff. /run has been recently changed to be noexec on jammy. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. [Test case] * Setup some scripts under AD to be executed, one for machine scripts (on startup), one for user scripts (on login). Those scripts can create some temporary files under /tmp for instance. * Reboot and login on the Ubuntu laptop connected with AD by adsys, with ua attached * Check that the scripts were executed by testing that the created file under /tmp are present. [Where problems could occur] This is technically a new .mount systemd unit service which takes the same mount option than /run, but don’t set noexec. The setup is similar than qemu .mount unit for instance. Worst impact could be that the script policy manager can’t run the scripts as it is already the case today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973751/+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 1973751] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973751 Title: Machines or Users scripts are not executed Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Machine and user scripts are not executed on startup/shutdown/login/logoff. /run has been recently changed to be noexec on jammy. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. [Test case] * Setup some scripts under AD to be executed, one for machine scripts (on startup), one for user scripts (on login). Those scripts can create some temporary files under /tmp for instance. * Reboot and login on the Ubuntu laptop connected with AD by adsys, with ua attached * Check that the scripts were executed by testing that the created file under /tmp are present. [Where problems could occur] This is technically a new .mount systemd unit service which takes the same mount option than /run, but don’t set noexec. The setup is similar than qemu .mount unit for instance. Worst impact could be that the script policy manager can’t run the scripts as it is already the case today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973751/+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 1973752] Update Released
The verification of the Stable Release Update for adsys 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 adsys in Ubuntu. https://bugs.launchpad.net/bugs/1973752 Title: Fix privilege permission which can not be set to disabled Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Disallowing local administrator does not work as excepted: - on some AD server, setting in the UI this key (and some other similars) to disabled, go to next GPO rule, then back to this one, AD will display the key as enabled. - on the client machine, we can see that the key has no state and nothing is forcibly allowed or disallowed. [Test case] * Install the new admx/adml with this version on the AD server. * On AD, go to disallow local administator, set it to disabled * Go to next GPO rules and then go back * The rule should still be disabled. * On an Ubuntu machine connected with AD by adsys, with ua attached, force a machine refresh with adsysctl policy update -m. * Check in adsysctl policy applied --all that the key is displayed as disabled * Confirm that no local administrator (part of the sudo group) can run "sudo". [Where problems could occur] The privilege manager and other policies impacts both Windows and client: - on Windows, this is in the admx/adml are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. - on the client, the privilege manager is the main consumer of those disabled key types. The other kinds of keys are not impacted. [Additional informations] * New test cases have been added for the client part. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973752/+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 1973752] Re: Fix privilege permission which can not be set to disabled
This bug was fixed in the package adsys - 0.8.5~22.04 --- adsys (0.8.5~22.04) jammy; urgency=medium [ Jean-Baptiste Lallement ] [ Didier Roche ] * Rename chapters to be in correct ascii order when viewed online. Thanks to Anton Drastrup-Fjordbak. * Include 22.04 in admx/adml for lts only releases. (LP: #1973745) * Bump embedeed dependencies minor versions for both bug fixes and minor security enhancements. * Fix dconf keys not being readable by user after applying policy. (LP: #1973748) * Ensure we can execute machine and user scripts: /run is now noexec on Ubuntu. Ensure that we can execute the scripts in /run/adsys subdirectories. The scripts mecanism has been reviewed by the security team, so we can reset them as executable. (LP: #1973751) * Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen to prepare future adwatchd daemon under cmd/ which will be SRUed with an exception in next update. This is a no-op in the finale deploy binaries, apart from admxgen which is now using Cobra. This binary though is not shipped in any package and only used in CI. * Fix privilege permission which can not be set to disabled. (LP: #1973752) * Adaptation or new tests for all above changes. * Add fuzz tests and include new potential crash fixes on invalid files generated by Windows AD. * CI fixes and changes (not impacting finale package): - Move CI to Go 1.18 (package is already building with 1.18 in jammy). - Fixes due to new github. - Fix to generate all LTS releases in admx/adml (see above). -- Didier Roche Mon, 16 May 2022 14:09:36 +0200 ** Changed in: adsys (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/1973752 Title: Fix privilege permission which can not be set to disabled Status in adsys package in Ubuntu: Fix Released Status in adsys source package in Focal: New Status in adsys source package in Jammy: Fix Released Bug description: [Impact] Disallowing local administrator does not work as excepted: - on some AD server, setting in the UI this key (and some other similars) to disabled, go to next GPO rule, then back to this one, AD will display the key as enabled. - on the client machine, we can see that the key has no state and nothing is forcibly allowed or disallowed. [Test case] * Install the new admx/adml with this version on the AD server. * On AD, go to disallow local administator, set it to disabled * Go to next GPO rules and then go back * The rule should still be disabled. * On an Ubuntu machine connected with AD by adsys, with ua attached, force a machine refresh with adsysctl policy update -m. * Check in adsysctl policy applied --all that the key is displayed as disabled * Confirm that no local administrator (part of the sudo group) can run "sudo". [Where problems could occur] The privilege manager and other policies impacts both Windows and client: - on Windows, this is in the admx/adml are statically generated and then shipped as thus. There is no runtime exercising this. The consequence of those generated files to be invalid is that Windows AD server will not show up "Ubuntu" in its GPO template. - on the client, the privilege manager is the main consumer of those disabled key types. The other kinds of keys are not impacted. [Additional informations] * New test cases have been added for the client part. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973752/+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 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This has been fixed since sssd 2.4.0. ** Changed in: sssd (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: In Progress Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Fix Released Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Fix Released Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Status in tilix package in Ubuntu: New Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Status in zsh package in Debian: Confirmed Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+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 1976123] Re: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dump
Solved-- wrote 0's to HD and reinstalled--works
- Original Message -
From: "Bug 1976123" <1976...@bugs.launchpad.net>
To: "w williams"
Sent: Tuesday, June 14, 2022 11:51:47 AM
Subject: [Bug 1976123] Re: package cups 2.2.7-1ubuntu2.8 failed to
install/upgrade: installed cups package post-installation script subprocess was
killed by signal (Bus error), core dumped
Hi, thanks for reporting your issue. One possible cuase for this is that
it seems your system is having disk problems, as seen in the dmesg
output:
[13489.632083] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[13489.632092] ata4.00: BMDMA stat 0x25
[13489.632097] ata4.00: failed command: READ DMA
[13489.632106] ata4.00: cmd c8/00:88:30:ea:23/00:00:00:00:00/e0 tag 0 dma 69632
in
res 51/40:47:68:ea:23/00:00:00:00:00/e0 Emask 0x9
(media error)
[13489.632111] ata4.00: status: { DRDY ERR }
[13489.632115] ata4.00: error: { UNC }
[13489.638118] ata4.00: configured for UDMA/133
[13489.638146] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[13489.638151] sd 3:0:0:0: [sda] tag#0 Sense Key : Medium Error [current]
[13489.638154] sd 3:0:0:0: [sda] tag#0 Add. Sense: Unrecovered read error -
auto reallocate failed
[13489.638160] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 23 ea 30 00 00 88
00
[13489.638163] print_req_error: I/O error, dev sda, sector 2353768
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1976123
Title:
package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed
cups package post-installation script subprocess was killed by signal
(Bus error), core dumped
Status in cups package in Ubuntu:
New
Bug description:
ubuntu 16 worked but 18 doesn't upgrade
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.8
ProcVersionSignature: Ubuntu 4.15.0-180.189-generic 4.15.18
Uname: Linux 4.15.0-180-generic i686
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: i386
CupsErrorLog:
E [27/May/2022:08:22:50 -0600] [cups-deviced] PID 1020 (gutenprint52+usb)
stopped with status 1!
W [27/May/2022:13:27:55 -0600] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'PHOTOSMART-P1000-Gray..\' already exists
W [27/May/2022:13:27:55 -0600] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'PHOTOSMART-P1000-RGB..\' already exists
W [27/May/2022:13:48:08 -0600] Notifier for subscription 13 (dbus://) went
away, retrying!
W [27/May/2022:13:48:08 -0600] Notifier for subscription 18 (dbus://) went
away, retrying!
Date: Fri May 27 12:07:06 2022
ErrorMessage: installed cups package post-installation script subprocess was
killed by signal (Bus error), core dumped
InstallationDate: Installed on 2022-05-27 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
Lpstat: device for PHOTOSMART-P1000:
hp:/usb/PhotoSmart_P1000?serial=MX16A1D0P8HP
Papersize: letter
PpdFiles: PHOTOSMART-P1000: HP Photosmart p1000, hpcups 3.16.3
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic
root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic
root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal,
3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu2.4
apt 1.6.14
SourcePackage: cups
Title: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed
cups package post-installation script subprocess was killed by signal (Bus
error), core dumped
UpgradeStatus: Upgraded to bionic on 2022-05-27 (0 days ago)
dmi.bios.date: 04/29/2005
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
dmi.board.name: D915GAV
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC64134-600
dmi.chassis.type: 2
dmi.modalias:
dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GAV:rvrAAC64134-600:cvn:ct2:cvr:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1976123/+subscriptions
--
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/1976123
Title:
package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed
cups package post-installation script subprocess was killed by signal
(Bus error), core dumped
Status in cups package in Ubuntu:
New
Bug description:
ubuntu 16 worked but 18 doesn't upgrade
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.8
ProcVersionSignature: Ubuntu 4.15.0-180.189-generi
Re: [Desktop-packages] [Bug 1976123] Re: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dump
Solved-- wrote 0's to HD and reinstalled--works - Original Message - From: "Steve Beattie" <1976...@bugs.launchpad.net> To: "w williams" Sent: Tuesday, June 14, 2022 11:48:39 AM Subject: [Bug 1976123] Re: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1976123 Title: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped Status in cups package in Ubuntu: New Bug description: ubuntu 16 worked but 18 doesn't upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-180.189-generic 4.15.18 Uname: Linux 4.15.0-180-generic i686 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CupsErrorLog: E [27/May/2022:08:22:50 -0600] [cups-deviced] PID 1020 (gutenprint52+usb) stopped with status 1! W [27/May/2022:13:27:55 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PHOTOSMART-P1000-Gray..\' already exists W [27/May/2022:13:27:55 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PHOTOSMART-P1000-RGB..\' already exists W [27/May/2022:13:48:08 -0600] Notifier for subscription 13 (dbus://) went away, retrying! W [27/May/2022:13:48:08 -0600] Notifier for subscription 18 (dbus://) went away, retrying! Date: Fri May 27 12:07:06 2022 ErrorMessage: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2022-05-27 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Lpstat: device for PHOTOSMART-P1000: hp:/usb/PhotoSmart_P1000?serial=MX16A1D0P8HP Papersize: letter PpdFiles: PHOTOSMART-P1000: HP Photosmart p1000, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.14 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped UpgradeStatus: Upgraded to bionic on 2022-05-27 (0 days ago) dmi.bios.date: 04/29/2005 dmi.bios.vendor: Intel Corp. dmi.bios.version: EV91510A.86A.0444.2005.0429.2108 dmi.board.name: D915GAV dmi.board.vendor: Intel Corporation dmi.board.version: AAC64134-600 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GAV:rvrAAC64134-600:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1976123/+subscriptions -- 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/1976123 Title: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped Status in cups package in Ubuntu: New Bug description: ubuntu 16 worked but 18 doesn't upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-180.189-generic 4.15.18 Uname: Linux 4.15.0-180-generic i686 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CupsErrorLog: E [27/May/2022:08:22:50 -0600] [cups-deviced] PID 1020 (gutenprint52+usb) stopped with status 1! W [27/May/2022:13:27:55 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PHOTOSMART-P1000-Gray..\' already exists W [27/May/2022:13:27:55 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PHOTOSMART-P1000-RGB..\' already exists W [27/May/2022:13:48:08 -0600
[Desktop-packages] [Bug 1978731] [NEW] verbosity cannot be increased (“debug” option broken)
Public bug reported: When the “debug” option is uncommented in /etc/ppp/options as well as the “-detach” option, the ppp logging is no more verbose than without those options. They seem to take no effect. This is the output I see either way: /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== I know that some people get more verbosity because I see posts showing more verbosity, like the output in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489243 At first I thought I was encountering this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639368 But I think that bug is different because Beraldo Costa Leal gets just one line of output (not even the standard output). In any case, these bugs are similar and should perhaps be examined at the same time. ** Affects: ppp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1978731 Title: verbosity cannot be increased (“debug” option broken) Status in ppp package in Ubuntu: New Bug description: When the “debug” option is uncommented in /etc/ppp/options as well as the “-detach” option, the ppp logging is no more verbose than without those options. They seem to take no effect. This is the output I see either way: /var/log/messages: ===8<-- $timestamp $host pppd[84797]: pppd 2.4.9 started by $user, uid 0 $timestamp $host pppd[84797]: Using interface ppp0 $timestamp $host pppd[84797]: Connect: ppp0 <--> /dev/ttyUSB0 $timestamp $host pppd[84797]: LCP: timeout sending Config-Requests $timestamp $host pppd[84797]: Connection terminated. $timestamp $host pppd[84797]: Modem hangup $timestamp $host pppd[84797]: Exit. -->8=== I know that some people get more verbosity because I see posts showing more verbosity, like the output in this bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=489243 At first I thought I was encountering this bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639368 But I think that bug is different because Beraldo Costa Leal gets just one line of output (not even the standard output). In any case, these bugs are similar and should perhaps be examined at the same time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1978731/+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 1864215] Re: Please add webp loader to gdk-pixbuf
webp-pixbuf-loader is in the Debian new queue now, https://ftp- master.debian.org/new.html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1864215 Title: Please add webp loader to gdk-pixbuf Status in gdk-pixbuf: Fix Released Status in gdk-pixbuf package in Ubuntu: Confirmed Status in gdk-pixbuf package in Baltix: Triaged Status in Debian: New Bug description: Attempting to load a webp image -- for instance, https://images.theweek.com/sites/default/files/styles/tw_image_9_4/public/FKK78W.jpg.webp or https://cdn.vox-cdn.com/thumbor/2YtWB5zH7sPycyc0FYv3JSB6SFw=/60x0:1140x720/920x613/filters:focal(60x0:1140x720):format(webp)/cdn.vox-cdn.com/uploads/chorus_image/image/49663815/timburton.0.0.jpg -- in a gdk-pixbuf app results in a "Couldn’t recognize the image file format" error. Bug 1318327 covers this issue in eye of gnome, and bug 1407644 in libwebp, but isn't this really a gdk-pixbuf issue? If it really does belong to libwebp, my apologies, please dup this bug to 1407644 (I'm confident it doesn't belong to eog since I don't use that program; I have other programs that use libgdk-pixbuf). You can probably use eog to test this, or run /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/gdk-pixbuf-query-loaders | grep -i webp (I assume the loader would mention webp if there was a loader for it). I have these packages installed in addition to libgdk-pixbuf2.0-0: libwebp-dev libwebp6 libwebpdemux2 libwebpmux3 webp. file recognizes the format: $ file /tmp/FKK78W.jpg.webp /tmp/FKK78W.jpg.webp: RIFF (little-endian) data, Web/P image, VP8 encoding, 1200x533, Scaling: [none]x[none], YUV color, decoders should clamp ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-1build1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 Date: Fri Feb 21 08:48:36 2020 InstallationDate: Installed on 2019-10-10 (133 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdk-pixbuf/+bug/1864215/+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 1978486] Re: Right clicks on file icons select a different file
The 'use-experimental-views' option appears to have been the problem. I reset it, and the problem seems to have gone away. I do not think I explicitly set that option, so I don't know how it got turned on. But this machine has been upgraded in place several times, so it may have been something that occurred years ago. No matter, it appears to be working correctly now, in several different directories & using several different zoom levels. I believe this bug report can be marked as 'resolved'. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: Incomplete Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1935000] Re: Generation of Error Message in gsd-backlight-helper Leading to An Information Disclosure Vulnerability
This seems to have been reported in
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/634 and
addressed in https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/-/merge_requests/275 ; given that, I am making this bug report
public. Thanks!
** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #634
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/634
** Information type changed from Private Security to Public Security
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1935000
Title:
Generation of Error Message in gsd-backlight-helper Leading to An
Information Disclosure Vulnerability
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
Hi,
I found a information disclosure vulnerability in the PolicyKit action
`org.gnome.settings-daemon.plugins.power.backlight-helper`
```shell
user@ubuntu:~$ pkaction --verbose --action-id
org.gnome.settings-daemon.plugins.power.backlight-helper
org.gnome.settings-daemon.plugins.power.backlight-helper:
description: Modify the laptop brightness
message: Authentication is required to modify the laptop
brightness
vendor:GNOME Settings Daemon
vendor_url:http://git.gnome.org/browse/gnome-settings-daemon
icon: battery
implicit any: no
implicit inactive: no
implicit active: yes
annotation:org.freedesktop.policykit.exec.path ->
/usr/libexec/gsd-backlight-helper
```
As above shows, an unprivileged attacker can execute
`/usr/libexec/gsd-backlight-helper` as root without authentication in
an active session.
This binary needs two arguments. The first argument is the backlight
directory and attackers can supply a full path to any arbitrary file.
According to the error message, an unprivileged user can check for the
existence of any files on the system as root. The following is an
example:
```bash
$ id
uid=1000(user) gid=1000(user) groups=1000(user)
$ pkexec /usr/libexec/gsd-backlight-helper /root/.bashrc 111
Error: Could not find the specified backlight "/root/.bashrc"
$ pkexec /usr/libexec/gsd-backlight-helper /root/not_exist 111
Error: Could not canonicalize given path (2: No such file or directory)
# some unprivileged user should set the $SHELL environment to run pkexec
$ id ; echo $SHELL
uid=65534(nobody) gid=65534(nogroup) groups=65534(nogroup)
/usr/sbin/nologin
$ pkexec /usr/libexec/gsd-backlight-helper /root/.bashrc 111
The value for the SHELL variable was not found the /etc/shells file
This incident has been reported.
$ SHELL=/bin/sh pkexec /usr/libexec/gsd-backlight-helper /root/.bashrc 111
Error: Could not find the specified backlight "/root/.bashrc"
$ SHELL=/bin/sh pkexec /usr/libexec/gsd-backlight-helper /root/not_exist 111
Error: Could not canonicalize given path (2: No such file or directory)
```
I paste the vulnerable code below(https://github.com/GNOME/gnome-
settings-daemon/blob/master/plugins/power/gsd-backlight-
helper.c#L88-L93). When the attackers-controlled file doesn't exist,
`realpath` will return `NULL`, thus results in a different error
message when the file exists.
```C
device = realpath (argv[1], NULL);
if (device == NULL) {
fprintf (stderr, "Error: Could not canonicalize given path (%d:
%s)\n", errno, strerror (errno));
result = GSD_BACKLIGHT_HELPER_EXIT_CODE_FAILED;
goto done;
}
```
Here is my test environment:
```shell
user@ubuntu:~$ lsb_release -rd
Description: Ubuntu 20.04.2 LTS
Release: 20.04
user@ubuntu:~$ apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
Installed: 3.36.1-0ubuntu1
Candidate: 3.36.1-0ubuntu1
Version table:
*** 3.36.1-0ubuntu1 500
500 http://mirrors.ustc.edu.cn/ubuntu focal-updates/main amd64
Packages
100 /var/lib/dpkg/status
3.36.0-1ubuntu2 500
500 http://mirrors.ustc.edu.cn/ubuntu focal/main amd64 Packages
```
Best Regards,
Aobo Wang
Chaitin Tech.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1935000/+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 1976123] Re: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1976123 Title: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped Status in cups package in Ubuntu: New Bug description: ubuntu 16 worked but 18 doesn't upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.8 ProcVersionSignature: Ubuntu 4.15.0-180.189-generic 4.15.18 Uname: Linux 4.15.0-180-generic i686 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CupsErrorLog: E [27/May/2022:08:22:50 -0600] [cups-deviced] PID 1020 (gutenprint52+usb) stopped with status 1! W [27/May/2022:13:27:55 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PHOTOSMART-P1000-Gray..\' already exists W [27/May/2022:13:27:55 -0600] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'PHOTOSMART-P1000-RGB..\' already exists W [27/May/2022:13:48:08 -0600] Notifier for subscription 13 (dbus://) went away, retrying! W [27/May/2022:13:48:08 -0600] Notifier for subscription 18 (dbus://) went away, retrying! Date: Fri May 27 12:07:06 2022 ErrorMessage: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped InstallationDate: Installed on 2022-05-27 (0 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) Lpstat: device for PHOTOSMART-P1000: hp:/usb/PhotoSmart_P1000?serial=MX16A1D0P8HP Papersize: letter PpdFiles: PHOTOSMART-P1000: HP Photosmart p1000, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.4 apt 1.6.14 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped UpgradeStatus: Upgraded to bionic on 2022-05-27 (0 days ago) dmi.bios.date: 04/29/2005 dmi.bios.vendor: Intel Corp. dmi.bios.version: EV91510A.86A.0444.2005.0429.2108 dmi.board.name: D915GAV dmi.board.vendor: Intel Corporation dmi.board.version: AAC64134-600 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GAV:rvrAAC64134-600:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1976123/+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 1976123] Re: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed cups package post-installation script subprocess was killed by signal (Bus error), core dumped
Hi, thanks for reporting your issue. One possible cuase for this is that
it seems your system is having disk problems, as seen in the dmesg
output:
[13489.632083] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[13489.632092] ata4.00: BMDMA stat 0x25
[13489.632097] ata4.00: failed command: READ DMA
[13489.632106] ata4.00: cmd c8/00:88:30:ea:23/00:00:00:00:00/e0 tag 0 dma 69632
in
res 51/40:47:68:ea:23/00:00:00:00:00/e0 Emask 0x9
(media error)
[13489.632111] ata4.00: status: { DRDY ERR }
[13489.632115] ata4.00: error: { UNC }
[13489.638118] ata4.00: configured for UDMA/133
[13489.638146] sd 3:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[13489.638151] sd 3:0:0:0: [sda] tag#0 Sense Key : Medium Error [current]
[13489.638154] sd 3:0:0:0: [sda] tag#0 Add. Sense: Unrecovered read error -
auto reallocate failed
[13489.638160] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 23 ea 30 00 00 88
00
[13489.638163] print_req_error: I/O error, dev sda, sector 2353768
--
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/1976123
Title:
package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed
cups package post-installation script subprocess was killed by signal
(Bus error), core dumped
Status in cups package in Ubuntu:
New
Bug description:
ubuntu 16 worked but 18 doesn't upgrade
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.8
ProcVersionSignature: Ubuntu 4.15.0-180.189-generic 4.15.18
Uname: Linux 4.15.0-180-generic i686
ApportVersion: 2.20.9-0ubuntu7.28
Architecture: i386
CupsErrorLog:
E [27/May/2022:08:22:50 -0600] [cups-deviced] PID 1020 (gutenprint52+usb)
stopped with status 1!
W [27/May/2022:13:27:55 -0600] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'PHOTOSMART-P1000-Gray..\' already exists
W [27/May/2022:13:27:55 -0600] CreateProfile failed:
org.freedesktop.ColorManager.AlreadyExists:profile id
\'PHOTOSMART-P1000-RGB..\' already exists
W [27/May/2022:13:48:08 -0600] Notifier for subscription 13 (dbus://) went
away, retrying!
W [27/May/2022:13:48:08 -0600] Notifier for subscription 18 (dbus://) went
away, retrying!
Date: Fri May 27 12:07:06 2022
ErrorMessage: installed cups package post-installation script subprocess was
killed by signal (Bus error), core dumped
InstallationDate: Installed on 2022-05-27 (0 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
Lpstat: device for PHOTOSMART-P1000:
hp:/usb/PhotoSmart_P1000?serial=MX16A1D0P8HP
Papersize: letter
PpdFiles: PHOTOSMART-P1000: HP Photosmart p1000, hpcups 3.16.3
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic
root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-180-generic
root=UUID=d36f19e0-4269-404a-96cd-f6c837cca4b9 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal,
3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
dpkg 1.19.0.5ubuntu2.4
apt 1.6.14
SourcePackage: cups
Title: package cups 2.2.7-1ubuntu2.8 failed to install/upgrade: installed
cups package post-installation script subprocess was killed by signal (Bus
error), core dumped
UpgradeStatus: Upgraded to bionic on 2022-05-27 (0 days ago)
dmi.bios.date: 04/29/2005
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
dmi.board.name: D915GAV
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC64134-600
dmi.chassis.type: 2
dmi.modalias:
dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GAV:rvrAAC64134-600:cvn:ct2:cvr:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1976123/+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 1977875] Re: Ubuntu Desktop boot hangs absent zeroconf packets and after avahi-daemon purge
Thanks for reporting this issue. I'm opening up it publicly since it would be useful for the people who work on the installer to see this. ** Information type changed from Private Security to Public Security -- 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/1977875 Title: Ubuntu Desktop boot hangs absent zeroconf packets and after avahi- daemon purge Status in gnome-shell package in Ubuntu: New Bug description: Our install procedures customarily airgap machines during installation, purge unnecessary and irrelevant packages such as avahi- daemon, ufw, netplan.io, ModemManager, network-manager, fprintd, etc., configure networking via systemd-networkd, and enable an iptables firewall to be in place before the network is up, all before exposing any machine to a network for further configuration. The iptables rules drop all zeroconf and broadcast traffic for obvious security reasons. The kernel is typically configured to forward packets, so these DROP rules are in the mangle table's PREROUTING chain, to scrub them before reaching the filter table's INPUT or FORWARD chains. Presumably, this also scrubs such traffic to the loopback interface. INPUT, OUTPUT, and FORWARD rules ACCEPT suitable traffic before a default DROP rule in each case. We have found the Ubuntu desktop 22.04 boot process to be especially fragile. System boot hangs every time, typically presenting as either an ordering cycle or a failure of partition mounts, which may be related. Occasionally, we note that dmesg.service and networkd- dispatcher.service fail by reason of time-out. Often, the last message in tty1 is Reached target Host and Network Name Lookups. Over the course of weeks, we have debugged our install scripts and packet filtering and although the modality is unclear, the cause is an absence of zeroconf network traffic or the purge of the avahi-daemon package. Curiously, none of this configuration has any effect and the boot process proceeds normally and as expected so long as a machine's Ethernet cables are unplugged. Once connected, attempts to upgrade a system (# apt update && apt upgrade) themselves hang, the machine reboots successfully, and then after dpkg --reconfigure -a, the attempted reboot hangs as before. Ubuntu desktop 20.04 machines do not exhibit this behavior. The expectation is that local processes would utilize d-bus or, if ip traffic somehow was necessary for local interprocess communication, that those processes would rely on name resolution other than broadcast traffic. Alternatively, the expectation is that the necessity of deliberately opening this security vulnerability would be well and conspicuously documented, including identifying the processes, ports, protocols, sources, destinations, interfaces, sockets, and any IP or MAC address so that the traffic can be suitably filtered. Persisting avahi-daemon and zeroconf is a non-starter. Release: Ubuntu desktop 22.04 LTS Version: gnome-shell 42.0-2ubuntu1 Expected behavior: Boot to gdm3 login prompt. Actual behavior: Consistent boot hang. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Jun 7 10:00:18 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-05-24 (14 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color PATH=(custom, no user) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 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/1977875/+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 1978707] [NEW] Dragging windows cause gnome-shell to hangs up temporarily
Public bug reported: Ubuntu 22.04, upgraded from previous versions, AMD Ryzen 7 5700G integrated video card, Wayland session. Steps to reproduce: 1. Open an app window. I used Chromium, but can also reproduce with nautilus or even gnome-settings. 2. Move it constantly. Expected behavior: Window moves. Actual behavior: Whole gnome-shell session hangs up for a several seconds with a lot of "Stack trace for context" errors in the logs. I attached a demo video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 19:59:38 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (5 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Запись экрана от 14.06.2022 19:58:43.webm" https://bugs.launchpad.net/bugs/1978707/+attachment/5597258/+files/%D0%97%D0%B0%D0%BF%D0%B8%D1%81%D1%8C%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%2014.06.2022%2019%3A58%3A43.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/1978707 Title: Dragging windows cause gnome-shell to hangs up temporarily Status in gnome-shell package in Ubuntu: New Bug description: Ubuntu 22.04, upgraded from previous versions, AMD Ryzen 7 5700G integrated video card, Wayland session. Steps to reproduce: 1. Open an app window. I used Chromium, but can also reproduce with nautilus or even gnome-settings. 2. Move it constantly. Expected behavior: Window moves. Actual behavior: Whole gnome-shell session hangs up for a several seconds with a lot of "Stack trace for context" errors in the logs. I attached a demo video. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 19:59:38 2022 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-06-08 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978707/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
** Changed in: fftw3 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
Invalid
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
Thanks to Sebastien Bacher for his selective fix proposal (delete the 'deny dbus send' section in '/etc/apparmor.d/abstractions/exo-open'). $ sudo apparmor_parser -r /etc/apparmor.d/abstractions/exo-open fails with error message 'AppArmor parser error for /etc/apparmor.d/abstractions/exo-open in profile /etc/apparmor.d/abstractions/dri-common at line 8: syntax error, unexpected TOK_MODE, expecting TOK_OPEN' But following command succeeds : $ sudo systemctl restart apparmor Then evince remembers last page, window size and side pane. -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in apparmor package in Ubuntu: New Status in evince package in Ubuntu: In Progress Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1978700] Re: Update gnome-text-editor to 42.2
** Also affects: gnome-text-editor (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: gnome-text-editor (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: gnome-text-editor (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-text-editor (Ubuntu Jammy) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1978700 Title: Update gnome-text-editor to 42.2 Status in gnome-text-editor package in Ubuntu: Fix Committed Status in gnome-text-editor source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the GNOME 42 series: https://gitlab.gnome.org/GNOME/gnome-text-editor/-/blob/42.2/NEWS Test Case - Install the new gnome-text-editor Verify that the app still opens a variety of files. What Could Go Wrong --- This app is not included by default in any Ubuntu flavor. This app should fall under the GNOME microrelease exception since it is a part of core GNOME since GNOME 42. It's not been formally added to the discourse wiki yet. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1978700/+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 1978700] [NEW] Update gnome-text-editor to 42.2
Public bug reported: Impact -- This is a new stable release in the GNOME 42 series: https://gitlab.gnome.org/GNOME/gnome-text-editor/-/blob/42.2/NEWS Test Case - Install the new gnome-text-editor Verify that the app still opens a variety of files. What Could Go Wrong --- This app is not included by default in any Ubuntu flavor. This app should fall under the GNOME microrelease exception since it is a part of core GNOME since GNOME 42. It's not been formally added to the discourse wiki yet. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME ** Affects: gnome-text-editor (Ubuntu) Importance: Medium Status: Fix Committed ** Tags: jammy upgrade-software-version -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1978700 Title: Update gnome-text-editor to 42.2 Status in gnome-text-editor package in Ubuntu: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series: https://gitlab.gnome.org/GNOME/gnome-text-editor/-/blob/42.2/NEWS Test Case - Install the new gnome-text-editor Verify that the app still opens a variety of files. What Could Go Wrong --- This app is not included by default in any Ubuntu flavor. This app should fall under the GNOME microrelease exception since it is a part of core GNOME since GNOME 42. It's not been formally added to the discourse wiki yet. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1978700/+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 1976371] Re: SRU for evolution-data-server 3.44.2
Steve, thank you for your thorough review. The wiki link pointed to comment 3 on Discourse but it should be comment 28 so I've updated the link on the wiki page. evolution-data-server isn't part of GNOME "core" but it is part of "core-deps" (but several of the "core-deps" aren't even maintained by GNOME and fall outside the intent of Ubuntu's GNOME microrelease exception). https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/28 https://gitlab.gnome.org/GNOME/gnome-build-meta/-/tree/master/elements/core-deps On the other hand, the evolution **app** isn't considered part of core GNOME currently nor is it formally included in the GNOME microrelease exception. One more point: evolution-data-server does show up in the list that GNOME formally releases as part of GNOME 42 https://people.debian.org/~fpeters/gnome/debian-gnome-42-status.html which pulls from https://download.gnome.org/teams/releng/42.2/versions which is built from https://gitlab.gnome.org/GNOME/releng/-/blob/master/tools/versions-stable ** No longer affects: evolution (Ubuntu) ** No longer affects: evolution (Ubuntu Jammy) ** Changed in: evolution-data-server (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1976371 Title: SRU for evolution-data-server 3.44.2 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Jammy: In Progress Bug description: Impact -- This is a new stable release in the 3.44 series. https://gitlab.gnome.org/GNOME/evolution-data- server/-/blob/3.44.2/NEWS Test Case - Install the update Log out and log back in (or restart) Ensure that GNOME Calendar and Evolution still work fine. What Could Go Wrong --- As a component of GNOME core, there is a micro-release exception for evolution-data-server https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1976371/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
I just realized that feeding NULL to the planner is not a supported
mode. I withdraw the bug report.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
New
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] Re: FFTW_PRESERVE_INPUT does not always preserve input
Additional details:
If `nfft` is changed from 125 to 128, the bug is not shown.
If `fftwf_plan_many_dft` is called with buffer pointers, the bug is not
shown.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
New
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978640] [NEW] FFTW_PRESERVE_INPUT does not always preserve input
Public bug reported:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied' failed.
Aborted (core dumped)
```
** Affects: fftw3 (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "reproduction example"
https://bugs.launchpad.net/bugs/1978640/+attachment/5597250/+files/test_fftw_preserve.cc
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to fftw3 in Ubuntu.
https://bugs.launchpad.net/bugs/1978640
Title:
FFTW_PRESERVE_INPUT does not always preserve input
Status in fftw3 package in Ubuntu:
New
Bug description:
libfftw3-dev:
Installed: (none)
Candidate: 3.3.8-2ubuntu8
Version table:
3.3.8-2ubuntu8 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
program to reproduce bug on Ubuntu 20.04 or 22.04 follows below
expected: success (no assert) because the input was preserved
observed: assert because the input was not preserved
```test_fftw_preserve.cc
#include
#include
#include
#include "assert.h"
int main()
{
typedef std::complex cpx;
int nfft = 125;
fftwf_plan plan = fftwf_plan_many_dft(1,&nfft,1,
NULL, NULL,1,nfft,
NULL, NULL,1,nfft,
FFTW_FORWARD,
FFTW_ESTIMATE|FFTW_PRESERVE_INPUT|FFTW_UNALIGNED);
std::vector in(nfft,cpx(1,2));
std::vector in_copied(in);
std::vector out(nfft);
fftwf_execute_dft(plan,
reinterpret_cast(in.data()),reinterpret_cast(out.data()));
assert(in == in_copied);
fftwf_destroy_plan(plan);
return 0;
}
```
To run:
```
$ g++ test_fftw_preserve.cc -lfftw3f && ./a.out
a.out: test_fftw_preserve.cc:21: int main(): Assertion `in == in_copied'
failed.
Aborted (core dumped)
```
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fftw3/+bug/1978640/+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 1978476] Re: Incorrect UNTIL recurrence with midnight start
** Tags added: focal jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1978476 Title: Incorrect UNTIL recurrence with midnight start Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Focal: Triaged Status in evolution-data-server source package in Jammy: Triaged Bug description: Impact -- EDS generates instances for recurring events starting at midnight with an UNTIL date incorrectly. Specifically, using e_cal_client_generate_instances() or e_cal_recur_generate_instances_sync() generates an instance one day after the UNTIL date. This bug was introduced with the migration to libical-glib and libecal-2.0, so this affects bot focal and jammy. It was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which will be part of the 3.45.1+ and 3.44.3+ releases respectively. Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/393 Test Case - What Could Go Wrong --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1978476/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 also works for me (XPS 9500). Furthermore, it fixes also the Night Light feature. Thank you Daniel! -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
I am experiencing a similar problem to the one described here, but on the more recent "Yoga 9 14IAP7". It does also use the ALC287 in a similar configuration. The speaker-bar above the keyboard works out of the box, but the bass speakers do not work. '$ cat /sys/class/sound/hwC0D0/subsystem_id' yields '0x17aa3801'. With this I also tried to apply the 'ALC287_FIXUP_IDEAPAD_BASS_SPK' and 'ALC269_FIXUP_HEADSET_MODE' pci quirks by adding a corresponding 'SND_PCI_QUIRK(0x17aa, 0x3801, "Yoga 9 14IAP7", ...)' to 'sound/pci/hda/patch_realtek.c'. But neither made a difference. I can also provide a dump of the HDA verbs send by a Windows 10 VM which were captured according to https://github.com/ryanprescott/realtek-verb- tools/wiki/How-to-sniff-verbs-from-a-Windows-sound-driver I tried to apply these verbs to /dev/snd/hwC0D0 using '$ hda-verb', but that did not work either. I tried Ubuntu first but am currently running Arch Linux since I am more familiar with building a kernel for it. Then I found this thread and compared the '$ alsa-info' output to mine (attached) and noticed that I am missing the 'DAC1', 'DAC2' and 'Bass Speaker Playback Switch' device nodes that were mentioned previously. I tried to use '$ hdajackretask' to reassign the the pins but I did not get it to work either. I don't think I am familiar enough with the linux sound stack to fix it myself and would be grateful for any help or further information on how to get Linux/Alsa to initialize/recognize the speakers. ** Attachment added: "alsa-info.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5597247/+files/alsa-info.txt -- 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/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+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 1922418] Re: [snap] Can't read files on /tmp
Snaps have a private /tmp for security reasons. Did you try to open it as a cmdline argument? It should be working from the fileselector using portals but direct access isn't going to work. Could you use another location? ** Changed in: evince (Ubuntu) Importance: Undecided => Low -- 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/1922418 Title: [snap] Can't read files on /tmp Status in evince package in Ubuntu: New Bug description: I have a .emc files that uses striata to decrypt to a /tmp folder and evince to read it. When trying to open the files I receive the message that the path is not accessible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1922418/+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 1954970] Re: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version"
We had several fixes landing in freerdp since that issue was report. Dmitry could you try if you still see the problem in the current version? ** Changed in: freerdp2 (Ubuntu) Status: Confirmed => Incomplete ** Changed in: freerdp2 (Ubuntu Jammy) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1954970 Title: remmina "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Status in freerdp2 package in Ubuntu: Incomplete Status in freerdp2 source package in Jammy: Incomplete Bug description: Xubuntu Jammy (21.04) after upgrade libfreerdp-client2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) libfreerdp2-2 (2.3.0+dfsg1-2ubuntu2 => 2.4.1+dfsg1-1) Remmina can't connect to any RDP server (Win2008 R2) with error: "Cannot connect to the RDP server ... via TLS. Check that the client and server support a common TLS version" Rollback to Impish version of libs libfreerdp-client2-2 2.3.0+dfsg1-2ubuntu2 libfreerdp2-2 2.3.0+dfsg1-2ubuntu2 makes it work normal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1954970/+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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Seems MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 solves the issue, hope it gets real fix soon without workarounds. -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: (initially reported as a comment on bug #1965085, and split into a separate bug report) After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. The only reliable workaround I've found is to press Ctrl+Alt+F1. That's on a fully up-to-date jammy, my hardware is an Intel NUC with a single Samsung monitor connected with a standard HDMI cable. This is a regression that started happening yesterday (2022-04-05) if I can remember correctly (I do apply pending updates at least once daily). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 6 15:19:30 2022 InstallationDate: Installed on 2020-09-16 (566 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
THe vfs mounttracker denial seems to discourage evince to use vfs, unsure why that section was added to the exo-open abstraction but I think it would make sense to delete it ** Changed in: apparmor (Ubuntu) Importance: Undecided => High -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in apparmor package in Ubuntu: New Status in evince package in Ubuntu: In Progress Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
The selective version of the fix works for me, even if I'm not using xubuntu (I use the Cinnamon desktop). Thanks to Sebastien! -- 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in apparmor package in Ubuntu: New Status in evince package in Ubuntu: In Progress Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1978476] Re: Incorrect UNTIL recurrence with midnight start
** Description changed: + Impact + -- + EDS generates instances for recurring events starting at midnight with an UNTIL date incorrectly. Specifically, using e_cal_client_generate_instances() or e_cal_recur_generate_instances_sync() generates an instance one day after the UNTIL date. This bug was introduced with the migration to libical-glib and libecal-2.0, so this affects bot focal and jammy. It was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which will be part of the 3.45.1+ and 3.44.3+ releases respectively. Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/393 + + Test Case + - + + + What Could Go Wrong + --- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1978476 Title: Incorrect UNTIL recurrence with midnight start Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Focal: Triaged Status in evolution-data-server source package in Jammy: Triaged Bug description: Impact -- EDS generates instances for recurring events starting at midnight with an UNTIL date incorrectly. Specifically, using e_cal_client_generate_instances() or e_cal_recur_generate_instances_sync() generates an instance one day after the UNTIL date. This bug was introduced with the migration to libical-glib and libecal-2.0, so this affects bot focal and jammy. It was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which will be part of the 3.45.1+ and 3.44.3+ releases respectively. Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/393 Test Case - What Could Go Wrong --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1978476/+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 1978476] Re: Incorrect UNTIL recurrence with midnight start
** Also affects: evolution-data-server (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: evolution-data-server (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: evolution-data-server (Ubuntu Jammy) Status: New => Triaged ** Changed in: evolution-data-server (Ubuntu Jammy) Importance: Undecided => Low ** Changed in: evolution-data-server (Ubuntu Focal) Status: New => Triaged ** Changed in: evolution-data-server (Ubuntu Focal) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1978476 Title: Incorrect UNTIL recurrence with midnight start Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-data-server source package in Focal: Triaged Status in evolution-data-server source package in Jammy: Triaged Bug description: EDS generates instances for recurring events starting at midnight with an UNTIL date incorrectly. Specifically, using e_cal_client_generate_instances() or e_cal_recur_generate_instances_sync() generates an instance one day after the UNTIL date. This bug was introduced with the migration to libical-glib and libecal-2.0, so this affects bot focal and jammy. It was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which will be part of the 3.45.1+ and 3.44.3+ releases respectively. Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data- server/-/issues/393 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1978476/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
Ok, after more investigating I could reproduce the issue and narrow down the problem, for some reason it isn't doing it on my upgraded system but it is a problem a fresh xubuntu install in a VM and seems to be due to the fix for bug #1891338 Editing /etc/apparmor.d/usr.bin.evince to delete L72 ' #include ' and then doing $ sudo aa-enforce evince seems to make it work again or a more selective version - edit /etc/apparmor.d/abstractions/exo-open - delete the section deny dbus send bus=session path=/org/gtk/vfs/mounttracker, - $ sudo apparmor_parser -r /etc/apparmor.d/abstractions/exo-open - $ sudo aa-enforce evince Alex, from the apparmor changelog adding the exo profile you worked on it, any idea about the issue? Using $ dbus-monitor --session | grep gvfs shows that evince fails to talk to gvfs with the apparmor profile loaded but it works once in complains mode or with the change suggested before ** Changed in: evince (Ubuntu) Status: Confirmed => In Progress ** Also affects: apparmor (Ubuntu) Importance: Undecided Status: 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/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in apparmor package in Ubuntu: New Status in evince package in Ubuntu: In Progress Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1978307] Re: gwenview aborts with a std::out_of_range exception raised in libexiv2
The problem seems not to appear on x86_64! On another system gwenview opens the very same file. Working packages on x86_64: libexiv2-14:amd64 0.25-3.1ubuntu0.18.04.1 amd64 gwenview 4:17.12.3-0ubuntu1 amd64 Non-working packages on x86: libexiv2-14:i386 0.25-3.1ubuntu0.18.04.1 i386 gwenview 4:17.12.3-0ubuntu1 i386 (sorry they were truncated in the bug description) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1978307 Title: gwenview aborts with a std::out_of_range exception raised in libexiv2 Status in exiv2 package in Ubuntu: New Status in gwenview package in Ubuntu: New Bug description: This bug seems to be a regression of KDE bug 441121: https://bugs.kde.org/show_bug.cgi?id=441121 When opening certain JPG files, gwenview aborts with an uncaught C++ exception std::out_of_range System is Ubuntu 18.04.6 LTS x86 with up-to-date packages. Terminal output and gdb backtrace follow. terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) Thread 1 "gwenview" received signal SIGABRT, Aborted. 0xf7fd5079 in __kernel_vsyscall () (gdb) bt #0 0xf7fd5079 in __kernel_vsyscall () #1 0xf5d1ea02 in __libc_signal_restore_set (set=0xbe8c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 #2 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 #3 0xf5d1fe91 in __GI_abort () at abort.c:79 #4 0xf5f3b97d in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #5 0xf5f43174 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #6 0xf5f431dd in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #7 0xf5f434dc in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #8 0xf5f6defa in std::__throw_out_of_range_fmt(char const*, ...) () from /usr/lib/i386-linux-gnu/libstdc++.so.6 #9 0xf5881da3 in ?? () from /usr/lib/i386-linux-gnu/libexiv2.so.14 Packages: libexiv2-14:i3860.25-3.1ubuntu0.18.0 i386 gwenview4:17.12.3-0ubuntu1 i386 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1978307/+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 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
It's fixed upstream as well now: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6920b6ceb1c2e7856ad76e118ee5b4dd36130735 -- 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/1977619 Title: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC Status in NetworkManager: New Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Fix Committed Bug description: * Impact The recent SRU created a regression in IPv6 routing order * Test Case 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. * Regression potential The patch change the IPv6 addresses order to match the behaviour from the previous version. If that was buggy the routing order would still be wrong, so we should check that IPv6 setups behave as expected. --- Situation: My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy perspective, for readability reasons and for network management policies, DHCPv6 should *always* be preferred over SLAAC addresses when available. And according to RFC 6724, the smaller /128 scope of the DHCPv6 address should be chosen over the larger /64 scope of the SLAAC address. NetworkManager has always been able to adhere to that by simply setting ip6.privacy=0 for the connection (in nm-connection-editor *not* selecting "Prefer temporary address" for IPv6 privacy extensions). Then it would use the DHCPv6 address as the source for all outgoing traffic. So if you would - for instance - run `curl ifconfig.co`, the DHCPv6 address would be used to connect to the outside world and be echoed back. Regression: Since the update to 1.36.6, this is no longer the case. NetworkManager now routes outgoing traffic through the SLAAC address, even if ip6.privacy=0 is set for the connection. Constantly removing the SLAAC addresses with `ip addr del` or disabling SLAAC RA's on the router are now the only ways to stop NetworkManager from preferring SLAAC over DHCPv6. None of the local options in NetworkManager 1.36.6 are able to restore the previous, desired and correct way of working: the SLAAC address should never be used as the preferred address if a DHCPv6 lease is given. Looking at the changelog of NetworkManager 1.36.6, multiple things regarding IP address order and temporary addresses have been changed in that release, any of them (or a combination) introducing this bug: * Fix a bug in synchronization of IP addresses with kernel that could lead to a wrong address order. * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag is set. * Ensure temporary IPv6 addresses are removed on disconnect and reapply. https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS Steps to reproduce: 1. Connect to a network where the router sends "A" and "M" bits in the RA's and has a DHCPv6 server running (e.g. any OpenWrt router). 2. When running `ip -6 a`, the list now sorts SLAAC addresses above DHCPv6 addresses. With NetworkManager 1.36.4 and earlier, this was not the case. (The Linux kernel uses the address highest in the list as preferred.) 3. When running something like `curl ifconfig.co`, the SLAAC address is being returned, which makes sense as that is now preferred by the kernel. (But it shouldn't be.) Desired behaviour: NetworkManager should always sort DHCPv6 addresses above SLAAC addresses, as is the case for all versions prior to 1.36.6 and also corrected again in 1.38.0. In case static addresses are manually set, those should take first priority, with DHCPv6 second and SLAAC/autoconf last. Implications: This can break many real-life use cases. For instance, my router gives out static leases to my machines. Those addresses are whitelisted in all kinds of firewalls to allow me to access servers for my work. Now that the "wrong" address is being preferred for outgoing traffic (a SLAAC address that I have
[Desktop-packages] [Bug 1971168] Re: [snap] Files on local network shares are not opened / written
** Changed in: firefox (Ubuntu) Status: Confirmed => Triaged ** Package changed: snapd (Ubuntu) => xdg-desktop-portal (Ubuntu) ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => High ** Changed in: xdg-desktop-portal (Ubuntu) Status: Confirmed => Triaged -- 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/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Triaged Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable
Apparently, this problem is happening again: https://bugs.launchpad.net/ubuntu/+source/gwenview/+bug/1978307 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1941752 Title: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable Status in Gwenview: Fix Released Status in exiv2 package in Ubuntu: Fix Released Status in gwenview package in Ubuntu: Fix Released Bug description: Since the recent security update of exiv2, Gwenview crashes when trying to open image files that got exported by darktable. Steps to reproduce: * Make a test installation of Kubuntu 21.04 in VirtualBox * Install all updates * Install darktable * Copy one of the images in /usr/share/wallpapers (or any other image) to your home directory and open it with darktable * Within darktable, export a copy of the image (no need to do any actual modifications) * Try to open that copy with Gwenview. Gwenview will crash. I'm attaching a crash report hinting that this is related to exiv2. Temporary workaround: If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so it seems the crash is related to changes in 0.27.3-3ubuntu1.5. I don't know if the underlying cause is actually some bug in exiv2, Gwenview or darktable. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: libexiv2-27 0.27.3-3ubuntu1.5 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Aug 26 15:16:47 2021 InstallationDate: Installed on 2021-08-26 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: exiv2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1971168] Re: [snap] Files on local network shares are not opened / written
** Changed in: firefox (Ubuntu) Importance: Undecided => High -- 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/1971168 Title: [snap] Files on local network shares are not opened / written Status in Mozilla Firefox: Unknown Status in firefox package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Firefox or Chromium as a Snap package in Ubuntu 22.04 2. Have a SMB file server available where the network shares can be mounted just by clicking on the share in Nautilus file manager (smb:// protocol, usually mounted dynamically via `/var/run/user/.../gvfs/...`) 3. Have one such share mounted and writable 4. Open any website containing images in Firefox / Chromium 5. Right-click on an image and select "Save Image As..." 6. In the file save dialog, navigate to the mounted share 7. Assert content of network share is visible and browsable from within the save dialog 8. Select "Save" at any folder in the network share Actual behavior: * File is not saved to selected network share location * No download entry is created * No error is shown Expected behavior: * File is saved to selected network share location * No error is shown Additional information: * When saving to a folder on the local machine instead, saving works correctly as expected * In contrast to files, new folders that are created from within the save dialog are saved correctly on the network share * Similar situation when trying to open a file with Ctrl + O on a network share from Firefox / Chromium. After double-clicking e.g. an image file in the file dialog, the file dialog closes but nothing happens otherwise. Opening an image on a local folder works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1971168/+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 1978486] Re: Right clicks on file icons select a different file
THanks, weird bug. Does changing the zoom level makes a difference? Do you only get the issue with files that display a preview? According to the report b'org.gnome.nautilus.preferences' b'use-experimental-views' b'true' does that make a difference? $ gsettings reset org.gnome.nautilus.preferences use-experimental-views -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978486 Title: Right clicks on file icons select a different file Status in nautilus package in Ubuntu: Incomplete Bug description: Upgraded to 20.04 from 18.04. Right clicking on files in icon view will always select a different file. This does not happen in list (or detail) mode. Switching between the two modes several times will sometimes make the functionality work for a while in icon mode. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-117.132-generic 5.4.189 Uname: Linux 5.4.0-117-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 13 11:47:32 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-11 (2894 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2022-06-07 (5 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2017-07-06T11:04:37.239623 usr_lib_nautilus: gnome-mplayer 1.0.9-3ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978486/+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 1978400] Re: GNOME Network Displays does not work with error Authorization supplicant timed out
Thanks! ** Changed in: wpa (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1978400 Title: GNOME Network Displays does not work with error Authorization supplicant timed out Status in hostap: Unknown Status in wpa package in Ubuntu: Triaged Bug description: I have a problem with connecting to a Miracast device via GNOME Network Displays package (https://gitlab.gnome.org/GNOME/gnome-network-displays) on Ubuntu. It sees the device normally (I see the device name in "Available Video Sinks" list), but when I'm trying to connect, after some time I've got the connection failed with the error: ``` p2p-dev-wlp0s20f3: Authorization supplicant timed out ``` Other systems (Android, Windows, MacOS) connects to it successfully. In the https://gitlab.gnome.org/GNOME/gnome-network-displays it's described that wpa_supplicant requires the patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/ Maybe just adding this one-line patch could resolve this issue? Or it is already applied? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 12 09:56:19 2022 InstallationDate: Installed on 2022-04-14 (58 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: wpa UpgradeStatus: Upgraded to jammy on 2022-04-14 (58 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/hostap/+bug/1978400/+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 1978547] Re: nautilus crash on search
could you also add the screenshot with an ascii filename, launchpad has a bug which makes it error out when trying to filenames with non ascii encoding -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978547 Title: nautilus crash on search Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 LTS (updated from 21.10) nautilus 1.42.1.1-0ubuntu 15.15.0-37-generic flatpak installed Type=x11 Expected to happen: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus do the search. What happens: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus crashes and prompt to end the process What I've tested: 1. sudo apt install --reinstall nautilus 2. rm ~/.config/nautilus none worked Strange result: sometimes (same search, same folder) it doesn't crash. After waiting about 1min (!) doing nothing, the search results appear. After this happy long time, if I try other searches without closing the window, they work as expected. I would have posted this a week earlier, but then the strange result first came out. So I thought that I could figure it out, but I couldn't. Before that I didn't realize how important the search box was. Now I have installed nemo as I was waiting nautilus to be fixed. If I could test anything that it could help, I would love to help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978547/+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 1978547] Re: nautilus crash on search
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978547 Title: nautilus crash on search Status in nautilus package in Ubuntu: Incomplete Bug description: Ubuntu 22.04 LTS (updated from 21.10) nautilus 1.42.1.1-0ubuntu 15.15.0-37-generic flatpak installed Type=x11 Expected to happen: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus do the search. What happens: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus crashes and prompt to end the process What I've tested: 1. sudo apt install --reinstall nautilus 2. rm ~/.config/nautilus none worked Strange result: sometimes (same search, same folder) it doesn't crash. After waiting about 1min (!) doing nothing, the search results appear. After this happy long time, if I try other searches without closing the window, they work as expected. I would have posted this a week earlier, but then the strange result first came out. So I thought that I could figure it out, but I couldn't. Before that I didn't realize how important the search box was. Now I have installed nemo as I was waiting nautilus to be fixed. If I could test anything that it could help, I would love to help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978547/+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 1978547] [NEW] nautilus crash on search
Public bug reported: Ubuntu 22.04 LTS (updated from 21.10) nautilus 1.42.1.1-0ubuntu 15.15.0-37-generic flatpak installed Type=x11 Expected to happen: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus do the search. What happens: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus crashes and prompt to end the process What I've tested: 1. sudo apt install --reinstall nautilus 2. rm ~/.config/nautilus none worked Strange result: sometimes (same search, same folder) it doesn't crash. After waiting about 1min (!) doing nothing, the search results appear. After this happy long time, if I try other searches without closing the window, they work as expected. I would have posted this a week earlier, but then the strange result first came out. So I thought that I could figure it out, but I couldn't. Before that I didn't realize how important the search box was. Now I have installed nemo as I was waiting nautilus to be fixed. If I could test anything that it could help, I would love to help! ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: 22.04 nautilus search ubuntu ** Attachment added: "Στιγμιότυπο στις 2022-06-14 12-11-43.png" https://bugs.launchpad.net/bugs/1978547/+attachment/5597210/+files/%CE%A3%CF%84%CE%B9%CE%B3%CE%BC%CE%B9%CF%8C%CF%84%CF%85%CF%80%CE%BF%20%CF%83%CF%84%CE%B9%CF%82%202022-06-14%2012-11-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1978547 Title: nautilus crash on search Status in nautilus package in Ubuntu: New Bug description: Ubuntu 22.04 LTS (updated from 21.10) nautilus 1.42.1.1-0ubuntu 15.15.0-37-generic flatpak installed Type=x11 Expected to happen: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus do the search. What happens: 1. open nautilus 2. type anything in search box in any folder (remote or not, empty or not) 3. nautilus crashes and prompt to end the process What I've tested: 1. sudo apt install --reinstall nautilus 2. rm ~/.config/nautilus none worked Strange result: sometimes (same search, same folder) it doesn't crash. After waiting about 1min (!) doing nothing, the search results appear. After this happy long time, if I try other searches without closing the window, they work as expected. I would have posted this a week earlier, but then the strange result first came out. So I thought that I could figure it out, but I couldn't. Before that I didn't realize how important the search box was. Now I have installed nemo as I was waiting nautilus to be fixed. If I could test anything that it could help, I would love to help! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1978547/+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 1978544] Re: /usr/bin/gnome-shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_native_apply_monitors_config:meta_monitor_manager_apply_mo
*** This bug is a duplicate of bug 1870454 *** https://bugs.launchpad.net/bugs/1870454 ** This bug has been marked a duplicate of bug 1870454 gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() -- 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/1978544 Title: /usr/bin/gnome- shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_native_apply_monitors_config:meta_monitor_manager_apply_monitors_config:restore_previous_config Status in gnome-shell package in Ubuntu: New 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 42.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fffcd112bc9125d02cba17f6d7df29cd806c4912 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978544/+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 1870454] Re: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign()
The Wayland version of this crash is being tracked in: https://errors.ubuntu.com/problem/fffcd112bc9125d02cba17f6d7df29cd806c4912 ** Description changed: https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 https://errors.ubuntu.com/problem/717fc039791d35516db85b1057b844960bb16d57 + https://errors.ubuntu.com/problem/fffcd112bc9125d02cba17f6d7df29cd806c4912 --- I don't really know what caused this, I didn't notice anything out of the ordinary, so I'm not sure exactly when it occurred. I usually plug and unplug an external monitor, this seems related. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 2 19:31:02 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-14 (475 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fdf6e50156b : mov 0x8(%rax,%rdi,1),%rax PC (0x7fdf6e50156b) ok source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 meta_monitor_config_manager_assign () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs() UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers separator: ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1820 https://gitlab.gnome.org/GNOME/mutter/-/issues/1820 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1820 Importance: Unknown Status: Unknown ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1870454 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs (monitor=0x0) from meta_monitor_config_manager_assign() Status in Mutter: Unknown Status in mutter package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/930950abdb6648752bc30584d0833b348c68f0ba https://errors.ubuntu.com/problem/50192237f22f17593e486f3349bf4770a1e28002 https://errors.ubuntu.com/problem/717fc039791d35516db85b1057b844960bb16d57 https://errors.ubuntu.com/problem/fffcd112bc9125d02cba17f6d7df29cd806c4912 --- I don't really know what caused this, I didn't notice anything out of the ordinary, so I'm not sure exactly when it occurred. I usually plug and unplug an external monitor, this seems related. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 2 19:31:02 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-12-14 (475 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SegvAnalysis: Segfault happened at: 0x7fdf6e50156b : mov 0x8(%rax,%rdi,1),%rax PC (0x7fdf6e50156b) ok source "0x8(%rax,%rdi,1)" (0xffb8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_monitor_get_outputs () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 meta_monitor_config_manager_assign () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 () at /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in meta_monitor_get_outputs() UpgradeStatus: Upgraded to focal on 2020-03-25 (8 days ago) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo vboxusers separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/187
[Desktop-packages] [Bug 1978544] [NEW] /usr/bin/gnome-shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_native_apply_monitors_config:meta_monitor_manager_apply_
*** This bug is a duplicate of bug 1870454 *** https://bugs.launchpad.net/bugs/1870454 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fffcd112bc9125d02cba17f6d7df29cd806c4912 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: impish jammy kinetic -- 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/1978544 Title: /usr/bin/gnome- shell:11:meta_monitor_get_outputs:meta_monitor_config_manager_assign:meta_monitor_manager_native_apply_monitors_config:meta_monitor_manager_apply_monitors_config:restore_previous_config Status in gnome-shell package in Ubuntu: New 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 42.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fffcd112bc9125d02cba17f6d7df29cd806c4912 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978544/+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 1965897] Re: gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from
Let's _assume_ this is fixed in 42.2 as suggested upstream: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5271 ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: fixed-in-42.2 fixed-upstream ** Changed in: gnome-shell (Ubuntu) Status: Fix Committed => Fix Released ** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu) -- 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/1965897 Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type(window=NULL) from meta_window_actor_queue_destroy() from meta_compositor_real_remove_window() from meta_window_unmanage() from meta_display_unmanage_windows() Status in GNOME Shell: New Status in mutter package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/0f9ebdf291c30c238c6f29d22b7d503ef8910bdd --- Crashed after I tried to restart the shell with the 'r' command. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 22 10:59:42 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2022-02-25 (24 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcCmdline: /usr/bin/gnome-shell RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_window_type () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0 meta_display_close () from /lib/x86_64-linux-gnu/libmutter-10.so.0 shell_global_reexec_self () from /usr/lib/gnome-shell/libgnome-shell.so Title: gnome-shell crashed with SIGSEGV in meta_window_get_window_type() UpgradeStatus: Upgraded to jammy on 2022-03-14 (7 days ago) UserGroups: sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1965897/+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 1978400] Re: GNOME Network Displays does not work with error Authorization supplicant timed out
Thanks for the info, I've posted the issue: https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/246 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-network-displays/-/issues #246 https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/246 ** Also affects: hostap via https://gitlab.gnome.org/GNOME/gnome-network-displays/-/issues/246 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1978400 Title: GNOME Network Displays does not work with error Authorization supplicant timed out Status in hostap: Unknown Status in wpa package in Ubuntu: Incomplete Bug description: I have a problem with connecting to a Miracast device via GNOME Network Displays package (https://gitlab.gnome.org/GNOME/gnome-network-displays) on Ubuntu. It sees the device normally (I see the device name in "Available Video Sinks" list), but when I'm trying to connect, after some time I've got the connection failed with the error: ``` p2p-dev-wlp0s20f3: Authorization supplicant timed out ``` Other systems (Android, Windows, MacOS) connects to it successfully. In the https://gitlab.gnome.org/GNOME/gnome-network-displays it's described that wpa_supplicant requires the patch: https://patchwork.ozlabs.org/project/hostap/patch/20200825062902.124600-1-benja...@sipsolutions.net/ Maybe just adding this one-line patch could resolve this issue? Or it is already applied? ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-6ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Jun 12 09:56:19 2022 InstallationDate: Installed on 2022-04-14 (58 days ago) InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info' SourcePackage: wpa UpgradeStatus: Upgraded to jammy on 2022-04-14 (58 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/hostap/+bug/1978400/+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 1978534] Re: Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument]
*** This bug is a duplicate of bug 1968040 *** https://bugs.launchpad.net/bugs/1968040 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1968040, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1968040 Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] -- 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/1978534 Title: Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument] Status in gnome-shell package in Ubuntu: New Bug description: Screen wont wake up using mouse or keyboard. The only way to wake it up is to use CTRL+ALT+F1. The behavior is similar to the one for this bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274 The following is the log while this situation occurs: Jun 14 10:30:13 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:13 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument [ X 300+ of the first 2 lines] Jun 14 10:30:18 xps gnome-shell[3623]: JS ERROR: Failed to open reauthentication channel: Gio.IOErrorEnum: Error receiving data: Connection reset by peer#012_promisify/proto[asyncFunc]/ Warning: Unsupported maximum keycode 708, clipping. Jun 14 10:30:36 xps gnome-shell[12148]: > X11 cannot support keycodes above 255. Jun 14 10:30:36 xps gnome-shell[12148]: Errors from xkbcomp are not fatal to the X server Jun 14 10:30:36 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Object .MetaInputDeviceNative (0x7fb97014c200), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jun 14 10:30:36 xps gnome-shell[3623]: == Stack trace for context 0x56180bd0f4b0 == Jun 14 10:30:36 xps gnome-shell[3623]: #0 56180f536160 i resource:///org/gnome/shell/ui/keyboard.js:1216 (2e077f8a62e0 @ 56) Jun 14 10:30:36 xps gnome-shell[3623]: #1 56180f5360b8 i resource:///org/gnome/shell/ui/keyboard.js:1222 (2e077f8a6330 @ 94) Jun 14 10:30:36 xps gnome-shell[3623]: #2 7ffe1f7901c0 b self-hosted:1181 (10952b4b0a10 @ 454) Jun 14 10:30:36 xps dbus-daemon[3485]: [session uid=1000 pid=3485] Activating service name='org.gnome.ArchiveManager1' requested by ':1.147' (uid=1000 pid=12112 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jun 14 10:30:37 xps gnome-shell[3623]: DING: Detected async api for thumbnails Jun 14 10:30:37 xps gnome-shell[3623]: DING: GNOME nautilus 42.1.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Thank you Daniel!
I have added the bug information here:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534
--
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/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Released
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+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 1978534] [NEW] Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument]
Public bug reported: Screen wont wake up using mouse or keyboard. The only way to wake it up is to use CTRL+ALT+F1. The behavior is similar to the one for this bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274 The following is the log while this situation occurs: Jun 14 10:30:13 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:13 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument [ X 300+ of the first 2 lines] Jun 14 10:30:18 xps gnome-shell[3623]: JS ERROR: Failed to open reauthentication channel: Gio.IOErrorEnum: Error receiving data: Connection reset by peer#012_promisify/proto[asyncFunc]/ Warning: Unsupported maximum keycode 708, clipping. Jun 14 10:30:36 xps gnome-shell[12148]: > X11 cannot support keycodes above 255. Jun 14 10:30:36 xps gnome-shell[12148]: Errors from xkbcomp are not fatal to the X server Jun 14 10:30:36 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Object .MetaInputDeviceNative (0x7fb97014c200), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jun 14 10:30:36 xps gnome-shell[3623]: == Stack trace for context 0x56180bd0f4b0 == Jun 14 10:30:36 xps gnome-shell[3623]: #0 56180f536160 i resource:///org/gnome/shell/ui/keyboard.js:1216 (2e077f8a62e0 @ 56) Jun 14 10:30:36 xps gnome-shell[3623]: #1 56180f5360b8 i resource:///org/gnome/shell/ui/keyboard.js:1222 (2e077f8a6330 @ 94) Jun 14 10:30:36 xps gnome-shell[3623]: #2 7ffe1f7901c0 b self-hosted:1181 (10952b4b0a10 @ 454) Jun 14 10:30:36 xps dbus-daemon[3485]: [session uid=1000 pid=3485] Activating service name='org.gnome.ArchiveManager1' requested by ':1.147' (uid=1000 pid=12112 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jun 14 10:30:37 xps gnome-shell[3623]: DING: Detected async api for thumbnails Jun 14 10:30:37 xps gnome-shell[3623]: DING: GNOME nautilus 42.1.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 10:32:00 2022 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-07 (675 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-27 (47 days ago) ** Affects: gnome-shell (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 gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1978534 Title: Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument] Status in gnome-shell package in Ubuntu: New Bug description: Screen wont wake up using mouse or keyboard. The only way to wake it up is to use CTRL+ALT+F1. The behavior is similar to the one for this bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274 The following is the log while this situation occurs: Jun 14 10:30:13 xps gnome-shell[3623]: Failed to post KMS update: drmM
[Desktop-packages] [Bug 1967121] Re: Dock auto-hides when a right click context menu is opened while a window is under the dock
Nice, now I get it. Thanks a lot for the detailed explanations! -- 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/1967121 Title: Dock auto-hides when a right click context menu is opened while a window is under the dock Status in Dash to dock: Fix Released Status in ubuntu-dock: Unknown Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Committed Status in gnome-shell-extension-ubuntu-dock source package in Jammy: Triaged Bug description: [Impact] If the dock is set to auto-hide and a window is under the dock, then the dock hides prematurely when a menu is opened from one of its icons. This only seems to happen with GNOME 42. [Test Plan] 1. Set the dock to auto hide. 2. Move a window under the dock's position so that it wants to auto-hide. 3. Open the dock and right click on one of the icons to open a menu. Expected: Dock stays open while the menu is open. Observed: Dock closes while the menu is open. [Where problems could occur] This fix may affect any scenarios relating to the dock auto-hiding. [Other Info] Upstream fixes: ubuntu-dock: https://github.com/micheleg/dash-to-dock/pull/1739 dash-to-dock: https://github.com/micheleg/dash-to-dock/pull/1751 To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1967121/+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
