[Desktop-packages] [Bug 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy
[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.] ** Changed in: network-manager (Ubuntu) Status: Incomplete => Expired -- 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/1964100 Title: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy Status in network-manager package in Ubuntu: Expired Bug description: I'm trying to connect to an open (i.e. no ecryption) WLAN with network-manager 1.36.0-1ubuntu2 on 22.04 but it's failing with the following error message (after selecting the network from the network- manager applet prompt): Mär 08 10:50:04 Isaac-Laptop NetworkManager[31754]: [1646733004.4425] audit: op="connection-add-activate" pid=12122 uid=1000 result="fail" reason="802-11-wireless-security.key-mgmt: Access point does not support PSK but setting requires it" I haven't changed any of the default settings for network-manager and this network worked on 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+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 1967885] Re: blanking locks screen although screen lock is disabled
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- 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/1967885 Title: blanking locks screen although screen lock is disabled Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+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 1967885] Re: blanking locks screen although screen lock is disabled
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1967885 Title: blanking locks screen although screen lock is disabled Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Bug description: I disabled screen lock from Settings > Privacy > Screen. Even so, I am forced to log in any time my screen has blanked. When I inspect dconf-editor (org.gnome.desktop.lockdown), I see that locking is indeed active. This looks like a discrepancy between the settings mechanism and dconf. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 16:06:06 2022 InstallationDate: Installed on 2022-03-27 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1967885/+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 1978366] [NEW] unlocking screen hangs for 20-40sec before working
Public bug reported: Ever since installing (not upgrading) Ubuntu-22.04, I've noticed that quite often (but not always) unlocking the screensaver freezes the entire system. By that I mean I will tap my keyboard, the blank screen will lighten up and show the password field, I start typing, get the "***" characters, and then it freezes: typing doesn't continue, mouse stops moving. If I wait, 30-40 (ish) seconds later it will catch up and start responding again and I can continue. Quite often the freeze doesn't occur until I have entered my password and hit ENTER - but it does freeze earlier too. I have figured out that if this happens, I can speed up the process by hitting Ctrl-Alt-F3 to go to a tty, then immediately Alt-F2 to go back to gnome - and that flushes out the problem. Definitely shaves many seconds off waiting around for the fault to clear by itself. I was also talking to a collegue who installed Ubuntu-22.04 this week - he's noticed the same issue. Also a Dell laptop - but different model. I would guess Wayland related - but don't have any evidence for that, so I put this as gnome-shell Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:02:34 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-13 (89 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1978366 Title: unlocking screen hangs for 20-40sec before working Status in gnome-shell package in Ubuntu: New Bug description: Ever since installing (not upgrading) Ubuntu-22.04, I've noticed that quite often (but not always) unlocking the screensaver freezes the entire system. By that I mean I will tap my keyboard, the blank screen will lighten up and show the password field, I start typing, get the "***" characters, and then it freezes: typing doesn't continue, mouse stops moving. If I wait, 30-40 (ish) seconds later it will catch up and start responding again and I can continue. Quite often the freeze doesn't occur until I have entered my password and hit ENTER - but it does freeze earlier too. I have figured out that if this happens, I can speed up the process by hitting Ctrl-Alt-F3 to go to a tty, then immediately Alt-F2 to go back to gnome - and that flushes out the problem. Definitely shaves many seconds off waiting around for the fault to clear by itself. I was also talking to a collegue who installed Ubuntu-22.04 this week - he's noticed the same issue. Also a Dell laptop - but different model. I would guess Wayland related - but don't have any evidence for that, so I put this as gnome-shell Thanks! ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 11 14:02:34 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-03-13 (89 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978366/+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 1978349] Re: Monitors sometimes permanently blanked after resume
** Package changed: ubuntu => xorg (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/1978349 Title: Monitors sometimes permanently blanked after resume Status in xorg package in Ubuntu: New Bug description: Sometimes monitors don't wake up after resume. Happened couple times with Ubuntu 22.04 so far. Journalctl lists only one instance of this, might have failed to save the logs on other times. kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039! 1. (assumedly) occurs when resuming from ram 2. suspend chosen from ui 3. resume by clicking key on keyboard 4.-11. not tested yet with mainline builds, since uncertain about how to reproduce reliably. 12. openssh-server only installed after today's instance, so don't have much debug data beyond what was saved in logs before sysrq-sub. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 23:02:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 4966 F pulseaudio /dev/snd/controlC1: iheino 4966 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6
[Desktop-packages] [Bug 1978349] [NEW] Monitors sometimes permanently blanked after resume
You have been subscribed to a public bug: Sometimes monitors don't wake up after resume. Happened couple times with Ubuntu 22.04 so far. Journalctl lists only one instance of this, might have failed to save the logs on other times. kernel BUG at drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039! 1. (assumedly) occurs when resuming from ram 2. suspend chosen from ui 3. resume by clicking key on keyboard 4.-11. not tested yet with mainline builds, since uncertain about how to reproduce reliably. 12. openssh-server only installed after today's instance, so don't have much debug data beyond what was saved in logs before sysrq-sub. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 23:02:04 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 5500/5500M / Pro 5500M] [1462:3822] InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iheino 4966 F pulseaudio /dev/snd/controlC1: iheino 4966 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-04-27 (44 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 RelatedPackageVersions: linux-restricted-modules-5.15.0-37-generic N/A linux-backports-modules-5.15.0-37-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/16/2012 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2106 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8B WS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias:
[Desktop-packages] [Bug 1978363] [NEW] The menu blinks constantly
Public bug reported: I've found this problem on Xubuntu 22.04, fresh update. When I click on the network icon in the taskbar, I expect to get the menu of available wifi networks, etc. This happens, but the menu blinks so much that it's impossible to use it. I'm attaching a small screencast to show the problem. When XFCE starts, I get a few seconds of "peace" before this starts. This might be related to https://bugs.launchpad.net/ubuntu/+source/network-manager- applet/+bug/1735367 I'd be happy to provide more information (logs, etc), but right now I don't know where to look. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screencast showing the problem" https://bugs.launchpad.net/bugs/1978363/+attachment/5596628/+files/wifi_applet_problem.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978363 Title: The menu blinks constantly Status in network-manager-applet package in Ubuntu: New Bug description: I've found this problem on Xubuntu 22.04, fresh update. When I click on the network icon in the taskbar, I expect to get the menu of available wifi networks, etc. This happens, but the menu blinks so much that it's impossible to use it. I'm attaching a small screencast to show the problem. When XFCE starts, I get a few seconds of "peace" before this starts. This might be related to https://bugs.launchpad.net/ubuntu/+source/network-manager- applet/+bug/1735367 I'd be happy to provide more information (logs, etc), but right now I don't know where to look. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978363/+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
For me too: upgraded from 21.10 to 22.04. -- 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 evince package in Ubuntu: Confirmed 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/evince/+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
If the problem doesn't occur on 22.04 fresh install, I can confirm it happens during upgrade from 21.10. Thanks for raising and responsiveness. -- 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 evince package in Ubuntu: Confirmed 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/evince/+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
Has anybody checked if this happens only when upgrading from 21.10 to 22.04? -- 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 evince package in Ubuntu: Confirmed 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/evince/+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
Changed to high, it's not going to automatically resolve the issue though, that needs debugging from someone who is getting the problem ** Changed in: evince (Ubuntu) Importance: Low => 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 evince package in Ubuntu: Confirmed 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/evince/+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 1977695] Re: Xorg fails to start: (EE) Error parsing the config file
That all makes sense. Thank you for carrying the lonely banner during this transition period so that us slow adopters aren't abruptly cast out in the cold. -- 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/1977695 Title: Xorg fails to start: (EE) Error parsing the config file Status in xorg-server package in Ubuntu: Invalid Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 xorg: Installed: 1:7.7+23ubuntu2 Candidate: 1:7.7+23ubuntu2 Version table: *** 1:7.7+23ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status 1. Uncomment WaylandEnable=false in /etc/gdm3/custom.conf 2. Reboot. 3. See black screen after selecting Ubuntu at GRUB prompt. Login screen never loads. Unplugging any external monitors appears to have no effect on the bug. I am aware that most users of Ubuntu 22.04 see an option at the login screen to change the display manager. I have never seen such an option. My machine always uses Wayland unless I modify /etc/gdm3/custom.conf directly. Using Wayland is detrimental to my health, because the Night Light feature does nothing. I have nvidia- driver-510 installed. I am happy to provide further debugging information upon request. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.73.05 Sat May 7 05:30:26 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:47:31 2022 DistUpgraded: 2022-05-07 18:27:00,043 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8259] Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] [103c:8259] InstallationDate: Installed on 2020-12-09 (543 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: HP OMEN by HP Laptop 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-35-generic root=UUID=13d7b775-7783-44fc-8e24-164127457fd4 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-05-08 (28 days ago) dmi.bios.date: 12/22/2020 dmi.bios.release: 15.56 dmi.bios.vendor: Insyde dmi.bios.version: F.56 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8259 dmi.board.vendor: HP dmi.board.version: 83.72 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 83.72 dmi.modalias: dmi:bvnInsyde:bvrF.56:bd12/22/2020:br15.56:efr83.72:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.72:cvnHP:ct10:cvrChassisVersion:skuW2N35UAR#ABA: dmi.product.family: 103C_5335KV HP Omen dmi.product.name: OMEN by HP Laptop dmi.product.sku: W2N35UAR#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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 22.0.1-1ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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/xorg-server/+bug/1977695/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[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
It is really cumbersome to work with Ubuntu now :( Please raise the importance. -- 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 evince package in Ubuntu: Confirmed 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/evince/+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 1975638] Re: Broken background portal autostart in 1.14.3
On 22.04: 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. -- 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: Incomplete Bug description: 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. 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 1978007] Re: Please merge network-manager-applet 1.28.0-1 from Debian unstable
> if that's not needed anymore we can remove it but that's not a delta remaining Ah, that caused the confusion, I put it in the wrong place in the change log. Fixed. ** Patch added: "1.28.0-1--1.28.0-1ubuntu1.v4.diff" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+attachment/5596538/+files/1.28.0-1--1.28.0-1ubuntu1.v4.diff ** Description changed: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium - * Merge with Debian. Remaining changes: - - d/control, d/rules: - + Run dh_translations. - - d/control: - + Drop , since the packages are now also available in s390x. - + Replace gnome-icon-theme by humanity-icon-theme in Recommends. - Both provide gnome-lockscreen's icon, but the latter is installed - by default in Ubuntu. - - d/patches: - + Force-online-state-with-unmanaged-devices.patch - + Have-the-appindicator-enabled-by-default.patch - + lp341684_device_sensitive_disconnect_notify.patch - + lp460144_correctly_update_notification.patch - + Make-policykit-restricted-actions-insensitive.patch - + Support-hiding-rather-than-desensitizing-disallowed-items.patch - * Drop patches applied upstream: - - git_owe_activation.patch - - gitlab_new_meson.patch + * Merge with Debian. Remaining changes: + - d/control, d/rules: + + Run dh_translations. + - d/control: + + Replace gnome-icon-theme by humanity-icon-theme in Recommends. + Both provide gnome-lockscreen's icon, but the latter is installed + by default in Ubuntu. + - d/patches: + + Force-online-state-with-unmanaged-devices.patch + + Have-the-appindicator-enabled-by-default.patch + + lp341684_device_sensitive_disconnect_notify.patch + + lp460144_correctly_update_notification.patch + + Make-policykit-restricted-actions-insensitive.patch + + Support-hiding-rather-than-desensitizing-disallowed-items.patch + * Drop patches applied upstream: + - git_owe_activation.patch + - gitlab_new_meson.patch + * Drop , since the packages are now also available in s390x. - -- Nathan Pratta Teodosio Fri, 10 Jun 2022 13:54:36 -0300 + -- Nathan Pratta Teodosio Fri, 10 Jun 2022 13:54:36 -0300 ==>END<== I tested it with Pbuilder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Incomplete Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: + Run dh_translations. - d/control: + Replace gnome-icon-theme by humanity-icon-theme in Recommends. Both provide gnome-lockscreen's icon, but the latter is installed by default in Ubuntu. - d/patches: + Force-online-state-with-unmanaged-devices.patch + Have-the-appindicator-enabled-by-default.patch + lp341684_device_sensitive_disconnect_notify.patch + lp460144_correctly_update_notification.patch + Make-policykit-restricted-actions-insensitive.patch + Support-hiding-rather-than-desensitizing-disallowed-items.patch * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch * Drop , since the packages are now also available in s390x. -- Nathan Pratta Teodosio Fri, 10 Jun 2022 13:54:36 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1978007] Re: Please merge network-manager-applet 1.28.0-1 from Debian unstable
> + + Drop , since the packages are now also available in s390x. hum, I might be not seeing that right, but s390x isn't mentioned in that patch out of the changelog nor in https://salsa.debian.org/utopia- team/network-manager-applet/-/blob/debian/master/debian/control , what's part of the patch is documenting exactly? we did had added to Depends > gnome-shell | policykit-1-gnome | > polkit-1-auth-agent , if that's not needed anymore we can remove it but that's not a delta remaining -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Incomplete Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: + Run dh_translations. - d/control: + Drop , since the packages are now also available in s390x. + Replace gnome-icon-theme by humanity-icon-theme in Recommends. Both provide gnome-lockscreen's icon, but the latter is installed by default in Ubuntu. - d/patches: + Force-online-state-with-unmanaged-devices.patch + Have-the-appindicator-enabled-by-default.patch + lp341684_device_sensitive_disconnect_notify.patch + lp460144_correctly_update_notification.patch + Make-policykit-restricted-actions-insensitive.patch + Support-hiding-rather-than-desensitizing-disallowed-items.patch * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch -- Nathan Pratta Teodosio Fri, 10 Jun 2022 13:54:36 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1978341] [NEW] Merge for xdg-desktop-portal 1.14.4 from Debian unstable
Public bug reported:
This is a merge request for 1.14.4.
==> debian/changelog <==
xdg-desktop-portal (1.14.4-1ubuntu1) UNRELEASED; urgency=medium
* Merge from Debian. Remaining changes:
- debian/patches/{01..11}webextensions-portal.patch
* Single patch file was split into multiple files to avoid dpkg-source
complaining that it patched files multiple times.
-- Nathan Pratta Teodosio Fri, 10 Jun 2022
14:08:05 -0300
==> END <==
Build tested with Pbuilder.
** Affects: xdg-desktop-portal (Ubuntu)
Importance: Wishlist
Status: Confirmed
** Patch added: "1.14.4-1--1.14.4-1ubuntu1.diff"
https://bugs.launchpad.net/bugs/1978341/+attachment/5596536/+files/1.14.4-1--1.14.4-1ubuntu1.diff
--
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/1978341
Title:
Merge for xdg-desktop-portal 1.14.4 from Debian unstable
Status in xdg-desktop-portal package in Ubuntu:
Confirmed
Bug description:
This is a merge request for 1.14.4.
==> debian/changelog <==
xdg-desktop-portal (1.14.4-1ubuntu1) UNRELEASED; urgency=medium
* Merge from Debian. Remaining changes:
- debian/patches/{01..11}webextensions-portal.patch
* Single patch file was split into multiple files to avoid dpkg-source
complaining that it patched files multiple times.
-- Nathan Pratta Teodosio Fri, 10 Jun 2022
14:08:05 -0300
==> END <==
Build tested with Pbuilder.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978341/+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 1978340] [NEW] "flatpak run ..." fails with "bwrap: Can't get type of source /mnt: Permission denied"
Public bug reported: When I try to start a flatpak app, I get: $ flatpak run org.gnome.gitg bwrap: Can't get type of source /mnt: Permission denied error: Failed to sync with dbus proxy $ echo $? 1 I have: $ flatpak list Name Application ID Version BranchInstallation Freedesktop Platform org.freedesktop.Platform 21.08.1421.08 system Mesa org.freedesktop.Platform.GL.default21.3.8 21.08 system openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system GNOME Application Platform version 41 org.gnome.Platform 41system gitg org.gnome.gitg 41 stablesystem Yaru Gtk Themeorg.gtk.Gtk3theme.Yaru 3.22 system ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 20:08:35 2022 InstallationDate: Installed on 2022-03-21 (80 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-03-21 (80 days ago) ** Affects: flatpak (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 flatpak in Ubuntu. https://bugs.launchpad.net/bugs/1978340 Title: "flatpak run ..." fails with "bwrap: Can't get type of source /mnt: Permission denied" Status in flatpak package in Ubuntu: New Bug description: When I try to start a flatpak app, I get: $ flatpak run org.gnome.gitg bwrap: Can't get type of source /mnt: Permission denied error: Failed to sync with dbus proxy $ echo $? 1 I have: $ flatpak list Name Application ID Version BranchInstallation Freedesktop Platform org.freedesktop.Platform 21.08.1421.08 system Mesa org.freedesktop.Platform.GL.default21.3.8 21.08 system openh264 org.freedesktop.Platform.openh264 2.1.0 2.0 system GNOME Application Platform version 41 org.gnome.Platform 41system gitg org.gnome.gitg 41 stablesystem Yaru Gtk Themeorg.gtk.Gtk3theme.Yaru 3.22 system ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: flatpak 1.12.7-1 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 Uname: Linux 5.15.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 20:08:35 2022 InstallationDate: Installed on 2022-03-21 (80 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: flatpak UpgradeStatus: Upgraded to jammy on 2022-03-21 (80 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flatpak/+bug/1978340/+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 1978007] Re: Please merge network-manager-applet 1.28.0-1 from Debian unstable
** Description changed: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: - + Run dh_translations + + Run dh_translations. - d/control: - + Drop , since the packages are now also available in s390x - + Drop >= 1.8 version requirement for network-manager since all - supported releases satisfy it + + Drop , since the packages are now also available in s390x. + + Replace gnome-icon-theme by humanity-icon-theme in Recommends. + Both provide gnome-lockscreen's icon, but the latter is installed + by default in Ubuntu. + - d/patches: + + Force-online-state-with-unmanaged-devices.patch + + Have-the-appindicator-enabled-by-default.patch + + lp341684_device_sensitive_disconnect_notify.patch + + lp460144_correctly_update_notification.patch + + Make-policykit-restricted-actions-insensitive.patch + + Support-hiding-rather-than-desensitizing-disallowed-items.patch * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch - -- Nathan Pratta Teodosio Fri, 10 Jun 2022 09:10:05 -0300 + -- Nathan Pratta Teodosio Fri, 10 Jun 2022 13:54:36 -0300 ==>END<== I tested it with Pbuilder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Incomplete Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: + Run dh_translations. - d/control: + Drop , since the packages are now also available in s390x. + Replace gnome-icon-theme by humanity-icon-theme in Recommends. Both provide gnome-lockscreen's icon, but the latter is installed by default in Ubuntu. - d/patches: + Force-online-state-with-unmanaged-devices.patch + Have-the-appindicator-enabled-by-default.patch + lp341684_device_sensitive_disconnect_notify.patch + lp460144_correctly_update_notification.patch + Make-policykit-restricted-actions-insensitive.patch + Support-hiding-rather-than-desensitizing-disallowed-items.patch * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch -- Nathan Pratta Teodosio Fri, 10 Jun 2022 13:54:36 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1977776] Re: Update gnome-shell to 42.2
Hello Jeremy, or anyone else affected, Accepted gnome-shell into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- shell/42.2-0ubuntu0.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-shell (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/196 Title: Update gnome-shell to 42.2 Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/gnome-shell/-/blob/42.2/NEWS Test Case 1 - sudo apt install gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: GNOME GNOME Classic Ubuntu Ubuntu on Xorg Test Case 2 --- Because a GNOME Shell update years ago broke some GNOME Shell extensions, it's also requested that we do a basic test of all the extensions included in the Ubuntu repositories. https://discourse.ubuntu.com/t/removal-of-gnome-shell-extension-from- universe-and-stop-auto-syncs/18437/9 Install all the extensions. Log out and then log back in. Use one of the Extensions apps to enable all the extensions. Verify that they can all be enabled without showing an error. What Could Go Wrong --- GNOME Shell is the heart of the Ubuntu desktop experience. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. GNOME Shell is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/196/+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 1976381] Re: Update mutter to 42.2
Hello Jeremy, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1976381 Title: Update mutter to 42.2 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: Impact -- There is a new bugfix release in the stable 42 series. https://gitlab.gnome.org/GNOME/mutter/-/blob/42.2/NEWS Test Case - sudo apt install budgie-desktop gnome-session gnome-shell-extensions Install the update. Log out. Select your name on the login screen. Click the gear button to choose a session to log in to. Finish logging in. Verify that things continue to work well for all these sessions: Budgie GNOME GNOME Classic Ubuntu Ubuntu on Xorg What Could Go Wrong --- Mutter is an essential component of the default Ubuntu desktop and for the desktop used by Ubuntu Budgie. A severe enough bug could mean that people are unable to use their desktop version of Ubuntu. Smaller bugs could interrupt people's workflows. mutter is part of GNOME Core and is included in the GNOME micro release exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1976381/+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 1969893] Re: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9]
Hello Daniel, or anyone else affected, Accepted mutter into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/42.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969893 Title: gnome-shell crashes with SIGSEGV just after logging "JS ERROR: TypeError: window is null" from _destroyWindow() [windowManager.js:1543:9] Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Bug description: Impact == GNOME Shell crashes when it's restarted on Xorg. (There is no option to restart GNOME Shell on Wayland.) Test Case = Install the update On the login screen, select your name. Click the gear button in the lower right and choose Ubuntu on Xorg Enter your password to finish logging in. Open the file browser. Press Alt-F2. In the dialog, enter 'r' GNOME Shell should restart without a crash message. Your file browser window should remain open. What Could Go Wrong === See the master bug for this update LP: #1976381 More Details gnome-shell crashes with SIGSEGV just after logging: gnome-shell[3117]: JS ERROR: TypeError: window is null _destroyWindow@resource:///org/gnome/shell/ui/windowManager.js:1543:9 _initializeUI/<@resource:///org/gnome/shell/ui/main.js:260:16 Examples: https://errors.ubuntu.com/oops/96ee1700-c208-11ec-a3de-fa163ef35206 https://errors.ubuntu.com/oops/e97480f0-c1bc-11ec-a3d8-fa163ef35206 https://errors.ubuntu.com/oops/aa5bf652-d517-11ec-9aa3-fa163e55efd0 Tracking in: https://errors.ubuntu.com/problem/eb1d2411708c44f1299f717f5a9c19c03cf80470 ^^^ this is the second most common gnome-shell crash on errors.ubuntu.com To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969893/+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 1978007] Re: Please merge network-manager-applet 1.28.0-1 from Debian unstable
>= 1.8 came indeed from Debian, but not s390x: https://merges.ubuntu.com/n/network-manager-applet/network-manager- applet_1.28.0-1.patch It was introduced in 1.8.18-2ubuntu5 according to the changelog. I hope the patch is correct now, thanks for your feedback! ** Patch added: "1.28.0-1--1.28.0-1ubuntu1.v3.diff" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+attachment/5596531/+files/1.28.0-1--1.28.0-1ubuntu1.v3.diff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Incomplete Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: + Run dh_translations - d/control: + Drop , since the packages are now also available in s390x + Drop >= 1.8 version requirement for network-manager since all supported releases satisfy it * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch -- Nathan Pratta Teodosio Fri, 10 Jun 2022 09:10:05 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1976547] Re: Update gnome-remote-desktop to 42.2
Hello Jeremy, or anyone else affected, Accepted gnome-remote-desktop into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome-remote-desktop/42.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-remote-desktop (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1976547 Title: Update gnome-remote-desktop to 42.2 Status in gnome-remote-desktop package in Ubuntu: Fix Released Status in gnome-remote-desktop source package in Jammy: Fix Committed Bug description: Impact -- This is a new stable release in the GNOME 42 series Test Case #1 Install all updates. Log out and log back in. Open the Settings app to the Sharing page. Turn on Sharing and turn on Remote Desktop Sharing. Turn it off then on because there may be a gnome-control-center bug with initial enabling. From a second computer, connect to the first computer using Remmina. The Remote Desktop page on the first computer provides the username and password to use. I wasn't able to get the "Remote Desktop Address" to work (maybe avahi doesn't work well?) so just use the first computer's IP address. So something like: RDP jeremy@192.168.1.1 Ensure that the connection works. Test Case #2 Do test case #1 but this time also enable the Legacy VNC option on the Remote Desktop Sharing page. Connect using VNC instead and ensure that the connection works. What Could Go Wrong --- RDP Sharing is a new feature for Ubuntu 22.04 LTS as part of GNOME 42. (Previously only VNC Sharing was offered.) RDP Sharing can be used for providing remote support so it's important that this feature works well because it may be difficult for the remote admin to fix issues in person. gnome-remote-desktop is part of GNOME Core and falls under the GNOME Stable Release Update microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1976547/+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 1978128] Re: Add additional workspace switching shortcuts
Thanks for your suggestion. Please note that the page is actually an upstream GNOME Help one, so I would suggest that you also report it as an upstream issue: https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues If you do, please submit the URL to the upstream issue here for tracking purposes. ** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) ** Changed in: gnome-user-docs (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1978128 Title: Add additional workspace switching shortcuts Status in gnome-user-docs package in Ubuntu: New Bug description: I think https://help.ubuntu.com/stable/ubuntu-help/shell-workspaces- switch.html.en would benefit from documentation of additional ways to switch workspaces: - holding the Super/Windows key and scrolling the mouse wheel. This also works to move windows between workspaces by left-clicking the window & holding with the mouse, and then holding the Super key and scrolling the mouse wheel. - scrolling the mouse wheel on the applications icon on the bottom left corner This came out of a public question on Ask Ubuntu: https://askubuntu.com/questions/976372/how-to-switch-workspace-with- mouse-wheel-in-gnome-shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1978128/+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 1977467] Re: Update gvfs to 1.48.2
Hello Jeremy, or anyone else affected, Accepted gvfs into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gvfs/1.48.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gvfs (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1977467 Title: Update gvfs to 1.48.2 Status in gvfs package in Ubuntu: Fix Released Status in gvfs source package in Jammy: Fix Committed Bug description: Impact -- There was a new release in the stable 1.48 series. https://gitlab.gnome.org/GNOME/gvfs/-/blob/1.48.2/NEWS The biggest improvement is greater compatibility with connecting over ssh/sftp https://gitlab.gnome.org/GNOME/gvfs/-/commit/f1b599da1141e Test Case - Install the update Open the Files app. Connect to a variety of Other Locations. - sftp - Google Drive (set up with GNOME Online Accounts) What Could Go Wrong --- gvfs provides mounting services for a variety of protocols: sftp, webdav, etc. And is used in apps like Nautilus or the GTK file chooser If gvfs breaks, you might not be able to access files stored on remote servers via your usual desktop apps. gvfs is part of core GNOME and has a microrelease exception https://wiki.ubuntu.com/StableReleaseUpdates/GNOME To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1977467/+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
** Also affects: evolution (Ubuntu) Importance: Undecided Status: New ** Changed in: evolution (Ubuntu) Status: New => Fix Released ** Changed in: evolution (Ubuntu Jammy) Status: New => Incomplete -- 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 package in Ubuntu: Fix Released Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution source package in Jammy: Incomplete Status in evolution-data-server source package in Jammy: Incomplete 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/+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 1978126] Re: Ctrl+Alt workspace shortcuts are incorrect in docs
*** This bug is a duplicate of bug 1948592 *** https://bugs.launchpad.net/bugs/1948592 ** Package changed: ubuntu-docs (Ubuntu) => gnome-user-docs (Ubuntu) ** This bug has been marked a duplicate of bug 1948592 Switching between workspaces is now Ctrl-Alt-Right or Left, no longer Up or Down -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1978126 Title: Ctrl+Alt workspace shortcuts are incorrect in docs Status in gnome-user-docs package in Ubuntu: New Bug description: In https://help.ubuntu.com/stable/ubuntu-help/shell-workspaces- switch.html.en, the keyboard docs say to use Ctrl+Alt+Up or Ctrl+Alt+Down to switch workspaces. However, that doesn't work on Ubuntu 22.04; you have to use Ctrl+Alt+Left and Ctrl+Alt+Right. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-user-docs/+bug/1978126/+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 1978128] [NEW] Add additional workspace switching shortcuts
You have been subscribed to a public bug: I think https://help.ubuntu.com/stable/ubuntu-help/shell-workspaces- switch.html.en would benefit from documentation of additional ways to switch workspaces: - holding the Super/Windows key and scrolling the mouse wheel. This also works to move windows between workspaces by left-clicking the window & holding with the mouse, and then holding the Super key and scrolling the mouse wheel. - scrolling the mouse wheel on the applications icon on the bottom left corner This came out of a public question on Ask Ubuntu: https://askubuntu.com/questions/976372/how-to-switch-workspace-with- mouse-wheel-in-gnome-shell ** Affects: gnome-user-docs (Ubuntu) Importance: Wishlist Status: New -- Add additional workspace switching shortcuts https://bugs.launchpad.net/bugs/1978128 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. -- 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 1978126] [NEW] Ctrl+Alt workspace shortcuts are incorrect in docs
You have been subscribed to a public bug: In https://help.ubuntu.com/stable/ubuntu-help/shell-workspaces- switch.html.en, the keyboard docs say to use Ctrl+Alt+Up or Ctrl+Alt+Down to switch workspaces. However, that doesn't work on Ubuntu 22.04; you have to use Ctrl+Alt+Left and Ctrl+Alt+Right. ** Affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New -- Ctrl+Alt workspace shortcuts are incorrect in docs https://bugs.launchpad.net/bugs/1978126 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. -- 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 1978331] [NEW] DING shows several errors when no monitor is attached
Public bug reported: Recent version of gnome shell or extension has been emitting large numbers of identical, or quote similar, entries in the system journal, when the monitor is turned off or physically disconnected. The error is: DING: (gjs:10210): Gdk-CRITICAL **: 09:58:45.854: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1978331 Title: DING shows several errors when no monitor is attached Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Recent version of gnome shell or extension has been emitting large numbers of identical, or quote similar, entries in the system journal, when the monitor is turned off or physically disconnected. The error is: DING: (gjs:10210): Gdk-CRITICAL **: 09:58:45.854: gdk_monitor_get_scale_factor: assertion 'GDK_IS_MONITOR (monitor)' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1978331/+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 1978330] [NEW] Extension does odd things when other extension is disabled
Public bug reported: When an extension that was enabled before DING is disabled, the desktop with the icons stops behaving like a desktop, and instead they behave like a transparent window that can be over other windows, be moved by pressing the "Windows" key, and so on. ** Affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Assignee: Sergio Costas (rastersoft-gmail) Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons-ng in Ubuntu. https://bugs.launchpad.net/bugs/1978330 Title: Extension does odd things when other extension is disabled Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: When an extension that was enabled before DING is disabled, the desktop with the icons stops behaving like a desktop, and instead they behave like a transparent window that can be over other windows, be moved by pressing the "Windows" key, and so on. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1978330/+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 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
I came here from 1969351. On a rig with two identical AMD GPUs (First driving one monitor, second driving three), I'll sometimes have the one monitor disconnect, but it won't detect the failure or cause the other three screens to rearrange until I try to apply a change in Display Settings, after which it will show the one monitor as missing. The system will continue operating normally for a minute or two, before crashing back to the login screen Dmesg shows these entries: [127759.552431] gnome-shell[4403]: segfault at 558324328300 ip 558324328300 sp 7ffd66257c98 error 15 [127780.586613] apport-gtk[272085]: segfault at 18 ip 7fa1e6314cf4 sp 7fff77ca9820 error 4 in libgtk-3.so.0.2404.29[7fa1e620c000+383000] [130882.632498] traps: gnome-shell[272824] general protection fault ip:7f3228a412e7 sp:7ffe4c6be868 error:0 in libgbm.so.1.0.0[7f3228a4+8000] [176834.926719] gnome-shell[285277]: segfault at 50100af ip 7f250fbc92e7 sp 7fff283ee988 error 4 in libgbm.so.1.0.0[7f250fbc8000+8000] - Sometimes the system crashes to the login screen during a screen lock without any interaction - Sometimes the system crashes to the login screen when attempting to unlock a locked session - Sometimes after unlock a session shows all the windows rearranged or consolidated into a single workspace as though a monitor was briefly disconnected. Often windows are 'maximized' with a strange offset from a monitor's edge, which is fixed by re-maximizing the window. - Sometimes after unlock everything is fine. I have crash reports for the most recent failure in /var/crash, though I'm not sure how to provide them. _usr_bin_gnome-shell.1000.crash is nearly 70MiB -- 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/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in mutter 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.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+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 1977764] Re: kernel modules "zstd" and "z3fold" missing.
Oh, now I remember why this one was more complicated: it's for the pi *desktop specifically*. Can't add this to ubuntu-raspi-settings directly as that'll pull in zstd, z3fold, and all the zswap stuff on the server images too, which increases the memory burden on the minimal Zero 2 and 3A+ platforms. So (for my own notes): this requires the creation of a new ubuntu-raspi- settings-desktop package (src:ubuntu-settings) and the addition of that package to the desktop-raspi seed in the ubuntu seed repo. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in linux-raspi package in Ubuntu: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: New Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1977764/+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
> As a component of GNOME core, How do I confirm that this is the case? https://wiki.ubuntu.com/StableReleaseUpdates/GNOME points to https://gitlab.gnome.org/GNOME/gnome-build- meta/-/tree/master/elements/core which does not list it. It does not appear in the discourse discussion at https://discourse.ubuntu.com/t/scope-of-gnome-mru/18041/3. I see that there have certainly been microrelease updates of eds in stable Ubuntu releases in the past, but I don't see how it's covered by the current (known-incomplete) microrelease exception. ** Changed in: evolution-data-server (Ubuntu Jammy) Status: In Progress => Incomplete -- 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: Incomplete 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 1978007] Re: Please merge network-manager-applet 1.28.0-1 from Debian unstable
Thanks, it is better, the changelog needs fixing though - d/control: + Drop , since the packages are now also available in s390x + Drop >= 1.8 version requirement for network-manager since all supported releases satisfy it is that really a delta we have over Debian? It sounds rather like a change we got from Debian. You also forgot to list back the patches One extra note, Debian added a recommends on gnome-icon-theme which is in universe in Ubuntu, could you replace it with humanity-icon-theme which also provides the gnome-lockscreen icon which justified the change and is installed by default on Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Incomplete Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: + Run dh_translations - d/control: + Drop , since the packages are now also available in s390x + Drop >= 1.8 version requirement for network-manager since all supported releases satisfy it * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch -- Nathan Pratta Teodosio Fri, 10 Jun 2022 09:10:05 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1978325] [NEW] Color profile applied to only half of a MST display
Public bug reported: I have a Dell UP3214Q monitor, which uses display port multi stream transport, to support the full 4K resolution. After updating from Ubuntu 20.04 to 22.04 the two halves of the monitor suddenly show different colors. After fiddling around for quite a while I realized that the problem goes away, when adding and activating the "Standard Space - sRGB" profile in the Gnome color settings panel. By default it uses the "Automatic - DELL UP3214Q" profile. It seems any selected profile gets applied only to the first of the two display port transport streams, although they both belong to the same display. This took quite a while to figure out, because either removing the "Automatic" profiles or just using the toggle switch in the color settings panel did not disable the color-management for the corresponding display. So there seems to be another bug. I am running on Xorg using the Nvidia 510 drivers, but I saw the same problem, when switching to the Intel drivers. colord: 1.4.6-1 xorg: 1:7.7+23ubuntu2 nvidia-driver-510: 510.73.05-0ubuntu0.22.04.1 ** Affects: colord (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1978325 Title: Color profile applied to only half of a MST display Status in colord package in Ubuntu: New Bug description: I have a Dell UP3214Q monitor, which uses display port multi stream transport, to support the full 4K resolution. After updating from Ubuntu 20.04 to 22.04 the two halves of the monitor suddenly show different colors. After fiddling around for quite a while I realized that the problem goes away, when adding and activating the "Standard Space - sRGB" profile in the Gnome color settings panel. By default it uses the "Automatic - DELL UP3214Q" profile. It seems any selected profile gets applied only to the first of the two display port transport streams, although they both belong to the same display. This took quite a while to figure out, because either removing the "Automatic" profiles or just using the toggle switch in the color settings panel did not disable the color-management for the corresponding display. So there seems to be another bug. I am running on Xorg using the Nvidia 510 drivers, but I saw the same problem, when switching to the Intel drivers. colord: 1.4.6-1 xorg: 1:7.7+23ubuntu2 nvidia-driver-510: 510.73.05-0ubuntu0.22.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1978325/+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 1966562] Re: ubuntu-minimal should not depend on isc-dhcp-client
Thanks for the explanation and pointer to the ML thread, makes sense to me now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1966562 Title: ubuntu-minimal should not depend on isc-dhcp-client Status in ubuntu-meta package in Ubuntu: Invalid Bug description: ubuntu-minimal already depends on `init` which depends on `systemd- sysv` which depends on `systemd` which comes with `systemd-networkd` that has a DHCP client in it. Having the isc-dhcp-client package feels redundant. # Additional information $ lsb_release -rd Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 $ apt-cache policy ubuntu-minimal ubuntu-minimal: Installed: 1.478 Candidate: 1.478 Version table: *** 1.478 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1966562/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
1. Yes, reducing resolution of the external monitor (1440 x 900, to be exact) fixed the issue. 2. I typed that in the terminal and issue persisted. 3. Unfortunately, my laptop doesn't support USB-C DisplayPort (i've tried with my friend's 2K monitor with DisplayPort to USB-C cable and the monitor wasn't receiving any signal), and changing refresh rate to bearable numbers (like 50Hz) didn't help. -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. 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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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/mutter/+bug/1975872/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
Hello Alexander, or anyone else affected, Accepted wpa into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: wpa (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older
** Description changed: + * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server + + * Test case + try to connect to a TLS <= 1.1 access point + + * Regression potential + the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels + + --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html - Workaround are described in #22 and #36 by basically using + Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1958267 Title: wpa can't connect to servers using TLS 1.1 or older Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Jammy: Fix Committed Status in wpa package in Debian: New Bug description: * Impact wpa built with in openssl3 fails to connect to TLS 1.1 or lower server * Test case try to connect to a TLS <= 1.1 access point * Regression potential the patch lowers the security level in some situation for compatibility, it shouldn't prevent connecting to newer hardware, still try to connect to different type of wifi with different security levels --- those uses MD5-SHA1 as digest in its signature algorithm which no longer meets OpenSSL default level of security of 80 bits http://lists.infradead.org/pipermail/hostap/2022-May/040563.html Workaround are described in #22 and #36 by basically using CipherString = DEFAULT@SECLEVEL=0 which lowers the security level --- With the current jammy version of wpasupplicant (2:2.10-1), I cannot connect to the WPA Enterprise network eduroam, which is used by Universities worldwide. I get a "Connection failed" message or a request to re-enter the password. - I've re-tried the credentials: no fix ;-) - Tried a 21.10 live session on the same machine: works fine! - Manually downgraded wpasupplicant to the impish version (2:2.9.0-21build1): connected normally. - Upgraded wpasupplicant to the latest version: fails to connect again. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: wpasupplicant 2:2.10-1 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 09:56:23 2022 InstallationDate: Installed on 2021-11-30 (48 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1977525] Re: [SRU] libreoffice 7.3.4 for jammy
Hello Rico, or anyone else affected, Accepted libreoffice into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.3.4-0ubuntu0.22.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu Jammy) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1977525 Title: [SRU] libreoffice 7.3.4 for jammy Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice source package in Jammy: Fix Committed Bug description: [Impact] * LibreOffice 7.3.4 is in its forth bugfix release of the 7.3 line: https://wiki.documentfoundation.org/ReleasePlan/7.3#7.3.4_release * Version 7.3.3 is currently released in jammy. For a list of fixed bugs compared to 7.3.3 see the list of bugs fixed in the release candidates of 7.3.4 (that's a total of ?? bugs): https://wiki.documentfoundation.org/Releases/7.3.4/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.3.4/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_73/1599/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/amd64/libr/libreoffice/20220603_201544_36a8d@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/arm64/libr/libreoffice/20220603_204754_3736d@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/armhf/libr/libreoffice/20220603_200320_e5429@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/ppc64el/libr/libreoffice/20220603_173801_fcc50@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-libreoffice-libreoffice-prereleases/jammy/s390x/libr/libreoffice/20220603_165906_4db31@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of ?? bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1977525/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1978007] Re: Please merge network-manager-applet 1.28.0-1 from Debian unstable
You were totally clear, I most definitely blundered by comparing the patches with Ubuntu's tree itself, sorry. I'm attaching a new patch, also tested with Pbuilder. ** Patch added: "1.28.0-1--1.28.0-1ubuntu1.v2.diff" https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+attachment/5596420/+files/1.28.0-1--1.28.0-1ubuntu1.v2.diff ** Description changed: This is a proposed merge for network-manager-applet 1.28.0-1. - - I verified that Ubuntu patches were applied and reached Debian, so they - were dropped, but some older modifications remain. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium - * Merge from Debian unstable. Remaining changes: - - Drop all Ubuntu patches. + * Merge with Debian. Remaining changes: + - d/control, d/rules: + + Run dh_translations - d/control: - + Drop , since the packages are now also available in s390x. - + Drop >= 1.8 version requirement for network-manager since all supported - releases satisfy it. - - d/control, d/rules: - + Run dh_translations. + + Drop , since the packages are now also available in s390x + + Drop >= 1.8 version requirement for network-manager since all + supported releases satisfy it + * Drop patches applied upstream: + - git_owe_activation.patch + - gitlab_new_meson.patch - -- Nathan Pratta Teodosio Wed, 08 Jun 2022 16:26:11 -0300 + -- Nathan Pratta Teodosio Fri, 10 Jun 2022 09:10:05 -0300 ==>END<== I tested it with Pbuilder. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1978007 Title: Please merge network-manager-applet 1.28.0-1 from Debian unstable Status in network-manager-applet package in Ubuntu: Incomplete Bug description: This is a proposed merge for network-manager-applet 1.28.0-1. ==> debian/changelog <== network-manager-applet (1.28.0-1ubuntu1) UNRELEASED; urgency=medium * Merge with Debian. Remaining changes: - d/control, d/rules: + Run dh_translations - d/control: + Drop , since the packages are now also available in s390x + Drop >= 1.8 version requirement for network-manager since all supported releases satisfy it * Drop patches applied upstream: - git_owe_activation.patch - gitlab_new_meson.patch -- Nathan Pratta Teodosio Fri, 10 Jun 2022 09:10:05 -0300 ==>END<== I tested it with Pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1978007/+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 1978312] [NEW] No US English Spell Checker in Snap Version of LibreOffice?
Public bug reported: I have been using LO for years now. I recently started using Snap apps in Kubuntu 22.04. I noticed my spell checker no longer works. If I click on TOOLS > SPELLING... in Writer and then click the down arrow on TEXT LANGUAGE, I can see dictionaries for other English locales, but nothing for the United States. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1978312 Title: No US English Spell Checker in Snap Version of LibreOffice? Status in libreoffice package in Ubuntu: New Bug description: I have been using LO for years now. I recently started using Snap apps in Kubuntu 22.04. I noticed my spell checker no longer works. If I click on TOOLS > SPELLING... in Writer and then click the down arrow on TEXT LANGUAGE, I can see dictionaries for other English locales, but nothing for the United States. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1978312/+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 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace
I'm attaching the source code for a sample X client application, for which the problem can be reproduced reliably. The application uses 'globally active' input focus model, just like Java (AWT/Swing) applications, but also waits for 10 milliseconds before reacting to WM_TAKE_FOCUS message. If such an artificial delay isn't performed (just comment out 'usleep' call in the source code), the problem can be reproduced as well, but only with a certain probability. The sample app can be compiled and launched using the following command: gcc twoFrames.c -lX11; ./a.out ** Attachment added: "twoFrames.c" https://bugs.launchpad.net/gnome-shell/+bug/1969574/+attachment/5596400/+files/twoFrames.c -- 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/1969574 Title: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: I have 3 apps open in 1 workspace, When i press window key and i want to select app 2 or 3 with mouse, app 1 shows up! I can only go to app 2 with [window + tab] or [alt + tab] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:05:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-25 (145 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969574/+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 1970148] Re: Brave & Chrome browsers freezes on download and print to pdf
I can support Douglas' statement #17. I installed the fuse package on my fresh Ubuntu 22.04 and it caused the ubuntu-desktop and xdg-desktop-portal packages to be removed. After this, I started getting weird behavior when uploading files on Chrome. I submitted a bug report to the fuse package here: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1978310 Reinstalling the ubuntu-desktop-minimal package solved the issues I was having with Chrome. (I am running the minimal version of Ubuntu). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1970148 Title: Brave & Chrome browsers freezes on download and print to pdf Status in chromium-browser package in Ubuntu: Invalid Bug description: Whenever any file is downloaded, the browser will freeze. Download files, from any page does not work. Same issue with Firefox. Similarly, the browser will freeze when a page is printed to pdf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1970148/+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 1969574] Re: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace
Even though https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1971693 seems to be resolved with the latest update (with mutter 42.1), the use case described in this ticket still doesn't work as expected every time. Here are the steps to reproduce the issue for the attached minimal Java application: 1. sudo apt install default-jre 2. Download attached file TwoFrames.java 3. From a terminal run the app java Downloads/TwoFrames.java 4. Press Super (Window) key on the keyboard and click with mouse on frame 1. Then press Super, and click on frame 2. Repeat several times. At some point, the focus switch will fail, with previously selected frame staying in focus. ** Attachment added: "TwoFrames.java" https://bugs.launchpad.net/gnome-shell/+bug/1969574/+attachment/5596399/+files/TwoFrames.java -- 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/1969574 Title: [Wayland] Can not select JetBrains IntelliJ IDEA windows (including Android Studio) with mouse in workspace Status in GNOME Shell: Unknown Status in mutter package in Ubuntu: Fix Released Bug description: I have 3 apps open in 1 workspace, When i press window key and i want to select app 2 or 3 with mouse, app 1 shows up! I can only go to app 2 with [window + tab] or [alt + tab] ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:05:02 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-11-25 (145 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-16 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1969574/+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 1978295] Re: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
Very limited testing in a focal VM using the package built in my PPA in conjunction with the chromium snap shows that this works. This will require further testing to ensure there are no regressions elsewhere. ** Changed in: xdg-desktop-portal (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: xdg-desktop-portal (Ubuntu Focal) Status: New => In Progress ** Changed in: xdg-desktop-portal (Ubuntu Focal) Importance: Undecided => Medium -- 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/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: In Progress Bug description: This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 1958224] Re: brltty claiming cp210x devices on 22.04
Olivier is right, seems like we had the issue in the past and even SRUed a change back then https://launchpad.net/ubuntu/+source/brltty/4.2-8ubuntu5.1 The change got unfortunately overwritten in the recent merge https://launchpad.net/ubuntu/+source/brltty/6.4-2ubuntu1 while bringing a new version from Debian with some refactoring that made the change less obvious to notice probably -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Fix Released Status in brltty source package in Jammy: Confirmed Status in brltty package in Debian: Confirmed Bug description: * Impact The brltty udev rules are claiming generic devices IDs which makes some other devices like Arduino cards not able to interact with the serial port anymore * Test Case Try to use an Arduino over a cp210x or FTDI serial port, it should be able to talk to the computer * Regression potential There are some braille devices on the market using generic IDs which are going to stop working out of the box. Those devices are uncommon and it's arguably an hardware bugs they are using those IDs. --- Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+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] [NEW] gwenview aborts with a std::out_of_range exception raised in libexiv2
Public bug reported: 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 ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New ** Affects: gwenview (Ubuntu) Importance: Undecided Status: New ** Also affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- 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 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
This happens to when connecting HDMI monitor to the laptop. The laptop's screen doesn't wake up while the external monitor turns on. Unplugging the HDMI cable, makes internal monitor works again. -- 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 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
> I don't know what you mean when said that remote desktop is a recent addition to the desktop... I'll just address this point, but continue the discussion of what should be included in the mandatory testing over on LP: #1978113. What I specifically meant by "recent addition" is that, prior to impish (I'd thought it was jammy, but checked back on the manifests and it was actually impish this occurred), while gnome-remote-desktop was available, it wasn't installed by default. If you look at the project page (https://launchpad.net/ubuntu/+source/gnome-remote-desktop) you'll see that the focal release has "release (universe)" after it, while the impish, jammy, etc. releases have "release (main)". In order for something to be included in the Ubuntu images at release it has to be in the "main pocket" (theoretically at least, there are some minor exceptions to this, mostly firmware related). If something's in the main pocket some team in Canonical has to take responsibility for looking out for its bugs and maintaining the package. If it's in "universe" that's "community support". You can install it, you can file bugs against it, but there's no guarantee anyone's going to look at them. Hence, prior to impish there's no chance gnome-remote-desktop could be in the ISO tracker tests, because it wasn't installed by default and those tests are all about ensuring the functionality of the image (not anything users choose to install after the fact). In other words, I should've been more specific: it's a recent(ish) addition to the Ubuntu image (rather than the Ubuntu repositories), and thus a recent addition to the set of packages we have a commitment to test and fix bugs in. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote
[Desktop-packages] [Bug 1977977] Re: Blanked screen doesn't wake up after locking
** Attachment added: "System log with connected USB mouse" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5596317/+files/kmsdebug2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1977977 Title: Blanked screen doesn't wake up after locking Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 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: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 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/1977977/+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 1977977] Re: Blanked screen doesn't wake up after locking
Connected USB mouse did the trick! I just noticed that I can only wake up the screen if a USB mouse is connected. -- 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/1977977 Title: Blanked screen doesn't wake up after locking Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 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: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 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/1977977/+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 1977977] Re: Blanked screen doesn't wake up after locking
** Attachment added: "System log without connected USB mouse" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1977977/+attachment/5596316/+files/kmsdebug1.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1977977 Title: Blanked screen doesn't wake up after locking Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 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: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 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/1977977/+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 1950828] Re: ibus-daemon crashed with SIGABRT in g_mutex_clear().
** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Marcos Casquero (mcasquero) ** Changed in: ibus (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1950828 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear(). Status in ibus package in Ubuntu: Fix Released Bug description: Bug report generated after logging in. Nothing other then the log in was done. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: ibus 1.5.25-2build1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 12 15:58:02 2021 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2021-10-27 (16 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211025) ProcCmdline: ibus-daemon --panel disable ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: ibus StacktraceTop: g_mutex_clear () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_mutex_clear() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1950828/+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
I'm still not able to trigger that issue :/ -- 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 evince package in Ubuntu: Confirmed 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/evince/+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 1978288] Re: Totem "The specified movie could not be found" for a .mov
** Package changed: gstreamer1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978288 Title: Totem "The specified movie could not be found" for a .mov Status in gstreamer-vaapi package in Ubuntu: New Bug description: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1978288/+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 1978295] Re: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
Given the changes are non-trivial, I'm building them in a PPA to test properly before uploading to the archive: https://launchpad.net/~osomon/+archive/ubuntu/bionic-xdp-fixes. -- 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/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: New Bug description: This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 1970013] Re: Totem Video player displays distorted video (Intel Ivy Bridge)
** Bug watch added: gitlab.gnome.org/GNOME/totem/-/issues #519 https://gitlab.gnome.org/GNOME/totem/-/issues/519 ** Also affects: totem via https://gitlab.gnome.org/GNOME/totem/-/issues/519 Importance: Unknown Status: Unknown ** Also affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Confirmed ** Changed in: totem (Ubuntu) Status: Incomplete => Confirmed ** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer/-/issues #1176 https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1176 ** Also affects: gstreamer1.0 via https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1176 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1970013 Title: Totem Video player displays distorted video (Intel Ivy Bridge) Status in Gstreamer1.0: Unknown Status in Totem: Unknown Status in gstreamer1.0 package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Ubuntu 22.04 freshly installed along with ubuntu-restricted-extra package. Default totem player unable to play videos properly. videos looks distorted. Forwarding videos does not work. Video get stopped once forwarded. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 23 11:02:49 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f9] InstallationDate: Installed on 2022-04-22 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 34601F4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=be040347-6300-407e-9e19-da58389c3a6f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2013 dmi.bios.release: 2.59 dmi.bios.vendor: LENOVO dmi.bios.version: G6ET99WW (2.59 ) dmi.board.asset.tag: Not Available dmi.board.name: 34601F4 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrG6ET99WW(2.59):bd11/19/2013:br2.59:efr1.4:svnLENOVO:pn34601F4:pvrThinkPadX1Carbon:rvnLENOVO:rn34601F4:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_3460: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 34601F4 dmi.product.sku: LENOVO_MT_3460 dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO 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/gstreamer1.0/+bug/1970013/+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 1975872] Re: [ASUS GL552VW] Loss of signal (black screen) on external monitor
See also bug 1929209 -- 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/1975872 Title: [ASUS GL552VW] Loss of signal (black screen) on external monitor Status in mutter package in Ubuntu: Incomplete Bug description: External screen flickers on and off (image is present and then signal is lost, flickering is random, but very often, ~3 times in 10 seconds) on a fresh installation. Details: - I'm using a laptop (ASUS GL552VW) with external monitor connected via HDMI. The HDMI port is connected to my iGPU, Intel HD 530 (there is no way to make that HDMI work with NVIDIA GTX 960M in my laptop). - Nothing was installed after installing the OS - i connected to the Internet while installing the system and marked the option to download the updates. - I had that issue on Windows 10 - I fixed it by installing a latest Intel GPU driver from laptop manufacturer's (ASUS) site, uninstalling drivers installed by Windows - they were the latest Intel drivers. - Internal screen works fine. - If I mirror external and internal monitor, external isn't flickering, but internal monitor's resolution is lower that external's one. 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 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu May 26 22:34:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1c5d] Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1c5d] InstallationDate: Installed on 2022-05-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: ASUSTeK COMPUTER INC. GL552VW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic root=UUID=be9d6e78-64ad-42f3-883b-15903e52b776 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL552VW.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL552VW dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL552VW.304:bd04/25/2019:br5.11:svnASUSTeKCOMPUTERINC.:pnGL552VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL552VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: GL dmi.product.name: GL552VW dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. 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/mutter/+bug/1975872/+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 1962630] Re: Video playback crashes with SIGSEGV in KernelDll_AllocateStates (intel-media-driver)
** No longer affects: totem (Ubuntu Jammy) ** No longer affects: totem (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1962630 Title: Video playback crashes with SIGSEGV in KernelDll_AllocateStates (intel-media-driver) Status in Libva: New Status in intel-media-driver package in Ubuntu: Triaged Status in intel-media-driver source package in Jammy: Triaged Bug description: https://errors.ubuntu.com/problem/a09f9aa6132a1f12a9e44103be3ca0a859abfa2d --- ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: libgstreamer1.0-0 1.20.0-1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Feb 27 15:56:18 2022 ExecutablePath: /usr/bin/totem InstallationDate: Installed on 2018-12-10 (1177 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/bin/totem --gapplication-service SegvAnalysis: Segfault happened at: 0x7fd4c2239ccf:cmpl $0x1,(%rbx) PC (0x7fd4c2239ccf) ok source "$0x1" ok destination "(%rbx)" (0x7fd57824ec90) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: gstreamer1.0 StacktraceTop: () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so () at /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so Title: totem crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1962630/+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 1978153] Re: Video plays back as grayscale and compressed on left
Sounds like you're the lucky one because other people aren't getting as far with gstreamer1.0-vaapi installed (bug 1962630). ** Package changed: gst-plugins-base1.0 (Ubuntu) => gstreamer-vaapi (Ubuntu) ** No longer affects: totem (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gstreamer-vaapi package in Ubuntu: New Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1978153/+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
Thank you for your bug report. Could you provide more detailed steps of how to trigger the issue and the impact which we could as a testcase to do a stable update? ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Incomplete -- 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: Incomplete Bug description: 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. 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 1977977] Re: Blanked screen doesn't wake up after locking
Did you forget the "Wait 10 seconds" step maybe? See comment #3. -- 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/1977977 Title: Blanked screen doesn't wake up after locking Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 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: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 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/1977977/+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 1977977] Re: Blanked screen doesn't wake up after locking
When a monitor turns off you will get a log message that contains: property 'ACTIVE' (22) to 0 which is not mentioned in the log of comment #17. So indeed that log is not from a time when the monitor was turned off via software. -- 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/1977977 Title: Blanked screen doesn't wake up after locking Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 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: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 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/1977977/+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 1978295] Re: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
The following commits are required: https://github.com/flatpak/xdg-desktop-portal/commit/32da40b465ada3f616efbecd508d193402b15a4f https://github.com/flatpak/xdg-desktop-portal/commit/9c81f444a2f38932c428c184fc1520015c527384 https://github.com/flatpak/xdg-desktop-portal/commit/8f3ab6091ab45cd67b555f6f17421eb6029c3c11 The second one (9c81f444a2f38932c428c184fc1520015c527384) applies with fuzz 2, so it needs refreshing. -- 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/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: New Bug description: This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 1977977] Re: Blanked screen doesn't wake up after locking
Either the log in comment #17 is not from when the screen was blank/black/off, or it was and the monitor/driver is faulty. Because the kernel seems to be reporting that the screen is successfully displaying new frames. If it's doing that but you can't see an image then it's a problem in the kernel or in the monitor itself. I think it's more likely that the log in comment #17 is just not from a time when the screen was blank. -- 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/1977977 Title: Blanked screen doesn't wake up after locking Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 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: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 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/1977977/+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
If someone does not want to disable apparmor for evince, then he can install the package "devilspie2" and use a lua configuration file to set the window size (see the manual of the program): if (get_window_class()=="Evince") then set_window_size(800,600) end But this is not optimal and not suitable for everyone. As a user that opens very frequently pdf files this bug is highly irritating and makes the ubuntu desktop experience very poor. Can someone raise the importance of this bug? -- 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 evince package in Ubuntu: Confirmed 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/evince/+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 1978295] Re: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
The upstream commit doesn't apply cleanly to version 1.6.0 that's in focal. -- 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/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: New Bug description: This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 1170217] Re: Path entry of desktop file not work when autostart
** Changed in: gnome-session (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1170217 Title: Path entry of desktop file not work when autostart Status in gnome-session package in Ubuntu: Incomplete Bug description: #precise #Ubuntu12.04.2 LTS This is about .desktop file in ~/.config/autostart In "[Desktop Entry]" section, "Path" is shouled to the workdir. Double click the .desktop file, it can run ok. But when it autostart after login, the workdir is not set to the "Path" value, still be ~ . The same .desktop file can work well in mint14. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1170217/+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 1887195] Re: [snap] "Show in folder" for downloaded files doesn't work
The implementation of OpenDirectory was fixed in xdg-desktop-portal 1.10.0 to correctly highlight the selected file. I filed bug #1978295 to proposed SRUing that specific patch to 20.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1887195 Title: [snap] "Show in folder" for downloaded files doesn't work Status in snapd: Invalid Status in chromium-browser package in Ubuntu: Fix Released Bug description: In the chromium snap (Version 83.0.4103.116 on focal at the moment), after downloading files, navigating to the downloaded file doesn't work. Clicking on "Show in folder" only opens nautilus, but doesn't actually highlight the file. This works as expected on chrome and older deb builds in bionic, for example. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1887195/+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 1978295] [NEW] org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file
Public bug reported: This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). ** Affects: xdg-desktop-portal (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: xdg-desktop-portal (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: xdg-desktop-portal (Ubuntu) Status: New => Fix Released ** Also affects: xdg-desktop-portal (Ubuntu Focal) 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/1978295 Title: org.freedesktop.portal.OpenURI.OpenDirectory doesn't highlight the selected file Status in xdg-desktop-portal package in Ubuntu: Fix Released Status in xdg-desktop-portal source package in Focal: New Bug description: This is an upstream issue (https://github.com/flatpak/xdg-desktop- portal/issues/564) that was fixed in xdg-desktop-portal 1.10.0. I'm proposing to SRU the corresponding patch to focal. This will be especially useful for browsers packaged as snaps (see bug #1887195 for chromium, and https://bugzilla.mozilla.org/show_bug.cgi?id=1772063 for firefox). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1978295/+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 70585] Re: doesn't recognise "~/" shortcut for /home/user/
** Changed in: gnome-session (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/70585 Title: doesn't recognise "~/" shortcut for /home/user/ Status in gnome-control-center: Invalid Status in gnome-session: Expired Status in gnome-session package in Ubuntu: Opinion Bug description: I installed the MoinMoin wiki (Desktop Edition) for my personal use. It is written in python, and in the terminal, the command to run it is: python ~/moin-desktop/moin.py However, when entered into the "Additional startup programs", this doesn't work. It does work when rewritten as: python /home/user/moin-desktop/moin.py To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/70585/+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 1978153] Re: Video plays back as grayscale and compressed on left
removing gstreamer1.0-vaapi solves also the problem https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978288 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1978153] Re: Video plays back as grayscale and compressed on left
after removing gstreamer1.0-vaapi the problem DISAPPEAR -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1978288] Re: Totem "The specified movie could not be found" for a .mov
after removing gstreamer1.0-vaapi the problem DISAPPEAR see https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1978153 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978288 Title: Totem "The specified movie could not be found" for a .mov Status in gstreamer1.0 package in Ubuntu: New Bug description: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978288/+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 1978153] Re: Video plays back as grayscale and compressed on left
with gst-play-1.0 --videosink="glsinkbin sink=gtkglsink" ... i have the same problem ** Attachment added: "Screenshot from 2022-06-10 09-57-17.png" https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1978153/+attachment/5596283/+files/Screenshot%20from%202022-06-10%2009-57-17.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1977977] Re: Blanked screen doesn't wake up after locking
The screen remained blank. II want to clarify that "blank screen" doesn't just mean that it's black, but also powered off. On X11 I found a workaround by disabling DPMS (in this case, "blank screen" means it's just black, not powered off). -- 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/1977977 Title: Blanked screen doesn't wake up after locking Status in gnome-shell package in Ubuntu: Incomplete Bug description: After I lock my screen and let it blank, moving the mouse or pressing any key on the keyboard won't wake it up. Pressing Ctrl+Alt+F1 doesn't help. That's on a fully up-to-date Ubuntu 22.04 (GNOME 42.1, Wayland). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 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: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jun 8 16:30:14 2022 InstallationDate: Installed on 2022-06-08 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 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/1977977/+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 1978268] Re: Internal monitor doesn't wake up if there is external monitor
*** This bug is a duplicate of bug 1968040 *** https://bugs.launchpad.net/bugs/1968040 Number of monitors is not really relevant. What is relevant is that you have a GPU (Intel) using atomic KMS and reporting: [67521.542529] zb gnome-shell[2826]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument [67521.542585] zb gnome-shell[2826]: Page flip discarded: drmModeAtomicCommit: Invalid argument [67521.543357] zb gnome-shell[2826]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument [67521.551378] zb gnome-shell[2826]: Page flip discarded: drmModeAtomicCommit: Invalid argument [67521.560697] zb gnome-shell[2826]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument [67521.560825] zb gnome-shell[2826]: Page flip discarded: 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/1978268 Title: Internal monitor doesn't wake up if there is external monitor Status in gnome-shell package in Ubuntu: New Bug description: Sometime when unlocking the session and there is external monitor connected, the internal monitor doesn't turn on, only the external one. Unplugging the external monitor solves the issue. 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: pass Date: Fri Jun 10 07:43:04 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (126 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978268/+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 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel
k, let's try to keep pushing for 1.18 first ** Changed in: modemmanager (Ubuntu) Importance: Undecided => Low ** Changed in: modemmanager (Ubuntu) Status: New => Fix Released -- 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/1978057 Title: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel Status in modemmanager package in Ubuntu: Fix Released Bug description: [Impact] On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly. With the new rules, the modem devices could be recognized correctly. And also could avoid wrong command for other protocols, like send 'AT' to wwan0mbim. [Where problems could occur] It's just a udev rules, no harm to the system. [Fix] https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8 udev: Match WWAN "type" attribute instead of device name Recent changes in the WWAN framework in the kernel changed the WWAN port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and "wwan0qmi0" [1, 2]. This means that the udev rules no longer match since AT/QMI are now lower-case and no longer at the end of the name. However, recently additionally a "type" sysfs attribute was added for all WWAN ports [3], which makes it much more reliable to match the WWAN port names without relying on their exact device name. Add some additional udev rules to apply the port hints based on the "type" sysfs attributes. This fixes the port enumeration on newer Linux kernels that include the aforementioned commits. Note that we still need to keep the old udev rules for now since Linux 5.13 does not have the "type" attribute yet. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f [2]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde [3]: https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c (cherry picked from commit 4282c8d8) [Test] With new rule, like Fibcomm L860 (8086:7560) could be recognized and show 'Mobile Broadband' item in the top-right menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+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 1978153] Re: Video plays back as grayscale and compressed on left
Do you get the issue if you do $ gst-play-1.0 --videosink="glsinkbin sink=gtkglsink" video.webm (where video.webm is the filename of what you try to play) Does uninstalling gstreamer1.0-vaapi fixes the issue? ** Changed in: totem (Ubuntu) Importance: Undecided => Low ** Changed in: totem (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978153 Title: Video plays back as grayscale and compressed on left Status in gst-plugins-base1.0 package in Ubuntu: New Status in totem package in Ubuntu: Incomplete Bug description: press 'printscreen' the window for screenshot/screencast open, start screencast the video produced is gray and compressed on the left part of the screen. see attachment 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: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jun 9 20:59:20 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base1.0/+bug/1978153/+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 1978288] [NEW] Totem "The specified movie could not be found" for a .mov
Public bug reported: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1978288 Title: Totem "The specified movie could not be found" for a .mov Status in gstreamer1.0 package in Ubuntu: New Bug description: trying to play a .mov video with totem i have the message "The specified movie could not be found" corrado@corrado-n3-kk-0601:~$ cd Videos corrado@corrado-n3-kk-0601:~/Videos$ ls 2020_1230_112749_002.MOV Screencasts Webcam corrado@corrado-n3-kk-0601:~/Videos$ totem 2020_1230_112749_002.MOV (totem:5685): GStreamer-CRITICAL **: 09:10:35.265: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.332: gst_buffer_get_meta: assertion 'buffer != NULL' failed (totem:5685): GStreamer-CRITICAL **: 09:10:35.360: gst_buffer_get_meta: assertion 'buffer != NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: libgstreamer1.0-0 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jun 10 09:19:14 2022 InstallationDate: Installed on 2022-06-01 (8 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220531) SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1978288/+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 1978268] Re: Internal monitor doesn't wake up if there is external monitor
*** This bug is a duplicate of bug 1968040 *** https://bugs.launchpad.net/bugs/1968040 Daniel, the other bug is about single monitor, but here I'm talking about multiple monitors. If you think it's the same issue, that's fine. -- 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/1978268 Title: Internal monitor doesn't wake up if there is external monitor Status in gnome-shell package in Ubuntu: New Bug description: Sometime when unlocking the session and there is external monitor connected, the internal monitor doesn't turn on, only the external one. Unplugging the external monitor solves the issue. 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: pass Date: Fri Jun 10 07:43:04 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (126 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978268/+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 1767668] Re: GNOME Shell stuck at lock screen for a long time when undocked
** Tags added: bionic -- 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/1767668 Title: GNOME Shell stuck at lock screen for a long time when undocked Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce on my Thinkpad X270 1. Start with laptop docked with internal and external screen in use 2. Lock machine (and potentially wait for blank screen to kick in - need to test) 3. Undock 4. Hit a key to wake screen up 5. Notice that the lock screen doesn't scroll up immediately 6. Wait for a couple of minutes until lock screen clears and you can type your password again 7. Notice that even though you can now use the desktop, you can switch to tty3, 4, etc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767668/+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 1978268] Re: Internal monitor doesn't wake up if there is external monitor
*** 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/1978268 Title: Internal monitor doesn't wake up if there is external monitor Status in gnome-shell package in Ubuntu: New Bug description: Sometime when unlocking the session and there is external monitor connected, the internal monitor doesn't turn on, only the external one. Unplugging the external monitor solves the issue. 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: pass Date: Fri Jun 10 07:43:04 2022 DisplayManager: gdm3 GsettingsChanges: InstallationDate: Installed on 2022-02-03 (126 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-21 (49 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978268/+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 1767668] Re: GNOME Shell stuck at lock screen for a long time when undocked
I experience that behavior as well while I have no mounted filesystem over the network. -- 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/1767668 Title: GNOME Shell stuck at lock screen for a long time when undocked Status in gnome-shell package in Ubuntu: Confirmed Bug description: Steps to reproduce on my Thinkpad X270 1. Start with laptop docked with internal and external screen in use 2. Lock machine (and potentially wait for blank screen to kick in - need to test) 3. Undock 4. Hit a key to wake screen up 5. Notice that the lock screen doesn't scroll up immediately 6. Wait for a couple of minutes until lock screen clears and you can type your password again 7. Notice that even though you can now use the desktop, you can switch to tty3, 4, etc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767668/+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
