[Desktop-packages] [Bug 1905825] Re: [SRU] Disable CRTCs when system becomes headless
Hello, Just a note that mutter 3.36.9-0ubuntu0.20.04.1 has introduced a regression in a VMware Horizon VDI environment, where gdm fails to start, and has taken out several hundred VDIs. I am tracking the issue in bug 1930359. The plan is to make a test package with the patches from bug 1905825 reverted before we start digging into the point release patches from 1919143. Thanks, Matthew -- 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/1905825 Title: [SRU] Disable CRTCs when system becomes headless Status in HWE Next: New Status in OEM Priority Project: New Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Committed Status in mutter source package in Hirsute: Fix Released Bug description: [Impact] On new Intel SoCs, after all connectors are unplugged and the system becomes headless, it cannot detect monitor hotplug event from type-c port. [Fix] https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1561 Based on "drm/i915 Intel GFX Driver, Hotplug" [1]: "Finally, the userspace is responsible for triggering a modeset upon receiving the hotplug uevent, disabling or enabling the crtc as needed." [Test] Unplug type-c monitor from an Intel Tiger Lake desktop. Replug the monitor back, monitor is blank. With the fix applied, the system can detect monitor again. [Where problems could occur] This fix disables CRTCs when there's no monitor, if driver has trouble dealing with it, we may see something break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905825/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1919143] Re: SRU mutter to 3.36.9
Hello, Just a note that mutter 3.36.9-0ubuntu0.20.04.1 has introduced a regression in a VMware Horizon VDI environment, where gdm fails to start, and has taken out several hundred VDIs. I am tracking the issue in bug 1930359. The plan is to make a test package with the patches from bug 1905825 reverted before we start digging into the point release patches from 1919143. Thanks, Matthew -- 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/1919143 Title: SRU mutter to 3.36.9 Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Bug description: [ Impact ] That's the current GNOME stable update, including some fixes and translation updates https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.9 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working [ Regression potential ] There have been relevant changes on DND, monitors handling and wayland windows configurations --- This is a request to update mutter to version >= 3.36.8 to fix various issues that have been fixed upstream. See https://gitlab.gnome.org/GNOME/mutter/-/issues/1700#note_1058654 for the original mutter issue report that will be fixed by 3.36.8. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: libmutter-6-0 3.36.7+git20201123-0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Mar 15 10:40:58 2021SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1919143/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930359] [NEW] gdm fails to start with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates
Public bug reported: [Impact] gdm fails to start in a VMware Horizon VDI environment, with Nvidia GRID gpus passed into the VDIs. Downgrading mutter from 3.36.9-0ubuntu0.20.04.1 to 3.36.1-3ubuntu3 in -release fixes the issue, and the issue does not occur with 3.36.7+git20201123-0.20.04.1. Currently looking into what landed in bug 1919143 and bug 1905825. [Testcase] [Where problems can occur] ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Affects: mutter (Ubuntu Focal) Importance: High Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Tags: regression-update sts ** Also affects: mutter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu Focal) Status: New => In Progress ** Changed in: mutter (Ubuntu Focal) Importance: Undecided => High ** Changed in: mutter (Ubuntu Focal) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Tags added: regression-update sts ** Description changed: [Impact] - gdm fails to start in a VMware Horizon VDI environment, with Nvidia GRID gpus - passed into the VDIs. + gdm fails to start in a VMware Horizon VDI environment, with Nvidia GRID + gpus passed into the VDIs. - Downgrading mutter from 3.36.9-0ubuntu0.20.04.1 to 3.36.1-3ubuntu3 in -release - fixes the issue, and the issue does not occur with 3.36.7+git20201123-0.20.04.1. + Downgrading mutter from 3.36.9-0ubuntu0.20.04.1 to 3.36.1-3ubuntu3 in + -release fixes the issue, and the issue does not occur with + 3.36.7+git20201123-0.20.04.1. Currently looking into what landed in bug 1919143 and bug 1905825. [Testcase] [Where problems can occur] -- 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/1930359 Title: gdm fails to start with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates Status in mutter package in Ubuntu: New Status in mutter source package in Focal: In Progress Bug description: [Impact] gdm fails to start in a VMware Horizon VDI environment, with Nvidia GRID gpus passed into the VDIs. Downgrading mutter from 3.36.9-0ubuntu0.20.04.1 to 3.36.1-3ubuntu3 in -release fixes the issue, and the issue does not occur with 3.36.7+git20201123-0.20.04.1. Currently looking into what landed in bug 1919143 and bug 1905825. [Testcase] [Where problems can occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user
Thanks Gordon, I can remember seeing the issue when running Linux Mint back at version 17 - can't remember if it was under MATE (Caja) or Cinnamon (nemo). Can we as udisk to mount physical media in /media/[volume] and not in the user-specific sub folders? For local users, that would be totally acceptable (and even useful) to be able to share access to USB sticks while plugged in. -- 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/1930312 Title: USB disks and SD cards mount for wrong user Status in Ubuntu MATE: New Status in gvfs package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD cards and USB sticks works perfectly, unless there is someone else logged in on the machine. eg: 1- user A logs in, then walks away and screen locks 2- user B switches to the login screen and logs in as user B 3- user B plugs in a USB stick, but it doesn't mount for user B 4- (hidden from sight) user A gets an "authentication is required to mount... /dev/sdb1" error and the window is asking for admin password - details of this are: polkit.subject-pid: 102318 polkit.caller-pid: 806 Action: org.freedesktop.udisks2.filesystem-mount-other-seat Vendor: The Udisks Project user B has no indication on why it didn't mount. If they click on the USB stick in the Caja side bar, they get an "Unable to mount USB Disk - an operation is already pending" So it seems that automount is trying to show the USB stick to the inactive user A, totally blocking user B. (user B doesn't even get the chance to enter an admin password to override) the only solution is basically to "switch account", log in as user A and log them out. (this clearly doesn't work if user B doesn't know their password!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930346] Re: package fonts-noto-extra 20200323-1build1 failed to install/upgrade: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht ge
That sounds as a hardware error. Can you please run: sudo apt install --reinstall fonts-noto-extra and let us know if it helps. ** Changed in: fonts-noto (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1930346 Title: package fonts-noto-extra 20200323-1build1 failed to install/upgrade: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf .dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in fonts-noto package in Ubuntu: Incomplete Bug description: got this crash report ProblemType: Package DistroRelease: Ubuntu 21.04 Package: fonts-noto-extra 20200323-1build1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon May 31 21:10:22 2021 Dependencies: ErrorMessage: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2011-01-09 (3795 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: fonts-noto Title: package fonts-noto-extra 20200323-1build1 failed to install/upgrade: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to hirsute on 2021-06-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1930346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930355] [NEW] gnome-calendar crashes disabling/enabling or removing/readding calendar (Signal 6)
Public bug reported: Gnome-calendar crashes reliably under two conditions. First 1. Open GNOME Calendar 2. Goto Manage your calendars 3. Disable the display one of the calendars 4. Renenable it Second 1. Open GNOME Calendar 2. Goto Manage your calendars 3. Goto Manage Calendars ... 4. Select one calendar 5. Remove calendar 6. Close Window "Manage Calendars" 7. Goto Manage your calendars 8. Goto Manage Calendars ... 9. Choose "Add Calendar..." 10. Selected calendar file removed in step 5 via file selection dialog This is gnome-calendar 3.36.2 under up to date ubuntu 20.04 If I start gnome-calendar from a terminal I get as error messages: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Aborted (core dumped) These are the same in both cases. ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1930355 Title: gnome-calendar crashes disabling/enabling or removing/readding calendar (Signal 6) Status in gnome-calendar package in Ubuntu: New Bug description: Gnome-calendar crashes reliably under two conditions. First 1. Open GNOME Calendar 2. Goto Manage your calendars 3. Disable the display one of the calendars 4. Renenable it Second 1. Open GNOME Calendar 2. Goto Manage your calendars 3. Goto Manage Calendars ... 4. Select one calendar 5. Remove calendar 6. Close Window "Manage Calendars" 7. Goto Manage your calendars 8. Goto Manage Calendars ... 9. Choose "Add Calendar..." 10. Selected calendar file removed in step 5 via file selection dialog This is gnome-calendar 3.36.2 under up to date ubuntu 20.04 If I start gnome-calendar from a terminal I get as error messages: GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Bail out! GcalTimeline:ERROR:../src/core/gcal-timeline.c:212:increase_completed_calendars: assertion failed: (self->completed_calendars <= g_hash_table_size (self->calendars)) Aborted (core dumped) These are the same in both cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1930355/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921794] Re: connection to scanner very slow
[Expired for simple-scan (Ubuntu) because there has been no activity for 60 days.] ** Changed in: simple-scan (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1921794 Title: connection to scanner very slow Status in simple-scan package in Ubuntu: Expired Bug description: When starting simple scan it does "search for scanners" for about 30 seconds, until "ready to scan". Previously (forgot when that was, but same hardware) it was almost immediate. Seems to be some software bug. --- The printer/scanner and driver are: Description: HP LaserJet MFP M426fdn Location: Local Printer Driver: HP LaserJet Pro MFP M426-M427 Postscript via CUPS. --- Running hp-check -i gives this output: Missing Required Dependencies error: 'libcups2' package is missing/incompatible error: 'python3-pyqt4' package is missing/incompatible error: 'gtk2-engines-pixbuf' package is missing/incompatible Missing Optional Dependencies error: 'python3-dbus.mainloop.qt' package is missing/incompatible ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Mar 30 00:59:36 2021 ExecutablePath: /usr/bin/simple-scan InstallationDate: Installed on 2018-06-15 (1018 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) LocalLibraries: /usr/local/lib/libjpeg-x86_64.so.9.2.0 MachineType: Dell Inc. OptiPlex 7040 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=63e54e9f-567c-498f-883a-5216d348a80f ro quiet splash vt.handoff=7 SourcePackage: simple-scan UpgradeStatus: Upgraded to focal on 2020-08-20 (221 days ago) dmi.bios.date: 07/19/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.5 dmi.board.name: 0HD5W2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.5:bd07/19/2019:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0HD5W2:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 7040 dmi.product.sku: 06B9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1921794/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930305] Re: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all
BTW, when you plug headphone and the system is not locked, does a pop-up dialogue show and let you choose what audio device you plugged? If it does and you select the Microphone (the rigtmost one), it is expected that the headphone can't output sound. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1930305 Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello, So I use Ubuntu 20.04 LTS for a month. Firstly thank you for such a good and progressive operating system. Here is the problem: Normally, sound works perfectly when the output device is speakers. It is also works when I plugged in the headphone on PC when the system is on. However whenever I try to plug in the headphone when the system is locked (on locked screen) the headphone does not work anymore even I restart. But it works when I try to plug in it when the lock screen is not active on next day. It is not working right now. The list of Output Devices in the Settings: - Speakers - Built-in Audio - Headphones - Built-in Audio When I select headphones, the sound is gone at all. Also yes, I tried to use headphone on another devices and they work perfectly. I will put all informations that you might want. Please let me know if you need more information. I am also not sure if I chose the right output device. Thank you. Release: Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:29:49 2021 InstallationDate: Installed on 2021-05-26 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05VVC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn05VVC5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.sku: Inspiron 5537 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1930305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930348] [NEW] package libreoffice-dev-doc 1:7.0.5-0ubuntu0.20.10.1 failed to install/upgrade: »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png.
Public bug reported: Got the following issue during apt upgrade: Vorbereitung zum Entpacken von .../1-libreoffice-dev-doc_1%3a7.1.3-0ubuntu0.21.04.1_all.deb ... Entpacken von libreoffice-dev-doc (1:7.1.3-0ubuntu0.21.04.1) über (1:7.0.5-0ubuntu0.20.10.1) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-HkAFni/1-libreoffice-dev-doc_1%3a7.1. 3-0ubuntu0.21.04.1_all.deb (--unpack): »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png.dpkg-new« kann nic ht geöffnet werden: Vorgang nicht zulässig ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libreoffice-dev-doc 1:7.0.5-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 1 04:58:37 2021 Dependencies: ErrorMessage: »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2011-01-09 (3795 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: libreoffice Title: package libreoffice-dev-doc 1:7.0.5-0ubuntu0.20.10.1 failed to install/upgrade: »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to hirsute on 2021-06-01 (0 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- 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/1930348 Title: package libreoffice-dev-doc 1:7.0.5-0ubuntu0.20.10.1 failed to install/upgrade: »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png .dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in libreoffice package in Ubuntu: New Bug description: Got the following issue during apt upgrade: Vorbereitung zum Entpacken von .../1-libreoffice-dev-doc_1%3a7.1.3-0ubuntu0.21.04.1_all.deb ... Entpacken von libreoffice-dev-doc (1:7.1.3-0ubuntu0.21.04.1) über (1:7.0.5-0ubuntu0.20.10.1) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-HkAFni/1-libreoffice-dev-doc_1%3a7.1. 3-0ubuntu0.21.04.1_all.deb (--unpack): »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png.dpkg-new« kann nic ht geöffnet werden: Vorgang nicht zulässig ProblemType: Package DistroRelease: Ubuntu 21.04 Package: libreoffice-dev-doc 1:7.0.5-0ubuntu0.20.10.1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Tue Jun 1 04:58:37 2021 Dependencies: ErrorMessage: »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2011-01-09 (3795 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: libreoffice Title: package libreoffice-dev-doc 1:7.0.5-0ubuntu0.20.10.1 failed to install/upgrade: »/usr/share/doc/libreoffice/sdk/docs/idl/ref/RealRectangle3D_8idl__dep__incl.png.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to hirsute on 2021-06-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1930348/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930305] Re: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all
When the headphone can't output sound, what input device is active? And when problem happens (headphone can't output sound), please run pa- info > log.txt, and upload the log.txt thx. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1930305 Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello, So I use Ubuntu 20.04 LTS for a month. Firstly thank you for such a good and progressive operating system. Here is the problem: Normally, sound works perfectly when the output device is speakers. It is also works when I plugged in the headphone on PC when the system is on. However whenever I try to plug in the headphone when the system is locked (on locked screen) the headphone does not work anymore even I restart. But it works when I try to plug in it when the lock screen is not active on next day. It is not working right now. The list of Output Devices in the Settings: - Speakers - Built-in Audio - Headphones - Built-in Audio When I select headphones, the sound is gone at all. Also yes, I tried to use headphone on another devices and they work perfectly. I will put all informations that you might want. Please let me know if you need more information. I am also not sure if I chose the right output device. Thank you. Release: Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:29:49 2021 InstallationDate: Installed on 2021-05-26 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05VVC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn05VVC5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.sku: Inspiron 5537 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1930305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930346] [NEW] package fonts-noto-extra 20200323-1build1 failed to install/upgrade: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht
Public bug reported: got this crash report ProblemType: Package DistroRelease: Ubuntu 21.04 Package: fonts-noto-extra 20200323-1build1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon May 31 21:10:22 2021 Dependencies: ErrorMessage: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2011-01-09 (3795 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: fonts-noto Title: package fonts-noto-extra 20200323-1build1 failed to install/upgrade: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to hirsute on 2021-06-01 (0 days ago) ** Affects: fonts-noto (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fonts-noto in Ubuntu. https://bugs.launchpad.net/bugs/1930346 Title: package fonts-noto-extra 20200323-1build1 failed to install/upgrade: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf .dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig Status in fonts-noto package in Ubuntu: New Bug description: got this crash report ProblemType: Package DistroRelease: Ubuntu 21.04 Package: fonts-noto-extra 20200323-1build1 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon May 31 21:10:22 2021 Dependencies: ErrorMessage: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig InstallationDate: Installed on 2011-01-09 (3795 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) PackageArchitecture: all Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: fonts-noto Title: package fonts-noto-extra 20200323-1build1 failed to install/upgrade: »/usr/share/fonts/truetype/noto/NotoSerifHebrew-ExtraCondensedThin.ttf.dpkg-new« kann nicht geöffnet werden: Vorgang nicht zulässig UpgradeStatus: Upgraded to hirsute on 2021-06-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1930346/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823516] Re: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions
This also appears to be relevant/needed: https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/673 -- 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/1823516 Title: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions Status in xorg-server package in Ubuntu: Fix Committed Status in xwayland package in Ubuntu: Triaged Bug description: Nvidia driver installed but X apps are using software rendering (LLVMpipe) in Wayland sessions. I am using kernel parameter nvidia-drm.modeset=1, which is required to get the "Ubuntu on Wayland" option. But after logging in I see: $ glxinfo | grep OpenGL OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 8.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.0.1 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.1 Mesa 19.0.1 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.0.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 OpenGL ES profile extensions: $ es2_info | grep ^GL GL_VERSION: OpenGL ES 3.0 Mesa 19.0.1 GL_RENDERER: llvmpipe (LLVM 8.0, 256 bits) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-driver-418 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 Date: Sun Apr 7 17:26:07 2019 InstallationDate: Installed on 2018-12-04 (124 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: nvidia-graphics-drivers-418 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1823516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
Thanks but I'm not sure that section of log is relevant here. And even if it is, there's not enough information so... 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-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- 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/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: # Steps to reproduce 0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll) 1. move mouse pointer over the dock 2. use the mouse scroller to scroll horizontally # What I expect to happen Nothing # What happens Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock. # Other info Slightly similar to LP #1875106, but I'm not using imwheel. I am using Wayland. Syslog seems to always point to this one function: "The offending callback was get_preferred_height(), a vfunc". I'll attach the relevant part from one crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:35:37 2021 InstallationDate: Installed on 2020-11-30 (182 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930275] Re: [nvidia] System does not wake up after suspend
Thanks for the bug report. Next time the problem happens and you have to "hard reboot", please then run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Summary changed: - Xorg freeze + [nvidia] System does not wake up after suspend ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia -- 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/1930275 Title: [nvidia] System does not wake up after suspend Status in linux package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Ubuntu 20.10 suspend is not working. After suspend it does not wake up. And I have to hard reboot machine. It is happening since last few days. Here is error message I see from logs: "Failed to start Application launched by gnome-session-binary. A start job for unit UNIT has finished with a failure. The job identifier is 368 and the job result is failed. Failed to start LSB: OpenIPMI Driver init script. A start job for unit openipmi.service has finished with a failure. The job identifier is 151 and the job result is failed. " ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 09:04:06 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061] InstallationDate: Installed on 2020-02-15 (471 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage
[Desktop-packages] [Bug 1930279] Re: [Ivy Bridge] winking triangles on screen
** Summary changed: - winking triangles on screen + [Ivy Bridge] winking triangles on screen ** Package changed: xorg (Ubuntu) => mesa (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1930279 Title: [Ivy Bridge] winking triangles on screen Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/+bug/1930279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer
You did however experience bug 1886059 on 2020-05-16. -- 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/1930192 Title: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter- offscreen-effect.c:213: Unable to create an Offscreen buffer Status in gnome-shell package in Ubuntu: Incomplete Bug description: Addition for bug report 1930128 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat May 29 12:20:21 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 GsettingsChanges: b'org.gnome.desktop.background' b'show-desktop-icons' b'true' b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true' b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false' b'org.gnome.desktop.session' b'idle-delay' b'uint32 0' InstallationDate: Installed on 2019-11-10 (566 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
Looks like Marco is releasing the fix to both now. In impish-proposed. ** Changed in: gnome-shell (Ubuntu Hirsute) Status: In Progress => Fix Committed ** Changed in: gnome-shell (Ubuntu Impish) Status: In Progress => Fix Committed -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Status in gnome-shell source package in Hirsute: Fix Committed Status in gnome-shell source package in Impish: Fix Committed Bug description: [Impact] Shell overview gets stuck where it's permanently toggled but not visible. Only app windows appear in their overview state. Can't interact with applications anymore. [Test Plan] 1. Log into GNOME. 2. Press Super+A 3. Click on 'Files' and wait till it has launched. 4. Press the Super key. Expect: Can interact with the application window. [Where problems could occur] Since the patch affects some of the core gnome-shell layout logic, anything is possible. Risk has been mitigated by the patch being small. [Original description] When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user
For the record, this is not specific to Ubuntu or Ubuntu MATE at all -- I see this on Gentoo regularly, for example. It seems to be caused by a race condition in Caja and UDisks which didn't appear until UDisks started mounting volumes under user-specific subdirectories of `/media` -- so for example `user1` has volumes mounted under `/media/user1` and `user2` has volumes mounted under `/media/user2`. In ye olden days, `user1`'s UDisks-utilizing process (such as Caja) would mount the volume; `user2`'s instance of Caja would wait for the volume to get mounted by `user1`'s Caja, then open the shared mountpoint at `/media/[volume]`. Nowadays this doesn't work in any case, since `user1` puts in the request to mount the volume first and the volume is mounted under `user1`'s private mount directory -- `/media/user1/[volume]`. I'm not sure how to fix this yet, though. Maybe (but just a WAG) UDisks needs some kind of integration with the display manager or logind? -- 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/1930312 Title: USB disks and SD cards mount for wrong user Status in Ubuntu MATE: New Status in gvfs package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD cards and USB sticks works perfectly, unless there is someone else logged in on the machine. eg: 1- user A logs in, then walks away and screen locks 2- user B switches to the login screen and logs in as user B 3- user B plugs in a USB stick, but it doesn't mount for user B 4- (hidden from sight) user A gets an "authentication is required to mount... /dev/sdb1" error and the window is asking for admin password - details of this are: polkit.subject-pid: 102318 polkit.caller-pid: 806 Action: org.freedesktop.udisks2.filesystem-mount-other-seat Vendor: The Udisks Project user B has no indication on why it didn't mount. If they click on the USB stick in the Caja side bar, they get an "Unable to mount USB Disk - an operation is already pending" So it seems that automount is trying to show the USB stick to the inactive user A, totally blocking user B. (user B doesn't even get the chance to enter an admin password to override) the only solution is basically to "switch account", log in as user A and log them out. (this clearly doesn't work if user B doesn't know their password!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- 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/1930312 Title: USB disks and SD cards mount for wrong user Status in Ubuntu MATE: New Status in gvfs package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD cards and USB sticks works perfectly, unless there is someone else logged in on the machine. eg: 1- user A logs in, then walks away and screen locks 2- user B switches to the login screen and logs in as user B 3- user B plugs in a USB stick, but it doesn't mount for user B 4- (hidden from sight) user A gets an "authentication is required to mount... /dev/sdb1" error and the window is asking for admin password - details of this are: polkit.subject-pid: 102318 polkit.caller-pid: 806 Action: org.freedesktop.udisks2.filesystem-mount-other-seat Vendor: The Udisks Project user B has no indication on why it didn't mount. If they click on the USB stick in the Caja side bar, they get an "Unable to mount USB Disk - an operation is already pending" So it seems that automount is trying to show the USB stick to the inactive user A, totally blocking user B. (user B doesn't even get the chance to enter an admin password to override) the only solution is basically to "switch account", log in as user A and log them out. (this clearly doesn't work if user B doesn't know their password!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- 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/1930312 Title: USB disks and SD cards mount for wrong user Status in Ubuntu MATE: New Status in gvfs package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Confirmed Bug description: I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD cards and USB sticks works perfectly, unless there is someone else logged in on the machine. eg: 1- user A logs in, then walks away and screen locks 2- user B switches to the login screen and logs in as user B 3- user B plugs in a USB stick, but it doesn't mount for user B 4- (hidden from sight) user A gets an "authentication is required to mount... /dev/sdb1" error and the window is asking for admin password - details of this are: polkit.subject-pid: 102318 polkit.caller-pid: 806 Action: org.freedesktop.udisks2.filesystem-mount-other-seat Vendor: The Udisks Project user B has no indication on why it didn't mount. If they click on the USB stick in the Caja side bar, they get an "Unable to mount USB Disk - an operation is already pending" So it seems that automount is trying to show the USB stick to the inactive user A, totally blocking user B. (user B doesn't even get the chance to enter an admin password to override) the only solution is basically to "switch account", log in as user A and log them out. (this clearly doesn't work if user B doesn't know their password!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930315] Re: firefox 89.0 FTBFS on ppc64el with clang 10
Tentative fix: https://bazaar.launchpad.net/~mozillateam/firefox/firefox.bionic/revision/1463. ** Changed in: firefox (Ubuntu) Status: In Progress => Fix Committed -- 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/1930315 Title: firefox 89.0 FTBFS on ppc64el with clang 10 Status in firefox package in Ubuntu: Fix Committed Bug description: (this is a different issue than bug #1923505) On ppc64el, building firefox 89.0 with clang 10 (the highest version of clang currently available for bionic and focal, either in the release or the security pocket) hangs forever when compiling gfx/wr/swgl/src/gl.cc. This regression was introduced by this upstream change: https://phabricator.services.mozilla.com/D109657. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923505] Re: thunderbird 78.9.0 FTBFS on ppc64el
The firefox build failures are a different issue: bug #1930315. -- 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/1923505 Title: thunderbird 78.9.0 FTBFS on ppc64el Status in thunderbird package in Ubuntu: Triaged Bug description: The build hangs forever when compiling the webrender rust crate (see https://launchpad.net/ubuntu/+source/thunderbird/1:78.9.0+build2-0ubuntu3/+build/21368163). I'm attaching the full build log for future reference. This happens when building with rustc 1.50.0+dfsg1+llvm-0ubuntu4 and 1.50.0+dfsg1+llvm-0ubuntu5 (the latter is the version currently in the hirsute release pocket). The build completes when building with rustc 1.50.0+dfsg1+llvm-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1923505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930315] Re: firefox 89.0 FTBFS on ppc64el with clang 10
** Branch linked: lp:~mozillateam/firefox/firefox.focal -- 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/1930315 Title: firefox 89.0 FTBFS on ppc64el with clang 10 Status in firefox package in Ubuntu: Fix Committed Bug description: (this is a different issue than bug #1923505) On ppc64el, building firefox 89.0 with clang 10 (the highest version of clang currently available for bionic and focal, either in the release or the security pocket) hangs forever when compiling gfx/wr/swgl/src/gl.cc. This regression was introduced by this upstream change: https://phabricator.services.mozilla.com/D109657. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930315] [NEW] firefox 89.0 FTBFS on ppc64el with clang 10
Public bug reported: (this is a different issue than bug #1923505) On ppc64el, building firefox 89.0 with clang 10 (the highest version of clang currently available for bionic and focal, either in the release or the security pocket) hangs forever when compiling gfx/wr/swgl/src/gl.cc. This regression was introduced by this upstream change: https://phabricator.services.mozilla.com/D109657. ** Affects: firefox (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Fix Committed -- 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/1930315 Title: firefox 89.0 FTBFS on ppc64el with clang 10 Status in firefox package in Ubuntu: Fix Committed Bug description: (this is a different issue than bug #1923505) On ppc64el, building firefox 89.0 with clang 10 (the highest version of clang currently available for bionic and focal, either in the release or the security pocket) hangs forever when compiling gfx/wr/swgl/src/gl.cc. This regression was introduced by this upstream change: https://phabricator.services.mozilla.com/D109657. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930315/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930312] Re: USB disks and SD cards mount for wrong user
** Tags added: focal ** Also affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Also affects: gvfs (Ubuntu) Importance: Undecided Status: New -- 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/1930312 Title: USB disks and SD cards mount for wrong user Status in Ubuntu MATE: New Status in gvfs package in Ubuntu: New Status in udisks2 package in Ubuntu: New Bug description: I have MATE 20.04 LTS installed on a laptop with 4 users. Plugging in SD cards and USB sticks works perfectly, unless there is someone else logged in on the machine. eg: 1- user A logs in, then walks away and screen locks 2- user B switches to the login screen and logs in as user B 3- user B plugs in a USB stick, but it doesn't mount for user B 4- (hidden from sight) user A gets an "authentication is required to mount... /dev/sdb1" error and the window is asking for admin password - details of this are: polkit.subject-pid: 102318 polkit.caller-pid: 806 Action: org.freedesktop.udisks2.filesystem-mount-other-seat Vendor: The Udisks Project user B has no indication on why it didn't mount. If they click on the USB stick in the Caja side bar, they get an "Unable to mount USB Disk - an operation is already pending" So it seems that automount is trying to show the USB stick to the inactive user A, totally blocking user B. (user B doesn't even get the chance to enter an admin password to override) the only solution is basically to "switch account", log in as user A and log them out. (this clearly doesn't work if user B doesn't know their password!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1930312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930305] Re: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1930305 Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Hello, So I use Ubuntu 20.04 LTS for a month. Firstly thank you for such a good and progressive operating system. Here is the problem: Normally, sound works perfectly when the output device is speakers. It is also works when I plugged in the headphone on PC when the system is on. However whenever I try to plug in the headphone when the system is locked (on locked screen) the headphone does not work anymore even I restart. But it works when I try to plug in it when the lock screen is not active on next day. It is not working right now. The list of Output Devices in the Settings: - Speakers - Built-in Audio - Headphones - Built-in Audio When I select headphones, the sound is gone at all. Also yes, I tried to use headphone on another devices and they work perfectly. I will put all informations that you might want. Please let me know if you need more information. I am also not sure if I chose the right output device. Thank you. Release: Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:29:49 2021 InstallationDate: Installed on 2021-05-26 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05VVC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn05VVC5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.sku: Inspiron 5537 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1930305/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930305] [NEW] [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all
You have been subscribed to a public bug: Hello, So I use Ubuntu 20.04 LTS for a month. Firstly thank you for such a good and progressive operating system. Here is the problem: Normally, sound works perfectly when the output device is speakers. It is also works when I plugged in the headphone on PC when the system is on. However whenever I try to plug in the headphone when the system is locked (on locked screen) the headphone does not work anymore even I restart. But it works when I try to plug in it when the lock screen is not active on next day. It is not working right now. The list of Output Devices in the Settings: - Speakers - Built-in Audio - Headphones - Built-in Audio When I select headphones, the sound is gone at all. Also yes, I tried to use headphone on another devices and they work perfectly. I will put all informations that you might want. Please let me know if you need more information. I am also not sure if I chose the right output device. Thank you. Release: Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:29:49 2021 InstallationDate: Installed on 2021-05-26 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oldner 3424 F pulseaudio /dev/snd/controlC1: oldner 3424 F pulseaudio /dev/snd/pcmC1D0c: oldner 3424 F...m pulseaudio /dev/snd/pcmC1D0p: oldner 3424 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [Inspiron 5537, Realtek ALC3223, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 05VVC5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.ec.firmware.release: 1.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd05/27/2019:efr1.1:svnDellInc.:pnInspiron5537:pvrA12:rvnDellInc.:rn05VVC5:rvrA00:cvnDellInc.:ct8:cvrA12: dmi.product.family: 00 dmi.product.name: Inspiron 5537 dmi.product.sku: Inspiron 5537 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Inspiron 5537, Realtek ALC3223, Black Headphone Out] No sound at all https://bugs.launchpad.net/bugs/1930305 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver 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 571588] Re: Ubuntu chat theme uses ugly avatar scaling
This bug may be closed by now. Thanks. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to adium-theme-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/571588 Title: Ubuntu chat theme uses ugly avatar scaling Status in adium-theme-ubuntu package in Ubuntu: New Bug description: Binary package hint: empathy The "Ubuntu" chat style for empathy in Lucid shows comic-style chat balloons with resized user avatar images. With a better scaling algorithm, the avatar images would look a lot nicer than they do now See screenshot and compare full size avatar in user info window with scaled avatar in chat window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adium-theme-ubuntu/+bug/571588/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795483] Re: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575)
Thank you, I tested the new values and it all works as expected for me. However, not sure what it is but the 225% value seems to change the rendering in an unpleasant way. Not sure if it's only not being used to it, but for the time being it feels more "comfortable" reverting to 200% and upping the font scaling a bit, as I did before. -- 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/1795483 Title: Experimental setting to enable fractional Hi-DPI scaling offers no option larger than 200% on 15.6 inch, 3840 x 2160 pixel display (Dell XPS 15 9575) Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Focal: In Progress Status in gnome-control-center source package in Hirsute: In Progress Bug description: [ Impact ] On my laptop's 15.6 inch, 3840 x 2160 pixel (282 PPI) display, the available scaling options in the gnome-control-center display settings are limited to 100, 200, 300, and 400%. This is insufficient as 200% is too small and 300% is too large. The missing fractional scaling options are dealt with in bug #1687246. However, the currently available experimental feature to enable fractional scaling (provided in the bug description of #1687246) does not solve the problem on my machine: gsettings set org.gnome.mutter experimental-features "['scale-monitor- framebuffer']" After applying and rebooting, the options offered change to 100, 125, 150, 175, and 200%. Note that there is no value larger than 200% which is too small on this display at least for me. In addition, the 25% steps enabled by the experimental option seem too far apart. With 200%, I am using a font scaling value in Gnome Tweaks of 1.20, so I suppose a fractional scaling of approx 240% would be equivalent. In bug #1687246, Daniel van Vugt (vanvugt) advised to open a new bug for gnome-control-center and added that "gnome-control-center seems to limit the scale to 200% on some machines, 300% on others. And I think I have seen 400% offered in some cases. I don't know why, but the inconsistency is definitely annoying." [ Test case ] In a setup with a display with HighDPi resolution (higher than 2880x1800) - Open gnome-control-center display panel - Scaling should show 5 level buttons to select - Selecting higher values will show all the selectable values closer to the chosen one - Any value could be used from 100% up to 400% (maximum varies on resolution) [ Regression potential ] Control center won't show any scaling value, or scaling value may be wrong. --- ProblemType: BugDistroRelease: Ubuntu 18.10 Package: gnome-control-center 1:3.30.0-0ubuntu1 Uname: Linux 4.19.0-041900rc5-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Oct 1 19:29:11 2018 InstallationDate: Installed on 2018-09-13 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912)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/1795483/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1904213] Re: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257]
Confirming, that workaround from #4 also fixes that issue in Ubuntu 20.04.2. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1904213 Title: Built-in microphone not working with 20.04 on ThinkBook 13s IML [Realtek ALC257] Status in sound-2.6 (alsa-kernel): New Status in alsa-driver package in Ubuntu: Confirmed Bug description: After installing current 20.04 release on ThinkBook 13s IML with Intel audio card built-in microphone is not working - I'm unable to record anything. I could confirm that it was working in Windows 10 (previously installed on that laptop), and when I'm using headphones their microphone is working fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.12 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anlar 1496 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Nov 13 19:07:34 2020 InstallationDate: Installed on 2020-10-29 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: Only some of inputs are working Title: [20RR, Realtek ALC257, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CQCN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 13s-IML dmi.modalias: dmi:bvnLENOVO:bvrCQCN24WW:bd10/29/2019:svnLENOVO:pn20RR:pvrLenovoThinkBook13s-IML:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook13s-IML: dmi.product.family: ThinkBook 13s-IML dmi.product.name: 20RR dmi.product.sku: LENOVO_MT_20RR_BU_idea_FM_ThinkBook 13s-IML dmi.product.version: Lenovo ThinkBook 13s-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1904213/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1690719] Re: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions
The backported input thread patches mainly laid a foundation to solve this issue. Mutter still needs more work to take advantage of the new input thread. That is why there isn't an improvement in GNOME 40. This is described here: https://blogs.gnome.org/shell-dev/2021/01/21 /threaded-input-adventures/ > The main thread is still in charge of KMS, and updating the cursor plane buffer and position. This means the pointer cursor will still freeze if the main thread stalled, despite the input thread handling events underneath. In the future, There would be another separate thread handling atomic KMS operations, so it’d be possible for the input and KMS threads to talk between them and bypassing any main thread stalls. -- 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/1690719 Title: Mouse pointer randomly pauses/stutters in gnome shell Wayland sessions Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Bug description: The mouse pointer randomly pauses/stutters in Gnome Shell (Wayland). It's not reliably smooth like you would see in Xorg or Mir demo servers. Feels like there is a blocking call being made in a GUI thread that shouldn't have any blocking calls. Although it's not clear if this is just a problem with pointer input or the shell compositing in general. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu7 Architecture: amd64 Date: Mon May 15 13:23:22 2017 DisplayManager: lightdm GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'scaling-factor' b'uint32 1' InstallationDate: Installed on 2017-05-03 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1690719/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@Hui Wang I've tested. Verbs from #17 have no effect, verbs from set-verbs-c930.sh completely disable all speakers, no sound. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870597] Re: libinput says: scheduled expiry is in the past... your system is too slow
I have the same sort of issue... Ubuntu 20.04 (Ubuntu Studio spin). >From Xorg.0.log [ 13886.780] (EE) client bug: timer event4 debounce short: scheduled expiry is in the past (-9ms), your system is too slow [ 13926.080] (EE) client bug: timer event4 debounce: scheduled expiry is in the past (-15ms), your system is too slow Video freezes, external display will go black or the system will crash (I expect it is only X that crashes because if I am editing audio in Audacity, the audio will continue to play, yet I will have to hard reset my machine to regain control. Keyboard and mouse input are dead as part of X system. I have not tried remoting in to it from another machine yet. Running a MacBook Pro retina mid 2012 with 8GB RAM and the i7 processor with GeForce GT 650M Mac Edition graphics chip at 4K@30Hz output. If I have the system running powersave, I get the hard crashes, with ondemand governor I get the timeouts. Going to performance causes the fans to run all the time which is loud. -- 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/1870597 Title: libinput says: scheduled expiry is in the past... your system is too slow Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: During the freeze, the output of the install had a message from "gdm-x-session" saying "your system is too slow". To reproduce: 1. Launch the Ubuntu installer 2. Begin the installation process 3. When the installation process begins, move the cursor around 4. Notice how the PC freezes and drops mouse events Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installed: 3.36.0-2ubuntu2 Candidate: 3.36.0-2ubuntu2 Version table: *** 3.36.0-2ubuntu2 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CasperVersion: 1.442 Date: Fri Apr 3 14:24:21 2020 DisplayManager: gdm3 GsettingsChanges: LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CasperVersion: 1.442 CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:0810] LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Inspiron 5570 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: xorg-server (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal ubuntu Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/15/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.3 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-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 1925320] Re: Backport packages for 20.04.3 HWE stack
Hello Timo, or anyone else affected, Accepted xorg-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xorg- server/2:1.20.11-1ubuntu1~20.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xorg-server (Ubuntu Focal) Status: New => Fix Committed -- 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/1925320 Title: Backport packages for 20.04.3 HWE stack Status in directx-headers package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-12 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in directx-headers source package in Focal: Fix Committed Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-12 source package in Focal: Fix Committed Status in mesa source package in Focal: Fix Committed Status in xorg-server source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.3 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] directx-headers: a new package, nothing can go wrong libdrm: adds some new api, no changes to old stuff llvm-12: a new package, no regression potential on it's own mesa: a new major release, but we'll pull the final stable release of 21.0.x series, so there shouldn't be any regressions left at that point xserver: a new point-release, 1.20.x series is in deep maintenance mode, so there should be little chance of breakage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
** Attachment added: "syslog Stack trace" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5501476/+files/syslog -- 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/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: # Steps to reproduce 0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll) 1. move mouse pointer over the dock 2. use the mouse scroller to scroll horizontally # What I expect to happen Nothing # What happens Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock. # Other info Slightly similar to LP #1875106, but I'm not using imwheel. I am using Wayland. Syslog seems to always point to this one function: "The offending callback was get_preferred_height(), a vfunc". I'll attach the relevant part from one crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:35:37 2021 InstallationDate: Installed on 2020-11-30 (182 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930304] [NEW] Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
Public bug reported: # Steps to reproduce 0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll) 1. move mouse pointer over the dock 2. use the mouse scroller to scroll horizontally # What I expect to happen Nothing # What happens Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock. # Other info Slightly similar to LP #1875106, but I'm not using imwheel. I am using Wayland. Syslog seems to always point to this one function: "The offending callback was get_preferred_height(), a vfunc". I'll attach the relevant part from one crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:35:37 2021 InstallationDate: Installed on 2020-11-30 (182 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Description changed: # Steps to reproduce 0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll) 1. move mouse pointer over the dock 2. use the mouse scroller to scroll horizontally # What I expect to happen Nothing # What happens Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock. # Other info - Slightly similar to #1875106, but I'm not using imwheel. + Slightly similar to LP #1875106, but I'm not using imwheel. I am using Wayland. Syslog seems to always point to this one function: "The offending callback was get_preferred_height(), a vfunc". I'll attach the relevant part from one crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:35:37 2021 InstallationDate: Installed on 2020-11-30 (182 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084 -- 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/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: # Steps to reproduce 0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll) 1. move mouse pointer over the dock 2. use the mouse scroller to scroll horizontally # What I expect to happen Nothing # What happens Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock. # Other info Slightly similar to LP #1875106, but I'm not using imwheel. I am using Wayland. Syslog seems to always point to this one function: "The offending callback was get_preferred_height(), a vfunc". I'll attach the relevant part from one crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:35:37 2021
[Desktop-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.
I have the same issue. The audio from Steam is emitted from internal speaker instead from USB Sound Card. Left/Right test also emitted from internal speaker. It is solved by doing tips on #41. Thank you! -- 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/1866194 Title: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all. Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: [Impact] Selected audio output device in Settings is ignored after upgrading to Ubuntu 20.04. [Test Case] Start with an older version of Ubuntu like 19.04 or 19.10 and upgrade to 20.04. When done, attempt to connect a Bluetooth or USB audio device and use it via Settings. [Regression Potential] Unknown/low. The fix is from upstream and has already been released to Ubuntu 20.10 without any problems. Only worth noting it works by detecting and removing audio configurations made via older versions of PulseAudio. So upon upgrading some old settings may be reset to defaults, but the idea is that's less bad than audio devices being unusable (this bug). [Original Bug Report] Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
** Also affects: gnome-shell (Ubuntu Hirsute)
Importance: Undecided
Status: New
** Also affects: gnome-shell (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: gnome-shell (Ubuntu Focal)
Status: New => Fix Committed
** Changed in: gnome-shell (Ubuntu Hirsute)
Status: New => Fix Committed
** Description changed:
+ [ Impact ]
+
+ gnome-shell-calendar-server crashes (and it seems to happen more in
+ aarch64).
+
https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1
+
+ [ Test case ]
+
+ There's not a clear test case, but this is relevant:
+ - Configure a supported calendar in your online accounts
+ - GNOME shell should show your events in the calendar (under notifications
panel)
+
+ [ Regression potential ]
+
+ gnome-shell-calendar-server may leak memory.
+
---
M1 Mac mini
Parallels Ubuntu VM
- ProblemType: Crash
- DistroRelease: Ubuntu 21.04
+ ProblemType: CrashDistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic aarch64
ApportVersion: 2.20.11-0ubuntu58
Architecture: arm64
AssertionMessage: double free or corruption (fasttop)
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 17 04:34:36 2021
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-calendar-server
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
InstallationDate: Installed on 2021-02-17 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
ProcCmdline: /usr/libexec/gnome-shell-calendar-server
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANG=en_US.UTF-8
RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
- Signal: 6
- SourcePackage: gnome-shell
+ Signal: 6SourcePackage: gnome-shell
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
malloc_printerr (str=str@entry=0x81240c08 "double free or corruption
(fasttop)") at malloc.c:5389
_int_free (av=, p=0xe9eee300, have_lock=0) at
malloc.c:4298
g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-shell-calendar-server assert failure: double free or corruption
(fasttop)
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
separator:
--
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/1915929
Title:
gnome-shell-calendar-server assert failure on arm64: double free or
corruption (fasttop)
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Committed
Status in gnome-shell source package in Focal:
Fix Committed
Status in gnome-shell source package in Hirsute:
Fix Committed
Bug description:
[ Impact ]
gnome-shell-calendar-server crashes (and it seems to happen more in
aarch64).
https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1
[ Test case ]
There's not a clear test case, but this is relevant:
- Configure a supported calendar in your online accounts
- GNOME shell should show your events in the calendar (under notifications
panel)
[ Regression potential ]
gnome-shell-calendar-server may leak memory.
---
M1 Mac mini
Parallels Ubuntu VM
ProblemType: CrashDistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic aarch64
ApportVersion: 2.20.11-0ubuntu58
Architecture: arm64
AssertionMessage: double free or corruption (fasttop)
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 17 04:34:36 2021
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-calendar-server
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
InstallationDate: Installed on 2021-02-17 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
ProcCmdline:
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
** Changed in: gnome-shell (Ubuntu Impish) Status: Won't Fix => In Progress ** Changed in: gnome-shell (Ubuntu Impish) Assignee: Daniel van Vugt (vanvugt) => Marco Trevisan (Treviño) (3v1n0) -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Hirsute: In Progress Status in gnome-shell source package in Impish: In Progress Bug description: [Impact] Shell overview gets stuck where it's permanently toggled but not visible. Only app windows appear in their overview state. Can't interact with applications anymore. [Test Plan] 1. Log into GNOME. 2. Press Super+A 3. Click on 'Files' and wait till it has launched. 4. Press the Super key. Expect: Can interact with the application window. [Where problems could occur] Since the patch affects some of the core gnome-shell layout logic, anything is possible. Risk has been mitigated by the patch being small. [Original description] When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915929] Re: gnome-shell-calendar-server assert failure on arm64: double free or corruption (fasttop)
** Tags added: fixed-in-3.38.5
--
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/1915929
Title:
gnome-shell-calendar-server assert failure on arm64: double free or
corruption (fasttop)
Status in GNOME Shell:
Unknown
Status in gnome-shell package in Ubuntu:
Fix Committed
Bug description:
https://errors.ubuntu.com/problem/028fd7df90d750d70c7fea9719974347af67fa5a
https://errors.ubuntu.com/problem/33eeeda9b48baf59fe82b6b1f0aaa9465193b7f1
---
M1 Mac mini
Parallels Ubuntu VM
ProblemType: Crash
DistroRelease: Ubuntu 21.04
Package: gnome-shell 3.38.3-2ubuntu2
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.8.0-36-generic aarch64
ApportVersion: 2.20.11-0ubuntu58
Architecture: arm64
AssertionMessage: double free or corruption (fasttop)
CasperMD5CheckResult: unknown
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 17 04:34:36 2021
DisplayManager: gdm3
ExecutablePath: /usr/libexec/gnome-shell-calendar-server
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.notifications' b'application-children' b"['apport-gtk']"
b'org.gnome.desktop.peripherals.keyboard' b'numlock-state' b'true'
InstallationDate: Installed on 2021-02-17 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha arm64 (20210217)
ProcCmdline: /usr/libexec/gnome-shell-calendar-server
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_DIR=
PATH=(custom, no user)
LANG=en_US.UTF-8
RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1
Signal: 6
SourcePackage: gnome-shell
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x81245180
"%s\n") at ../sysdeps/posix/libc_fatal.c:155
malloc_printerr (str=str@entry=0x81240c08 "double free or corruption
(fasttop)") at malloc.c:5389
_int_free (av=, p=0xe9eee300, have_lock=0) at
malloc.c:4298
g_variant_builder_clear () from /lib/aarch64-linux-gnu/libglib-2.0.so.0
?? ()
Title: gnome-shell-calendar-server assert failure: double free or corruption
(fasttop)
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/gnome-shell/+bug/1915929/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930279] Re: winking triangles on screen
The attachment "Screenshot from 2021-05-31 18-00-04.png" 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.] ** Tags added: patch -- 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/1930279 Title: winking triangles on screen Status in xorg package in Ubuntu: New Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/1930279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930279] Re: winking triangles on screen
** 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/1930279 Title: winking triangles on screen Status in xorg package in Ubuntu: New Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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/1930279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930279] [NEW] winking triangles on screen
You have been subscribed to a public bug: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 groovy third-party-packages ubuntu -- winking triangles on screen https://bugs.launchpad.net/bugs/1930279 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 1930297] [NEW] Clipboard sharing is disabled when using RDP backend
Public bug reported: We disabled RDP clipoard as part of gnome-remote-desktop 40.1-1 as it requires libfuse-3 to be in main. ** Affects: gnome-remote-desktop (Ubuntu) Importance: Medium Status: Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1930297 Title: Clipboard sharing is disabled when using RDP backend Status in gnome-remote-desktop package in Ubuntu: Triaged Bug description: We disabled RDP clipoard as part of gnome-remote-desktop 40.1-1 as it requires libfuse-3 to be in main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1930297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1916840] Re: gnome-remote-desktop-daemon crashed with SIGSEGV in rfbMakeRichCursorFromXCursor() from rfbSendCursorShape() from rfbSendFramebufferUpdate() from rfbUpdateClient()
This was fixed in gnome-remote-desktop 0.1.9-3 ** Changed in: gnome-remote-desktop (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1916840 Title: gnome-remote-desktop-daemon crashed with SIGSEGV in rfbMakeRichCursorFromXCursor() from rfbSendCursorShape() from rfbSendFramebufferUpdate() from rfbUpdateClient() from rfbProcessEvents() Status in GNOME Remote Desktop: Unknown Status in gnome-remote-desktop package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-remote-desktop. This problem was most recently seen with package version 0.1.9-3, the problem page at https://errors.ubuntu.com/problem/713181c657d8b2aabbee630257cc46cdb92bd308 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/gnome-remote-desktop/+bug/1916840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927393] Re: Potential privacy violation: The lock screen shows the desktop contents long enough to take a picture, before showing the password prompt.
I think that this bug could be considered a medium severity information disclosure vulnerability. I'm not concerned so much about my privacy as I am for a journalist or political dissenter who locks their screen while they have documents with sensitive information open on the screen. Then, when there is keyboard activity, the contents of any open documents on the desktop are shown long enough to take a picture with a cell phone before the login prompt is shown. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1927393 Title: Potential privacy violation: The lock screen shows the desktop contents long enough to take a picture, before showing the password prompt. Status in gnome-screensaver package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 The gnome-screensaver package is not installed, so I'm not sure which package handles the lock screen: sudo apt-cache policy gnome-screensaver [sudo] password for steve: gnome-screensaver: Installed: (none) Candidate: 3.6.1-11ubuntu4 Version table: 3.6.1-11ubuntu4 500 500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-screensaver (not installed) ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 6 08:43:26 2021 InstallationDate: Installed on 2020-11-22 (164 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-screensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1927393/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
Hi Paride Thanks for your feedback. I'm a bit confused and concerned that a critical behaviour like this has to be addressed on package level and is not part of aptitude, but so be it. I will file individual bug reports against the affected packages when a configuration file is next overridden in this package, to avoid to address something that may have already been fixed (e.g. I couldn't say when the last time ssh was updated and sshd_config overridden, while Compose was overridden just recently, and grub.cfg gets overridden almost every time discovery runs). Dominik -- 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/1929854 Title: Vital and critical configuration files get overridden by system updates without warning Status in grub2 package in Ubuntu: New Status in libx11 package in Ubuntu: New Status in openssh package in Ubuntu: Incomplete Bug description: • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of special compose keys defined. • In my /boot/grub/grub.cfg I have a very complicated special setup for my various boot configurations, and a 5-sec timout for my EFI-config. • My /etc/ssh/sshd_config contains a well-balanced configuration All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING or ASKING BACK by ubuntu system setups (discover). I set all of them to read-only by root and no-access for group and other users, but they still get overridden by every other system update. I even have a shutdown process in place which should actually make sure that changes to these files are reverted by writing a backup copy over any newly installed override — unfortunately, everything I did to run either a custom shutdown process or a startup process with systemd turned out to not work and be a nightmare to make work. How somebody could be as bold as to override vital configuration files like this without even asking for consent is one of the strange miracles in this world which I'll probably never understand. However, if "ubuntu" is really what it translates to, it should take a little bit more care about pre-existing configurations on systems on which it is set up and running well — until one system update suddenly jeopardizes the functioning of the entire system. I'm pretty sure these are not the only configuration files which are carelessly just overridden. They're just the ones every other update breaks my system and inflinges on my the costs of hours of research until I find out that — of course — it was an overridden critical system configuration again. The really mean thing is that you don't notice anything when you run the update … only next time you start your system and of course are not aware anymore that you did a system update, the new (absolutely wrong and/or insufficent) settings are in place and shoot you in the leg. Take an example from gentoo's etc-update feature which lets you merge new configuration files with pre-existing ones using a diff3-update. I went away from gentoo for other reasons, but I always praised that feature. Please make sure immediately that critical configuration files do not get overridden if they are non-writable by root, and then gradually introduce a system that merges changes to configuration files with the current situation on the target system. Or at least present the configs that would be changed in a particular directory, so that anybody who is interested in preserving local settings could merge them in a suitable way. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 27 18:48:15 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (132 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-53-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not
[Desktop-packages] [Bug 1929854] Re: Vital and critical configuration files get overridden by system updates without warning
Hello Dominik and thanks for this bug report. An umbrella bug report doesn't really help here, especially given that there's no single "reset config files on updates" policy in Ubuntu. Actually it's quite the contrary: as a Debian derivative Ubuntu basically inherits [1] and in particular [2]. Please file individual bug reports against the affected packages, possibly providing steps to reproduce the problem. In the case of openssh-server I can say that the overwrite shouldn't happen, as ssh_config is handles via ucf [3]. But let's discuss this in a dedicated bug, once opened. I'll just add that the newer versions of openssh- server support dropping custom config snippets in /etc/ssh/sshd_config.d/, for easier handling of custom configurations. Thanks! [1] https://www.debian.org/doc/debian-policy/ch-files.html#configuration-files [2] https://www.debian.org/doc/debian-policy/ch-files.html#behavior [3] http://manpages.ubuntu.com/manpages/focal/man1/ucf.1.html ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- 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/1929854 Title: Vital and critical configuration files get overridden by system updates without warning Status in grub2 package in Ubuntu: New Status in libx11 package in Ubuntu: New Status in openssh package in Ubuntu: Incomplete Bug description: • In my /usr/share/X11/locale/en_US.UTF-8/Compose I have about 10'000 lines of special compose keys defined. • In my /boot/grub/grub.cfg I have a very complicated special setup for my various boot configurations, and a 5-sec timout for my EFI-config. • My /etc/ssh/sshd_config contains a well-balanced configuration All these files are regularly overridden WITHOUT EVEN A SINGLE WARNING or ASKING BACK by ubuntu system setups (discover). I set all of them to read-only by root and no-access for group and other users, but they still get overridden by every other system update. I even have a shutdown process in place which should actually make sure that changes to these files are reverted by writing a backup copy over any newly installed override — unfortunately, everything I did to run either a custom shutdown process or a startup process with systemd turned out to not work and be a nightmare to make work. How somebody could be as bold as to override vital configuration files like this without even asking for consent is one of the strange miracles in this world which I'll probably never understand. However, if "ubuntu" is really what it translates to, it should take a little bit more care about pre-existing configurations on systems on which it is set up and running well — until one system update suddenly jeopardizes the functioning of the entire system. I'm pretty sure these are not the only configuration files which are carelessly just overridden. They're just the ones every other update breaks my system and inflinges on my the costs of hours of research until I find out that — of course — it was an overridden critical system configuration again. The really mean thing is that you don't notice anything when you run the update … only next time you start your system and of course are not aware anymore that you did a system update, the new (absolutely wrong and/or insufficent) settings are in place and shoot you in the leg. Take an example from gentoo's etc-update feature which lets you merge new configuration files with pre-existing ones using a diff3-update. I went away from gentoo for other reasons, but I always praised that feature. Please make sure immediately that critical configuration files do not get overridden if they are non-writable by root, and then gradually introduce a system that merges changes to configuration files with the current situation on the target system. Or at least present the configs that would be changed in a particular directory, so that anybody who is interested in preserving local settings could merge them in a suitable way. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 27 18:48:15 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (132 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64
[Desktop-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable
*** This bug is a duplicate of bug 1872778 *** https://bugs.launchpad.net/bugs/1872778 @adolf You can follow deziel's excellent advise in post #8 https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/comments/8 but you should still revert to your mail provider and look for their update plans. -- 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/1866974 Title: The Diffie-Hellman prime sent by the server is not acceptable Status in evolution package in Ubuntu: Confirmed Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: I can no longer connect to my ISP mail server. Works in previous version 19.10 "The reported error was “Failed to get capabilities: Error performing TLS handshake: The Diffie-Hellman prime sent by the server is not acceptable (not long enough).”." I've tried finding a workaround but so far no luck. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evolution 3.35.92-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 11:07:01 2020 InstallationDate: Installed on 2020-03-03 (7 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303) SourcePackage: evolution UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1866974/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930275] [NEW] Xorg freeze
Public bug reported: Ubuntu 20.10 suspend is not working. After suspend it does not wake up. And I have to hard reboot machine. It is happening since last few days. Here is error message I see from logs: "Failed to start Application launched by gnome-session-binary. A start job for unit UNIT has finished with a failure. The job identifier is 368 and the job result is failed. Failed to start LSB: OpenIPMI Driver init script. A start job for unit openipmi.service has finished with a failure. The job identifier is 151 and the job result is failed. " ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 09:04:06 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061] InstallationDate: Installed on 2020-02-15 (471 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-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 freeze groovy 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/1930275 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.10 suspend is not working. After suspend it does not wake up. And I have to hard reboot machine. It is happening since last few days. Here is error message I see from logs: "Failed to start Application launched by gnome-session-binary. A start job for unit UNIT has finished with a failure. The job identifier is 368 and the job result is failed. Failed to start LSB: OpenIPMI Driver init script. A start job for unit openipmi.service has finished with a failure. The job identifier is 151 and the job result is failed. " ProblemType: Bug
[Desktop-packages] [Bug 1930167] Re: New Firefox 88 freezes on Wayland then system crash
Hi there! This report page doesn't have any from reported version but it does have the report from the previous version, version 87: https://crash-stats.mozilla.org/report/index/09389e82-1bfb-43fe- bd10-2b8940210408 -- 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/1930167 Title: New Firefox 88 freezes on Wayland then system crash Status in firefox package in Ubuntu: Incomplete Bug description: After updating firefox deb to version 88, every time I play YouTube videos, some times in several tabs, then Wayland crashes and the system freezes. For try workaround this crash, I've to use the magic key SysRq (Alt + SysReq) with "REISUB" characters to safely reboot my Ubuntu though. Every time I open Firefox 88 deb via console, the message below appears even though these modules are installed: Gtk-Message: 14:01:56.615: Failed to load module "appmenu-gtk-module" Gtk-Message: 14:01:56.662: Failed to load module "canberra-gtk-module" Gtk-Message: 14:01:56.664: Failed to load module "canberra-gtk-module" /usr/share/libdrm/amdgpu.ids: No such file or directory I'm currently using Firefox 78 ESR snap because the main installation is unusable, unfortunately ... Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 88.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: douglas 15771 F pulseaudio /dev/snd/controlC2: douglas 15771 F pulseaudio /dev/snd/controlC0: douglas 15771 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 30 13:54:03 2021 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/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-12 (198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.2 metric 100 MostRecentCrashID: bp-09389e82-1bfb-43fe-bd10-2b8940210408 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/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=84.0.2/20210105180113 (Out of date) Profile0 - LastVersion=88.0.1/20210504152106 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-09389e82-1bfb-43fe-bd10-2b8940210408 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50d dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50d:bd07/02/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B350 MB dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930119] Re: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1
>From DpkgTerminalLog.txt: ==> Installing the chromium snap error: cannot perform the following tasks: - Download snap "chromium" (1595) from channel "stable" (download too slow: 0.00 bytes/sec) So this is a network issue, either on your end or with the snap store. Can you retry and let us know how it goes? sudo apt reinstall chromium-browser ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1930119 Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: i am install chromium browser but show some unwanted error ProblemType: Package DistroRelease: Ubuntu 21.04 Package: chromium-browser (not installed) ProcVersionSignature: Ubuntu 5.11.0-1008.8-raspi 5.11.12 Uname: Linux 5.11.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: chromium-browser:arm64: Install NULL: ConfigurePending Architecture: arm64 CasperMD5CheckResult: unknown Date: Tue May 25 19:57:47 2021 ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 ImageMediaBuild: 20210421 Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: chromium-browser Title: package chromium-browser (not installed) failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1930119/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray
*** This bug is a duplicate of bug 1905370 *** https://bugs.launchpad.net/bugs/1905370 @rajesh, have you updated gnome-shell-appindicator to the official update released for focal? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908921] Re: No system tray detected by hp-systray
*** This bug is a duplicate of bug 1905370 *** https://bugs.launchpad.net/bugs/1905370 this bug also affects me. neither of the suggested solutions work. (neither setting sleep nor downgrading gnome-shell-appindicator). any new suggestions are welcomed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1908921 Title: No system tray detected by hp-systray Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have hp-systray -x as one of the startup applications when I login. This app exits with the following error: HPLIP Status service No system tray detected on this system. Unable to start, exiting. Once logged in, if I start hp-systray -x from the terminal it works fine. This started happening after updating gnome-shell-extension- appindicator from version 33-1 to version 33.1-0ubuntu0.20.04.1. Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 21 11:41:23 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2016-06-10 (1655 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1908921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923505] Re: thunderbird 78.9.0 FTBFS on ppc64el
I am now seeing similar build failures (where the build hangs forever before eventually being killed) when building the firefox 89.0 release candidate, on pcc64el, on bionic and focal (the version of rustc is 1.47.0+dfsg1+llvm-1ubuntu1. Groovy, hirsute and impish are not affected. I need to look into it further to understand if the hang also happens when building the webrender crate. -- 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/1923505 Title: thunderbird 78.9.0 FTBFS on ppc64el Status in thunderbird package in Ubuntu: Triaged Bug description: The build hangs forever when compiling the webrender rust crate (see https://launchpad.net/ubuntu/+source/thunderbird/1:78.9.0+build2-0ubuntu3/+build/21368163). I'm attaching the full build log for future reference. This happens when building with rustc 1.50.0+dfsg1+llvm-0ubuntu4 and 1.50.0+dfsg1+llvm-0ubuntu5 (the latter is the version currently in the hirsute release pocket). The build completes when building with rustc 1.50.0+dfsg1+llvm-0ubuntu2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1923505/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930167] Re: New Firefox 88 freezes on Wayland then system crash
Thank you for the report Douglas. If you open "about:crashes" in firefox, are there corresponding crash entries? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- 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/1930167 Title: New Firefox 88 freezes on Wayland then system crash Status in firefox package in Ubuntu: Incomplete Bug description: After updating firefox deb to version 88, every time I play YouTube videos, some times in several tabs, then Wayland crashes and the system freezes. For try workaround this crash, I've to use the magic key SysRq (Alt + SysReq) with "REISUB" characters to safely reboot my Ubuntu though. Every time I open Firefox 88 deb via console, the message below appears even though these modules are installed: Gtk-Message: 14:01:56.615: Failed to load module "appmenu-gtk-module" Gtk-Message: 14:01:56.662: Failed to load module "canberra-gtk-module" Gtk-Message: 14:01:56.664: Failed to load module "canberra-gtk-module" /usr/share/libdrm/amdgpu.ids: No such file or directory I'm currently using Firefox 78 ESR snap because the main installation is unusable, unfortunately ... Thank you! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 88.0.1+build1-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: douglas 15771 F pulseaudio /dev/snd/controlC2: douglas 15771 F pulseaudio /dev/snd/controlC0: douglas 15771 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 30 13:54:03 2021 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/firefox/omni.ja:greprefs.js:352 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-11-12 (198 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.2 metric 100 MostRecentCrashID: bp-09389e82-1bfb-43fe-bd10-2b8940210408 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/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=84.0.2/20210105180113 (Out of date) Profile0 - LastVersion=88.0.1/20210504152106 RunningIncompatibleAddons: False SourcePackage: firefox SubmittedCrashIDs: bp-09389e82-1bfb-43fe-bd10-2b8940210408 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50d dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50d:bd07/02/2020:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: B350 MB dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1930167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926165] Re: Bass speakers not enabled on Lenovo Yoga 9i
@ivandrs, Looks like the patch works as expected, the Bass spk is assigned to NID 0x17 with the patched kernel. Now let us test the verbs. First, boot with the patched kernel, then run verbs in the #17, check if the bass spk works. If not work, please power off the machine then boot the machine with the patched kernel, then run the attached verbs (set-verbs-c930.sh, this verbs is composed according to hda-log-win.txt in the https://bugzilla.kernel.org/show_bug.cgi?id=205755) and check if the bass spk works or not. ** Bug watch added: Linux Kernel Bug Tracker #205755 https://bugzilla.kernel.org/show_bug.cgi?id=205755 ** Attachment added: "set-verb-c930.sh" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+attachment/5501304/+files/set-verb-c930.sh -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1926165 Title: Bass speakers not enabled on Lenovo Yoga 9i Status in alsa-driver package in Ubuntu: Confirmed Bug description: The Lenovo Yoga 9i has two sets of speakers: regular ones and bass speakers. The former work but while latter are detected and show up in alsamixer, they play no sound. Plugging headphones in and out or toggling any of the volume options does not fix the issue. A possibly related issue for a different Yoga version: https://bugzilla.kernel.org/show_bug.cgi?id=205755 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4466 F pulseaudio ubuntu 6219 F alsamixer /dev/snd/pcmC0D0p: ubuntu 4466 F...m pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.461 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 26 15:10:05 2021 LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - sof-hda-dsp Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [82BG, Realtek ALC287, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2021 dmi.bios.release: 1.40 dmi.bios.vendor: LENOVO dmi.bios.version: EHCN40WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 14ITL5 dmi.ec.firmware.release: 1.40 dmi.modalias: dmi:bvnLENOVO:bvrEHCN40WW:bd01/28/2021:br1.40:efr1.40:svnLENOVO:pn82BG:pvrYoga914ITL5:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrYoga914ITL5: dmi.product.family: Yoga 9 14ITL5 dmi.product.name: 82BG dmi.product.sku: LENOVO_MT_82BG_BU_idea_FM_Yoga 9 14ITL5 dmi.product.version: Yoga 9 14ITL5 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1926165/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer
Hi Daniel, sorry but in this case there is no error tracker for 2021-05-29: https://errors.ubuntu.com/user/39229ebea988d6578bed98d7e18bd96fd9cd523cf89495ed70d4ce4c0f8b7937667368f389be8d8b2588bafc31d1935109305b4abf52dbb724a7cf43c3b425b4 -- 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/1930192 Title: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter- offscreen-effect.c:213: Unable to create an Offscreen buffer Status in gnome-shell package in Ubuntu: Incomplete Bug description: Addition for bug report 1930128 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat May 29 12:20:21 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 GsettingsChanges: b'org.gnome.desktop.background' b'show-desktop-icons' b'true' b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true' b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false' b'org.gnome.desktop.session' b'idle-delay' b'uint32 0' InstallationDate: Installed on 2019-11-10 (566 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
** Changed in: oem-priority Assignee: (unassigned) => ethan.hsieh (ethan.hsieh) -- 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/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: New Status in OEM Priority Project focal series: New Status in xorg-server package in Ubuntu: Fix Released Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer
Thanks for the bug report. Unfortunately automatic crash dump analysis
seems to have failed but this looks like the problem:
g_warning ("%s: Unable to create an Offscreen buffer", G_STRLOC);
cogl_object_unref (priv->target);
priv->target = NULL;
Seems like the crash is probably priv->target being used as NULL,
somewhere. But we don't know where or why. Seems strange a GeForce RTX
2070 would run out of resources, if that's what you're still using...
Please 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.
** Tags added: nvidia
** 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/1930192
Title:
gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-
offscreen-effect.c:213: Unable to create an Offscreen buffer
Status in gnome-shell package in Ubuntu:
Incomplete
Bug description:
Addition for bug report 1930128
ProblemType: Crash
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.7-0ubuntu0.20.04.1
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: GNOME-Greeter:GNOME
Date: Sat May 29 12:20:21 2021
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
ExecutableTimestamp: 1608008084
GsettingsChanges:
b'org.gnome.desktop.background' b'show-desktop-icons' b'true'
b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true'
b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false'
b'org.gnome.desktop.session' b'idle-delay' b'uint32 0'
InstallationDate: Installed on 2019-11-10 (566 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
ProcCmdline: /usr/bin/gnome-shell
ProcCwd: /var/lib/gdm3
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/false
RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930192/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930128] Re: Xorg freeze
*** This bug is a duplicate of bug 1930192 ***
https://bugs.launchpad.net/bugs/1930192
** This bug has been marked a duplicate of bug 1930192
Addition for bug 1930128
--
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/1930128
Title:
Xorg freeze
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Hello!
I just started Foxit Reader to config it. While I browse through the
title menues to find the preferences the whole GDM or x.org sessione
freezes. The only way to restart was to some restart commands over the
Off-Shell (Ctrl + Alt + F3).
Wont fixed the issue:
- busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting...")'
- sudo killall -HUP gnome-shell
- sudo systemctl restart gdm (kicked me back to login after every login)
Fixed the issue:
- sudo systemctl restart systemd-logind
The last command fixed it after a short time. I tried to jump back
every time with Ctrl + Alt + F1 and anytime it worked.
I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.
I additionally attached you my latest protocols. In this time the
freeze occured.
Best regards,
Johannes
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54
UTC 2021
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 29 12:28:07 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A]
[1043:875c]
InstallationDate: Installed on 2019-11-10 (566 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.40
dmi.board.name: Z390 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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-server/+bug/1930128/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1930192] Re: gnome-shell crashed with SIGSEGV: ../clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer
** Summary changed: - Addition for bug 1930128 + gnome-shell crashed with SIGSEGV: ../clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer ** Summary changed: - gnome-shell crashed with SIGSEGV: ../clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer + gnome-shell crashed with SIGSEGV: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer ** Summary changed: - gnome-shell crashed with SIGSEGV: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer + gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter-offscreen-effect.c:213: Unable to create an Offscreen buffer -- 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/1930192 Title: gnome-shell crashed with SIGSEGV just after: clutter/clutter/clutter- offscreen-effect.c:213: Unable to create an Offscreen buffer Status in gnome-shell package in Ubuntu: New Bug description: Addition for bug report 1930128 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat May 29 12:20:21 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 GsettingsChanges: b'org.gnome.desktop.background' b'show-desktop-icons' b'true' b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true' b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false' b'org.gnome.desktop.session' b'idle-delay' b'uint32 0' InstallationDate: Installed on 2019-11-10 (566 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
** Description changed: + [Impact] + + Shell overview gets stuck where it's permanently toggled but not + visible. Only app windows appear in their overview state. Can't interact + with applications anymore. + + [Test Plan] + + 1. Log into GNOME. + 2. Press Super+A + 3. Click on 'Files' and wait till it has launched. + 4. Press the Super key. + Expect: Can interact with the application window. + + [Where problems could occur] + + Since the patch affects some of the core gnome-shell layout logic, + anything is possible. Risk has been mitigated by the patch being small. + + [Original description] + When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. - Since trying 21.04 sometimes this + Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window - 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. + 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Hirsute: In Progress Status in gnome-shell source package in Impish: Won't Fix Bug description: [Impact] Shell overview gets stuck where it's permanently toggled but not visible. Only app windows appear in their overview state. Can't interact with applications anymore. [Test Plan] 1. Log into GNOME. 2. Press Super+A 3. Click on 'Files' and wait till it has launched. 4. Press the Super key. Expect: Can interact with the application window. [Where problems could occur] Since the patch affects some of the core gnome-shell layout logic, anything is possible. Risk has been mitigated by the patch being small. [Original description] When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06
[Desktop-packages] [Bug 1930128] Re: Xorg freeze
Done. :)
--
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/1930128
Title:
Xorg freeze
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Hello!
I just started Foxit Reader to config it. While I browse through the
title menues to find the preferences the whole GDM or x.org sessione
freezes. The only way to restart was to some restart commands over the
Off-Shell (Ctrl + Alt + F3).
Wont fixed the issue:
- busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting...")'
- sudo killall -HUP gnome-shell
- sudo systemctl restart gdm (kicked me back to login after every login)
Fixed the issue:
- sudo systemctl restart systemd-logind
The last command fixed it after a short time. I tried to jump back
every time with Ctrl + Alt + F1 and anytime it worked.
I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.
I additionally attached you my latest protocols. In this time the
freeze occured.
Best regards,
Johannes
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54
UTC 2021
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 29 12:28:07 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A]
[1043:875c]
InstallationDate: Installed on 2019-11-10 (566 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.40
dmi.board.name: Z390 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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-server/+bug/1930128/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930192] Re: Addition for bug 1930128
** Information type changed from Private to Public -- 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/1930192 Title: Addition for bug 1930128 Status in gnome-shell package in Ubuntu: New Bug description: Addition for bug report 1930128 ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106 Uname: Linux 5.4.0-73-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Greeter:GNOME Date: Sat May 29 12:20:21 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1608008084 GsettingsChanges: b'org.gnome.desktop.background' b'show-desktop-icons' b'true' b'org.gnome.desktop.lockdown' b'disable-lock-screen' b'true' b'org.gnome.desktop.screensaver' b'idle-activation-enabled' b'false' b'org.gnome.desktop.session' b'idle-delay' b'uint32 0' InstallationDate: Installed on 2019-11-10 (566 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /var/lib/gdm3 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1930192/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
Ubuntu fix proposed in https://salsa.debian.org/gnome-team/gnome- shell/-/merge_requests/49 -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Hirsute: In Progress Status in gnome-shell source package in Impish: Won't Fix Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1930128] Re: Xorg freeze
Bug 1930192 is private so I can't view it. Please:
1. Remove any sensitive personal data from the bug that you don't wish
to share and then
2. Change bug 1930192 to Public (top right of the page).
--
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/1930128
Title:
Xorg freeze
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Hello!
I just started Foxit Reader to config it. While I browse through the
title menues to find the preferences the whole GDM or x.org sessione
freezes. The only way to restart was to some restart commands over the
Off-Shell (Ctrl + Alt + F3).
Wont fixed the issue:
- busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting...")'
- sudo killall -HUP gnome-shell
- sudo systemctl restart gdm (kicked me back to login after every login)
Fixed the issue:
- sudo systemctl restart systemd-logind
The last command fixed it after a short time. I tried to jump back
every time with Ctrl + Alt + F1 and anytime it worked.
I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.
I additionally attached you my latest protocols. In this time the
freeze occured.
Best regards,
Johannes
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54
UTC 2021
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 29 12:28:07 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A]
[1043:875c]
InstallationDate: Installed on 2019-11-10 (566 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.40
dmi.board.name: Z390 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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-server/+bug/1930128/+subscriptions
--
Mailing list:
[Desktop-packages] [Bug 1930128] Re: Xorg freeze
Hi Daniel!
Thank you for your help. I've tried step 1 and 2 but both failed at
first. So I've done step 3 and applied the workaround, restarted the
system and tried to reproduce the issue. Nothing, all is working fine.
But now I've tried to resend the crash file and now it worked.
Here's the new bug report: https://bugs.launchpad.net/ubuntu/+source
/gnome-shell/+bug/1930192
--
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/1930128
Title:
Xorg freeze
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Hello!
I just started Foxit Reader to config it. While I browse through the
title menues to find the preferences the whole GDM or x.org sessione
freezes. The only way to restart was to some restart commands over the
Off-Shell (Ctrl + Alt + F3).
Wont fixed the issue:
- busctl --user call org.gnome.Shell /org/gnome/Shell org.gnome.Shell Eval s
'Meta.restart("Restarting...")'
- sudo killall -HUP gnome-shell
- sudo systemctl restart gdm (kicked me back to login after every login)
Fixed the issue:
- sudo systemctl restart systemd-logind
The last command fixed it after a short time. I tried to jump back
every time with Ctrl + Alt + F1 and anytime it worked.
I have no idea if this is a Foxit Reader bug or a issue by GDM/xorg.
I additionally attached you my latest protocols. In this time the
freeze occured.
Best regards,
Johannes
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54
UTC 2021
GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May 29 12:28:07 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
nvidia, 460.80, 5.4.0-73-generic, x86_64: installed
virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
NVIDIA Corporation TU106 [GeForce RTX 2070 Rev. A] [10de:1f07] (rev a1)
(prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2070 Rev. A]
[1043:875c]
InstallationDate: Installed on 2019-11-10 (566 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-73-generic
root=UUID=454b3874-3032-4cb6-9e5c-92a00ed53afb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/02/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P4.40
dmi.board.name: Z390 Phantom Gaming 4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrP4.40:bd12/02/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ390PhantomGaming4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~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:
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Roman, please try these separately: * Logging into 'Ubuntu on Wayland' (select it on the login screen). * A newer kernel such as: - https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/amd64/ - https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12.8/amd64/ (you need all .debs _except_ the "lowlatency" ones) -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
That's unrelated and should get a separate report because it means something has crashed. This bug is not a crash. -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in gnome-shell 3.38
This is now "Won't fix" for Ubuntu 21.10 because the offending code won't exist anymore by the time 21.10 gets GNOME 40.x A fix will still be created for Ubuntu 21.04. ** Changed in: gnome-shell (Ubuntu Hirsute) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu Impish) Status: In Progress => Won't Fix -- 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/1922353 Title: Overview sometimes fails to appear or disappear in gnome-shell 3.38 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell source package in Hirsute: In Progress Status in gnome-shell source package in Impish: Won't Fix Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 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: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Yes, it is still the same configuration. I also get another issue all the time, maybe it is somewhat connected to this one: When switching between users, either Gnome or X crashes. The OS asks me each time to send a report and I did it a few times. Or maybe this is worth a separate bug report? ** Attachment added: "newjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+attachment/5501256/+files/newjournal.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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856032] Re: Removable media icon stays on the dock after eject.
** Changed in: oem-priority Importance: Undecided => Low -- 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/1856032 Title: Removable media icon stays on the dock after eject. Status in OEM Priority Project: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: 1) Ubuntu 19.10 2) Dock 3) I placed a DVD in the optical drive. An optical disc with a DVD tag appeared on the dock. I pressed the button on the optical drive to open it. I removed the disc and pressed in the tray. The icon should have disappeared from the dock. 4) The icon did NOT disappear from the dock. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1856032/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1730606] Re: systemd idleaction=suspend not working in multiseat while a screen is showing login prompt
After upgrade to Ubuntu version 20.4 the issue with the idle status reporting by lightdm-greeter remains. This continues to have idle setting of logind.conf ignored: https://www.freedesktop.org/software/systemd/man/logind.conf.html > Note that this requires that user sessions correctly report the idle status > to the system. The system will execute the action after *all sessions* report > that they are idle, no idle inhibitor lock is active, and subsequently, the > time configured with IdleActionSec= (see below) has expired. At the other hand, installing lightdm and unity-greeter causes suspend to happen every 20 minutes while one screen shows greeter, regardless of all other screens. Reported also at https://askubuntu.com/questions/1337649/how-to-disable-suspend-in-20 -minutes-from-the-lightdm-login-screen and as https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1928305 There is a workaround available there (set both org.gnome.settings- daemon.plugins.power and com.canonical.unity.settings- daemon.plugins.power sleep-inactive-ac-type to 'nothing'), preventing the unexpected suspend by greeter. Issue of this bug remains since the greeter still does not report idle to logind. The script to check idle status of all session and force suspend overriding login screen needs update, systemd-inhibit --list does not have parseable output, like it was the case in systemd version 229. Needed to be replaced by command gdbus call --system --dest org.freedesktop.login1 --object-path /org/freedesktop/login1 --method org.freedesktop.login1.Manager.ListInhibitors There are several other reports of this problem, for example also at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896083 or https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/22 but I am not sure about be the best upstream place to track this. It looks like gdm/lightdm greeter is not designed to work under logind but attempts to control the system sleep status on its own. ** Bug watch added: Debian Bug tracker #896083 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=896083 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #22 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/22 ** Attachment added: "Workaround, checking idle/inhibit status of all sessions, ignoring greeter" https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606/+attachment/5501243/+files/idlecheck.pl -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1730606 Title: systemd idleaction=suspend not working in multiseat while a screen is showing login prompt Status in lightdm package in Ubuntu: Confirmed Bug description: Ubuntu 16.04.3 LTS, multiseat setup. systemd: Installed: 229-4ubuntu21 lightdm: Installed: 1.18.3-0ubuntu1.1 logind.conf:IdleAction=suspend logind.conf:IdleActionSec=300 Using multiseat, it is not possible to have gnome settings controlling idle suspend, as it would ignore the other seat. IdleAction=suspend in /etc/systemd/logind.conf works well, provided both seats are logged in or locked. After boot, or after logout the seat remains showing login screen and the system never suspends. loginctl show-session provides IdleHint=yes that allows to determine whether the user is active. For some reason Active property is yes all the time. But for the login screen the show-session does not provide the hint about seat idling: $ loginctl show-session c9 Id=c9 User=108 Name=lightdm Timestamp=Sun 2017-11-05 22:35:37 CET TimestampMonotonic=13418600852 VTNr=7 Seat=seat0 Display=:1 Remote=no Service=lightdm-greeter Scope=session-c9.scope Leader=12431 Audit=0 Type=x11 Class=greeter Active=yes State=active IdleHint=no IdleSinceHint=0 IdleSinceHintMonotonic=0 Working on a script to check for IdleHint=Yes and Service=lightdm- greeter and suspend based on this. I am marking this as a bug in lightdm because I think it is not correctly reporting the idle status to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1730606/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
