[Desktop-packages] [Bug 1942764] Re: Enable riscv64 build of mesa-opencl-icd
To be completely thorough here, `libhmsbeagle` needs either `mesa- opencl-icd` or some package that can provide `opencl-icd`. `pocl-opencl- icd` used to build on riscv64 and then fulfilled this dependency but some recent changes broke this package (currently investigating). So building `mesa-opencl-icd` is not mandatory for `libhmsbeagle` but as it builds fine on riscv64 , it should be enabled. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: New Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942791] Re: _has_integrated_gpu() needs to consider the desktop case
def _has_integrated_gpu(self):
status = False;
path = '/var/lib/ubuntu-drivers-common/last_gfx_boot'
if os.path.isfile(path):
with open(path, 'r') as f:
t = f.read()
if t.find('8086') != -1 or t.lower().find('10de') != -1:
status = True
f.close()
return status
---
According to the discussion with Alberto[1], we are agree to check sysfs (e.g.
vendor, chassis, etc..) instead.
https://chat.canonical.com/canonical/pl/buqmskei77bkucdqj9g7dwwxcy
--
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/1942791
Title:
_has_integrated_gpu() needs to consider the desktop case
Status in OEM Priority Project:
Confirmed
Status in nvidia-prime package in Ubuntu:
New
Bug description:
In recovery (from a storage) case, the /var/lib/ubuntu-drivers-
common/last_gfx_boot is empty. Thus, the _has_integrated_gpu() returns
false in I+N laptop case. In this case, there is a iGPU actually.
---
During the recovery, a worker executes ubuntu-drivers install.
The expected result is "on-demand" but it goes to "on" because
/var/lib/ubuntu-drivers-common/last_gfx_boot doesn't exist
`ubuntu-drivers install` calls `prime-select on-demand` calls
enable_profile() and then enable_profile() calls _has_integrated_gpu()
before switching mode.
Since _has_integrated_gpu() returns false, it won't switch nvidia mode
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1942791/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942828] Re: [Huawei MateBook X] Display driver is corrupted
description implies 5.8 HWE kernel worked; thus issue likely kernel related ** Package changed: xorg (Ubuntu) => linux (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/1942828 Title: [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works fine Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: display driver In the kernel 5.8.0-generic is work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 7 09:18:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Device [1e83:3e35] InstallationDate: Installed on 2021-06-20 (78 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HUAWEI MACHD-WXX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2021 dmi.bios.release: 1.18 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.18 dmi.board.asset.tag: N/A dmi.board.name: MACHD-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020: dmi.product.family: MateBook X dmi.product.name: MACHD-WXX9 dmi.product.sku: C170 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1027 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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/linux-hwe-5.11/+bug/1942828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942828] Re: [Huawei MateBook X] Display driver is corrupted
** Summary changed: - Display driver is corrupted + [Huawei MateBook X] Display driver is corrupted -- 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/1942828 Title: [Huawei MateBook X] Display is corrupted in kernel 5.11 but 5.8 works fine Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: display driver In the kernel 5.8.0-generic is work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 7 09:18:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Device [1e83:3e35] InstallationDate: Installed on 2021-06-20 (78 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HUAWEI MACHD-WXX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2021 dmi.bios.release: 1.18 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.18 dmi.board.asset.tag: N/A dmi.board.name: MACHD-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020: dmi.product.family: MateBook X dmi.product.name: MACHD-WXX9 dmi.product.sku: C170 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1027 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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/linux-hwe-5.11/+bug/1942828/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942828] [NEW] Display driver is corrupted
Public bug reported: display driver In the kernel 5.8.0-generic is work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 7 09:18:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Device [1e83:3e35] InstallationDate: Installed on 2021-06-20 (78 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HUAWEI MACHD-WXX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2021 dmi.bios.release: 1.18 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.18 dmi.board.asset.tag: N/A dmi.board.name: MACHD-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020: dmi.product.family: MateBook X dmi.product.name: MACHD-WXX9 dmi.product.sku: C170 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1027 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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 corruption 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/1942828 Title: Display driver is corrupted Status in xorg package in Ubuntu: New Bug description: display driver In the kernel 5.8.0-generic is work fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 7 09:18:00 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Device [1e83:3e35] InstallationDate: Installed on 2021-06-20 (78 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: HUAWEI MACHD-WXX9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=37779fb3-62b0-45d9-bd7f-dc9c3ea1f0ae ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2021 dmi.bios.release: 1.18 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.18 dmi.board.asset.tag: N/A dmi.board.name: MACHD-WXX9-PCB dmi.board.vendor: HUAWEI dmi.board.version: M1020 dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1020 dmi.ec.firmware.release: 1.18 dmi.modalias: dmi:bvnHUAWEI:bvr1.18:bd06/11/2021:br1.18:efr1.18:svnHUAWEI:pnMACHD-WXX9:pvrM1020:rvnHUAWEI:rnMACHD-WXX9-PCB:rvrM1020:cvnHUAWEI:ct10:cvrM1020: dmi.product.family: MateBook X dmi.product.name: MACHD-WXX9 dmi.product.sku: C170 dmi.product.version: M1020 dmi.sys.vendor: HUAWEI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1027 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-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.x
[Desktop-packages] [Bug 1942655] Re: Minimized windows stay ghosted on the background wallpaper
I would recommend reintroducing 4 extensions on the first day. If the bug returns then remove 2 of them. If the bug has not returned then add 2 more, and so on. After a few days you should be able to figure out exactly which extension was triggering the problem. Or just reintroduce them one by one. -- 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/1942655 Title: Minimized windows stay ghosted on the background wallpaper Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942824] Re: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf()
I wonder if the fix for bug 1870737 is what solved it... -- 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/1942824 Title: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/13b5b42983c1bf07a08dc6892f786589829ad85c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942824] Re: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf()
Zero crashes in 21.04 and later so consider it fixed. ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1942824 Title: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/13b5b42983c1bf07a08dc6892f786589829ad85c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942824] Re: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1942824 Title: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/13b5b42983c1bf07a08dc6892f786589829ad85c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942622] Re: Gnome control center displays tab crashes if you unplug all monitors
*** This bug is a duplicate of bug 1942824 *** https://bugs.launchpad.net/bugs/1942824 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 1942824, 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 1942824 gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf() -- 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/1942622 Title: Gnome control center displays tab crashes if you unplug all monitors Status in gnome-control-center package in Ubuntu: Incomplete Bug description: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed ps. Also tested this on Ubuntu 21.04 using a live USB stick and interestingly Gnome control center does not crash but freezes instead and has to be force quit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942824] Re: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf()
** Summary changed: - /usr/bin/gnome-control-center:11:__find_specmb:__vfprintf_internal:__vasprintf_internal:g_vasprintf:g_strdup_vprintf + gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf() -- 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/1942824 Title: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/13b5b42983c1bf07a08dc6892f786589829ad85c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942824] [NEW] gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf()
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/13b5b42983c1bf07a08dc6892f786589829ad85c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: eoan focal groovy -- 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/1942824 Title: gnome-control-center crashed with SIGSEGV in __find_specmb() from __vfprintf_internal() from __vasprintf_internal() from g_vasprintf() from g_strdup_vprintf() Status in gnome-control-center package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.38.3-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/13b5b42983c1bf07a08dc6892f786589829ad85c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942824/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942655] Re: problem after minimizing windows
** Tags added: amdgpu -- 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/1942655 Title: Minimized windows stay ghosted on the background wallpaper Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1942655] Re: problem after minimizing windows
Being all day trying to replicate the bug, with the extensions disabled, the bug was not replicated at any time, using the PC in a normal way, as at all times, I attach the extensions that I use, I do not deduce which can cause the bug . [image: image.png] El lun, 6 sept 2021 a las 8:46, Diego Iboy () escribió: > Hello good Morning > I attach the resulting txt. > > I have disabled the extensions, but I have not been able to replicate the > bug, I have to mention that it happens randomly throughout the day. With > which I will continue using it in this way until the end of the day to see > if it can be replicated. > > Greetings > > El dom, 5 sept 2021 a las 22:10, Daniel van Vugt (< > 1942...@bugs.launchpad.net>) escribió: > >> Also please run: >> >> lspci -kv > lspci.txt >> >> and attach the resulting text file here. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1942655 >> >> Title: >> problem after minimizing windows >> >> Status in GNOME Shell: >> Unknown >> Status in gnome-shell package in Ubuntu: >> Incomplete >> >> Bug description: >> Hello, the problem that I am presented with is basic, but quite >> annoying. >> At any time without any type of pattern, when minimizing a window (of >> any program), these remain as "background", and become part of the >> wallpaper. You do not interact with it but it remains static on the site. >> I attach an example. >> The only temporary solution that has worked for me is to log out, but >> it almost certainly happens again. >> I appreciate the help :) >> (The theme has nothing to do with it, it happens to me even though it >> is stock) >> >> ProblemType: Bug >> DistroRelease: Ubuntu 21.04 >> Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 >> ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 >> Uname: Linux 5.11.0-31-generic x86_64 >> ApportVersion: 2.20.11-0ubuntu65.1 >> Architecture: amd64 >> CasperMD5CheckResult: unknown >> CurrentDesktop: ubuntu:GNOME >> Date: Fri Sep 3 17:12:04 2021 >> DisplayManager: gdm3 >> InstallationDate: Installed on 2021-08-28 (6 days ago) >> InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 >> (20210209.1) >> RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 >> SourcePackage: gnome-shell >> UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions >> >> ** Attachment added: "image.png" https://bugs.launchpad.net/bugs/1942655/+attachment/5523354/+files/image.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1942655 Title: Minimized windows stay ghosted on the background wallpaper Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942655] Re: Minimized windows stay ghosted on the background wallpaper
** Summary changed: - problem after minimizing windows + Minimized windows stay ghosted on the background wallpaper -- 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/1942655 Title: Minimized windows stay ghosted on the background wallpaper Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()
** Tags added: regression-release -- 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/1942685 Title: pulseaudio crashed with SIGSEGV in _IceTransClose() Status in pulseaudio package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e --- Installing Xubuntu Impish daily ISO 04092021 After install I rebooted - applied updates and then rebooted again- the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() ) occurred after logging in. ProblemType: Crash DistroRelease: Ubuntu 21.10 Package: pulseaudio 1:15.0+dfsg1-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: kx 847 F pulseaudio CasperMD5CheckResult: pass Date: Sat Sep 4 16:43:45 2021 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2021-09-04 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal Signal: 11 SourcePackage: pulseaudio StacktraceTop: _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6 _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6 IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6 SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6 ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so Title: pulseaudio crashed with SIGSEGV in _IceTransClose() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V14-IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL: dmi.product.family: V14-IIL dmi.product.name: 82C4 dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL dmi.product.version: Lenovo V14-IIL dmi.sys.vendor: LENOVO separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942799] Re: Exiv2 creates out of range exception with XMP data
The code in question for both Pix and gthumb looks to be one of the FOR loops in "exiv2_read_metadata" in exiv2-utils.cpp, where this line... md->print().c_str() ...creates the out of range exception. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1942799 Title: Exiv2 creates out of range exception with XMP data Status in exiv2 package in Ubuntu: Confirmed Bug description: Applying the latest update to Exiv2 in both Pix and gThumb, images that contain XMP data will crash the given application. The issue looks to be when Xmp data is not able to properly handle the call to "c_str()". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1942799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942799] Re: Exiv2 creates out of range exception with XMP data
XMP data is commonly included in image metadata of images that have been exported from darktable. Opening such an image in gthumb causes a non- handled std::out_of_range exception in Exiv2::Xmpdatum::write. Finally, gthumb terminates with the message terminate called after throwing an instance of 'std::out_of_range' what(): basic_string::at: __n (which is 19) >= this->size() (which is 19) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1942799 Title: Exiv2 creates out of range exception with XMP data Status in exiv2 package in Ubuntu: Confirmed Bug description: Applying the latest update to Exiv2 in both Pix and gThumb, images that contain XMP data will crash the given application. The issue looks to be when Xmp data is not able to properly handle the call to "c_str()". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1942799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942799] Re: Exiv2 creates out of range exception with XMP data
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: exiv2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1942799 Title: Exiv2 creates out of range exception with XMP data Status in exiv2 package in Ubuntu: Confirmed Bug description: Applying the latest update to Exiv2 in both Pix and gThumb, images that contain XMP data will crash the given application. The issue looks to be when Xmp data is not able to properly handle the call to "c_str()". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1942799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942799] [NEW] Exiv2 creates out of range exception with XMP data
Public bug reported: Applying the latest update to Exiv2 in both Pix and gThumb, images that contain XMP data will crash the given application. The issue looks to be when Xmp data is not able to properly handle the call to "c_str()". ** Affects: exiv2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1942799 Title: Exiv2 creates out of range exception with XMP data Status in exiv2 package in Ubuntu: New Bug description: Applying the latest update to Exiv2 in both Pix and gThumb, images that contain XMP data will crash the given application. The issue looks to be when Xmp data is not able to properly handle the call to "c_str()". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1942799/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942797] Re: 21.04 - Printer uncooperative (And incohesive) behavior after PWR ON+OFF+ON
** Also affects: cups (Ubuntu) Importance: Undecided Status: New -- 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/1942797 Title: 21.04 - Printer uncooperative (And incohesive) behavior after PWR ON+OFF+ON Status in Ubuntu MATE: New Status in cups package in Ubuntu: New Bug description: On a clone desktop running 21.04-latest which has the following LAN printer connected to it: $ lpstat -p130 ↵ printer _xeroxofficetq1_ is idle. enabled since Mon 06 Sep 2021 01:33:46 PM printer C405 is idle. enabled since Mon 06 Sep 2021 01:33:46 PM printer Xerox-CommonXCPT is idle. enabled since Wed 21 Jul 2021 09:58:10 AM $ If/when my system is up and I power off the printer, leave it off for a few hours, replug the printer back, wait for it to boot and then print using that same system's firefox, it will not work. But if I open Libre Office Writer and print: then it shall print. Immediately after, going back to the firefox window and re-printing what has originally failed now prints too! Here is what /var/log/cups/ had to say (This happened around 5 minutes ago): $ cat access_log localhost - - [06/Sep/2021:00:00:01 -0400] "POST / HTTP/1.1" 200 349 Create-Printer-Subscriptions successful-ok localhost - - [06/Sep/2021:00:00:01 -0400] "POST / HTTP/1.1" 200 176 Create-Printer-Subscriptions successful-ok localhost - - [06/Sep/2021:10:22:53 -0400] "POST / HTTP/1.1" 401 186 Renew-Subscription successful-ok localhost - dd [06/Sep/2021:10:22:53 -0400] "POST / HTTP/1.1" 200 186 Renew-Subscription successful-ok localhost - - [06/Sep/2021:13:29:16 -0400] "POST /printers/C405 HTTP/1.1" 200 405871 Print-Job successful-ok localhost - - [06/Sep/2021:13:29:19 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 442 Create-Job successful-ok localhost - - [06/Sep/2021:13:29:19 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 466895 Send-Document successful-ok localhost - - [06/Sep/2021:13:31:37 -0400] "POST /printers/C405 HTTP/1.1" 200 405871 Print-Job successful-ok localhost - - [06/Sep/2021:13:31:40 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 442 Create-Job successful-ok localhost - - [06/Sep/2021:13:31:40 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 466823 Send-Document successful-ok localhost - - [06/Sep/2021:13:33:19 -0400] "POST /printers/C405 HTTP/1.1" 200 190 Create-Job successful-ok localhost - - [06/Sep/2021:13:33:19 -0400] "POST /printers/C405 HTTP/1.1" 200 1480 Send-Document successful-ok localhost - - [06/Sep/2021:13:33:22 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 396 Create-Job successful-ok localhost - - [06/Sep/2021:13:33:22 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 17334 Send-Document successful-ok localhost - - [06/Sep/2021:13:33:43 -0400] "POST /printers/C405 HTTP/1.1" 200 479195 Print-Job successful-ok localhost - - [06/Sep/2021:13:33:46 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 442 Create-Job successful-ok localhost - - [06/Sep/2021:13:33:46 -0400] "POST /printers/_xeroxofficetq1_ HTTP/1.1" 200 468503 Send-Document successful-ok $ cat page_log C405 dd 1115 [06/Sep/2021:13:29:19 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - _xeroxofficetq1_ lp 1116 [06/Sep/2021:13:29:38 -0400] total 0 - localhost PrtDrv-Rl0gMg - - C405 dd 1117 [06/Sep/2021:13:31:40 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - _xeroxofficetq1_ lp 1118 [06/Sep/2021:13:31:43 -0400] total 0 - localhost PrtDrv-Jtjdjo - - C405 dd 1119 [06/Sep/2021:13:33:22 -0400] total 0 - localhost Untitled 1 - - _xeroxofficetq1_ lp 1120 [06/Sep/2021:13:33:22 -0400] total 0 - localhost PrtDrv-RwY6Hm - - C405 dd 1121 [06/Sep/2021:13:33:46 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - _xeroxofficetq1_ lp 1122 [06/Sep/2021:13:33:46 -0400] total 0 - localhost PrtDrv-sH8aT0 - - $ date Mon 06 Sep 2021 01:38:54 PM EDT $ Rewinding back to the previous LOG, THIS is the entry that never went through and gave my printer an error: _xeroxofficetq1_ lp 1116 [06/Sep/2021:13:29:38 -0400] total 0 - localhost PrtDrv-Rl0gMg - - C405 dd 1117 [06/Sep/2021:13:31:40 -0400] total 0 - localhost Centre de retours en ligne na_letter_8.5x11in_borderless - While this is the blank print test I did off Writer which worked: _xeroxofficetq1_ lp 1118 [06/Sep/2021:13:31:43 -0400] total 0 - localhost PrtDrv-Jtjdjo - - C405 dd 1119 [06/Sep/2021:13:33:22 -0400] total 0 - localhost Untitled 1 - - While finally having retried printing the original document and... it worked! _xeroxofficetq1_ lp 1120 [06/Sep/2021:13:33:22 -0400] total 0 - localhost PrtDrv-RwY6Hm - - C405 dd 1121 [06/Sep/2021:13:33:46 -0400]
[Desktop-packages] [Bug 1942622] Re: Gnome control center displays tab crashes if you unplug all monitors
The link is: https://errors.ubuntu.com/oops/47a66160-0f28-11ec-b051-fa163e6cac46 -- 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/1942622 Title: Gnome control center displays tab crashes if you unplug all monitors Status in gnome-control-center package in Ubuntu: Incomplete Bug description: 1. Open gnome control center. 2. Open the "Displays" tab 3. Unplug ALL monitors 4. Plug a monitor back in. 5. Gnome Control center has crashed ps. Also tested this on Ubuntu 21.04 using a live USB stick and interestingly Gnome control center does not crash but freezes instead and has to be force quit. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 19:25:36 2021 InstallationDate: Installed on 2021-08-26 (7 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1942622/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942791] [NEW] _has_integrated_gpu() needs to consider the desktop case
Public bug reported: In recovery (from a storage) case, the /var/lib/ubuntu-drivers- common/last_gfx_boot is empty. Thus, the _has_integrated_gpu() returns false in I+N laptop case. In this case, there is a iGPU actually. --- During the recovery, a worker executes ubuntu-drivers install. The expected result is "on-demand" but it goes to "on" because /var/lib/ubuntu-drivers-common/last_gfx_boot doesn't exist `ubuntu-drivers install` calls `prime-select on-demand` calls enable_profile() and then enable_profile() calls _has_integrated_gpu() before switching mode. Since _has_integrated_gpu() returns false, it won't switch nvidia mode ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1942028 originate-from-1942041 stella ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Tags added: oem-priority originate-from-1942041 stella ** Tags added: originate-from-1942028 -- 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/1942791 Title: _has_integrated_gpu() needs to consider the desktop case Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Bug description: In recovery (from a storage) case, the /var/lib/ubuntu-drivers- common/last_gfx_boot is empty. Thus, the _has_integrated_gpu() returns false in I+N laptop case. In this case, there is a iGPU actually. --- During the recovery, a worker executes ubuntu-drivers install. The expected result is "on-demand" but it goes to "on" because /var/lib/ubuntu-drivers-common/last_gfx_boot doesn't exist `ubuntu-drivers install` calls `prime-select on-demand` calls enable_profile() and then enable_profile() calls _has_integrated_gpu() before switching mode. Since _has_integrated_gpu() returns false, it won't switch nvidia mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942791/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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] [NEW] On-demand and RTD3 need to be separated
Public bug reported:
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')
```
** Affects: oem-priority
Importance: High
Assignee: jeremyszu (os369510)
Status: Confirmed
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Assignee: (unassigned) => jeremyszu (os369510)
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Status: New => Confirmed
--
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/1942789
Title:
On-demand and RTD3 need to be separated
Status in OEM Priority Project:
Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
New
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')
```
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 1942788] [NEW] Nvidia doesn't support RTD3 on laptop
Public bug reported: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. ** Affects: oem-priority Importance: High Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed -- 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/1942788 Title: Nvidia doesn't support RTD3 on laptop Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1942655] Re: problem after minimizing windows
Hello good Morning I attach the resulting txt. I have disabled the extensions, but I have not been able to replicate the bug, I have to mention that it happens randomly throughout the day. With which I will continue using it in this way until the end of the day to see if it can be replicated. Greetings El dom, 5 sept 2021 a las 22:10, Daniel van Vugt (< 1942...@bugs.launchpad.net>) escribió: > Also please run: > > lspci -kv > lspci.txt > > and attach the resulting text file here. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1942655 > > Title: > problem after minimizing windows > > Status in GNOME Shell: > Unknown > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > Hello, the problem that I am presented with is basic, but quite annoying. > At any time without any type of pattern, when minimizing a window (of > any program), these remain as "background", and become part of the > wallpaper. You do not interact with it but it remains static on the site. > I attach an example. > The only temporary solution that has worked for me is to log out, but it > almost certainly happens again. > I appreciate the help :) > (The theme has nothing to do with it, it happens to me even though it is > stock) > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 > ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 > Uname: Linux 5.11.0-31-generic x86_64 > ApportVersion: 2.20.11-0ubuntu65.1 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: ubuntu:GNOME > Date: Fri Sep 3 17:12:04 2021 > DisplayManager: gdm3 > InstallationDate: Installed on 2021-08-28 (6 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions > > ** Attachment added: "lspci.txt" https://bugs.launchpad.net/bugs/1942655/+attachment/5523253/+files/lspci.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1942655 Title: problem after minimizing windows Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hello, the problem that I am presented with is basic, but quite annoying. At any time without any type of pattern, when minimizing a window (of any program), these remain as "background", and become part of the wallpaper. You do not interact with it but it remains static on the site. I attach an example. The only temporary solution that has worked for me is to log out, but it almost certainly happens again. I appreciate the help :) (The theme has nothing to do with it, it happens to me even though it is stock) ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 17:12:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-28 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-08-31 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1942655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 229343] Re: saned does not have permission to access the scanner
*** This bug is a duplicate of bug 236956 *** https://bugs.launchpad.net/bugs/236956 Ubuntu focal. I have the same problem >From what the MFP is defined as a printer. And therefore the group on the USB port is placed: lp So I am doing: usermor -G lp -a saned IT works. :))) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/229343 Title: saned does not have permission to access the scanner Status in sane-backends package in Ubuntu: Triaged Status in sane-backends source package in Hardy: Won't Fix Bug description: Starting with Hardy, my scanner device is no longer owned by the group "scanner", instead (AIUI) the PolicyKit / ConsoleKit /HAL scheme uses ACLs to allow the user with the active session access to the scanner. However this scheme does not permit the SANE Network Demon "saned" to access the scanner and hence other machines on the network can no longer access the scanner. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/229343/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932328] Re: Thunderbird under Wayland does not correctly close (or manage) windows
Like it was said before, this issue is probably not specific to Thunderbird. I get the same problem with ImageMagick ! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1932328 Title: Thunderbird under Wayland does not correctly close (or manage) windows Status in Mozilla Thunderbird: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: Using Ubuntu 21.04 (Hirsute) that starts in Wayland, by default. Thunderbird version: 78.11.0 with "gnome-support" package. Same problem in safe mode. Description: By default in this context, TB is a Wayland task. When opening a compose windows (or reply or transfer), sending mail apparently close the windows, but gnome shell continue to show multiple "points", as if multiple windows are still active. And after closing TB, it seems maintained in the same state, so it becomes impossible to relaunch it from the desk. But task manager of "looking glass" does not show it and it is possible to launch from terminal. Provisional solution: Modify .desktop file to launch with --display=:0 option, that force to use XWayland interface, as shown by xlsclients (for example). But it is actually a bug under Wayland context, that also badly interfer with many add-ons or extensions. To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1932328/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942764] [NEW] Enable riscv64 build of mesa-opencl-icd
Public bug reported: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1942764 Title: Enable riscv64 build of mesa-opencl-icd Status in mesa package in Ubuntu: New Bug description: Ubuntu release: impish Package version: 21.2.1-2ubuntu1 `mesa-opencl-icd` is needed for `libhmsbeagle` to be installable, so is it possible to enable this package as I have done here: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+sourcepub/12687486/+listing- archive-extra ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1942764/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942733] Re: Disk Capacity shows "Unknow" when installing OS on eMMC
Thanks Andy, I've included the bug reference in the changelog, which is a requirement of the SRU process, and uploaded ** Changed in: udisks2 (Ubuntu) Importance: Undecided => Low ** Changed in: udisks2 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1942733 Title: Disk Capacity shows "Unknow" when installing OS on eMMC Status in OEM Priority Project: New Status in udisks2 package in Ubuntu: Fix Released Bug description: [Impact] * This fix "Disk Capacity" in gnome-control-center shows "Unknown" if installing Focal on eMMC [Test Plan] * Install Focal on eMMC desktop or laptop. * Open "Settings" application and select "About" * Check the volume of "Disk Capacity" [Where problems could occur] * This changes eMMC's media removable property to false. * All the changes is in Hirsute, so only effect on Focal. [Other Info] * Upstream bug: https://github.com/storaged-project/udisks/pull/834 * Due to MediaRemoveable is false, gnome-control-center will skip this device and "Unknown" will show in "Disk Capacity" To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942733/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen
Well I'm less concerned with getting the old GPU to work (again just a test system trying to debug dual GPU in general) as I am getting my NEW GPU's on my workstation working in 21.04 and future releases. Right now Dual GPU is horribly broken and it's spans tons huge swathes of the system. My set up has been fine for years...though updates have slowly broken more and more. However 20.04 and newer completely break things. I'm not really down with having to buy a new computers to run my other GPU's or just ripping my GPU's out and tossing them and my screens aside because something / someone decided to break everything moving forward. I will say after some updates and tinkering I got 21.04 (XFCE) stable but lots of things are just broken/unusable. On a normal Ubuntu install for example launching anything on the other GPU's/Xscreens results in ignored theming, broken input and Win95 like Window smearing just to name a few problems. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1942738 Title: XOrg / nouveau - hard lockups and does not draw to screen Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Changing display settings hard locks the machine (no reisub save). Installing nouveau-firmware allows changes to be made without hard lock ups but the screen using nouveau draws the mouse cursor and will launch apps on it but does not draw anything on screen. Dmesg is flooded with nouveau and XOrg failure messages. Description: Ubuntu 21.04 Release: 21.04 xorg: Installed: 1:7.7+22ubuntu1 Candidate: 1:7.7+22ubuntu1 Version table: *** 1:7.7+22ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status nouveau-firmware: Installed: 20091212-0ubuntu1 Candidate: 20091212-0ubuntu1 Version table: *** 20091212-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 Packages 100 /var/lib/dpkg/status xserver-xorg-video-nouveau: Installed: 1:1.0.17-1 Candidate: 1:1.0.17-1 Version table: *** 1:1.0.17-1 500 500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Sep 5 23:52:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] [1019:2601] Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (prog-if 00 [VGA controller]) Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 250/350] [1092:0250] InstallationDate: Installed on 2021-04-07 (151 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer ASE380/AST180/APM8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: R01-B1 dmi.board.name: EM61SM/EM61PM dmi.board.vendor: Acer dmi.chassis.asset.tag: Asset tag number: at least 22 digits dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr: dmi.product.name: ASE380/AST180/APM8 dmi.product.version: R01-B1 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-e
[Desktop-packages] [Bug 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen
I also wish older GPUs were still supported but Nvidia makes it tricky. The open source "nouveau" driver is almost always buggy and the closed source drivers only ever support GPUs for a limited number of years (admittedly the Linux kernel driver model is to blame for that rather than Nvidia but being closed source is part of it). If there was anything we (Canonical) could do to improve the situation then we would. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1942738 Title: XOrg / nouveau - hard lockups and does not draw to screen Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-ati package in Ubuntu: New Status in xserver-xorg-video-nouveau package in Ubuntu: New Bug description: Changing display settings hard locks the machine (no reisub save). Installing nouveau-firmware allows changes to be made without hard lock ups but the screen using nouveau draws the mouse cursor and will launch apps on it but does not draw anything on screen. Dmesg is flooded with nouveau and XOrg failure messages. Description: Ubuntu 21.04 Release: 21.04 xorg: Installed: 1:7.7+22ubuntu1 Candidate: 1:7.7+22ubuntu1 Version table: *** 1:7.7+22ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status nouveau-firmware: Installed: 20091212-0ubuntu1 Candidate: 20091212-0ubuntu1 Version table: *** 20091212-0ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 Packages 500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 Packages 100 /var/lib/dpkg/status xserver-xorg-video-nouveau: Installed: 1:1.0.17-1 Candidate: 1:1.0.17-1 Version table: *** 1:1.0.17-1 500 500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sun Sep 5 23:52:43 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] [1019:2601] Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] [1002:6610] (prog-if 00 [VGA controller]) Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 250/350] [1092:0250] InstallationDate: Installed on 2021-04-07 (151 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer ASE380/AST180/APM8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2006 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: R01-B1 dmi.board.name: EM61SM/EM61PM dmi.board.vendor: Acer dmi.chassis.asset.tag: Asset tag number: at least 22 digits dmi.chassis.type: 3 dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr: dmi.product.name: ASE380/AST180/APM8 dmi.product.version: R01-B1 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : ht
[Desktop-packages] [Bug 1942702] Re: Ubuntu Dock "Show Applications" button: click target doesn't extend to screen edges
Dash To Dock is the correct project. I only assigned it to Ubuntu before to work around a Launchpad bug. ** Package changed: ubuntu => dash-to-dock ** Changed in: dash-to-dock Importance: Unknown => Undecided -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1942702 Title: Ubuntu Dock "Show Applications" button: click target doesn't extend to screen edges Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: How to reproduce === Boot up Impish live media, with the default left-side dock setup, swing the mouse pointer to the bottom-leftmost corner of the screen. The "Show Applications" button is not highlighted and cannot be activated. Also see Demonstration in attachment. Expected behaviour === The click target of this button should extend to the very edges of the screen like the rest of the UI elements. Fitts's law should be fulfilled. Apport info === ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-shell-extension-ubuntu-dock 70~ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu68 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 5 09:14:42 2021 LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1942702/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
