[Desktop-packages] [Bug 1965563] Re: gnome-extensions-app fails to start (Protocol error)
FWIW: On the installation where have the issue, this is what it looks like in a Xorg session: $ gnome-extensions-app Segmentation fault (core dumped) Same as bug #1966221 in other words. (The command shown in the bug description was run in a Wayland session.) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1965563 Title: gnome-extensions-app fails to start (Protocol error) Status in gnome-shell package in Ubuntu: Confirmed Bug description: $ dpkg-query -W gnome-shell-extension-prefs gnome-shell-extension-prefs 42~beta-1ubuntu3 $ gnome-extensions-app Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error Caveat: I currently have a mix of packages from jammy-release and jammy-proposed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966376] Re: Video playback not so great
Please tell us which player/app is affected. Please also try: sudo apt update sudo apt install mpv vainfo mesa-va-drivers and try using 'mpv' instead. MPV is the only player I would personally recommend. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1966376 Title: Video playback not so great Status in Ubuntu: Incomplete Bug description: Video playback always results in lines across the screen no matter what platform you're viewing it in. I am no expert in these sort of things but will be willing to help find out what the issue is and maybe a sollution! Ubuntu 20.04.4 LTS X86_64 XFCE (Xubuntu) xorg Version: Version table: *** 1:7.7+19ubuntu14 500 500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Mar 25 07:17:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1355] InstallationDate: Installed on 2022-02-18 (34 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5e0 Chicony Electronics Co., Ltd VGA WebCam Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A315-54K ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=855fae32-2844-4d07-955b-e32d41f1cd23 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2019 dmi.bios.release: 1.3 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sleepy_KL dmi.board.vendor: KBL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd07/05/2019:br1.3:efr1.3:svnAcer:pnAspireA315-54K:pvrV1.03:rvnKBL:rnSleepy_KL:rvrV1.03:cvnAcer:ct10:cvrV1.03:sku: dmi.product.family: Aspire 3 dmi.product.name: Aspire A315-54K dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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/ubuntu/+bug/1966376/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966376] [NEW] Video playback not so great
Public bug reported: Video playback always results in lines across the screen no matter what platform you're viewing it in. I am no expert in these sort of things but will be willing to help find out what the issue is and maybe a sollution! Ubuntu 20.04.4 LTS X86_64 XFCE (Xubuntu) xorg Version: Version table: *** 1:7.7+19ubuntu14 500 500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Mar 25 07:17:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1355] InstallationDate: Installed on 2022-02-18 (34 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5e0 Chicony Electronics Co., Ltd VGA WebCam Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A315-54K ProcEnviron: LANGUAGE=en_ZA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=855fae32-2844-4d07-955b-e32d41f1cd23 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2019 dmi.bios.release: 1.3 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.03 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sleepy_KL dmi.board.vendor: KBL dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.03 dmi.ec.firmware.release: 1.3 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.03:bd07/05/2019:br1.3:efr1.3:svnAcer:pnAspireA315-54K:pvrV1.03:rvnKBL:rnSleepy_KL:rvrV1.03:cvnAcer:ct10:cvrV1.03:sku: dmi.product.family: Aspire 3 dmi.product.name: Aspire A315-54K dmi.product.sku: dmi.product.version: V1.03 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1966376 Title: Video playback not so great Status in xorg package in Ubuntu: New Bug description: Video playback always results in lines across the screen no matter what platform you're viewing it in. I am no expert in these sort of things but will be willing to help find out what the issue is and maybe a sollution! Ubuntu 20.04.4 LTS X86_64 XFCE (Xubuntu) xorg Version: Version table: *** 1:7.7+19ubuntu14 500 500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Fri Mar 25 07:17:50 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1355] InstallationDate: Installed on 2022-02-18 (34 days ago) InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b5e0 Chicony Electronics Co., Ltd VGA WebCam Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire A315-54K ProcEnviron: LANGUAGE=en_ZA:en
[Desktop-packages] [Bug 1966356] Re: ibus input method not working
I can't reproduce it either. It can be noted that a (possible) issue on standard Ubuntu related to how ibus-daemon is started is not an issue with ibus but rather with gnome-shell. Anyway, this is a bit odd: $ env | grep -i type XDG_SESSION_TYPE=x11 $ ps ux | grep ibus-daemon gunnar 2932 0.0 0.0 2888 956 ?Ss 06:04 0:00 sh -c /usr/bin/ibus-daemon --panel disable $([[ $XDG_SESSION_TYPE == "x11" ]] && echo "--xim") gunnar 2935 0.4 0.0 406192 14220 ?Sl 06:04 0:02 /usr/bin/ibus-daemon --panel disable gunnar 5761 0.0 0.0 24844 2632 pts/0S+ 06:14 0:00 grep --color=auto ibus-daemon OTOH I can't tell the significance of '--xim' not being included in the second ibus-daemon process. @Yuan-Chen Cheng: Well, if nobody — not even you — is able to reproduce the issue on an upgraded jammy, the bug shouldn't be set to "Incomplete" but rather be closed. So I closed it. Please feel free to request it to be reopened or submit a new bug if the issue reappears. ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid ** Changed in: ibus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in gnome-shell package in Ubuntu: Invalid Status in ibus package in Ubuntu: Invalid Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966356] Re: ibus input method not working
Hmm, weird that I can't reproduce this issue now. I'll set this to in- complete temporary. Btw, I try to add nomodeset to booting parameter, and I found that I can't run in Wayland mode. It's only x11 mode (and the icon to select between wayland and x11 mode is not there) ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: Incomplete Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966334] Re: GLVND: Set current thread state to NULL in teardown
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libglvnd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1966334 Title: GLVND: Set current thread state to NULL in teardown Status in libglvnd package in Ubuntu: Confirmed Bug description: A new fix has been merged into the libglvnd repo at https://gitlab.freedesktop.org/glvnd/libglvnd This change fixes an issue where if eglReleaseThread gets externally called after the EGL destructor, a double free occurs due to the threadState that eglReleaseThread checks is not null being not null despite being freed by the destuctor. The change makes the threadState null in the destructor to fix this. Can this make it into the libs in 20.04 LTS? Source package where the issue is encountered: https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1966334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965537] Re: Desktop Icons NG gjs high CPU usage when moving/resizing any window
Let's consider it partially fixed and reopen it. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: Fix Released => In Progress -- 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/1965537 Title: Desktop Icons NG gjs high CPU usage when moving/resizing any window Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: In Progress Bug description: Desktop Icons NG gjs high CPU usage when moving window - check enclosed video. When I disable Desktop Icons NG extensions CPU usage is fine. System spec: Intel® Core™ i7-2600 CPU @ 3.40GHz × 8 AMD® Radeon rx 560 series Wayland Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1965537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932005] Re: nm-applet not showing in system tray
** Changed in: ubuntu-mate Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1932005 Title: nm-applet not showing in system tray Status in Ubuntu MATE: Incomplete Status in network-manager-applet package in Ubuntu: New Bug description: Hello all, I noticed this morning that the network options (i am not sure if it suppose to be nm-applet) is no longer showing in system tray and for a while now that KDE Connect indicator is not showing in the system tray. I am currently Ubuntu Mate 20.04 on a raspberry PI400 uname -a Linux pi400 5.4.0-1036-raspi #39-Ubuntu SMP PREEMPT Wed May 12 17:37:51 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux cat /etc/os-release NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal apt policy network-manager network-manager: Installed: 1.22.10-1ubuntu2.2 Candidate: 1.22.10-1ubuntu2.2 Version table: *** 1.22.10-1ubuntu2.2 500 500 http://ports.ubuntu.com/ubuntu-ports focal-updates/main arm64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports focal/main arm64 Packages Does anyone else have a similar issue? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1932005/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966356] Re: ibus input method not working
Could you give us steps to reproduce? It works for me after adding Others/Chewing in keyboard setup in the jammy VM. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: New Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966328] Re: Xorg freeze
Thanks for the bug report. There's an error in your kernel log: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A which makes me think this is bug 1767654 (specific to the model of CPU you have) or bug 1806242. In case that's not the problem then please also check for crashes using these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Summary changed: - Xorg freeze + Screen freeze -- 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/1966328 Title: Screen freeze Status in Ubuntu: Incomplete Bug description: sometimes my pc freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Mankas permeso: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 16:16:46 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:10b0] InstallationDate: Installed on 2022-01-23 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic root=UUID=b5b63f0c-74df-4fe8-9cf0-a1eaa29c1260 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: E dmi.product.name: E200HA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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/ubuntu/+bug/1966328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966206] Re: external display not detected
Thanks for the bug report. It looks like you don't have a driver installed for your Nvidia GPU so that's the first thing to fix. Please open the 'Additional Drivers' app and select an Nvidia driver, then reboot. If the problem isn't fixed after that then please run: lspci -k > lspci.txt journalctl -b0 > journal.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: 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/1966206 Title: external display not detected Status in Ubuntu: Incomplete Bug description: 1) Description: Ubuntu 20.04.3 LTS Release: 20.04 2) N: Unable to locate package pkgname 3) My current issue is the external display not being detected, but I don't know how it will behave, given the different issues, at different boots, being that the repairs/updates from the recovery session may have changed something, don't know. The timeline regarding the issue(s): My laptop screen started showing what looked like a broken screen when after booting, while on the log in screen (I could not see it). I shut down and the started again, entered recovery mode (the newer version), chose to recover, went to boot, after login saw the same broken screen on the laptop and nothing on the external. Shut down, start, and back to login screen, rebooted from there (as per instructed somewhere along the process, don't remember where, something like "if you can't go in, reboot from login menu").This time the laptop screen remained unusable but was working on the external monitor. Had the laptop working for hours and then it froze. Shut down, start and the same thing, broken laptop screen, this time no external monitor recognized, as before. Shut down, start and now, for the first time the laptop screen works but the external monitor is not recognized. Changing the hdmi cable from a usb-c hub to the hdmi port, the screen brightness got a lot dimmer, but nothing on the settings->display menu. My current issue is the external display not being detected, but I don't know how it will behave, given the different issues, at different boots, being that the repairs/updates from the recovery session may have changed something, don't know. 4) External monitor recognized and working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 12:51:10 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: hid-apple, 1.0, 5.13.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a43] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3a3f] InstallationDate: Installed on 2021-11-30 (113 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82B5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=fd06b914-e9cb-4b39-b897-5f9c9a75fb82 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1966221] Re: gnome-extensions-app crashes with "Segmentation fault (core dumped)"
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966221 Title: gnome-extensions-app crashes with "Segmentation fault (core dumped)" Status in gnome-shell package in Ubuntu: Incomplete Bug description: when I use the command "gnome-extensions-app" in command line ,it will crash and report "Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:32:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-09 (42 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 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/1966221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966221] Re: I can't start it
Maybe related to bug 1965563? ** Summary changed: - I can't start it + gnome-extensions-app crashes with "Segmentation fault (core dumped)" -- 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/1966221 Title: gnome-extensions-app crashes with "Segmentation fault (core dumped)" Status in gnome-shell package in Ubuntu: Incomplete Bug description: when I use the command "gnome-extensions-app" in command line ,it will crash and report "Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:32:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-09 (42 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 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/1966221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966187] Re: crash xorg
*** This bug is a duplicate of bug 1861609 *** https://bugs.launchpad.net/bugs/1861609 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1861609, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1861609 [focal] Xorg crashed with assertion failure (usually in a VM) at [privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed] and call stack comes from DRIMoveBuffersHelper -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1966187 Title: crash xorg Status in xorg-server package in Ubuntu: Incomplete Bug description: Randomly, system (Ubuntu 20.04) crashes and login screen appears. apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status file at var/crash says: ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:15:15 2022 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1639491253 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/tidop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcMaps: 55742c038000-55742c075000 r--p 08:12 12976830 /usr/lib/xorg/Xorg 55742c075000-55742c207000 r-xp 0003d000 08:12 12976830 /usr/lib/xorg/Xorg 55742c207000-55742c28 r--p 001cf000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28-55742c284000 r--p 00247000 08:12 12976830 /usr/lib/xorg/Xorg 55742c284000-55742c28f000 rw-p 0024b000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28f000-55742c2cd000 rw-p 00:00 0 55742d4a5000-557439da6000 rw-p 00:00 0 [heap] 7fe3c000-7fe3c0021000 rw-p 00:00 0 7fe3c0021000-7fe3c400 ---p 00:00 0 7fe3c400-7fe3c4021000 rw-p 00:00 0 7fe3c4021000-7fe3c800 ---p 00:00 0 7fe3c800-7fe3c8021000 rw-p 00:00 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 10:15:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:2489] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:4667] InstallationDate: Installed on 2022-02-11 (40 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=bcea4888-7b37-4ace-a9da-8a0a74fce240 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 10.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1017 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B560-F GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB560-FGAMINGWIFI:rvrRev1.xx: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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri:
[Desktop-packages] [Bug 1964037] Re: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session
** Summary changed: - gnome-shell crashes when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session + gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session -- 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/1964037 Title: gnome-shell crashes (fatal error logged in create_fallback_offscreen) when attempting to enable second monitor on second GPU (Nvidia >= 495) in a Wayland session Status in Mutter: Unknown Status in mutter package in Ubuntu: In Progress Bug description: This is on my weird desktop setup, with one monitor plugged into an AMD card and one into an NVIDIA card. When using the Wayland session, by default Shell will come up on the monitor connected to the AMD card, and the second (NVIDIA) monitor will be blank. Attempting to enable the second monitor in Display Settings will immediately and reproducibly crash gnome-shell. This is trivial for me to reproduce, so if you need patches tested I can easily do so. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0+bcachefs.git2026.1fa97551d-1.1-generic 5.15.2 Uname: Linux 5.15.0+bcachefs.git2026.1fa97551d-1-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu78 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 8 09:37:51 2022 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-11-02 (125 days ago) InstallationMedia: Ubuntu 21.10.0 2021.10.19 amd64 "bcachefs" (20211028) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 41.3-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 () at /lib/x86_64-linux-gnu/libmutter-9.so.0 meta_monitor_mode_foreach_crtc () at /lib/x86_64-linux-gnu/libmutter-9.so.0 Title: gnome-shell crashed with signal 5 UpgradeStatus: Upgraded to jammy on 2021-11-02 (124 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1964037/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965659] Re: Yaru color themes make some apps unreadable white
** Bug watch added: github.com/ubuntu/yaru/issues #3516 https://github.com/ubuntu/yaru/issues/3516 ** Also affects: yaru via https://github.com/ubuntu/yaru/issues/3516 Importance: Unknown Status: Unknown ** Summary changed: - Yaru color themes make some apps unreadable white + Yaru color themes make GTK 2.0 apps unreadable white -- 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/1965659 Title: Yaru color themes make GTK 2.0 apps unreadable white Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: In Progress Bug description: Ubuntu 22.04 development branch @ 20/03/2022 When picking a new yaru color theme from settings/apareance every color besides the default orange some programs have some unreadable white parts or tabs (in my case hexchat and xscreensaver-demo) this can be fixed by picking yaru-dark legacy apps from gnome-tweaks and keep the color theme for icons only but for users that does not use gnome-tweaks, that should not be happening by default? (see screenshots) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: yaru-theme-gtk 22.04.2 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Mar 20 09:17:48 2022 PackageArchitecture: all SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1965659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966356] Re: ibus input method not working
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: New Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965537] Re: Desktop Icons NG gjs high CPU usage when moving/resizing any window
This bug was fixed in the package gnome-shell-extension-desktop-icons-ng - 43-1 --- gnome-shell-extension-desktop-icons-ng (43-1) unstable; urgency=medium * New upstream release -- Gunnar Hjalmarsson Wed, 23 Mar 2022 15:03:28 +0100 ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: In Progress => Fix Released -- 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/1965537 Title: Desktop Icons NG gjs high CPU usage when moving/resizing any window Status in Gnome Shell Extension Desktop Icons Ng: Unknown Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Fix Released Bug description: Desktop Icons NG gjs high CPU usage when moving window - check enclosed video. When I disable Desktop Icons NG extensions CPU usage is fine. System spec: Intel® Core™ i7-2600 CPU @ 3.40GHz × 8 AMD® Radeon rx 560 series Wayland Ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1965537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966356] [NEW] ibus input method not working
Public bug reported: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Description changed: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. - Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, + Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, by modify /usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service, then it works. ** Description changed: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. - Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, by modify /usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service, + Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. + + Note: per test, add --xim works for below cases: + + 1. x11 mode + 2. Wayland mode, x11 client, test by using microsoft edge. + 3. Wayland mode, Wayland client, tested by using gnome-terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: New Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966007] Re: Flood of Bluetooth Malicious advertisind data
In my case, it's related with home assistant container, which hci0 is controlled by home assistant. I install HACS and passive ble monitor for receiving xiaomi LYWSD03MMC Temp/Humidity sensor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1966007 Title: Flood of Bluetooth Malicious advertisind data Status in gnome-terminal package in Ubuntu: Confirmed Bug description: This problem occurred with the ugrade of the kernel to patch level 105. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:48:22 2022 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2018-06-21 (1370 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_AU.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1966007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966007] Re: Flood of Bluetooth Malicious advertisind data
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1966007 Title: Flood of Bluetooth Malicious advertisind data Status in gnome-terminal package in Ubuntu: Confirmed Bug description: This problem occurred with the ugrade of the kernel to patch level 105. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:48:22 2022 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2018-06-21 (1370 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: LANG=en_AU.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1966007/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1884303] Re: LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??)
** No longer affects: ubuntu-mate -- 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/1884303 Title: LAN printing hell on 20.04 (UPnP VS mDNS? Or maybe IPv4 vs IPv6??) Status in cups package in Ubuntu: New Bug description: Hello, I have been experiencing this problem for at least 2 LTS versions I believe and it concerns and issue with a LAN printer. I am still not quite too sure if it involves a happy mix-up of TCPvsmDNSvsuPnP and|or if it's a lpstat VS GUI binary setting and|or ?? Anyways, when using 20.04 fully patched(and also possibly not) while using a LAN printer there seems to be a "duplicated-corrupted entry" that ends up somewhat generated in the system. For example: $ lpstat -p printer Samsung_C460_Series_SEC30CDA7A49F15_ now printing Samsung_C460_Series_SEC30CDA7A49F15_-12. enabled since Fri 19 Jun 2020 01:09:47 PM $ And MATE agrees with that (See attachment "1.jpg") But when using Atril (See "2.jpg") or LOWriter (See "3.jpg") (or any other binary such as firefox) the story isn't so clear. That brought me back to this: $ lpstat -p lpstat: No destinations added. $ And MATE still agrees with that (See "4.jpg") Yet LOWriter (and co) seemed a bit still challenged (See "5.jpg") Anyways, time to delete everything and readd. But why are there 2x choices? (See "6.jpg") Looking carefully at both entries, I believe that one is the TCP socket (See "7.jpg") while the 2nd one is via SSDP/UPnP (See "8.jpg"). But anyways, I always go for the TCP entry and that's done (See "9.jpg"). $ lpstat -p 1 ↵ printer Samsung-C460 is idle. enabled since Fri 19 Jun 2020 02:36:42 PM $ And MATE again agrees (See "10.jpg") Yaaay! Time to print out that SOB, so let's go back into Atril and print it (See "11.jpg") Nothing surprising there: the old ghosted/MAC addressed profile still shows. But did printing on the newly added via TCP one actually worked? YES! This time it did. Why this time? Because in other times it will just die in the spoiler and have me started back at the very beginning of this ticket. Also, a major point of interest is: after having readded the printer, notice how lpstat named it, it was "Samsung-C460". Well, if/when I'll reboot the system, that simple name will be gone and will have been changed to "Samsung-C460-Series-SEC30CDA7A49F15" while still showing this "Samsung_C460_Series_SEC30CDA7A49F15_" ghost. From the printer's perspective, here is what's opened on it: PORT STATE SERVICE VERSION 80/tcpopen httpSamsung SyncThru Web Service |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9 | http-methods: |_ Supported Methods: GET POST | http-robots.txt: 1 disallowed entry |_* |_http-title: Site doesn't have a title (text/html; charset=utf-8). 427/tcp open svrloc? 515/tcp open printer? | fingerprint-strings: | TerminalServerCookie: |_PortThru lpd: No Jobs on this queue 631/tcp open httpSamsung SyncThru Web Service |_http-favicon: Unknown favicon MD5: 10E320BB701D0D099E175B6C339958F9 | http-methods: |_ Supported Methods: GET POST |_http-title: Site doesn't have a title (text/html; charset=utf-8). 5200/tcp open targus-getdata? | fingerprint-strings: | DNSStatusRequestTCP, DNSVersionBindReqTCP, FourOhFourRequest, GenericLines, GetRequest, HTTPOptions, Help, Kerberos, LDAPSearchReq, LPDString, RPCCheck, RTSPRequest, SMBProgNeg, SSLSessionReq, TLSSessionReq, TerminalServerCookie, X11Probe: | HTTP/1.1 405 Method Not Allowed | Connection: close |_Server: ESWeb/0.5 9100/tcp open jetdirect? 10001/tcp open scp-config? Here's what /var/log/cups/error_log as to say about all of this: E [19/Jun/2020:00:00:00 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [19/Jun/2020:13:02:02 -0400] [Job 10] File \'\' not found E [19/Jun/2020:13:05:58 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [19/Jun/2020:13:08:09 -0400] [Job 11] No destination host name supplied by cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is cups-browsed running? E [19/Jun/2020:13:08:39 -0400] [Job 12] No destination host name supplied by cups-browsed for printer \"Samsung_C460_Series_SEC30CDA7A49F15_\", is cups-browsed running? E [19/Jun/2020:13:09:58 -0400] [Client 2371] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from localhost. E [19/Jun/2020:13:09:58 -0400] [Client 2493] Returning IPP client-error-not-possible for Cancel-Job (ipp://localhost/jobs/11) from localhost. E [19/Jun/2020:13:10:07 -0400] [Job 12] No destination host name supplied
[Desktop-packages] [Bug 1888127] Re: firefox crash
** No longer affects: ubuntu-mate -- 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/1888127 Title: firefox crash Status in firefox package in Ubuntu: Invalid Bug description: firefox crashes when i leave it open i suspend the pc then when i open it firefox crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1888127/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895369] Re: Network printer goes missing after 1x print when IPv6 is disabled
** Also affects: cups (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1895369 Title: Network printer goes missing after 1x print when IPv6 is disabled Status in cups package in Ubuntu: New Bug description: Using 20.04.1-latest and having disabled IPv6 @ /etc/sysctl.conf via the following settings: net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 When I open a .TXT using Libre Office Writer and print it, the first time it prints well. If I then close LOW immediately after, open another .txt and print it I get "Could not start printer. Please check your printer configuration". $ cat /var/log/cups/error_log 130 ↵ E [12/Sep/2020:00:00:01 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [12/Sep/2020:00:44:29 -0400] [Job 7] File \'\' not found E [12/Sep/2020:00:46:05 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [12/Sep/2020:00:46:05 -0400] [Job 7] File \'\' not found W [12/Sep/2020:00:46:05 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Samsung_C460_Series_SEC30CDA7A49F15_-Gray..\' already exists W [12/Sep/2020:00:46:05 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Samsung_C460_Series_SEC30CDA7A49F15_-DeviceN..\' already exists E [12/Sep/2020:00:47:25 -0400] Unable to open listen socket for address [v1.::1]:631 - Cannot assign requested address. E [12/Sep/2020:00:47:25 -0400] [Job 7] File \'\' not found W [12/Sep/2020:00:47:28 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Samsung_C460_Series_SEC30CDA7A49F15_-Gray..\' already exists W [12/Sep/2020:00:47:28 -0400] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id \'Samsung_C460_Series_SEC30CDA7A49F15_-DeviceN..\' already exists $ Also, the first document that I requested to be printed 1x copy will print a 2nd time without being asked. The solution is to wait. If I then close LOW and wait around 2-3 minutes then reopen that 2nd document and print it: it will print immediately and per requested. Another thing to mention is everytime I am in LOW and CTRL+P I always see the print window pop-up alongside my Samsung printer in it. The error/duplicate/refusal to print will happen after having clicked on "OK". PS1: This of course occurs when using a LAN printer. PS2: I did not installed any proprietary samsung binaries. Am instead using the default/vanilla network printer install that was done by UMC. PS3: This problem has been around since at least 18.04 if not prior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1895369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1901349] Re: Rhythmbox, first song played doesn't start at beginning
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1901349 Title: Rhythmbox, first song played doesn't start at beginning Status in rhythmbox package in Ubuntu: New Bug description: After updating from Ubuntu-MATE 20.04 to 20.10, the first song played after opening Rhythmbox doesn't start at the beginning. All other songs work fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1901349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931388] Re: Firefox disaplayerror after Update on last version 89
** No longer affects: ubuntu-mate -- 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/1931388 Title: Firefox disaplayerror after Update on last version 89 Status in firefox package in Ubuntu: Confirmed Bug description: After the last Update from Firefox Browser to Version 89 Firefox is unsuable. The Program starts but the window is somehow transparent and white. I removed and reinstalled Firefox but the problem is the same. My computer is an Amd Mashine running Ubuntu Mate 20.10 Mate 1.24.1 I took a Screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1931388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1936275] Re: Caja is slow when deleting large folders (>100k files)
** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Changed in: caja (Ubuntu) Status: New => Invalid ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1936275 Title: Caja is slow when deleting large folders (>100k files) Status in caja package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Bug description: Expected behaviour The folder is removed quickly (<10s). Actual behaviour It takes 1:12 minutes. Steps to reproduce the behaviour download https://static.rust-lang.org/dist/rustc-1.53.0-src.tar.gz (or any other larger project) and unpack it. Possibly even build to increase the size further. Permanently delete it afterwards. MATE general version 1.24.0 Package version Linux Distribution Ubuntu mate 20.04 Ryzen 2600 and an NVME-SSD Link to caja bugreport: https://github.com/mate-desktop/caja/issues/1537 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1936275/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950410] Re: PS4 DualShock wireless controller connected/disconnected/unusable
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1950410 Title: PS4 DualShock wireless controller connected/disconnected/unusable Status in blueman package in Ubuntu: New Status in bluez package in Ubuntu: New Bug description: Using a laptop running 21.10-latest, using a Sony Wireless Controller Model CUH-ZCT2U (The PS4 model), it seems impossible to connect via bluetooth to my laptop. Even though both hcitool & bluetooth manager are able to see the device, bonus mission bluetooth devices can also connect to it, but this is fairly short as it automatically disconnects. Here is what dmesg had to say about this. ``` [ 2479.109487] sony 0005:054C:09CC.0002: unknown main item tag 0x0 [ 2479.123654] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input28 [ 2479.124094] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input29 [ 2479.124676] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0002/input/input27 [ 2479.125046] sony 0005:054C:09CC.0002: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2490.957043] sony 0005:054C:09CC.0003: unknown main item tag 0x0 [ 2490.971080] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input31 [ 2490.971525] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input32 [ 2490.972397] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:4/0005:054C:09CC.0003/input/input30 [ 2490.973740] sony 0005:054C:09CC.0003: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2498.688287] sony 0005:054C:09CC.0004: unknown main item tag 0x0 [ 2498.699789] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input34 [ 2498.700142] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input35 [ 2498.700962] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:5/0005:054C:09CC.0004/input/input33 [ 2498.701415] sony 0005:054C:09CC.0004: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2511.533433] sony 0005:054C:09CC.0005: unknown main item tag 0x0 [ 2511.543132] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input37 [ 2511.543793] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input38 [ 2511.544577] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:6/0005:054C:09CC.0005/input/input36 [ 2511.545359] sony 0005:054C:09CC.0005: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2517.758693] sony 0005:054C:09CC.0006: unknown main item tag 0x0 [ 2517.766837] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input40 [ 2517.767834] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input41 [ 2517.768642] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:7/0005:054C:09CC.0006/input/input39 [ 2517.769168] sony 0005:054C:09CC.0006: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 [ 2522.932282] sony 0005:054C:09CC.0007: unknown main item tag 0x0 [ 2522.947350] input: Wireless Controller Touchpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input43 [ 2522.947965] input: Wireless Controller Motion Sensors as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input44 [ 2522.948593] input: Wireless Controller as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:8/0005:054C:09CC.0007/input/input42 [ 2522.951519] sony 0005:054C:09CC.0007: input,hidraw1: BLUETOOTH HID v81.00 Gamepad [Wireless Controller] on 9c:b6:d0:8f:c1:70 ``` When I plug the same controller via USB it's not only automatically recognized
[Desktop-packages] [Bug 1951220] Re: Caja and Nautilus umacceptably slow for more than 50 files
** Changed in: caja (Ubuntu) Status: New => Incomplete ** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1951220 Title: Caja and Nautilus umacceptably slow for more than 50 files Status in caja package in Ubuntu: Incomplete Status in nautilus package in Ubuntu: New Bug description: The latest update of Caja seems to have replaced the existing algorithms with ones that do not scale. Right clicking takes >3 minutes to open the menu if there are more than 300 files in the current folder. Opening a directory with 12,000 files takes so long that I get to catch up on my reading. Also Caja frequently crashes (even more often than Chrome). This was not a problem in earlier versions of Ubuntu MATE (18.04 through 20.04.3 without the last 3 updates). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caja/+bug/1951220/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959473] Re: Evolution: Migrate to People API to retain programmatic access to Google Contacts.
*** This bug is a duplicate of bug 1952107 *** https://bugs.launchpad.net/bugs/1952107 ** No longer affects: ubuntu-mate ** This bug has been marked a duplicate of bug 1952107 Google Contacts API Deprecated -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1959473 Title: Evolution: Migrate to People API to retain programmatic access to Google Contacts. Status in Evolution: Unknown Status in evolution package in Ubuntu: Confirmed Status in evolution-data-server package in Ubuntu: Confirmed Bug description: I'm running Ubuntu MATE 20.04; I stick with LTS for this system. I use Evolution for email and calendar. Tonight I got this message: = Failed to connect address book “guy.rouill...@gmail.com : Contacts” Invalid request URI or header, or unsupported nonstandard parameter: Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration. == I went to report this on the GNOME bug tracker and found this existing issue: https://gitlab.gnome.org/GNOME/evolution/-/issues/1655 That issue was closed with this comment: == "Andre Klapper Issue found on latest Evolution in Debian 11 (3.38.3-1) That version is ancient and not maintained anymore by GNOME developers. Feel free to file a bug report in your distribution's issue tracker." The version in MATE is even older: 3.36.5-0ubuntu1 So apparently Evolution in MATE is currently not functional. We need to update to a later release. I will update to the newer LTS of MATE when it is released. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2018-10-05 (1212 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Package: evolution-data-server PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Tags: third-party-packages focal Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-17 (622 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/evolution/+bug/1959473/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1538615] Re: Cat causes login screen to hang
Hey! I had the same issue a couple times. Password field has been unclickable. I've been forced to hard reset my laptop. Take a look to my beauty cat ) $ apt policy unity-greeter unity-greeter: Installed: (none) Candidate: 18.04.0+20.04.20200312-0ubuntu2 Version table: 18.04.0+20.04.20200312-0ubuntu2 500 500 http://pt.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ** Attachment added: "photo_2022-03-25_00-03-28.jpg" https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1538615/+attachment/5572740/+files/photo_2022-03-25_00-03-28.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1538615 Title: Cat causes login screen to hang Status in unity-greeter package in Ubuntu: Fix Released Status in unity-greeter source package in Trusty: Triaged Bug description: Steps to reproduce: 1. Leave laptop unattended in a cold room with a warm cat. 2. Cat will sit on laptop keyboard. 3. Wait 1 hour. 4. Lightdm will become unresponsive. Symptoms: Due to excessive password input by cat, lightdm acts oddly. I try to hit enter to try the invalid password and then type in the correct password, but enter has no affect. The cursor is not blinking, and hitting backspace has no effect. Using Ctrl+a or using shift+Ctrl+left arrow doesn't select the whole password to delete it. Hitting capslock causes the warning symbol to appear or disappear. The mouse moves, but clicking on the settings icon, date, sound icon, or language icon has no effect. One person suggested seeing if the cat had triggered scroll lock, but toggling between ctrl+q and ctrl+s had no effect. Logging in on a virtual terminal still works. Alternative steps to reproduce if cat is unavailable or uncooperative about being placed on keyboard (see attached pictures): 0. Glare at cat. 1. Restart lightdm. 2. Log in as a normal user. 3. Lock screen with ctrl+alt+l (I'm running Ubuntu 15.10). 4. Weigh self. Weigh self + cat. Find books approximately equal to 10 lbs, and various household items to simulate cat paws (I used two large nail clippers, a fat key, and a bottle opener). 5. Put items on keyboard, avoiding function keys, backspace, and enter. Place books on top of household items. 6. Wait 1 hour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1538615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966348] Re: seahorse crashed with SIGSEGV in g_main_context_dispatch()
*** This bug is a duplicate of bug 1963837 *** https://bugs.launchpad.net/bugs/1963837 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1963837, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1966348/+attachment/5572730/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1966348/+attachment/5572732/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1966348/+attachment/5572735/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1966348/+attachment/5572736/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1966348/+attachment/5572737/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1966348/+attachment/5572738/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1966348/+attachment/5572739/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1963837 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to seahorse in Ubuntu. https://bugs.launchpad.net/bugs/1966348 Title: seahorse crashed with SIGSEGV in g_main_context_dispatch() Status in seahorse package in Ubuntu: New Bug description: Just booted up. And this message showed. Reporting the error as its occuring on 22.04 beta build. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: seahorse 41.0-2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:21:06 2022 ExecutablePath: /usr/bin/seahorse InstallationDate: Installed on 2022-03-06 (18 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) ProcCmdline: /usr/bin/seahorse --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_AU:en LANG=en_AU.UTF-8 SegvAnalysis: Segfault happened at: 0x7f0d0d6cc73e:movl $0x1,0xa8(%rax) PC (0x7f0d0d6cc73e) ok source "$0x1" ok destination "0xa8(%rax)" (0x56433f045fcb) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: seahorse StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 ?? () from /lib/x86_64-linux-gnu/libavahi-client.so.3 ?? () from /lib/x86_64-linux-gnu/libavahi-glib.so.1 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: seahorse crashed with SIGSEGV in g_main_context_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/1966348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966345] Re: gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist()
*** This bug is a duplicate of bug 1945430 *** https://bugs.launchpad.net/bugs/1945430 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1945430, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1966345/+attachment/5572720/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1966345/+attachment/5572722/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1966345/+attachment/5572725/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1966345/+attachment/5572726/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1966345/+attachment/5572727/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1966345/+attachment/5572728/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1966345/+attachment/5572729/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1945430 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1966345 Title: gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist() Status in gnome-session package in Ubuntu: New Bug description: I'm unsure how this happened; probably upon reboot, because I didn't particularly notice any crashes. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Mar 24 14:11:42 2022 ExecutablePath: /usr/libexec/gnome-session-binary InstallationDate: Installed on 2022-03-22 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220321) ProcCmdline: /usr/libexec/gnome-session-binary --autostart /usr/share/gdm/greeter/autostart ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7f60fe98e483 : mov (%rax),%rdi PC (0x7f60fe98e483) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%rdi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-session StacktraceTop: g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_by_name () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () ?? () g_hash_table_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-session-binary crashed with SIGSEGV in g_signal_emit_valist() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1966345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966340] [NEW] Dock icon menu at wrong location and does not go away
Public bug reported: Right-click on the thunderbird dock icon produces the dock icon menu at the top of the screen and not right next to the dock icon. The dock icon menu will stay there regardless if I try to activate a menu item or activate another window, etc. The only thing that will make the menu go away is to press the key to see all the windows. After pressing again, the menu will go away. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.7.0+build2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laza 3005 F pulseaudio BuildID: 20220305171341 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:55:35 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-06 (77 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.1.254 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.76 metric 600 192.168.42.0/24 dev wg0 proto kernel scope link src 192.168.42.100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.7.0/20220305171341 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3000KGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.24:svnLENOVO:pn20N3000KGE:pvrThinkPadT490:rvnLENOVO:rn20N3000KGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3000KGE dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1966340 Title: Dock icon menu at wrong location and does not go away Status in thunderbird package in Ubuntu: New Bug description: Right-click on the thunderbird dock icon produces the dock icon menu at the top of the screen and not right next to the dock icon. The dock icon menu will stay there regardless if I try to activate a menu item or activate another window, etc. The only thing that will make the menu go away is to press the key to see all the windows. After pressing again, the menu will go away. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.7.0+build2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laza 3005 F pulseaudio BuildID: 20220305171341 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:55:35 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @
[Desktop-packages] [Bug 1966339] Re: Dock icon still shown after exit with many window indicatros (red dots)
Screenshot of the dock area with the thunderbird dock icon ** Attachment added: "Screenshot of the dock area with the thunderbird dock icon" https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1966339/+attachment/5572682/+files/202203242251-screenshot.png -- 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/1966339 Title: Dock icon still shown after exit with many window indicatros (red dots) Status in thunderbird package in Ubuntu: New Bug description: After closing thunderbird successfully, the dock icon is still shown with many window indicators (red dots along the icon). It's not possible to start thunderbird again from that dock icon. It's possible to start thunderbird from a shell though. I have not seen this behaviour with any other app. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.7.0+build2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laza 3005 F pulseaudio BuildID: 20220305171341 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:44:30 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-06 (77 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.1.254 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.76 metric 600 192.168.42.0/24 dev wg0 proto kernel scope link src 192.168.42.100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.7.0/20220305171341 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3000KGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.24:svnLENOVO:pn20N3000KGE:pvrThinkPadT490:rvnLENOVO:rn20N3000KGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3000KGE dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1966339/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966339] [NEW] Dock icon still shown after exit with many window indicatros (red dots)
Public bug reported: After closing thunderbird successfully, the dock icon is still shown with many window indicators (red dots along the icon). It's not possible to start thunderbird again from that dock icon. It's possible to start thunderbird from a shell though. I have not seen this behaviour with any other app. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.7.0+build2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laza 3005 F pulseaudio BuildID: 20220305171341 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:44:30 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2022-01-06 (77 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 192.168.1.254 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 192.168.1.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.1.76 metric 600 192.168.42.0/24 dev wg0 proto kernel scope link src 192.168.42.100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=91.7.0/20220305171341 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2021 dmi.bios.release: 1.75 dmi.bios.vendor: LENOVO dmi.bios.version: N2IET97W (1.75 ) dmi.board.asset.tag: Not Available dmi.board.name: 20N3000KGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrN2IET97W(1.75):bd10/09/2021:br1.75:efr1.24:svnLENOVO:pn20N3000KGE:pvrThinkPadT490:rvnLENOVO:rn20N3000KGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20N3_BU_Think_FM_ThinkPadT490: dmi.product.family: ThinkPad T490 dmi.product.name: 20N3000KGE dmi.product.sku: LENOVO_MT_20N3_BU_Think_FM_ThinkPad T490 dmi.product.version: ThinkPad T490 dmi.sys.vendor: LENOVO ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- 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/1966339 Title: Dock icon still shown after exit with many window indicatros (red dots) Status in thunderbird package in Ubuntu: New Bug description: After closing thunderbird successfully, the dock icon is still shown with many window indicators (red dots along the icon). It's not possible to start thunderbird again from that dock icon. It's possible to start thunderbird from a shell though. I have not seen this behaviour with any other app. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thunderbird 1:91.7.0+build2-0ubuntu0.21.10.1 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laza 3005 F pulseaudio BuildID: 20220305171341 CasperMD5CheckResult: pass Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:44:30 2022 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:359 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate:
[Desktop-packages] [Bug 1859899] Re: Please add a ZFS gui
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-disk-utility (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1859899 Title: Please add a ZFS gui Status in gnome-disk-utility package in Ubuntu: Confirmed Bug description: Right now the only way is with CLI. I do know the CLI methods but simple operations that I'd like to be able to see visually, like the RAID array or the allocated drives with ZFS, pools, datasets etc would all be nicely placed in a GUI that would double as an input to modify them. There are GUI's that exist on Ubuntu for non-ZFS volumes, but since Ubuntu is moving towards ZFS as a standard it only makes sense that a GUI would be created for such tasks. It's nice to see things like your currently configured cron jobs, like scrubs and disk usage etc.. A GUI for ZFS would be a tremendous advance in terms of expediency, utility, and ease of use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1859899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966334] [NEW] GLVND: Set current thread state to NULL in teardown
Public bug reported: A new fix has been merged into the libglvnd repo at https://gitlab.freedesktop.org/glvnd/libglvnd This change fixes an issue where if eglReleaseThread gets externally called after the EGL destructor, a double free occurs due to the threadState that eglReleaseThread checks is not null being not null despite being freed by the destuctor. The change makes the threadState null in the destructor to fix this. Can this make it into the libs in 20.04 LTS? Source package where the issue is encountered: https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2 ** Affects: libglvnd (Ubuntu) Importance: Undecided Status: New ** Description changed: A new fix has been merged into the libglvnd repo at https://gitlab.freedesktop.org/glvnd/libglvnd - This change fixes an issue where if eglReleaseThread gets externally - called after the EGL destructor, a double free occurs due to some - values that eglReleaseThread checks not getting set to null in the - destructor. + This change fixes an issue where if eglReleaseThread gets externally called after the EGL destructor, a double free occurs due to the threadState that eglReleaseThread checks is not null being not null despite being freed by the destuctor. + The change makes the threadState null in the destructor to fix this. Can this make it into the libs in 20.04 LTS? Source package where the issue is encountered: https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libglvnd in Ubuntu. https://bugs.launchpad.net/bugs/1966334 Title: GLVND: Set current thread state to NULL in teardown Status in libglvnd package in Ubuntu: New Bug description: A new fix has been merged into the libglvnd repo at https://gitlab.freedesktop.org/glvnd/libglvnd This change fixes an issue where if eglReleaseThread gets externally called after the EGL destructor, a double free occurs due to the threadState that eglReleaseThread checks is not null being not null despite being freed by the destuctor. The change makes the threadState null in the destructor to fix this. Can this make it into the libs in 20.04 LTS? Source package where the issue is encountered: https://launchpad.net/ubuntu/+source/libglvnd/1.3.2-1~ubuntu0.20.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1966334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966330] Re: gnome-control-center crashed with SIGSEGV while adding google account in settings
*** This bug is a duplicate of bug 1965702 *** https://bugs.launchpad.net/bugs/1965702 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1965702, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1966330/+attachment/5572632/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1966330/+attachment/5572634/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1966330/+attachment/5572638/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1966330/+attachment/5572639/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1966330/+attachment/5572640/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1966330/+attachment/5572641/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1966330/+attachment/5572642/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1965702 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1966330 Title: gnome-control-center crashed with SIGSEGV while adding google account in settings Status in gnome-control-center package in Ubuntu: New Bug description: Trying to add google account via Settings -> Online accounts and it crashes as soon I press on 'Google'. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu8 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 20:56:32 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-21 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) ProcCmdline: gnome-control-center SegvAnalysis: Segfault happened at: 0x7ff73d3d930b:mov0x8,%rax PC (0x7ff73d3d930b) ok source "0x8" (0x0008) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libwebkit2gtk-4.0.so.37 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /lib/x86_64-linux-gnu/libwayland-server.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966330/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966130] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1966130/+attachment/5572627/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1966130 Title: xdg-desktop-portal crashed with SIGSEGV in map_pid_if_needed() Status in xdg-desktop-portal package in Ubuntu: New Bug description: This crash happens while starting Epiphany. Despite the crash, the browser seems to work correctly. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:58:47 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2020-02-26 (755 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x564faad74421:mov0x8(%rax),%rcx PC (0x564faad74421) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966130] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1966130/+attachment/5572628/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1966130/+attachment/5572319/+files/CoreDump.gz ** Changed in: xdg-desktop-portal (Ubuntu) Importance: Undecided => Medium ** Summary changed: - xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic() + xdg-desktop-portal crashed with SIGSEGV in map_pid_if_needed() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1966130 Title: xdg-desktop-portal crashed with SIGSEGV in map_pid_if_needed() Status in xdg-desktop-portal package in Ubuntu: New Bug description: This crash happens while starting Epiphany. Despite the crash, the browser seems to work correctly. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:58:47 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2020-02-26 (755 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x564faad74421:mov0x8(%rax),%rcx PC (0x564faad74421) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966130] xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic()
StacktraceTop: map_pid_if_needed (app_info=, pid=, error=0x7faa717f96e8) at src/realtime.c:65 map_pid_if_needed (app_info=0x7faa60003ff0, pid=pid@entry=0x7faa717f96f4, error=error@entry=0x7faa717f96e8) at src/realtime.c:58 handle_make_thread_realtime_with_pid (object=, invocation=0x7faa6c03a500, process=, thread=6, priority=5) at src/realtime.c:124 ffi_call_unix64 () at ../src/x86/unix64.S:105 ffi_call_int (cif=, fn=, rvalue=, avalue=, closure=) at ../src/x86/ffi64.c:672 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1966130 Title: xdg-desktop-portal crashed with SIGSEGV in map_pid_if_needed() Status in xdg-desktop-portal package in Ubuntu: New Bug description: This crash happens while starting Epiphany. Despite the crash, the browser seems to work correctly. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:58:47 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2020-02-26 (755 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x564faad74421:mov0x8(%rax),%rcx PC (0x564faad74421) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966130] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1966130/+attachment/5572626/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1966130 Title: xdg-desktop-portal crashed with SIGSEGV in map_pid_if_needed() Status in xdg-desktop-portal package in Ubuntu: New Bug description: This crash happens while starting Epiphany. Despite the crash, the browser seems to work correctly. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: xdg-desktop-portal 1.14.1-1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:58:47 2022 ExecutablePath: /usr/libexec/xdg-desktop-portal InstallationDate: Installed on 2020-02-26 (755 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225.4) ProcCmdline: /usr/libexec/xdg-desktop-portal SegvAnalysis: Segfault happened at: 0x564faad74421:mov0x8(%rax),%rcx PC (0x564faad74421) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! destination "%rcx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xdg-desktop-portal StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libffi.so.8 ?? () from /lib/x86_64-linux-gnu/libffi.so.8 g_cclosure_marshal_generic () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: xdg-desktop-portal crashed with SIGSEGV in g_cclosure_marshal_generic() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal/+bug/1966130/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966115] Re: wrong icon used with the new branding
This bug was fixed in the package gnome-initial-setup - 42.0.1-1ubuntu1 --- gnome-initial-setup (42.0.1-1ubuntu1) jammy; urgency=medium * Resynchronize with Debian. Remaining changes: + debian/control.in: - Build-Depends on libsnapd-glib-dev, libsoup2.4-dev, libsysmetrics-dev + Add Ubuntu-specific patches: - 0001-Make-summary-page-explicitly-request-navigation-butt.patch - 0001-Ensure-stamp-file-if-the-user-quit-the-wizard.patch - 0001-Add-Ubuntu-mode-with-special-pages.patch - 0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch - 0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch - 0007-goa-adjust-description-to-not-mention-email-or-conta.patch - Don-t-show-Facebook-in-Ubuntu.patch - 0008-Ubuntu-location-default.patch - ubuntu_newuser_wizard.patch: + revert the new upstream behaviour of not using the wizard for existing users since it has a purpose in Ubuntu -- Sebastien Bacher Thu, 24 Mar 2022 16:23:11 +0100 ** Changed in: gnome-initial-setup (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1966115 Title: wrong icon used with the new branding Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: Since the updated ubuntu branding has landed, the icon isn't just the logo. See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1966115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966328] [NEW] Xorg freeze
Public bug reported: sometimes my pc freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Mankas permeso: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 16:16:46 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:10b0] InstallationDate: Installed on 2022-01-23 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic root=UUID=b5b63f0c-74df-4fe8-9cf0-a1eaa29c1260 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA 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.:bvrE200HA.300:bd06/01/2016:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: E dmi.product.name: E200HA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1966328 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: sometimes my pc freezes ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-105.119-generic 5.4.174 Uname: Linux 5.4.0-105-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Mankas permeso: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 16:16:46 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GpuHangFrequency: Very infrequently GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1043:10b0] InstallationDate: Installed on 2022-01-23 (60 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-105-generic root=UUID=b5b63f0c-74df-4fe8-9cf0-a1eaa29c1260 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC.
[Desktop-packages] [Bug 1917185] Re: Nextcloud settings window does not get decorated with window control buttons
The Next Cloud declares its windows as modal. _NET_WM_STATE(ATOM) = _NET_WM_STATE_MODAL This is a little unusual, since modals should be used for dialog boxes. That said, the Yaru Metacity theme set the geometry for modal windows as having no buttons. I will re-instate the window buttons for modal windows in Yaru. ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-mate-artwork (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-mate-artwork (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Also affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Changed in: yaru-theme (Ubuntu) Status: New => In Progress ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Medium ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: ubuntu-mate-artwork (Ubuntu) Status: In Progress => Invalid -- 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/1917185 Title: Nextcloud settings window does not get decorated with window control buttons Status in ubuntu-mate-artwork package in Ubuntu: Invalid Status in yaru-theme package in Ubuntu: In Progress Bug description: Ubuntu Mate 21.04 daily build fresh install today. Selected "Redmond" layout. Installed nextcloud-desktop and connected to my server. Clicked on the nextcloud icon in the panel and selected "settings". What should happen: - Nextcloud settings app should appear with close/minimise/restore buttons What actually happens: - Nextcloud settings app appears without these buttons. Has to be closed via the task list on the dock. mate-window-applets-common 20.04.0-1 nextcloud-desktop 3.1.1-1 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-window-applets-common 20.04.0-1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: MATE Date: Sat Feb 27 23:46:33 2021 InstallationDate: Installed on 2021-02-27 (0 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210227) PackageArchitecture: all SourcePackage: mate-window-applets UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-artwork/+bug/1917185/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966317] gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
StacktraceTop: pthread_setschedparam () from /tmp/apport_sandbox_k30w_mg7/lib/x86_64-linux-gnu/libc.so.6 ?? () ?? () ?? () ?? () ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() Status in gvfs package in Ubuntu: New Bug description: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966317] Re: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
I think this is causing bug 1965652. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() Status in gvfs package in Ubuntu: New Bug description: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966316] Re: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor()
*** This bug is a duplicate of bug 1962761 *** https://bugs.launchpad.net/bugs/1962761 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1962761, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1966316/+attachment/5572575/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1966316/+attachment/5572577/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1966316/+attachment/5572581/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1966316/+attachment/5572582/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1966316/+attachment/5572583/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1966316/+attachment/5572584/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1966316/+attachment/5572585/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1962761 nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966316 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() Status in nautilus package in Ubuntu: New Bug description: Nautilis crashed in background ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: nautilus 1:42~rc-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 17:08:59 2022 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2022-01-07 (76 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220106) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7fdf39fb0a88 : cmp %rax,(%rbx) PC (0x7fdf39fb0a88) ok source "%rax" ok destination "(%rbx)" (0x00012590) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: nautilus StacktraceTop: gtk_widget_get_ancestor () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: nautilus crashed with SIGSEGV in gtk_widget_get_ancestor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: evince42.1-1 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.43.90-1ubuntu1 nautilus-share0.7.3-2ubuntu4 python3-nautilus 1.2.3-3.1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1966316/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966317] [NEW] gvfsd-fuse crashed with SIGABRT in __pthread_setname_np()
Public bug reported: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash impish need-amd64-retrace third-party-packages ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1966317 Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() Status in gvfs package in Ubuntu: New Bug description: I encountered this crash during a dist-upgrade from impish to jammy, i.e. running `do-release-upgrade --devel-release`. My desktop session crashed, and my VM can no longer boot the desktop (but I can ssh still). ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: gvfs-fuse 1.47.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckMismatches: ./boot/grub/grub.cfg CasperMD5CheckResult: fail Date: Thu Mar 24 12:10:04 2022 ExecutablePath: /usr/libexec/gvfsd-fuse ExecutableTimestamp: 1615801987 InstallationDate: Installed on 2022-02-02 (49 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcCmdline: /usr/libexec/gvfsd-fuse /run/user/1000/gvfs -f -o big_writes ProcCwd: /home/nr ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: gvfs StacktraceTop: __pthread_setname_np (th=1251, name=0x6 ) at ./nptl/pthread_setname.c:32 ?? () Title: gvfsd-fuse crashed with SIGABRT in __pthread_setname_np() UpgradeStatus: Upgraded to impish on 2022-03-24 (0 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1966317/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966091] Re: Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic
Same here, I have a Lenovo X13 Gen1 notebook with an AMD 4750U Ryzen processor. The integrated sound chip works without problem, but when using the sound card in the Lenovo USB dock, the problem appears. Rebooted several times but the problem persists. Downgrading to the 5.13.0-35 kernel removes the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1966091 Title: Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a recent update to linux-image-5.13.0-37-generic, I started experiencing random noises about every five seconds. After rebooting into linux-image-5.13.0-35-generic, the noises were gone. Some details that I've noticed: 1. When launching pulseaudio manually, not as a daemon, the problem disappears. 2. If I set the log-level in /etc/pulse/daemon.conf to debug and reload it, the log has a lot of: Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA! Which roughly correspond with the noises. 3. The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa force-reload" doesn't seem to help. Only a kernel downgrade does. 4. This happens both in Firefox (where I first noticed it) as well as in Totem and in system sounds. 5. I tried to report the bug using "ubuntu-bug audio", but it showed me six inputs of which three looked the same, and for each of them it told me that it pulseaudio wasn't configured to use it. I'm ready to collect logs and other info within the next days. Additional Info $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description: Ubuntu 20.04.4 LTS Release: 20.04 Codename: focal $ apt-cache policy linux-image-generic-hwe-20.04 linux-image-generic-hwe-20.04: Installed: 5.13.0.37.42~20.04.22 Candidate: 5.13.0.37.42~20.04.22 Version table: *** 5.13.0.37.42~20.04.22 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 5.4.0.26.32 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages $ apt-cache policy pulseaudio pulseaudio: Installed: 1:13.99.1-1ubuntu3.13 Candidate: 1:13.99.1-1ubuntu3.13 Version table: *** 1:13.99.1-1ubuntu3.13 500 500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.99.1-1ubuntu3.8 500 500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages 1:13.99.1-1ubuntu3 500 500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966059] Re: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound
I also use a HyperX USB-Audio headset with my Ubuntu 21.10, and recently noticed random pops and cracks in the audio output. I have tried recording these noises using Audacity, but it is apparently not possible. I also tried my headset on a different PC and OS and the issue was not present there, so I assume that the headset works correctly. When I found this bug report, I have checked that I am using Kernel version 5.13.0-37.42. After I restarted my PC and selected the previous Kernel, version 5.13.0-35.40, the issue went away. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1966059 Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Confirmed Bug description: I can rollback to old kernel and audio works fine there. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pekka 2097 F pulseaudio /dev/snd/controlC2: pekka 2097 F pulseaudio /dev/snd/controlC0: pekka 2097 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:59:30 2022 InstallationDate: Installed on 2022-01-05 (76 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Sound successful Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_PulseAudioLog: maalis 23 12:56:55 ubuntu dbus-daemon[1217]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' (uid=126 pid=1429 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") maalis 23 12:57:06 ubuntu systemd[1408]: pulseaudio.service: Deactivated successfully. maalis 23 12:57:17 ubuntu systemd[1408]: pulseaudio.socket: Deactivated successfully. Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx: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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966059] Re: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1966059 Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: Confirmed Bug description: I can rollback to old kernel and audio works fine there. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pekka 2097 F pulseaudio /dev/snd/controlC2: pekka 2097 F pulseaudio /dev/snd/controlC0: pekka 2097 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 12:59:30 2022 InstallationDate: Installed on 2022-01-05 (76 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Sound successful Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic Symptom_PulseAudioLog: maalis 23 12:56:55 ubuntu dbus-daemon[1217]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' (uid=126 pid=1429 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") maalis 23 12:57:06 ubuntu systemd[1408]: pulseaudio.service: Deactivated successfully. maalis 23 12:57:17 ubuntu systemd[1408]: pulseaudio.socket: Deactivated successfully. Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/17/2020 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3103 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B450-F GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx: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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
** No longer affects: ubuntu-drivers-common (Ubuntu) ** No longer affects: ubuntu-drivers-common (Ubuntu Jammy) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964923 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in OEM Priority Project: New Status in update-notifier package in Ubuntu: Confirmed Status in update-notifier source package in Jammy: Confirmed Bug description: This bug occurred after install of Ubuntu Mate Jammy daily ISO 15-03-2022 Test machine Dell Optiplex 7060 in UEFI+secure boot mode. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: update-notifier-common 3.192.51 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Mar 15 10:21:14 2022 ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages InstallationDate: Installed on 2022-03-15 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220315) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages'] PythonDetails: N/A SourcePackage: update-notifier Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966206] Re: external display not detected
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1966206 Title: external display not detected Status in xorg package in Ubuntu: New Bug description: 1) Description: Ubuntu 20.04.3 LTS Release: 20.04 2) N: Unable to locate package pkgname 3) My current issue is the external display not being detected, but I don't know how it will behave, given the different issues, at different boots, being that the repairs/updates from the recovery session may have changed something, don't know. The timeline regarding the issue(s): My laptop screen started showing what looked like a broken screen when after booting, while on the log in screen (I could not see it). I shut down and the started again, entered recovery mode (the newer version), chose to recover, went to boot, after login saw the same broken screen on the laptop and nothing on the external. Shut down, start, and back to login screen, rebooted from there (as per instructed somewhere along the process, don't remember where, something like "if you can't go in, reboot from login menu").This time the laptop screen remained unusable but was working on the external monitor. Had the laptop working for hours and then it froze. Shut down, start and the same thing, broken laptop screen, this time no external monitor recognized, as before. Shut down, start and now, for the first time the laptop screen works but the external monitor is not recognized. Changing the hdmi cable from a usb-c hub to the hdmi port, the screen brightness got a lot dimmer, but nothing on the settings->display menu. My current issue is the external display not being detected, but I don't know how it will behave, given the different issues, at different boots, being that the repairs/updates from the recovery session may have changed something, don't know. 4) External monitor recognized and working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 12:51:10 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: hid-apple, 1.0, 5.13.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a43] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3a3f] InstallationDate: Installed on 2021-11-30 (113 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82B5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=fd06b914-e9cb-4b39-b897-5f9c9a75fb82 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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/ubuntu/+source/xorg/+bug/1966206/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to
[Desktop-packages] [Bug 1944113]
*** Bug 147888 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1944113 Title: Many UI elements (list box, drop down) don't work at all in kf5 environment Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Fix Released Bug description: Many UI elements (list box, drop down) don't work at all in kf5 environment. This makes LO unusable. For example, try to insert a table from standard toolbar in LO Writer – nothing inserted. Same happens with other drop down elements (styles, font family, font size, font color, font highlight, etc). Bug reports at LO's bug tracker: https://bugs.documentfoundation.org/show_bug.cgi?id=144037 https://bugs.documentfoundation.org/show_bug.cgi?id=144562 https://gerrit.libreoffice.org/c/core/+/122116 Operating System: Kubuntu 20.04 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.11.0-34-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4310U CPU @ 2.00GHz Memory: 7,7 GiB Version: 7.2.1.2 / LibreOffice Community Build ID: 20(Build:2) CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: kf5 (cairo+xcb) Locale: hu-HU (hu_HU.UTF-8); UI: hu-HU Ubuntu package version: 1:7.2.1~rc2-0ubuntu0.20.04.1~lo3 Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1944113/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966206] [NEW] external display not detected
You have been subscribed to a public bug: 1) Description: Ubuntu 20.04.3 LTS Release: 20.04 2) N: Unable to locate package pkgname 3) My current issue is the external display not being detected, but I don't know how it will behave, given the different issues, at different boots, being that the repairs/updates from the recovery session may have changed something, don't know. The timeline regarding the issue(s): My laptop screen started showing what looked like a broken screen when after booting, while on the log in screen (I could not see it). I shut down and the started again, entered recovery mode (the newer version), chose to recover, went to boot, after login saw the same broken screen on the laptop and nothing on the external. Shut down, start, and back to login screen, rebooted from there (as per instructed somewhere along the process, don't remember where, something like "if you can't go in, reboot from login menu").This time the laptop screen remained unusable but was working on the external monitor. Had the laptop working for hours and then it froze. Shut down, start and the same thing, broken laptop screen, this time no external monitor recognized, as before. Shut down, start and now, for the first time the laptop screen works but the external monitor is not recognized. Changing the hdmi cable from a usb-c hub to the hdmi port, the screen brightness got a lot dimmer, but nothing on the settings->display menu. My current issue is the external display not being detected, but I don't know how it will behave, given the different issues, at different boots, being that the repairs/updates from the recovery session may have changed something, don't know. 4) External monitor recognized and working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 12:51:10 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: hid-apple, 1.0, 5.13.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation Device [10de:1f99] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3a43] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev c6) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:3a3f] InstallationDate: Installed on 2021-11-30 (113 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: LENOVO 82B5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=fd06b914-e9cb-4b39-b897-5f9c9a75fb82 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:skuLENOVO_MT_82B5_BU_idea_FM_Legion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- external display not detected https://bugs.launchpad.net/bugs/1966206 You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761844] Re: Very large emojis displayed in subject line and in the email list
Launchpad has imported 76 comments from the remote bug at https://bugzilla.mozilla.org/show_bug.cgi?id=1390015. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-08-14T02:31:20+00:00 naught101 wrote: Created attachment 8896820 Screenshot_20170814_122746.png User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0 Build ID: 20170807221116 Steps to reproduce: Open a mail folder that includes an email with emoji characters in the subject line. Actual results: Huge get displayed over the top of the mail list. See attached screen shot. The truck appears far too large in the message list. It also appears in the subject line in the mail view panes. Expected results: The truck should be the correct size. I guess this may be a font issue? Thunderbird 52.2.1 on Kde Neon user edition (based on *buntu 16.04 LTS). Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/0 On 2017-08-14T09:10:23+00:00 Jorgk-bmo wrote: Could you please check the message source and paste the subject line here so we can try it and see how large our truck gets. I've never seen it on Windows. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/1 On 2017-08-15T07:31:52+00:00 naught101 wrote: Subject: =?UTF-8?Q?=F0=9F=9A=9A_ORDER_SENT:_TETRIS_NINTENDO_GAME...?= Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/2 On 2017-08-15T07:55:13+00:00 Jorgk-bmo wrote: Created attachment 8897323 emoji.eml - Sample mail with emoji in subject Thanks, works fine for me, I see a truck which has about the height of the text "ORDER SENT". I guess this is a Linux Font problem. Richard, can you reproduce this with the attached e-mail? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/3 On 2017-08-15T08:08:49+00:00 Richard Marti wrote: Tested it on Mint 18.2, Ubuntu 17.4 and Fedora 26. All show a tiny truck and not like at naught. I tested it with TB 57 and 56 as I have no 52 on these systems, but this should be no difference for this issue. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/4 On 2017-08-24T04:32:06+00:00 naught101 wrote: I had to wipe my root partition and re-install over the weekend. I now have 52.2.1 installed on Kubuntu 17.04 beta, and the problem does not appear. I guess perhaps it was caused by some kind of library mis-match in KDE Neon? Anyway, may as well close this. Others can re-open if it seems necessary.. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/5 On 2017-08-27T12:28:51+00:00 Jorgk-bmo wrote: *** Bug 1394133 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/6 On 2017-08-27T12:34:02+00:00 Jorgk-bmo wrote: *** Bug 1390879 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/7 On 2017-08-27T12:38:53+00:00 agentcobra wrote: same problem for me under gnome-shell Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/8 On 2018-02-08T16:28:44+00:00 Jorgk-bmo wrote: *** Bug 1436363 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/9 On 2018-03-09T21:57:18+00:00 Jorgk-bmo wrote: *** Bug 1444099 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/10 On 2018-03-26T09:06:15+00:00 Jorgk-bmo wrote: *** Bug 1448708 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1761844/comments/11 On 2018-03-26T12:03:45+00:00 Petr-nehez
[Desktop-packages] [Bug 1966306] [NEW] Update to 98.0.2
Public bug reported: https://www.mozilla.org/en-US/firefox/98.0.2/releasenotes/ ** Affects: firefox (Ubuntu) Importance: Undecided Status: Fix Released ** Changed in: firefox (Ubuntu) Status: New => Fix Released -- 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/1966306 Title: Update to 98.0.2 Status in firefox package in Ubuntu: Fix Released Bug description: https://www.mozilla.org/en-US/firefox/98.0.2/releasenotes/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966306/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956835] Re: zsys cleanup of /boot should be reevaluated
** Package changed: initramfs-tools (Ubuntu) => zsys (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1956835 Title: zsys cleanup of /boot should be reevaluated Status in zsys package in Ubuntu: New Bug description: After updating the system, rebooted and this error appeared. Fixed a problem related to /boot/grub/grubenv - "Error in environment" and grub-common.service by providing absolute path to grub-editenv. /boot/grub/grubenv was full of 0x0, rather than 0x2323 as it has now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.24 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 3520 F pulseaudio CasperMD5CheckResult: skip Date: Sat Jan 8 17:37:06 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-12 (422 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8470p PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2018 dmi.bios.release: 15.113 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.71 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU3109W10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 66.56 dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470p dmi.product.sku: C3Q91UC#ABU dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1956835/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956835] [NEW] zsys cleanup of /boot should be reevaluated
You have been subscribed to a public bug: After updating the system, rebooted and this error appeared. Fixed a problem related to /boot/grub/grubenv - "Error in environment" and grub-common.service by providing absolute path to grub-editenv. /boot/grub/grubenv was full of 0x0, rather than 0x2323 as it has now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187.24 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alistair 3520 F pulseaudio CasperMD5CheckResult: skip Date: Sat Jan 8 17:37:06 2022 Dependencies: ErrorMessage: installed linux-firmware package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-11-12 (422 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP EliteBook 8470p PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_x1by5v@/vmlinuz-5.11.0-44-generic root=ZFS=rpool/ROOT/ubuntu_x1by5v ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 SourcePackage: initramfs-tools Title: package linux-firmware 1.187.24 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2018 dmi.bios.release: 15.113 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.71 dmi.board.name: 179B dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.38 dmi.chassis.asset.tag: CNU3109W10 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 66.56 dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.71:bd04/12/2018:br15.113:efr66.56:svnHewlett-Packard:pnHPEliteBook8470p:pvrA1029D1102:skuC3Q91UC#ABU:rvnHewlett-Packard:rn179B:rvrKBCVersion42.38:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 8470p dmi.product.sku: C3Q91UC#ABU dmi.product.version: A1029D1102 dmi.sys.vendor: Hewlett-Packard ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal rls-jj-incoming -- zsys cleanup of /boot should be reevaluated https://bugs.launchpad.net/bugs/1956835 You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966221] [NEW] I can't start it
Public bug reported: when I use the command "gnome-extensions-app" in command line ,it will crash and report "Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:32:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-09 (42 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966221 Title: I can't start it Status in gnome-shell package in Ubuntu: New Bug description: when I use the command "gnome-extensions-app" in command line ,it will crash and report "Segmentation fault (core dumped)" ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell-extension-prefs 42~beta-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 22:32:21 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-02-09 (42 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) RelatedPackageVersions: mutter-common 42~beta-1ubuntu2 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/1966221/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965740] Re: BlueZ 5.64 release
This bug was fixed in the package bluez - 5.64-0ubuntu1 --- bluez (5.64-0ubuntu1) jammy; urgency=medium * New upstream release 5.64 (LP: #1965740): - Fix issue with handling A2DP discover procedure. - Fix issue with media endpoint replies and SetConfiguration. - Fix issue with HoG queuing events before report map is read. - Fix issue with HoG and read order of GATT attributes. - Fix issue with HoG and not using UHID_CREATE2 interface. - Fix issue with failed scanning for 5 minutes after reboot. * Drop upstreamed patches: - hog-Fix-read-order-of-attributes.patch - media-Fix-crash-when-endpoint-replies-with-an-error-to-Se.patch - gdbus-Emit-InterfacesAdded-of-parents-objects-first.patch * Refreshed patches: - ubuntu_error_restart.patch -- Daniel van Vugt Thu, 24 Mar 2022 14:30:38 +0800 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1965740 Title: BlueZ 5.64 release Status in bluez package in Ubuntu: Fix Released Bug description: http://www.bluez.org/release-of-bluez-5-64/ At least for 22.10, but maybe for 22.04 too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1965740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
did you enable focal-proposed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT 1.2.4-1ubuntu0.1 UPSTREAM BUG https://sourceforge.net/p/pcmanfm/bugs/1089/ ADDITIONAL NOTES Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) seem to have the same problems. This is probably at least rooted in a GTK2 bug: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710 To further assert this, note that there is
[Desktop-packages] [Bug 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait
libwnck3 40.1 reverts "pager: do not change workspace size from size_allocate" that fixes this issue. - https://gitlab.gnome.org/GNOME/libwnck/-/commit/8191f080c0c0b2471f329d4bee329487a2b37729 - https://gitlab.gnome.org/GNOME/libwnck/-/commit/7fab141ba787cecb576b732c9182b006453d82f4 Options are: - Upload libwnck3 40.1 to Jammy - Include commit 8191f080c0c0b2471f329d4bee329487a2b37729 as a patch in libwnck 40.0 package. ** Changed in: libwnck3 (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1947420 Title: Buggish interface @ workstation panels previews when using dual portrait Status in MATE Desktop: New Status in libwnck3 package in Ubuntu: Confirmed Status in mate-panel package in Ubuntu: Confirmed Bug description: ...Freshly upgraded to 21.10 using the same OS that I used to open most of my previous video glitches ever... Using 2x monitor in portrait mode, the preview panel/widget(?) located at the bottom right side shows 2 things wrong: 1. The "Workspace 1" preview is very elongated when compared to not only all of it's previous incarnations (from 14.04 to 21.10) but also has an inconsistent size when compared to it's neighbouring "Workspace 2". Expectation: both 1 and 2 should be sized identically. 2. When hovering the mouse cursor on "Workspace 2" only it's left portion will highlight. Expectation: both monitors of "2" should highlight See enclosed picture. To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1947420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1947420] Re: Buggish interface @ workstation panels previews when using dual portrait
** No longer affects: ubuntu-mate -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwnck3 in Ubuntu. https://bugs.launchpad.net/bugs/1947420 Title: Buggish interface @ workstation panels previews when using dual portrait Status in MATE Desktop: New Status in libwnck3 package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Confirmed Bug description: ...Freshly upgraded to 21.10 using the same OS that I used to open most of my previous video glitches ever... Using 2x monitor in portrait mode, the preview panel/widget(?) located at the bottom right side shows 2 things wrong: 1. The "Workspace 1" preview is very elongated when compared to not only all of it's previous incarnations (from 14.04 to 21.10) but also has an inconsistent size when compared to it's neighbouring "Workspace 2". Expectation: both 1 and 2 should be sized identically. 2. When hovering the mouse cursor on "Workspace 2" only it's left portion will highlight. Expectation: both monitors of "2" should highlight See enclosed picture. To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1947420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922276] Re: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output
As seb128 explained, this is an issue with libvte-2.91-0 and is scheduled to be addressed in 0.68 and work arounds do exist. ** Changed in: mate-terminal (Ubuntu) Status: Confirmed => Invalid ** No longer affects: mate-desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1922276 Title: Select All (Shift+Ctrl+A) followed by Copy (Shift+Ctrl+C) copies only visible part of terminal output Status in mate-terminal package in Ubuntu: Invalid Status in vte2.91 package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu MATE 21.04 installed (or use Live session) 2. Launch MATE Terminal 3. Enable infinite history (Edit - Profile Preferences - Scrolling, Scrollback - Unlimited) 4. Execute command with long output such as `journalctl | cat` 5. Select Edit - Select All (or press ++), then Edit - Copy (or press ++) 6. Open Pluma text editor and paste just copied terminal output Expected results: * whole terminal output is copied - staring by `user@host:~$ journalctl | cat` and ending by `user@host:~$` Actual results: * only last 15 lines were copied (depends on terminal size) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 1 17:35:47 2021 LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-terminal/+bug/1922276/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926256] Re: Pasted text in the terminal is always highlighted and selected
** Changed in: vte2.91 (Ubuntu) Status: Confirmed => Invalid ** Changed in: bash (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1926256 Title: Pasted text in the terminal is always highlighted and selected Status in bash package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in mate-terminal package in Ubuntu: Invalid Status in readline package in Ubuntu: Confirmed Status in vte2.91 package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu 21.04 installed 2. Launch terminal 3a. Execute some command, select this command to copy it, then paste command 3b. Paste some command from clipboard to terminal Expected result: * pasted command is not highlighted and is not selected Actual result: * pasted command is selected and highlighted ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mate-terminal 1.24.1-1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Apr 27 09:43:56 2021 InstallationDate: Installed on 2021-04-23 (3 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: mate-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1926256/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854383] Re: Extra window decorations are created on windows with client-side decorations.
This issue is caused by `mate-maximus` which is part of the `mate- netboot` package. `mate-netboot` doesn't get much upstream development attention so unlikely to fixed in the near future. Ubuntu MATE provides several resolution-efficient panel layouts, so removing `mate-netbook` from Ubuntu MATE is the best option for addressing this issue. mate-netbook was removed from ubuntu-mate-meta 1.281: - https://launchpad.net/ubuntu/+source/ubuntu-mate-meta/1.281 ** Changed in: marco (Ubuntu) Status: New => Invalid ** Changed in: gtk+3.0 (Ubuntu) Status: Confirmed => Invalid ** Also affects: mate-netbook (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate ** Also affects: ubuntu-mate-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-mate-meta (Ubuntu) Assignee: (unassigned) => Martin Wimpress (flexiondotorg) ** Changed in: ubuntu-mate-meta (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-mate-meta (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1854383 Title: Extra window decorations are created on windows with client-side decorations. Status in gtk+3.0 package in Ubuntu: Invalid Status in marco package in Ubuntu: Invalid Status in mate-netbook package in Ubuntu: New Status in ubuntu-mate-meta package in Ubuntu: Fix Released Bug description: Steps to reproduce after a minimal/full install of Ubuntu MATE: 1. Start up a Gtk3 application with a header bar (tested with Gnome Software) or a browser (such as Firefox) without using a standard window title bar that saves the position and size of the window before it was closed. 2. Maximize the application window, then close it without changing the window size 3. Relaunch the application and resize/unmaximize it After this, dummy window decorations will be created around the window. This issue has been tested on a Dell XPS 9570 and using Gnome Boxes 3.34. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1854383/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Since this machine has all-in-one in chassis type, only enabled off-load mode and disabled RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Since this machine has all-in-one in chassis type, only
enabled off-load mode and disabled RTD3.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
Fix Released
Status in nvidia-prime source package in Focal:
Fix Committed
Status in nvidia-prime source package in Hirsute:
Won't Fix
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
subprocess.call(['prime-select', 'on-demand'])
except:
pass
# Create the override file for gpu-manager
with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
f.write('# File created by ubuntu-drivers\n')
```
---
[Impact]
* Ubuntu will set GPU mode to performance as default which may use more power
* User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
* According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Test Plan]
* Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU
driver. After the installation, reboot the system. Execute "prime-select query"
should get "on-demand"
* Old GPU (which supported by nvidia-390 only) will keep in performance
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
* On non-laptop machine. Can set GPU mode to on-demand
* On laptop with GPU in runtime PM support list. Set GPU mode to on-demand
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
[Where problems could occur]
* With GPU supported RTD3 not able enable runtime PM on non-laptop.
But based on the Nvidia README, this case shall not happened.
[Other Info]
Changelogs:
nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)
[ Alberto Milone ]
* prime-select:
- Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
- on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
- Use bootvga detection when last_gfx_boot
is not available.
- Don't check the current profile when setting
a profile (LP: #1946476).
- Handle BrokenPipeError (LP: #1965520).
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Since this machine has all-in-one in chassis type, only enabled off-load mode and disabled RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications
I have updated my docker image to use ubuntu 20.04 and I still see this error with eclipse when running UI SWTBot tests. I get the following error [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. java: ../../src/xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/1782984 Title: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications Status in libx11 package in Ubuntu: Fix Released Status in libx11 source package in Bionic: Fix Committed Status in libx11 source package in Focal: Fix Committed Status in libx11 source package in Groovy: Won't Fix Bug description: [Impact] There is a race in libx11 causing applications to randomly abort. It's not trivial to reproduce, but there are enough duplicates that this deserves an SRU to bionic & focal. [Fix] Backport a commit from upstream: From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001 From: Frediano Ziglio Date: Wed, 29 Jan 2020 09:06:54 + Subject: [PATCH] Fix poll_for_response race condition In poll_for_response is it possible that event replies are skipped and a more up to date message reply is returned. This will cause next poll_for_event call to fail aborting the program. This was proved using some slow ssh tunnel or using some program to slow down server replies (I used a combination of xtrace and strace). How the race happens: - program enters into poll_for_response; - poll_for_event is called but the server didn't still send the reply; - pending_requests is not NULL because we send a request (see call to append_pending_request in _XSend); - xcb_poll_for_reply64 is called from poll_for_response; - xcb_poll_for_reply64 will read from server, at this point server reply with an event (say sequence N) and the reply to our last request (say sequence N+1); - xcb_poll_for_reply64 returns the reply for the request we asked; - last_request_read is set to N+1 sequence in poll_for_response; - poll_for_response returns the response to the request; - poll_for_event is called (for instance from another poll_for_response); - event with sequence N is retrieved; - the N sequence is widen, however, as the "new" number computed from last_request_read is less than N the number is widened to N + 2^32 (assuming last_request_read is still contained in 32 bit); - poll_for_event enters the nested if statement as req is NULL; - we compare the widen N (which now does not fit into 32 bit) with request (which fits into 32 bit) hitting the throw_thread_fail_assert. To avoid the race condition and to avoid the sequence to go back I check again for new events after getting the response and return this last event if present saving the reply to return it later. To test the race and the fix it's helpful to add a delay (I used a "usleep(5000)") before calling xcb_poll_for_reply64. Original patch written by Frediano Ziglio, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34 Reworked primarily for readability by Peter Hutterer, see https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53 Signed-off-by: Peter Hutterer bionic needs another commit so that the real fix applies. [Test case] It's a race condition, the SRU sponsor (tjaalton) does not have a test case for this, but the bug subscribers seem to. [Where things could go wrong] In theory there might be a case where a race still happens, but since this has been upstream for a year now with no follow-up commits, it's safe to assume that there are no regressions. -- STEPS TO REPRODUCE == The bug seems to occur when clicking on a file or folder. It is random and difficult to provide clear steps to reproduce. It is, however, a common situation. EXPECTED RESULTS pcmanfm works without problem. ACTUAL RESULTS == All pcmanfm windows become unresponsive, though background processes (e.g. copying) may continue without problem. with the same error message in ~/.cache/lxsession/LXDE/run.log: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. pcmanfm: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6 ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload (note the timestamp on the message will vary) AFFECTED VERSIONS = 1.2.5-3ubuntu1 NOT
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
The attachment "nvidia-495-fix.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Status in xorg-server source package in Jammy: Fix Committed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966115] Re: wrong icon used with the new branding
Jeremy, I think the bug refers to the launcher icon, not the accounts one ** Package changed: gnome-online-accounts (Ubuntu) => gnome-initial- setup (Ubuntu) ** Changed in: gnome-initial-setup (Ubuntu) Importance: Medium => High ** Changed in: gnome-initial-setup (Ubuntu) Assignee: (unassigned) => Sebastien Bacher (seb128) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1966115 Title: wrong icon used with the new branding Status in gnome-initial-setup package in Ubuntu: Triaged Bug description: Since the updated ubuntu branding has landed, the icon isn't just the logo. See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1966115/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923305] Re: LibreOffice 6.4 OpenType Features unusable
The reason it wasn’t backported is stated upstream: https://gerrit.libreoffice.org/c/core/+/92591 We don’t backport patches that introduce translatable strings, because of the additional work that it would impose to volunteer translators. Just use a newer series of the software. ** Changed in: libreoffice (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1923305 Title: LibreOffice 6.4 OpenType Features unusable Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Won't Fix Bug description: When using OpenType features (Format - Character - Feature) from a capable font like EB Garamond 12, LibreOffice automatically enables a fractional style, which essentially makes all numerics unusable, and there's no obvious way to disable this in the GUI once you've opened the Features dialog. There are two workaround, as all OpenType features get disabled when selecting another font, and back again. And, of course, one can remove :frac=1 manually from the font name field. This has however been fixed in LibreOffice 7.0 onward, but somehow wasn't cherrypicked into 6.4.x, even though the change seems trivial: https://github.com/LibreOffice/core/commit/d28c9d56df8a2629321bda116a6d2dcfa587d160 Please consider including this cherrypick in a future package for Ubuntu Focal. The patch won't apply directly due to a filename typo getting corrected, which needs to be uncorrected in the patch: vcl/source/font/OpenTypeFeatureDefinitionList.cxx vcl/source/font/OpenTypeFeatureDefinitonList.cxx To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1923305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1935063] Re: gnome-initial-setup: cannot build on RISC-V
That's fixed now, https://bugs.launchpad.net/ubuntu/+source/gnome- initial-setup/42~beta-1ubuntu1/+build/23176125 ** Changed in: gnome-initial-setup (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-initial-setup in Ubuntu. https://bugs.launchpad.net/bugs/1935063 Title: gnome-initial-setup: cannot build on RISC-V Status in gnome-initial-setup package in Ubuntu: Fix Released Bug description: version: 40.2-1ubuntu1 platform: RISC-V gnome-initial-setup cannot be built on RISC-V due to a dependency on libsysmetrics-dev. libsysmetrics-dev is built from source package ubuntu-report. Building of ubuntu-report fails because the Go language does not support -buildmode=c-shared on RISC-V yet. The dependency is due to our patch 0001-Add-Ubuntu-mode-with-special- pages.patch. The report implemented in gis-ubuntu-report-page.c is used to send system info to Canonical. Feasible solutions would be * remove the report completely * disable it for RISC-V Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1935063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966190] Re: Do not break Firefox with snap
** Changed in: firefox (Ubuntu) Status: New => Won't Fix -- 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/1966190 Title: Do not break Firefox with snap Status in firefox package in Ubuntu: Won't Fix Bug description: Do not break Firefox with snap. Snap is horrendously slow and it breaks programs. Users do not want snap. Users hate snap. Stop forcing it on users. Stop creating transitional packages to trick users into installing snap versions. This is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966187] Re: crash xorg
Ok, I manage to do step 2. There were two links. Here it is the direction: https://errors.ubuntu.com/user/5daba6cd6c1de01072b18f684b9c63f7377a5c384123d52f78286ea072e3e6183789589e311daebef2abeab83519bd813eb1aaaefc244da95bc540b9a62283eb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1966187 Title: crash xorg Status in xorg-server package in Ubuntu: Incomplete Bug description: Randomly, system (Ubuntu 20.04) crashes and login screen appears. apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status file at var/crash says: ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:15:15 2022 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1639491253 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/tidop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcMaps: 55742c038000-55742c075000 r--p 08:12 12976830 /usr/lib/xorg/Xorg 55742c075000-55742c207000 r-xp 0003d000 08:12 12976830 /usr/lib/xorg/Xorg 55742c207000-55742c28 r--p 001cf000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28-55742c284000 r--p 00247000 08:12 12976830 /usr/lib/xorg/Xorg 55742c284000-55742c28f000 rw-p 0024b000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28f000-55742c2cd000 rw-p 00:00 0 55742d4a5000-557439da6000 rw-p 00:00 0 [heap] 7fe3c000-7fe3c0021000 rw-p 00:00 0 7fe3c0021000-7fe3c400 ---p 00:00 0 7fe3c400-7fe3c4021000 rw-p 00:00 0 7fe3c4021000-7fe3c800 ---p 00:00 0 7fe3c800-7fe3c8021000 rw-p 00:00 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 10:15:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:2489] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:4667] InstallationDate: Installed on 2022-02-11 (40 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=bcea4888-7b37-4ace-a9da-8a0a74fce240 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 10.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1017 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B560-F GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB560-FGAMINGWIFI:rvrRev1.xx: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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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:
[Desktop-packages] [Bug 1966190] [NEW] Do not break Firefox with snap
Public bug reported: Do not break Firefox with snap. Snap is horrendously slow and it breaks programs. Users do not want snap. Users hate snap. Stop forcing it on users. Stop creating transitional packages to trick users into installing snap versions. This is wrong. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- 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/1966190 Title: Do not break Firefox with snap Status in firefox package in Ubuntu: New Bug description: Do not break Firefox with snap. Snap is horrendously slow and it breaks programs. Users do not want snap. Users hate snap. Stop forcing it on users. Stop creating transitional packages to trick users into installing snap versions. This is wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966187] Re: crash xorg
Hi, when I do ubuntu-bug /var/crash/_usr_lib_xorg_Xorg.1000.crash it appears a window saying Ubuntu 20.04 has experimented an internal error. I don't know where to look at the ID here, but in 'show details' I see: ExecutablePath /usr/lib/xorg/Xorg Package xserver-sorg-core 2:1.20.13-1ubuntu1~20.04.2 ProblemaType Crash Title Xorg assert failure: Xorg: ../../../../../../include/privates.h:121:dixGetPrivateAddr:Assertion `key->initialized' failed. . . . BootLog Error: [Errno 13] Permit denied: '/var/log/boot.log' ... And some others. I also press the send button. On the other hand, I cannot open whoopsie-id file due to permit issues. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1966187 Title: crash xorg Status in xorg-server package in Ubuntu: Incomplete Bug description: Randomly, system (Ubuntu 20.04) crashes and login screen appears. apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status file at var/crash says: ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:15:15 2022 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1639491253 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/tidop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcMaps: 55742c038000-55742c075000 r--p 08:12 12976830 /usr/lib/xorg/Xorg 55742c075000-55742c207000 r-xp 0003d000 08:12 12976830 /usr/lib/xorg/Xorg 55742c207000-55742c28 r--p 001cf000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28-55742c284000 r--p 00247000 08:12 12976830 /usr/lib/xorg/Xorg 55742c284000-55742c28f000 rw-p 0024b000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28f000-55742c2cd000 rw-p 00:00 0 55742d4a5000-557439da6000 rw-p 00:00 0 [heap] 7fe3c000-7fe3c0021000 rw-p 00:00 0 7fe3c0021000-7fe3c400 ---p 00:00 0 7fe3c400-7fe3c4021000 rw-p 00:00 0 7fe3c4021000-7fe3c800 ---p 00:00 0 7fe3c800-7fe3c8021000 rw-p 00:00 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 10:15:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:2489] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:4667] InstallationDate: Installed on 2022-02-11 (40 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=bcea4888-7b37-4ace-a9da-8a0a74fce240 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 10.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1017 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B560-F GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB560-FGAMINGWIFI:rvrRev1.xx: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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
[Desktop-packages] [Bug 1966180] Re: Creates junk directories in $HOME
*** This bug is a duplicate of bug 1958813 *** https://bugs.launchpad.net/bugs/1958813 ** This bug has been marked a duplicate of bug 1958813 [snap] I have on clean install some weird folder /home/user/Downloads/firefox.tmp/ -- 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/1966180 Title: Creates junk directories in $HOME Status in firefox package in Ubuntu: New Bug description: Upon upgrading to Ubuntu 22.04, Firefox creates junk $HOME/firefox.tmp and $HOME/snap directories. This is a very rude and discourteous thing to do. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Mar 24 09:41:43 2022 InstallationDate: Installed on 2020-07-14 (617 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-03-18 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
Many thanks Daniel & Mazen! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Status in xorg-server source package in Jammy: Fix Committed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966187] Re: crash xorg
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** 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/1966187 Title: crash xorg Status in xorg-server package in Ubuntu: Incomplete Bug description: Randomly, system (Ubuntu 20.04) crashes and login screen appears. apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status file at var/crash says: ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:15:15 2022 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1639491253 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/tidop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcMaps: 55742c038000-55742c075000 r--p 08:12 12976830 /usr/lib/xorg/Xorg 55742c075000-55742c207000 r-xp 0003d000 08:12 12976830 /usr/lib/xorg/Xorg 55742c207000-55742c28 r--p 001cf000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28-55742c284000 r--p 00247000 08:12 12976830 /usr/lib/xorg/Xorg 55742c284000-55742c28f000 rw-p 0024b000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28f000-55742c2cd000 rw-p 00:00 0 55742d4a5000-557439da6000 rw-p 00:00 0 [heap] 7fe3c000-7fe3c0021000 rw-p 00:00 0 7fe3c0021000-7fe3c400 ---p 00:00 0 7fe3c400-7fe3c4021000 rw-p 00:00 0 7fe3c4021000-7fe3c800 ---p 00:00 0 7fe3c800-7fe3c8021000 rw-p 00:00 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 10:15:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:2489] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:4667] InstallationDate: Installed on 2022-02-11 (40 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=bcea4888-7b37-4ace-a9da-8a0a74fce240 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 10.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1017 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B560-F GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB560-FGAMINGWIFI:rvrRev1.xx: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
[Desktop-packages] [Bug 1966187] [NEW] crash xorg
Public bug reported: Randomly, system (Ubuntu 20.04) crashes and login screen appears. apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status file at var/crash says: ProblemType: Crash Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 23 17:15:15 2022 DistroRelease: Ubuntu 20.04 ExecutablePath: /usr/lib/xorg/Xorg ExecutableTimestamp: 1639491253 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcCwd: /home/tidop ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcMaps: 55742c038000-55742c075000 r--p 08:12 12976830 /usr/lib/xorg/Xorg 55742c075000-55742c207000 r-xp 0003d000 08:12 12976830 /usr/lib/xorg/Xorg 55742c207000-55742c28 r--p 001cf000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28-55742c284000 r--p 00247000 08:12 12976830 /usr/lib/xorg/Xorg 55742c284000-55742c28f000 rw-p 0024b000 08:12 12976830 /usr/lib/xorg/Xorg 55742c28f000-55742c2cd000 rw-p 00:00 0 55742d4a5000-557439da6000 rw-p 00:00 0 [heap] 7fe3c000-7fe3c0021000 rw-p 00:00 0 7fe3c0021000-7fe3c400 ---p 00:00 0 7fe3c400-7fe3c4021000 rw-p 00:00 0 7fe3c4021000-7fe3c800 ---p 00:00 0 7fe3c800-7fe3c8021000 rw-p 00:00 0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Mar 24 10:15:01 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation Device [10de:2489] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:4667] InstallationDate: Installed on 2022-02-11 (40 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) MachineType: ASUS System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic root=UUID=bcea4888-7b37-4ace-a9da-8a0a74fce240 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/12/2021 dmi.bios.release: 10.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1017 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B560-F GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1017:bd07/12/2021:br10.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB560-FGAMINGWIFI:rvrRev1.xx: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: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1966187 Title: crash xorg Status in xorg package in Ubuntu: New Bug description: Randomly, system (Ubuntu 20.04) crashes and login screen appears. apt-cache policy xorg xorg: Instalados: 1:7.7+19ubuntu14 Candidato: 1:7.7+19ubuntu14 Tabla de versión: *** 1:7.7+19ubuntu14 500 500 http://es.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status file at var/crash says: ProblemType: Crash Architecture: amd64
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Check nvidia module parameter with "cat /proc/driver/nvidia/params | grep DynamicPowerManagement" and get result 2 which means GPU enabled with RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable
focal-proposed channel, install nvidia with "sudo ubuntu-drivers install
nvidia" then reboot system. Check system is in on-demand with "prime-
select query". Check nvidia module parameter with "cat
/proc/driver/nvidia/params | grep DynamicPowerManagement" and get result
2 which means GPU enabled with RTD3.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
Fix Released
Status in nvidia-prime source package in Focal:
Fix Committed
Status in nvidia-prime source package in Hirsute:
Won't Fix
Bug description:
RTD3 is a nvidia GPU feature to support runtime suspend.
On-demand would be a X offloading feature.
They are independent, according to discussion on
https://github.com/tseliot/ubuntu-drivers-common/issues/55.
Some parts need to be adjusted, e.g.
```
# If we are dealing with NVIDIA PRIME, and runtimepm
# is supported, enable it
if (os.path.isfile('/run/nvidia_runtimepm_supported') and
os.path.isfile('/usr/bin/prime-select')):
print('Trying to select the on-demand PRIME profile')
try:
subprocess.call(['prime-select', 'on-demand'])
except:
pass
# Create the override file for gpu-manager
with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f:
f.write('# File created by ubuntu-drivers\n')
```
---
[Impact]
* Ubuntu will set GPU mode to performance as default which may use more power
* User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not
supported
* According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Test Plan]
* Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU
driver. After the installation, reboot the system. Execute "prime-select query"
should get "on-demand"
* Old GPU (which supported by nvidia-390 only) will keep in performance
mode, refer LP:1957094. Execute "prime-select query" should get "nvidia"
* On non-laptop machine. Can set GPU mode to on-demand
* On laptop with GPU in runtime PM support list. Set GPU mode to on-demand
and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02"
[Where problems could occur]
* With GPU supported RTD3 not able enable runtime PM on non-laptop.
But based on the Nvidia README, this case shall not happened.
[Other Info]
Changelogs:
nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium
[ Jeremy Szu ]
* Set on-demand mode as default nvidia mode (LP: #1942307)
[ Alberto Milone ]
* prime-select:
- Detect chassis type and enable RTD3 only
on laptops (LP: #1942788).
- on-demand mode doesn't need to depend on
RTD3 (LP: #1942789).
- Use bootvga detection when last_gfx_boot
is not available.
- Don't check the current profile when setting
a profile (LP: #1946476).
- Handle BrokenPipeError (LP: #1965520).
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Check nvidia module parameter with "cat /proc/driver/nvidia/params | grep DynamicPowerManagement" and get result 2 which means GPU enabled with RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959995] Re: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46)
If you don't like to wait for the patch to be applied, here is what you can do (for focal): 1. mkdir xorg-server && cd xorg-server 2. git clone -b applied/ubuntu/focal-security https://git.launchpad.net/ubuntu/+source/xorg-server 3. cd xorg-server/debian/patches 4. wget https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1959995/+attachment/5572420/+files/nvidia-495-fix.patch 5. echo "nvidia-495-fix.patch" >> series 6. cd ../.. 7. dpkg-buildpackage -us -uc 8. cd .. 9. sudo dpkg -i ./*.deb 10. sudo systemctl reboot Done. Next you can install newer Nvidia drivers and there shouldn't be any issues. Note: This is the patch from https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 ** Patch added: "nvidia-495-fix.patch" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1959995/+attachment/5572420/+files/nvidia-495-fix.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1959995 Title: present: Crash in 'present_scmd_get_crtc' and 'present_flush' (NVIDIA 495.46) Status in X.Org X server: Unknown Status in xorg-server package in Ubuntu: Fix Committed Status in xorg-server source package in Focal: Confirmed Status in xorg-server source package in Impish: Confirmed Status in xorg-server source package in Jammy: Fix Committed Bug description: This bug causes xserver to crash when using newer Nvidia drivers (NVIDIA 495.46+) with Optimus. It's apparently triggered when using the MATE desktop environment. It has been noticed on xorg-server-21.1, but it's likely affecting version 1.20.13 as well. It has been fixed already, but could you please backport the fix? Patch that fixes it is here: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/841/diffs?commit_id=22d5818851967408bb7c903cb345b7ca8766094c The bug report at freedesktop.org is here: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275 Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1959995/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966178] Re: Screen-privacy couldn't work
@seb, It's buggy even on 5.17 kernel, we could not control from g-c-c. Thanks! -- 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/1966178 Title: Screen-privacy couldn't work Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c couldn't control it. From the GUI, I click 'Restrict Viewing Angle' on and off, there are no change at screen. From Fn+D, it could let screen change, and the GUI could follow the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859899] Re: Please add a ZFS gui
Hello Hello With the arrival of version 22.04, it is now certain that ZFS is a way to do an installation. It seems abnormal to me that gnome-disks keeps saying that ZFS is an unknown system and doesn't know how to mount it. Please do the needful quickly. Do not forget that the partition can be encrypted. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1859899 Title: Please add a ZFS gui Status in gnome-disk-utility package in Ubuntu: New Bug description: Right now the only way is with CLI. I do know the CLI methods but simple operations that I'd like to be able to see visually, like the RAID array or the allocated drives with ZFS, pools, datasets etc would all be nicely placed in a GUI that would double as an input to modify them. There are GUI's that exist on Ubuntu for non-ZFS volumes, but since Ubuntu is moving towards ZFS as a standard it only makes sense that a GUI would be created for such tasks. It's nice to see things like your currently configured cron jobs, like scrubs and disk usage etc.. A GUI for ZFS would be a tremendous advance in terms of expediency, utility, and ease of use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1859899/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966178] Re: Screen-privacy couldn't work
The kernel support landed in 5.17 only yes. Marco, do we have a way to hide the UI if the kernel support is missing? ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- 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/1966178 Title: Screen-privacy couldn't work Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c couldn't control it. From the GUI, I click 'Restrict Viewing Angle' on and off, there are no change at screen. From Fn+D, it could let screen change, and the GUI could follow the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966180] [NEW] Creates junk directories in $HOME
Public bug reported: Upon upgrading to Ubuntu 22.04, Firefox creates junk $HOME/firefox.tmp and $HOME/snap directories. This is a very rude and discourteous thing to do. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Mar 24 09:41:43 2022 InstallationDate: Installed on 2020-07-14 (617 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-03-18 (5 days ago) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966180 Title: Creates junk directories in $HOME Status in firefox package in Ubuntu: New Bug description: Upon upgrading to Ubuntu 22.04, Firefox creates junk $HOME/firefox.tmp and $HOME/snap directories. This is a very rude and discourteous thing to do. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Mar 24 09:41:43 2022 InstallationDate: Installed on 2020-07-14 (617 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-03-18 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1966180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840] Re: Spell checking more than one language in Firefox
** Changed in: firefox Status: In Progress => Fix Released ** Bug watch added: Mozilla Bugzilla #1760824 https://bugzilla.mozilla.org/show_bug.cgi?id=1760824 -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
Pushed by dmi...@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/264664a44f49 Support multiple dictionaries in mozISpellCheckingEngine.idl; r=smaug https://hg.mozilla.org/integration/autoland/rev/1af11d34c213 Support multiple hunspell instances in mozHunspell; r=smaug https://hg.mozilla.org/integration/autoland/rev/043d88291491 Support multiple dictionaries in mozSpellChecker; r=smaug https://hg.mozilla.org/integration/autoland/rev/4a3b7ee6a51e Support multiple dictionaries in RemoteSpellcheckEngine; r=smaug https://hg.mozilla.org/integration/autoland/rev/74f061f43c77 Support multiple dictionaries in EditorSpellCheck; r=smaug https://hg.mozilla.org/integration/autoland/rev/338485f1d803 Support multiple dictionaries in InlineSpellChecker; r=smaug,Gijs https://hg.mozilla.org/integration/autoland/rev/64b43b5b1bba Fix dictionary extension loading code in XPIProvider.jsm; r=smaug,extension-reviewers,mixedpuppy https://hg.mozilla.org/integration/autoland/rev/e86c493e43a4 Update unit tests for multiple dictionaries; r=smaug https://hg.mozilla.org/integration/autoland/rev/465a18abbd0e Add mochitest for multiple dictionaries; r=smaug -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
There's failures on test-verification with these changes, but there's failures on test-verification on these tests without the changes as well, e.g. https://treeherder.mozilla.org/jobs?repo=try=99fedcc1a058b3377c7def7938d3f27173edaee6 where I added some comments to trigger test-verification on the existing tests. Fixing https://bugzilla.mozilla.org/show_bug.cgi?id=1760824 should help make the tests less flaky. I've tried to improve them a bit as part of these changes as well. -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662840]
https://hg.mozilla.org/mozilla-central/rev/264664a44f49 https://hg.mozilla.org/mozilla-central/rev/1af11d34c213 https://hg.mozilla.org/mozilla-central/rev/043d88291491 https://hg.mozilla.org/mozilla-central/rev/4a3b7ee6a51e https://hg.mozilla.org/mozilla-central/rev/74f061f43c77 https://hg.mozilla.org/mozilla-central/rev/338485f1d803 https://hg.mozilla.org/mozilla-central/rev/64b43b5b1bba https://hg.mozilla.org/mozilla-central/rev/e86c493e43a4 https://hg.mozilla.org/mozilla-central/rev/465a18abbd0e -- 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/662840 Title: Spell checking more than one language in Firefox Status in Mozilla Firefox: Fix Released Status in firefox package in Ubuntu: Triaged Bug description: Binary package hint: firefox After upgrading to Ubuntu 10.10 x64 with Firefox 3.6.10 I lost Firefox capability to spell check for multiple languages in text forms. This is very annoying as I use two or three different languages in a single form when composing emails for example, and also switch between tabs/firefox windows to fill out forms in different languages, and now I have to switch between dictionaries back and forth. Never was an issue before. There is a need to set up multiple dictionaries/languages to be used at once for seamless spell check on a text form. Am I missing something? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: firefox 3.6.10+build1+nobinonly-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Mon Oct 18 21:59:46 2010 FirefoxPackages: firefox 3.6.10+build1+nobinonly-0ubuntu3 firefox-gnome-support 3.6.10+build1+nobinonly-0ubuntu3 firefox-branding 3.6.10+build1+nobinonly-0ubuntu3 abroswer N/A abrowser-branding N/A InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) ProcEnviron: LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: firefox To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/662840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966178] Re: Screen-privacy couldn't work
Cause the 5.15.0-23-generic couldn't support it, I used 5.17 mainline kernel. $ cat /proc/acpi/ibm/lcdshadow status: 0 commands: 0, 1 And after press the Fn + D, the screen display angle changed, and the content of /proc/acpi/ibm/lcdshadow is changed, and the GUI of 'Restrict Viewing Angle' is changed between on and off. Here is the bug for kernel. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966061 ** Tags added: oem-priority originate-from-1956808 sutton -- 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/1966178 Title: Screen-privacy couldn't work Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: New Bug description: On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c couldn't control it. From the GUI, I click 'Restrict Viewing Angle' on and off, there are no change at screen. From Fn+D, it could let screen change, and the GUI could follow the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965757] Re: Dark theme, text is not visible on axis due to similar color of background in Power Statistics app
** Changed in: gnome-power-manager (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1965757 Title: Dark theme, text is not visible on axis due to similar color of background in Power Statistics app Status in gnome-power-manager package in Ubuntu: New Bug description: When using a dark theme the data in the Power Statistics is barely visible because text color and background color are almost the same. Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Application: gnome-power-statistics To reproduce: - Switch to dark theme in Ubuntu appearance settings. - Open 'Power Statistics' app - Select 'Laptop battery' - Select 'History' tab - Text on both axes is not visible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-power-manager 3.32.0-2build1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Mar 21 13:49:14 2022 ExecutablePath: /usr/bin/gnome-power-statistics InstallationDate: Installed on 2022-03-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1965757/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966178] [NEW] Screen-privacy couldn't work
Public bug reported: On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c couldn't control it. >From the GUI, I click 'Restrict Viewing Angle' on and off, there are no change at screen. >From Fn+D, it could let screen change, and the GUI could follow the changes. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1956808 sutton -- 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/1966178 Title: Screen-privacy couldn't work Status in gnome-control-center package in Ubuntu: New Bug description: On ThinkPad X13 it supports 'Privacy Guard', but on jammy the g-c-c couldn't control it. From the GUI, I click 'Restrict Viewing Angle' on and off, there are no change at screen. From Fn+D, it could let screen change, and the GUI could follow the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1966178/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
