[Desktop-packages] [Bug 1983717] Re: Monitor layout hotkey does not show single display options
** Tags added: super-p ** Tags added: multimonitor -- 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/1983717 Title: Monitor layout hotkey does not show single display options Status in gnome-shell package in Ubuntu: New Bug description: 0) More detailed description: The default hotkey to switch which monitor to display the desktop on (Super+P) only shows two options: Mirror and Join Displays. There is no option "External Only" or "Built-in Only". This computer is configured with an AMD graphics card plugged into two external monitors, running Ubuntu 22.04 in the Wayland session. 1) lsb_release -rd Description: Ubuntu 22.04.1 LTS Release: 22.04 2) apt-cache policy gnome-shell gnome-shell: Installed: 42.2-0ubuntu0.2 Candidate: 42.2-0ubuntu0.2 Version table: *** 42.2-0ubuntu0.2 500 500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-2ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3) Expected to happen: Meta+P hotkey showing all four possibilities for display configurations (Mirror, Join Displays, External Only, Built-in Only). 4) What happened instead: Only two options appear on screen while pressing Meta+P: "Mirror" and "Join Displays". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Aug 5 09:17:19 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-05-01 (95 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1983717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
** Tags added: super-p ** Tags added: multimonitor -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1878953] Re: Display settings is lost when switching between modes with Super+P
** Tags added: super-p -- 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/1878953 Title: Display settings is lost when switching between modes with Super+P Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When switching between modes (built-in only, joint, ...) with Super+P, the display settings are lost. That even occurs when selecting already selected mode (selecting "joint" while being in "joint" mode). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .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 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 18:12:11 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-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-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1878953/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Tested with Upstream ModemManager, libmbim and libqmi. The WWAN function can be turned on through gnome-control-center, and 5G function works correctly. The upstream version get with "git rev-parse --short HEAD" listed as below: ModemManager: eebdbc45 libmbim: add668b libqmi: fa6c7a97 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] Re: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
** Tags added: oem-priority originate-from-1981417 somerville -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1984147/+attachment/5607596/+files/ProcEnviron.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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1984147/+attachment/5607597/+files/ShellJournal.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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1984147/+attachment/5607598/+files/monitors.xml.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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1984147/+attachment/5607595/+files/ProcCpuinfoMinimal.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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1984147/+attachment/5607594/+files/GsettingsChanges.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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1984147/+attachment/5607593/+files/Dependencies.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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984147] [NEW] Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland
Public bug reported: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy oem-priority originate-from-1981417 somerville wayland-session ** Tags added: apport-collected jammy wayland-session ** Description changed: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-08-10 (0 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + Package: gnome-shell 42.0-2ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 + RelatedPackageVersions: mutter-common 42.0-3ubuntu2 + Tags: jammy wayland-session + Uname: Linux 5.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- 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/1984147 Title: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on Wayland Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Monitor switcher popup (Super-P) is not displayed on desktop with joined display on GNOME 3 in Wayland mode [Reproduce Steps] 1. Use a desktop PC and start GNOME 3 in Wayland mode (therefore using NVIDIA GPU does not trigger the bug) 2. Connect the PC with 2 monitors 3. Use Super-P to switch to joined display (note that using Displays from Settings does not trigger the issue) 4. Use Super-P to switch display mode again [Expected Result] Display Switcher popup should appear [Actual Result] Display Switcher does not popup, but tapping Super-P 3 times can still switch back to Mirror mode [Version] gnome-shell42.2-0ubuntu0.2 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-10 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Package: gnome-shell 42.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to:
[Desktop-packages] [Bug 1170217] Re: Path entry of desktop file not work when autostart
[Expired for gnome-session (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Expired -- 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: Expired 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 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
** Also affects: libmbim Importance: Undecided Status: New ** No longer affects: libmbim ** Also affects: libmbim Importance: Undecided Status: New ** Project changed: libmbim => libmbim (Ubuntu) ** Also affects: libqmi Importance: Undecided Status: New ** Project changed: libqmi => libqmi (Ubuntu) -- 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/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983010]
I am able to reproduce the messages by hovering over various programme titles in Netflix and then refreshing the page. I get: libva info: va_openDriver() returns 0 Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_14 ATTENTION: default value of option mesa_glthread overridden by environment. libva info: va_openDriver() returns 0 username@hostname:~$ libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so libva info: Found init function __vaDriverInit_1_14 ATTENTION: default value of option mesa_glthread overridden by environment. libva info: va_openDriver() returns 0 Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu libva info: VA-API version 1.14.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983010 Title: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: I use Firefox Beta and launch it from the terminal. While watching Netflix on Firefox, I get the following messages on my terminal: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index2/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/cpu0/cache/index3/size Sandbox: attempt to open unexpected file /sys/devices/system/cpu/present Sandbox: attempt to open unexpected file /sys/devices/system/cpu Sandbox: Unexpected EOF, op 0 flags 00 path /proc/cpuinfo ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox (not installed) ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Thu Jul 28 15:01:35 2022 InstallationDate: Installed on 2022-06-21 (36 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1983010/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
** Tags added: oem-priority originate-from-1962525 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Status: New => Confirmed -- 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/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984067] Re: Xorg crash
Thanks for the bug report. I think we need proper debug symbols to get a more accurate stack trace. So please just follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1984067 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
[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(
** Tags added: dt-458 -- 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: Confirmed 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 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
** Tags added: oem-priority originate-from-1962525 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center source package in Jammy: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983748] Re: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurü
Guten tag, mein Deutsch ist sehr slecht, aber ich hoffe gut genug.. Ich glaube, sie mussen: sudo snap install firefox wenn dass schoen ist: sudo dpkg --configure -a sudo apt install -f Bitte schreiben sie schon wieder, falls es nicht genug. Danke ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1983748 Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: »neues firefox-Skript des Paketes pre- installation«-Unterprozess gab den Fehlerwert 1 zurück Status in firefox package in Ubuntu: New Bug description: ICh verstehe kein Englich und komme mit den Fehlerberichten nicht zurecht, da ich nicht weis was ich machen soll oder machen muss ProblemType: Package DistroRelease: Ubuntu 22.04 Package: firefox 103.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-122.138-generic 5.4.192 Uname: Linux 5.4.0-122-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ingo 21810 F pulseaudio BuildID: 20220718155818 CasperMD5CheckResult: unknown Channel: Unavailable Date: Sat Aug 6 11:39:59 2022 ErrorMessage: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück ForcedLayersAccel: False InstallationDate: Installed on 2022-08-06 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.0.1 dev enp1s0 proto dhcp metric 100 default via 192.168.86.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev enp1s0 scope link metric 1000 192.168.0.0/24 dev enp1s0 proto kernel scope link src 192.168.0.42 metric 100 192.168.86.0/24 dev wlp2s0 proto kernel scope link src 192.168.86.88 metric 600 NoProfiles: True PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 3.10.4-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.6 RunningIncompatibleAddons: False SourcePackage: firefox Title: package firefox 103.0+build1-0ubuntu0.20.04.1 failed to install/upgrade: »neues firefox-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X541NA.321 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X541NA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX541NA.321:bd08/24/2018:svnASUSTeKCOMPUTERINC.:pnX541NA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX541NA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: X541NA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1983748/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 27867]
Redirect a needinfo that is pending on an inactive user to the triage owner. :jaws, since the bug has recent activity, could you have a look please? For more information, please visit [auto_nag documentation](https://wiki.mozilla.org/Release_Management/autonag#inactive_ni_pending.py). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 27867]
You can find the option here: https://bugs.edge.launchpad.net/firefox/+bug/27867 Thanks george grace https://www.workebook.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 27867]
I am Ameliaroy , working for techandbusinessnews as PR consultant. With more than 6 years experience in PR and Digital Industry, helping teams to achieve goals by streamilining the process. https://www.techandbusinessnews.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 27867]
you can find the data related to this @ https://www.marketingbusinessweb.com/digital-technology-of-the-future @johnwelster www.marketingbusinessweb.com -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 27867]
Cloud verbal exchange is now not a telephone line clients use to reach you, thanks to the latest updates and advancements. As a result, it's far now a essential aspect of emblem constructing that can quick install the necessary resources and manipulate the entire brand conversation device. Read More:- https://www.primewebreviews.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 27867]
The skin absorbs approximately 60% of whatever implemented to it. However, the pores and skin is a protective barrier that prevents dangerous compounds from getting into the frame. Interestingly, topical non-public care products can reach frame systems, inflicting untold health outcomes. Read More:- https://www.gethealthandbeauty.com/ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/27867 Title: Background color is always white, top banner is never displayed in Firefox Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Fix Released Bug description: Problem shows whatever the version of Epiphany (before and after today's upodate ie). Whatever the website I visit, the background colour is always white, and the logo/banner at the top of the page, is not displayed. I attached an example, showing Ubuntu bugzilla. No Ubuntu logo at the top, and no yellow background. http://bugzilla.gnome.org/show_bug.cgi?id=121118: http://bugzilla.gnome.org/show_bug.cgi?id=121118 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/27867/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959747]
More interesting, is can anyone reproduce this when using version 102? from https://www.thunderbird.net/ Webrender is much improved in version 102 for Windows. Perhaps it is also better for Linux. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1959747 Title: [upstream] Very high CPU and slow responsiveness in Thunderbird 91 Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Very high CPU and slow responsiveness in Thunderbird 91.5.0. Just moving the mouse cursor over a message list results in 365% CPU for me. I had to set this in the config editor to fix it: gfx.webrender.force-disabled = TRUE Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1730423 To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1959747/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 711305]
I have this problem in Ubuntu 22.04.1 LTS with Thunderbird 91.11.0 and am shocked to see that this bug has persisted for 12 years. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/711305 Title: Thunderbird is already running, but is not responding. To open a new window, you must first close the existing Thunderbird process, or restart your system. Error received when clicking a mailto link in firefox. Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Triaged Bug description: Binary package hint: thunderbird This thunderbird error is given when clicking a mailto link. Instead of using the thunderbird that's already open it tries to open a new instance. Preferred Applications has Thunderbird select, but I have also tried Custom command "thunderbird %s". This has been tested on 10.04 and 10.10. Both result in this error if thunderbird is already running. Thunderbird is already running, but is not responding. To open a new window, you must first close the existing Thunderbird process, or restart your system. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: thunderbird 3.1.7+build3+nobinonly-0ubuntu0.10.10.1 ProcVersionSignature: Ubuntu 2.6.35-25.44-generic 2.6.35.10 Uname: Linux 2.6.35-25-generic i686 Architecture: i386 Date: Tue Feb 1 10:19:09 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcEnviron: LANG=en_CA.utf8 SHELL=/bin/bash SourcePackage: thunderbird To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/711305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1877038]
Greeting, any progress on this bug? If you have a branch, I can help review and collaborate on the feature. Please provide the blockers and estimated completion date. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877038 Title: [upstream] Firefox lacks FIDO2 support with Yubikeys Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu LTS versions affected. "Passwordless" authentications with Yubikeys using Firefox don't work with FIDO2. Tested both with the yubikey software packages from the bionic/universe repo and those from the vendor https://www.yubico.com/ To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1877038/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984132] [NEW] chromium-browser snap for armv7 does not read from .config/chromium-flags.conf
Public bug reported: Running Ubuntu 22.04 LTS and the chromium-browser snap on ARMv7 version 104.0.5112.79. Added --ozone-platform-hint=auto to .config/chromium-flags.conf Start the chromium browser and it expects X11 components. Manually starting chromium-browser with --ozone-platform=wayland works. On ARMv8/arm64 this works fine. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: wayland -- 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/1984132 Title: chromium-browser snap for armv7 does not read from .config/chromium- flags.conf Status in chromium-browser package in Ubuntu: New Bug description: Running Ubuntu 22.04 LTS and the chromium-browser snap on ARMv7 version 104.0.5112.79. Added --ozone-platform-hint=auto to .config/chromium-flags.conf Start the chromium browser and it expects X11 components. Manually starting chromium-browser with --ozone-platform=wayland works. On ARMv8/arm64 this works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1984132/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977769] Re: Customize default content translucency color to Ubuntu's color scheme
** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/ubuntu/yaru/issues #3666 https://github.com/ubuntu/yaru/issues/3666 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3666 Importance: Unknown Status: Unknown ** Changed in: gnome-console (Ubuntu) Status: In Progress => Fix Committed ** Changed in: yaru-theme (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1977769 Title: Customize default content translucency color to Ubuntu's color scheme Status in Yaru Theme: Unknown Status in gnome-console package in Ubuntu: Fix Committed Status in yaru-theme package in Ubuntu: Triaged Bug description: It was requested in LP: #1973828 that GNOME Console be patched to use Ubuntu's color hinting for the translucent content background color, since Ubuntu's GNOME Terminal had this feature. As a stretch goal, maybe it could use the Yaru color style instead of just purple. To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1977769/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
** Package changed: tracker (Ubuntu) => tracker-miners (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 Status in tracker-miners package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. However, the crash occurs because of a unhandled SIGSYS, meaning a seccomp filter issue. I've tried backporting this patch fixing a similar issue: https://gitlab.gnome.org/GNOME/tracker- miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef but it doesn't apply, likely due to the code having diverged too much since. My proposal is thus to disable tracker-extract during upgrade, including in all user sessions. I'm assuming that the new version will be enabled automatically as its unit file changed name anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker-miners/+bug/1983859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984107] [NEW] Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed"
Public bug reported: If a printer preferrably prints through ipps, Cups will store the printers (self signed) certificate in /etc/cups/ssl/ However, if this certificate becomes outdated or invalid, or if it changes, it will *not be removed* and Cups only complains that the "backend returned status 4", "No suitable destination host found by cups-browsed". Even removing the printer manually will not remove the old certificate, rendering the printer invalid for life: when te printer re-appears, the old, invalid certificate is still there, resulting in the printer still not working. Steps to reproduce: - use a printer that prefers ipps, let's call it printer_bob - let this printer appear in your printer list - make a test print - Now remove the printer and check that the certificate will survive: lpadmin -x printer_bob; ls -al /etc/cups/ssl/*bob*crt What happens: - certificate is still there What should happen: - a removed printer should not have a certificate left Now in this example, it's rather harmless because the certificate is probably still valid. But a printer update, rename or otherwise will render it invalid and printing will become impossible. You could simulate a name change for printers: mv /etc/cups/ssl/printer-carol.local.crt /etc/cups/ssl/printer-bob.local.crt Or simply mess up the certificate: sed -i '2s/./a/g' /etc/cups/ssl/printer-bob.local.crt After this, you will *not* be able to print to printer-bob, because bob has the wrong certificate (obviously). Removing printer-bob does not help. You will need to manually remove the certificate in order to make bob print again. /var/log/cups/error.log will only say that "no suitable destination host found", which is not true: there *is* a destination but the SSL certificate does not match and Cups will only try the first printing method, ipps. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Printer SSL certificates are added but never removed, resulting in non working printers + Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1984107 Title: Printer SSL certificates are added but never removed, resulting in "no suitable destination host found by cups-browsed" Status in cups package in Ubuntu: New Bug description: If a printer preferrably prints through ipps, Cups will store the printers (self signed) certificate in /etc/cups/ssl/ However, if this certificate becomes outdated or invalid, or if it changes, it will *not be removed* and Cups only complains that the "backend returned status 4", "No suitable destination host found by cups-browsed". Even removing the printer manually will not remove the old certificate, rendering the printer invalid for life: when te printer re-appears, the old, invalid certificate is still there, resulting in the printer still not working. Steps to reproduce: - use a printer that prefers ipps, let's call it printer_bob - let this printer appear in your printer list - make a test print - Now remove the printer and check that the certificate will survive: lpadmin -x printer_bob; ls -al /etc/cups/ssl/*bob*crt What happens: - certificate is still there What should happen: - a removed printer should not have a certificate left Now in this example, it's rather harmless because the certificate is probably still valid. But a printer update, rename or otherwise will render it invalid and printing will become impossible. You could simulate a name change for printers: mv /etc/cups/ssl/printer-carol.local.crt /etc/cups/ssl/printer-bob.local.crt Or simply mess up the certificate: sed -i '2s/./a/g' /etc/cups/ssl/printer-bob.local.crt After this, you will *not* be able to print to printer-bob, because bob has the wrong certificate (obviously). Removing printer-bob does not help. You will need to manually remove the certificate in order to make bob print again. /var/log/cups/error.log will only say that "no suitable destination host found", which is not true: there *is* a destination but the SSL certificate does not match and Cups will only try the first printing method, ipps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1984107/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984106] [NEW] "Position of new icons" can't work
Public bug reported: Our OEM vendor reported this issue. [Steps to reproduce] 1.Install Ubuntu 22.04 2.Enter OS 3.Click Settings->Appearance->Position of new icons [Expected result] Choose different position,folder will follow the command [Actual result] Choose different position,it is unchanged. [Failure rate] 100% ** 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/1984106 Title: "Position of new icons" can't work Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: New Bug description: Our OEM vendor reported this issue. [Steps to reproduce] 1.Install Ubuntu 22.04 2.Enter OS 3.Click Settings->Appearance->Position of new icons [Expected result] Choose different position,folder will follow the command [Actual result] Choose different position,it is unchanged. [Failure rate] 100% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1984106/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
The native chromium works. So I did not think it is a ubuntu-frame bug.
I test the previous snap chromium version before, and it also works.
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
It would be nice if you could run your test on normal Ubuntu Wayland, as it
could be a bug in Ubuntu Frame.
Especially given https://github.com/MirServer/ubuntu-frame/issues/75, it would
be reasonable to disregard your failure report.
** Bug watch added: github.com/MirServer/ubuntu-frame/issues #75
https://github.com/MirServer/ubuntu-frame/issues/75
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel candidate/hwacc chromium
2. If on Xorg (`echo $WAYLAND_DISPLAY` is empty),
snap run chromium --disable-features=UseChromeOSDirectVideoDecoder
--enable-features=VaapiVideoDecoder
If on Wayland (`echo $WAYLAND_DISPLAY` is not empty),
chromium --enable-features=VaapiVideoDecoder --disable-
features=UseChromeOSDirectVideoDecoder --ozone-platform=wayland
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples
4. Enter about:media-internals in the address bar and note what the
page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx}VideoDecoder;
- If failed, the video used for testing, including codec and resolution if
possible;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
About the last point, it may be that unfortunately only those with
newer generations of Intel CPUs will have luck with this, but it's
still an uncertainty. So reports are highly welcome.
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984067] Re: Xorg crash
** Attachment added: "xorg.1 file from crashed session" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1984067/+attachment/5607529/+files/Xorg.1.log.old -- 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/1984067 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-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:
[Desktop-packages] [Bug 1984067] [NEW] Xorg crash
Public bug reported: All logs should be added automatically but the central issue is: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Backtrace: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x139) [0x55b7984596e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 1: /lib/x86_64-linux-gnu/libc.so.6 (__sigaction+0x50) [0x7f3e6a242520] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 2: /usr/lib/xorg/Xorg (NewCurrentScreen+0x1b9) [0x55b7982ee1e9] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 3: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x4d5) [0x55b7982efc85] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 4: /usr/lib/xorg/Xorg (MaybeDeliverEventsToClient+0x9d3) [0x55b7982f0183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 5: /usr/lib/xorg/Xorg (WindowsRestructured+0x163) [0x55b7982f1183] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 6: /usr/lib/xorg/Xorg (InitProximityClassDeviceStruct+0x1fdd) [0x55b7983cfa7d] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 7: /usr/lib/xorg/Xorg (XkbHandleActions+0x1dc) [0x55b7983f9e4c] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 8: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x7c1) [0x55b7983f2f21] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 9: /usr/lib/xorg/Xorg (XkbRemoveResourceClient+0x9be) [0x55b7983f311e] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 10: /usr/lib/xorg/Xorg (TimerSet+0x170) [0x55b798452c60] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x258) [0x55b798452ee8] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 12: /usr/lib/xorg/Xorg (SendErrorToClient+0x117) [0x55b7982e3257] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 13: /usr/lib/xorg/Xorg (InitFonts+0x3c4) [0x55b7982e7524] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_init_first+0x90) [0x7f3e6a229d90] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0x80) [0x7f3e6a229e40] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) 16: /usr/lib/xorg/Xorg (_start+0x25) [0x55b7982d05f5] Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Segmentation fault at address 0x7ffc51d3 Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Fatal server error: Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Caught signal 11 (Segmentation fault). Server aborting Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: Please consult the The X.Org Foundation support Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: #011 at http://wiki.x.org Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: for help. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) Please also check the log file at "/var/log/Xorg.1.log" for additional information. Aug 9 15:02:17 ice-ubuntu /usr/libexec/gdm-x-session[4523]: (EE) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-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: Tue Aug 9 15:22:16 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu DkmsStatus: acpi-call/1.2.2, 5.15.0-41-generic, x86_64: installed acpi-call/1.2.2, 5.15.0-43-generic, x86_64: installed fwts-efi-runtime-dkms/22.03.00, 5.15.0-41-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms/22.03.00, 5.15.0-43-generic, x86_64: installed (WARNING! Diff between built and installed module!) DpkgLog:
[Desktop-packages] [Bug 1982898] Re: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf
** Changed in: gdk-pixbuf (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1982898 Title: CVE-2021-46829: Buffer overwrite in io-gif-animation.c composite_frame() in gdk-pixbuf Status in gdk-pixbuf package in Ubuntu: Fix Released Status in gdk-pixbuf source package in Focal: Fix Released Bug description: [Impact] * A buffer overwrite exists in gdk-pixbuf's thumbnailer. * The GIF loader runs out of memory with specifically crafted files with bad frame data (and images with its sizes) over the integer limit. * After gdk-pixbuf-thum runs out of memory, other apps can and on low RAM systems like my old iMac, the system can completely run out of memory. * Or, in other ways, bad gif files in other applications can open the door for exploits. * Any app using gdk-pixbuf is affected, mainly file managers and image viewers. [Test Plan] * Take the POC's - they can be found in the issue in the GNOME repo * Open them in an application that uses gdk-pixbuf. I have managed to produce reactions with: - Nautilus, GNOME's file manager - Nemo, Cinnamon's file manager - Thunar, XFCE's file manager, which has its own thumbnailere (tumbler) that also inevitably fails and crashes - PCManFM, LXDE's file manager which straight up crashes - Caja, MATE's file manager causes libpixbufloader-gif to segfault (app still usable, no memory issues) - Eye of GNOME (eog) triggers the segfault in syslog - Eye of MATE (eom) segfaults * If you or the system couldn't tell something is wrong, cat /var/log/syslog and enjoy the segfaults or out of memory warnings or even kernel spam. [Where problems could occur] * The patch itself is simple, but since gdk-pixbuf is often used with GTK apps a mistake here could be problematic. * It is possible, and has happened in the past (which has been patched) that other bad GIFs can cause other crashes. * That patch is essentially overflow checks - changes with GLib (GNOME's, not to be confused with glibc) and the functions used in not only the patch but all of gdk-pixbuf can cause problems * Other failures to properly handle GIFs and broken or intentionally tampered GIFs can continue and always will open the door for security holes for other bugs * Again, overall a simple patch but as long as the GIFs remain handled properly, and no changes to the GLib functions are made and to other apps that use gdk-pixbuf (and assuming are not affected by the change and still work), the patch does not have much regression potential. [Other Info] * Besides Buffer overwrite/overflow issues, as aforementioned out of memory errors can happen. * Files attached are examples or crashes * Again, all apps using gdk-pixbuf are affected * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/merge_requests/121/ * https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/190 * https://github.com/pedrib/PoC/blob/master/fuzzing/CVE-2021-46829/CVE-2021-46829.md ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgdk-pixbuf2.0-0 2.40.0+dfsg-3ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Tue Jul 26 19:33:41 2022 InstallationDate: Installed on 2021-11-24 (244 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210826) SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1982898/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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.
** No longer affects: linux-raspi (Ubuntu) -- 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 Ubuntu Seeds: New Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid 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-seeds/+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 1983859] Re: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04
I tried to produce a usable backtrace by copying the crash file back to a VM that were in the state before the upgrade, but the backtrace there has GDB warnings: Section `.reg-xstate/$number' in core file too small. I assume that the crash happens when already some package were updated. What I saw the the journal log: dbus-daemon[813]: Unknown group "power" in message bus configuration file You can try to create the GDB backtrace directly after the crash. Modify ExecStart in /usr/lib/systemd/user/tracker-extract.service to: ExecStart=/usr/bin/gdb --batch --ex run --ex bt /usr/libexec/tracker- extract -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1983859 Title: tracker-extract crashes with SIGSYS when upgrading from 20.04 to 22.04 Status in tracker package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: When upgrading Ubuntu Desktop from 20.04 to 22.04, there's often (pretty much always) a crash from tracker-extract, as described in the following error report: https://errors.ubuntu.com/oops/d7866d85-14cc-11ed-a52b-fa163e55efd0 The crash occurs during the upgrade, which means it's fairly hard to investigate exactly what's going on as apport fails to extract a stack trace, the binaries being overwritten during the upgrade. However, the crash occurs because of a unhandled SIGSYS, meaning a seccomp filter issue. I've tried backporting this patch fixing a similar issue: https://gitlab.gnome.org/GNOME/tracker- miners/-/commit/4cda983b02e49f6bd28b94a6b96c9fe7026887ef but it doesn't apply, likely due to the code having diverged too much since. My proposal is thus to disable tracker-extract during upgrade, including in all user sessions. I'm assuming that the new version will be enabled automatically as its unit file changed name anyway. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1983859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983998] Re: USB sound card not detected
Hello Erich! May be it is really inappropriate project to report but i found that usbc not working at all. I suspect usb power problems in kernel. Please help me to find appropriate project on launchpad (i'm new here). As i understand, device will not be disconnected in case of just not compliant to anything. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1983998 Title: USB sound card not detected Status in alsa-driver package in Ubuntu: Invalid Bug description: usbc mics https://www.boya-mic.com/lavaliermicrophones/1430.html connects and immediately disconnects, ls usb hangs for a while, when usbc device is connected. it works on win laptop well. ``` [10877.622942] usb 3-4: new full-speed USB device number 28 using xhci_hcd [10877.779590] usb 3-4: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10877.779596] usb 3-4: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10877.779599] usb 3-4: Product: USB PnP Audio Device [10877.983589] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10877.983593] usb 3-4: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.009593] usb 3-4: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.009597] usb 3-4: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.035587] usb 3-4: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.035591] usb 3-4: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.038757] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-4/3-4:1.3/0003:0C76:153F.001B/input/input45 [10878.095081] hid-generic 0003:0C76:153F.001B: input,hidraw6: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-4/input3 [10878.095179] usb 3-3: USB disconnect, device number 27 [10878.426945] usb 3-3: new full-speed USB device number 29 using xhci_hcd [10878.587590] usb 3-3: New USB device found, idVendor=0c76, idProduct=153f, bcdDevice= 1.00 [10878.587597] usb 3-3: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [10878.587599] usb 3-3: Product: USB PnP Audio Device [10878.783592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.783597] usb 3-3: [51] FU [Mic Playback Volume] ch = 1, val = 0/7936/16 [10878.809597] usb 3-3: Warning! Unlikely big volume range (=1008), cval->res is probably wrong. [10878.809601] usb 3-3: [49] FU [Speaker Playback Volume] ch = 2, val = -16129/-1/16 [10878.835592] usb 3-3: Warning! Unlikely big volume range (=496), cval->res is probably wrong. [10878.835596] usb 3-3: [50] FU [Mic Capture Volume] ch = 1, val = 0/7936/16 [10878.838754] input: USB PnP Audio Device as /devices/pci:00/:00:01.2/:02:00.0/:03:08.0/:06:00.3/usb3/3-3/3-3:1.3/0003:0C76:153F.001C/input/input46 [10878.895092] hid-generic 0003:0C76:153F.001C: input,hidraw5: USB HID v1.00 Device [USB PnP Audio Device] on usb-:06:00.3-3/input3 [10878.895190] usb 3-4: USB disconnect, device number 28 ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-45.48-generic 5.15.39 Uname: Linux 5.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vany 12211 F pulseaudio /dev/snd/controlC0: vany 12211 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Aug 8 18:28:32 2022 InstallationDate: Installed on 2020-11-26 (619 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: Upgraded to jammy on 2022-05-23 (76 days ago) dmi.bios.date: 04/01/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:br5.14:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: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 To manage
[Desktop-packages] [Bug 1981974] Re: FP identify is not working with broadcom sensor on Jammy
** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1981974 Title: FP identify is not working with broadcom sensor on Jammy Status in libfprint-2-tod1-broadcom: New Status in libfprint package in Ubuntu: New Bug description: Broadcom Jammy package is provided to canonical team (Andy), attached the log file shows FP identify operation says that verification is successful, but Login screen will NOT be unlocked. To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1981974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973033] Re: [MIR] wpebackend-fdo
$ ./change-override -c main -S wpebackend-fdo Override component to main wpebackend-fdo 1.12.0-1 in kinetic: universe/misc -> main libwpebackend-fdo-1.0-1 1.12.0-1 in kinetic amd64: universe/libs/optional/100% -> main libwpebackend-fdo-1.0-1 1.12.0-1 in kinetic arm64: universe/libs/optional/100% -> main libwpebackend-fdo-1.0-1 1.12.0-1 in kinetic armhf: universe/libs/optional/100% -> main libwpebackend-fdo-1.0-1 1.12.0-1 in kinetic i386: universe/libs/optional/100% -> main libwpebackend-fdo-1.0-1 1.12.0-1 in kinetic ppc64el: universe/libs/optional/100% -> main libwpebackend-fdo-1.0-1 1.12.0-1 in kinetic riscv64: universe/libs/optional/100% -> main libwpebackend-fdo-1.0-1 1.12.0-1 in kinetic s390x: universe/libs/optional/100% -> main libwpebackend-fdo-1.0-dev 1.12.0-1 in kinetic amd64: universe/libdevel/optional/100% -> main libwpebackend-fdo-1.0-dev 1.12.0-1 in kinetic arm64: universe/libdevel/optional/100% -> main libwpebackend-fdo-1.0-dev 1.12.0-1 in kinetic armhf: universe/libdevel/optional/100% -> main libwpebackend-fdo-1.0-dev 1.12.0-1 in kinetic i386: universe/libdevel/optional/100% -> main libwpebackend-fdo-1.0-dev 1.12.0-1 in kinetic ppc64el: universe/libdevel/optional/100% -> main libwpebackend-fdo-1.0-dev 1.12.0-1 in kinetic riscv64: universe/libdevel/optional/100% -> main libwpebackend-fdo-1.0-dev 1.12.0-1 in kinetic s390x: universe/libdevel/optional/100% -> main Override [y|N]? y 15 publications overridden. ** Changed in: wpebackend-fdo (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpebackend-fdo in Ubuntu. https://bugs.launchpad.net/bugs/1973033 Title: [MIR] wpebackend-fdo Status in wpebackend-fdo package in Ubuntu: Fix Released Bug description: [Availability] The package wpebackend-fdo is already in Ubuntu universe. The package wpebackend-fdo build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf i386 ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/wpebackend-fdo [Rationale] - The package wpebackend-fdo is required in Ubuntu main as a dependency of webkit2gtk. The dependency is optional but the default upstream and in other distributions and the only one upstream is really testing (turned out some of the issues we had previous cycle are because we aren't using the default backend, which also made a lower priority for upstream to work on fixes). Upstream is also planning to deprecate the nonwpe codepath. We might also need to build with that backend on older series at some point due to the previous statement. - The package wpebackend-fdo is required in Ubuntu main no later than aug 25 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Ubuntu and Debian and has currently no reports - Ubuntu https://bugs.launchpad.net/ubuntu/+source/wpebackend-fdo/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=wpebackend-fdo - The package does not deal with exotic hardware we cannot support [Quality assurance - testing] - The package does not run a test at build time because upstream doesn't have one. That's something we need to work on. BLOCKER ^ - The package does not run an autopkgtest because upstream has no test and Debian didn't have some either. If webkit2gtk is built with it as it default backend then the webkitgtk autopkgtests are going to exercise wpe, is that enough? BLOCKER? ^ We need to work on the testing story, backup plan is to write some manual test plans. [Quality assurance - packaging] - debian/watch is present and works -- There is only one lintian warning # lintian --pedantic P: wpebackend-fdo source: package-uses-old-debhelper-compat-version 12 12 isn't that old but we will work on updating to 13 - There is one lintian overrides for having the .so distributed in the library rather than the dev because browsers try to load the .so and it should be available. The change was added in Debian to https://salsa.debian.org/webkit-team/wpebackend-fdo/-/commit/07a67e57 - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf questions - Packaging and build is easy, link to d/rules https://salsa.debian.org/webkit-team/wpebackend- fdo/-/blob/master/debian/rules [UI
[Desktop-packages] [Bug 1973031] Re: [MIR] libwpe
$ ./change-override -c main -S libwpe Override component to main libwpe 1.12.0-1 in kinetic: universe/misc -> main libwpe-1.0-1 1.12.0-1 in kinetic amd64: universe/libs/optional/100% -> main libwpe-1.0-1 1.12.0-1 in kinetic arm64: universe/libs/optional/100% -> main libwpe-1.0-1 1.12.0-1 in kinetic armhf: universe/libs/optional/100% -> main libwpe-1.0-1 1.12.0-1 in kinetic i386: universe/libs/optional/100% -> main libwpe-1.0-1 1.12.0-1 in kinetic ppc64el: universe/libs/optional/100% -> main libwpe-1.0-1 1.12.0-1 in kinetic riscv64: universe/libs/optional/100% -> main libwpe-1.0-1 1.12.0-1 in kinetic s390x: universe/libs/optional/100% -> main libwpe-1.0-dev 1.12.0-1 in kinetic amd64: universe/libdevel/optional/100% -> main libwpe-1.0-dev 1.12.0-1 in kinetic arm64: universe/libdevel/optional/100% -> main libwpe-1.0-dev 1.12.0-1 in kinetic armhf: universe/libdevel/optional/100% -> main libwpe-1.0-dev 1.12.0-1 in kinetic i386: universe/libdevel/optional/100% -> main libwpe-1.0-dev 1.12.0-1 in kinetic ppc64el: universe/libdevel/optional/100% -> main libwpe-1.0-dev 1.12.0-1 in kinetic riscv64: universe/libdevel/optional/100% -> main libwpe-1.0-dev 1.12.0-1 in kinetic s390x: universe/libdevel/optional/100% -> main Override [y|N]? y 15 publications overridden. ** Changed in: libwpe (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwpe in Ubuntu. https://bugs.launchpad.net/bugs/1973031 Title: [MIR] libwpe Status in libwpe package in Ubuntu: Fix Released Bug description: [Availability] The package libwpe is already in Ubuntu universe. The package libwpe build for the architectures it is designed to work on. It currently builds and works for architectures: amd64 arm64 armhf i386 ppc64el riscv64 s390x Link to package https://launchpad.net/ubuntu/+source/libwpe [Rationale] The package libwpe is required in Ubuntu main as a dependency of webkit2gtk. The dependency is optional but the default upstream and in other distributions and the only one upstream is really testing (turned out some of the issues we had previous cycle are because we aren't using the default backend, which also made a lower priority for upstream to work on fixes). Upstream is also planning to deprecate the nonwpe codepath. - The package wpebackend-fdo is required in Ubuntu main no later than aug 25 due to feature freeze [Security] - No CVEs/security issues in this software in the past - no executables in `/sbin` and `/usr/sbin` - Package does not install services, timers or recurring jobs - Packages does not open privileged ports (ports < 1024) - Packages does not contain extensions to security-sensitive software [Quality assurance - function/usage] - The package works well right after install [Quality assurance - maintenance] - The package is maintained well in Ubuntu and Debian and has currently no reports - Ubuntu https://bugs.launchpad.net/ubuntu/+source/libwpe/+bug - Debian https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libwpe [Quality assurance - testing] - The package does not run a test at build time because upstream doesn't have one. That's something we need to work on. BLOCKER ^ If webkit2gtk is built with it as it default backend then the webkitgtk autopkgtests are going to exercise wpe, is that enough? BLOCKER? ^ We need to work on the testing story, backup plan is to write some manual test plans. It's likely that the test plan for wpebackend-fdo will cover the library. [Quality assurance - packaging] - debian/watch is present and works -- There is only one lintian warning # lintian --pedantic P: libwpe source: package-uses-old-debhelper-compat-version 12 12 isn't that old but we will work on updating to 13 - Lintian overrides are not present - This package does not rely on obsolete or about to be demoted packages. - This package has no python2 or GTK2 dependencies - The package will be installed by default, but does not ask debconf question - Packaging and build is easy, link to d/rules https://salsa.debian.org/webkit-team/libwpe/-/blob/master/debian/rules [UI standards] - Application is not end-user facing (does not need translation) [Dependencies] - No further depends or recommends dependencies that are not yet in main [Standards compliance] - This package correctly follows FHS and Debian Policy [Maintenance/Owner] - Owning Team will be desktop-packages - Team is not yet, but will subscribe to the package before promotion - This does not use static builds - This does not use vendored code - The package successfully built during the most recent test rebuild [Background information] The Package description explains the package well Upstream Name is libwpe Link to upstream project https://github.com/WebPlatformForEmbedded/libwpe To manage notifications
