[Desktop-packages] [Bug 1933198] Re: [nvidia] Display mode after wake-up
You can install other desktop environments by: sudo apt install unity-session sudo apt install xfce4-session etc... Then on the login screen use the icon in the bottom right corner of the screen to select which one. -- 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/1933198 Title: [nvidia] Display mode after wake-up Status in mutter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: My dual display setup sometimes switches to a mirror display mode (from joined display) when waking up from sleep. This could be totally unrelated but I have two graphic cards, and both screens are connected to the same one (Hdmi and display port). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular file. .proc.driver.nvidia.gpus..26.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 06:55:54 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 22 09:26:34 2021 DistUpgraded: 2021-06-09 14:41:25,219 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 460.80, 5.11.0-18-generic, x86_64: installed nvidia, 460.80, 5.8.0-55-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2060 Rev. A] [1458:37d9] NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:146b] InstallationDate: Installed on 2021-04-16 (66 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd MS-7B86 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=cbccb375-44f4-4f88-a12a-2a70cc613676 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-06-09 (12 days ago) dmi.bios.date: 04/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: H.60 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B450 GAMING PLUS MAX (MS-7B86) dmi.board.vendor: Micro-Star International Co., Ltd dmi.board.version: 3.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd dmi.chassis.version: 3.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrH.60:bd04/18/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr3.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUSMAX(MS-7B86):rvr3.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr3.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B86 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 3.0 dmi.sys.vendor: Micro-Star International Co., Ltd 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.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1933198/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Bluez bug (https://github.com/bluez/bluez/issues/162) closed and fix merged in bluez. https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=c939747f543a76ffd556312f753cf9d36c047c94 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Unknown Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Robie, "Fix Committed" means the fix is committed here: https://git.launchpad.net/~bluetooth/bluez/commit/?id=04298c5e46 It's part of the 5.59 release for Impish that is awaiting sponsorship (bug 1933078). Declaring "Fix Committed" when a fix exists in an upstream tributary before anything has reached proposed is a procedure requested by seb128 and we now follow on the desktop team. ** Also affects: bluez via https://github.com/bluez/bluez/issues/162 Importance: Unknown Status: Unknown ** Tags added: fixed-in-bluez-5.60 fixed-upstream -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in Bluez Utilities: Unknown Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1100326]
Doesn't look like I have permission to re-open, but I'd love to see this or some alternatively to allow integrating with any system geolocation methods I have set up, such as a Bluetooth GPS. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1100326 Title: Location requested by websites should be able to use GPS/mobile positioning Status in Chromium Browser: Fix Committed Status in Mozilla Firefox: Unknown Status in GeoClue: Won't Fix Status in WebKit: Fix Released Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-providers package in Ubuntu: Invalid Bug description: It would be nice if location requested by websites could use location found from GPS or GSM/CDMA positioning. To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1100326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899989] Re: outdated instructions on bookmarking
The upstream fix was included in gnome-user-docs 3.38.2+git20210212-0ubuntu1. ** Changed in: gnome-user-docs (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1899989 Title: outdated instructions on bookmarking Status in Gnome Documentation: Unknown Status in gnome-user-docs package in Ubuntu: Fix Released Bug description: This page is wrong: https://help.ubuntu.com/stable/ubuntu-help/nautilus-bookmarks-edit.html.en Under 'Add a bookmark:' it should simply read: Press Ctrl + d The mentioned menu was removed in Ubuntu 20.04, it is available in 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-docs/+bug/1899989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 461128]
So it's WFM anyway after years -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/461128 Title: [Upstream] Draw shifts, breaks apart, and merges icons importing SVG Status in LibreOffice: Invalid Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 2) apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:3.4.2-2ubuntu3 Candidate: 1:3.4.2-2ubuntu3 Version table: *** 1:3.4.2-2ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Draw via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887683/+files /gliffy-biznet.svg && lodraw -nologo gliffy-biznet.svg is the file looks as it does in Inkscape. 4) What happens instead is all the icons are shifed around as shown by a screenshot: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887688/+files /gliffy-biznet-ooomangle.png ProblemType: Bug Architecture: amd64 Date: Mon Oct 26 15:17:08 2009 DistroRelease: Ubuntu 9.10 Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:3239): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (npviewer.bin:4074): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/461128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 461128]
No longer reproducible with Version: 6.2.0.0.alpha0+ Build ID: f5f6781acb292783033caea0147ff98490c78d89 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-06-23_00:13:45 Locale: de-DE (de_DE); Calc: CL Was still REPRODUCIBLE with Version: 6.1.0.0.alpha0+ (x64) Build ID: 77adb770164fd703a31d8e828d777a4f827a5407 CPU threads: 4; OS: Windows 6.1; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2017-12-17_03:10:29 Locale: de-DE (de_DE); Calc: group threaded So WFM target 6.2.? I did not check possible other reasons for the problem like User Profile related ones. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/461128 Title: [Upstream] Draw shifts, breaks apart, and merges icons importing SVG Status in LibreOffice: Invalid Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 2) apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:3.4.2-2ubuntu3 Candidate: 1:3.4.2-2ubuntu3 Version table: *** 1:3.4.2-2ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Draw via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887683/+files /gliffy-biznet.svg && lodraw -nologo gliffy-biznet.svg is the file looks as it does in Inkscape. 4) What happens instead is all the icons are shifed around as shown by a screenshot: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887688/+files /gliffy-biznet-ooomangle.png ProblemType: Bug Architecture: amd64 Date: Mon Oct 26 15:17:08 2009 DistroRelease: Ubuntu 9.10 Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:3239): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (npviewer.bin:4074): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/461128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 461128]
Dear Christopher M. Penalver, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/461128 Title: [Upstream] Draw shifts, breaks apart, and merges icons importing SVG Status in LibreOffice: Invalid Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 2) apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:3.4.2-2ubuntu3 Candidate: 1:3.4.2-2ubuntu3 Version table: *** 1:3.4.2-2ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Draw via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887683/+files /gliffy-biznet.svg && lodraw -nologo gliffy-biznet.svg is the file looks as it does in Inkscape. 4) What happens instead is all the icons are shifed around as shown by a screenshot: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887688/+files /gliffy-biznet-ooomangle.png ProblemType: Bug Architecture: amd64 Date: Mon Oct 26 15:17:08 2009 DistroRelease: Ubuntu 9.10 Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:3239): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (npviewer.bin:4074): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/461128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 461128] Re: [Upstream] Draw shifts, breaks apart, and merges icons importing SVG
** Changed in: df-libreoffice Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/461128 Title: [Upstream] Draw shifts, breaks apart, and merges icons importing SVG Status in LibreOffice: Invalid Status in OpenOffice: Invalid Status in libreoffice package in Ubuntu: Confirmed Status in openoffice.org package in Ubuntu: Won't Fix Bug description: Binary package hint: openoffice.org 1) lsb_release -rd Description: Ubuntu oneiric (development branch) Release: 11.10 2) apt-cache policy libreoffice-draw libreoffice-draw: Installed: 1:3.4.2-2ubuntu3 Candidate: 1:3.4.2-2ubuntu3 Version table: *** 1:3.4.2-2ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 3) What is expected to happen in LibreOffice Draw via the Terminal: cd ~/Desktop && wget https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887683/+files /gliffy-biznet.svg && lodraw -nologo gliffy-biznet.svg is the file looks as it does in Inkscape. 4) What happens instead is all the icons are shifed around as shown by a screenshot: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/461128/+attachment/887688/+files /gliffy-biznet-ooomangle.png ProblemType: Bug Architecture: amd64 Date: Mon Oct 26 15:17:08 2009 DistroRelease: Ubuntu 9.10 Package: openoffice.org-core 1:3.1.1-5ubuntu1 ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: openoffice.org Uname: Linux 2.6.31-14-generic x86_64 XsessionErrors: (polkit-gnome-authentication-agent-1:3239): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (npviewer.bin:4074): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/461128/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1141034] Re: [upstream] RTL Spreadsheet Insert Cells
** Changed in: df-libreoffice Status: Confirmed => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1141034 Title: [upstream] RTL Spreadsheet Insert Cells Status in LibreOffice: In Progress Status in libreoffice package in Ubuntu: Confirmed Bug description: When using a right-to-left spreadsheet, right clicking and selected "insert cells" shows the normal LTR option to shift cells right, although when used it actually shifts cells left. I believe that shifting cells left is the correct behaviour in this case, but the text of the option should be changed to read "shift cells left". This was first noticed when using the Hebrew language user interface, but the problem is present when using English UI too. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice-calc 1:3.5.7-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37 Uname: Linux 3.2.0-38-generic i686 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: i386 CheckboxSubmission: ad9a15703e19217cb3448f881e125f6a CheckboxSystem: abc83e3988b72e7c3a9b3aa684cb92fd Date: Sun Mar 3 00:47:21 2013 MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: Upgraded to precise on 2012-05-01 (305 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1141034/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x
I tested evolution-data-server version 3.40.0-1ubuntu1.1 from proposed in Hirsute. I can confirm that iCloud accounts can be accessed again. Thanks for your work, Brian, Sebastien and Iain! ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1925742 Title: Recent iCloud versions trigger an issue in IMAP x Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Focal: Fix Released Status in evolution-data-server source package in Hirsute: Fix Committed Bug description: * Impact The Icloud service introduced changes that are confusing evolution- data-server which means evolution is now failing to connect to the email server * Test case Set up an iCloud account and try to use it for emails in evolution * Regression potential The change is in the imapx connection code, it could create problems with other type of servers so we should try to test on different providers. - The bug has been fixed yesterday by Evolution's developer: https://gitlab.gnome.org/GNOME/evolution/-/issues/1468 However, the package in Ubuntu (at least in Focal Fosa) still needs to be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933365] [NEW] [MINOR] The localization pack is not installed by default
Public bug reported: Hello, the Ubuntu installer does not install localization packs for Firefox. Instead, Firefox uses English by default and the packages have to be downloaded manually. This may affect other users too, and this may be bad for their user experience. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1933365 Title: [MINOR] The localization pack is not installed by default Status in firefox package in Ubuntu: New Bug description: Hello, the Ubuntu installer does not install localization packs for Firefox. Instead, Firefox uses English by default and the packages have to be downloaded manually. This may affect other users too, and this may be bad for their user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1933365/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933361] Re: Audio Problem, soundcard not detected
You forgot to install linux-modules-extra package, the audio driver is in that package. -- 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/1933361 Title: Audio Problem, soundcard not detected Status in alsa-driver package in Ubuntu: New Bug description: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from the HDMI cable. My GPU is an GTX 1080 Ti. I have got a KVM Switch in which is connected my monitor, Keyboard and Mouse. Before the last update of Ubuntu, all worked well. When I go to settings in Ubuntu, I couldn't watch any audio device check the image attached. Regards. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 17:30:22 2021 InstallationDate: Installed on 2021-01-14 (159 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
** Changed in: xwayland (Ubuntu Hirsute) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: Invalid Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933361] Re: Audio Problem, soundcard not detected
Added aditional info. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+attachment/5506501/+files/prevboot.txt -- 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/1933361 Title: Audio Problem, soundcard not detected Status in alsa-driver package in Ubuntu: New Bug description: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from the HDMI cable. My GPU is an GTX 1080 Ti. I have got a KVM Switch in which is connected my monitor, Keyboard and Mouse. Before the last update of Ubuntu, all worked well. When I go to settings in Ubuntu, I couldn't watch any audio device check the image attached. Regards. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 17:30:22 2021 InstallationDate: Installed on 2021-01-14 (159 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933361] Re: Audio Problem, soundcard not detected
Added aditional info. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+attachment/5506502/+files/lspcik.txt -- 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/1933361 Title: Audio Problem, soundcard not detected Status in alsa-driver package in Ubuntu: New Bug description: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from the HDMI cable. My GPU is an GTX 1080 Ti. I have got a KVM Switch in which is connected my monitor, Keyboard and Mouse. Before the last update of Ubuntu, all worked well. When I go to settings in Ubuntu, I couldn't watch any audio device check the image attached. Regards. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 17:30:22 2021 InstallationDate: Installed on 2021-01-14 (159 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933361] [NEW] Audio Problem, soundcard not detected
Public bug reported: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from the HDMI cable. My GPU is an GTX 1080 Ti. I have got a KVM Switch in which is connected my monitor, Keyboard and Mouse. Before the last update of Ubuntu, all worked well. When I go to settings in Ubuntu, I couldn't watch any audio device check the image attached. Regards. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 17:30:22 2021 InstallationDate: Installed on 2021-01-14 (159 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ** Attachment added: "Captura de pantalla de 2021-06-23 17-35-37.png" https://bugs.launchpad.net/bugs/1933361/+attachment/5506495/+files/Captura%20de%20pantalla%20de%202021-06-23%2017-35-37.png ** Description changed: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from the HDMI cable. My GPU is an GTX 1080 Ti. + I have got a KVM Switch in which is connected my Screen, Keyboard and + Mouse. + + Before the last update of Ubuntu, all worked well. + When I go to settings in Ubuntu, I couldn't watch any audio device check the image attached. - Regards. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 17:30:22 2021 InstallationDate: Installed on 2021-01-14 (159 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=es_ES.UTF-8 - SHELL=/bin/bash + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=es_ES.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3001 dmi.board.asset.tag: Default string dmi.board.name: PRIME X570-PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Description changed: Hi, After last patch in Ubuntu 20.04.2 LTS, I have lost my audio. I have got an Asus monitor with speakers inside the monitor. The sound come to the monitor from
[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on a Thinkpad E480 Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When the screen of my laptop (Thinkpad E480) is supposed to turn off (because of inactivity or when actively locking screen), the screen dims, turns off for a second and then turns back on while remaining dimmed. I can see the backlight of the screen and the cursor. This bug is only present when using a wayland-session regardless of my settings. It also happens with a fresh user account. Additionally, I tested with the 5.8 and 5.12 kernels with the same result. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 26 08:13:27 2021 InstallationDate: Installed on 2021-05-24 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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-settings-daemon/+bug/1929650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480
Same problem on Asus Zenbook 14/Ubuntu 21.04. Backlight stays on even in Suspend mode. Did not have that problem with 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on a Thinkpad E480 Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When the screen of my laptop (Thinkpad E480) is supposed to turn off (because of inactivity or when actively locking screen), the screen dims, turns off for a second and then turns back on while remaining dimmed. I can see the backlight of the screen and the cursor. This bug is only present when using a wayland-session regardless of my settings. It also happens with a fresh user account. Additionally, I tested with the 5.8 and 5.12 kernels with the same result. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 26 08:13:27 2021 InstallationDate: Installed on 2021-05-24 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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-settings-daemon/+bug/1929650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on a Thinkpad E480
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on a Thinkpad E480 Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When the screen of my laptop (Thinkpad E480) is supposed to turn off (because of inactivity or when actively locking screen), the screen dims, turns off for a second and then turns back on while remaining dimmed. I can see the backlight of the screen and the cursor. This bug is only present when using a wayland-session regardless of my settings. It also happens with a fresh user account. Additionally, I tested with the 5.8 and 5.12 kernels with the same result. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 26 08:13:27 2021 InstallationDate: Installed on 2021-05-24 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) 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-settings-daemon/+bug/1929650/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Merge proposal unlinked:
https://code.launchpad.net/~os369510/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/403448
** Project changed: plainbox-provider-checkbox => ubuntu-translations
** No longer affects: ubuntu-translations
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
In Progress
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/issues #1358 https://gitlab.freedesktop.org/mesa/mesa/issues/1358 ** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #4275 https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Also, the current upload references bug 1933221 which is a dupe. I'm not sure how SRU tooling will handle this. Unless you can confirm that it will work, please could you reference the master bug in your upload instead? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
The fix for this seems missing in Impish. What does "Fix Committed" mean here? What are your plans to fix this in Impish? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1933198] Re: [nvidia] Display mode after wake-up
I would need help on how to try that, and testing it would be rather inconvenient since the problem doesn't show up every time. But if you can provide instructions I could try (sorry I'm a regular user without any technical knowledge). I can say this is a recent problem though Le mer. 23 juin 2021 à 04:15, Daniel van Vugt <1933...@bugs.launchpad.net> a écrit : > Thanks. This is a recurring issue in mutter/gnome-shell so I don't think > it's driver specific. > > To confirm if it is a mutter bug only, are you able to test some other > desktop environment(s) that use Xorg? > > ** Package changed: nvidia-graphics-drivers-460 (Ubuntu) => xorg-server > (Ubuntu) > > ** Changed in: xorg-server (Ubuntu) >Status: New => Incomplete > > ** Changed in: mutter (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1933198 > > Title: > [nvidia] Display mode after wake-up > > Status in mutter package in Ubuntu: > Incomplete > Status in xorg-server package in Ubuntu: > Incomplete > > Bug description: > My dual display setup sometimes switches to a mirror display mode > (from joined display) when waking up from sleep. > > This could be totally unrelated but I have two graphic cards, and both > screens are connected to the same one (Hdmi and display port). > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: xorg 1:7.7+22ubuntu1 > ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 > Uname: Linux 5.11.0-18-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular > file. > .proc.driver.nvidia.capabilities.gpu1: Error: path was not a regular > file. > .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. > .proc.driver.nvidia.gpus..25.00.0: Error: path was not a regular > file. > .proc.driver.nvidia.gpus..26.00.0: Error: path was not a regular > file. > .proc.driver.nvidia.registry: Binary: "" > .proc.driver.nvidia.suspend: suspend hibernate resume > .proc.driver.nvidia.suspend_depth: default modeset uvm > .proc.driver.nvidia.version: >NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.80 Fri May 7 > 06:55:54 UTC 2021 >GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) > ApportVersion: 2.20.11-0ubuntu65.1 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: unknown > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Jun 22 09:26:34 2021 > DistUpgraded: 2021-06-09 14:41:25,219 DEBUG Running PostInstallScript: > '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' > DistroCodename: hirsute > DistroVariant: ubuntu > DkmsStatus: >nvidia, 460.80, 5.11.0-18-generic, x86_64: installed >nvidia, 460.80, 5.8.0-55-generic, x86_64: installed > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >NVIDIA Corporation TU106 [GeForce RTX 2060 Rev. A] [10de:1f08] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: Gigabyte Technology Co., Ltd TU106 [GeForce RTX 2060 Rev. > A] [1458:37d9] >NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:2484] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: NVIDIA Corporation GA104 [GeForce RTX 3070] [10de:146b] > InstallationDate: Installed on 2021-04-16 (66 days ago) > InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 > (20201022) > MachineType: Micro-Star International Co., Ltd MS-7B86 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=fr_FR.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic > root=UUID=cbccb375-44f4-4f88-a12a-2a70cc613676 ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > UpgradeStatus: Upgraded to hirsute on 2021-06-09 (12 days ago) > dmi.bios.date: 04/18/2020 > dmi.bios.release: 5.14 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: H.60 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: B450 GAMING PLUS MAX (MS-7B86) > dmi.board.vendor: Micro-Star International Co., Ltd > dmi.board.version: 3.0 > dmi.chassis.asset.tag: To be filled by O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Micro-Star International Co., Ltd > dmi.chassis.version: 3.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrH.60:bd04/18/2020:br5.14:svnMicro-StarInternationalCo.,Ltd:pnMS-7B86:pvr3.0:rvnMicro-StarInternationalCo.,Ltd:rnB450GAMINGPLUSMAX(MS-7B86):rvr3.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr3.0: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: MS-7B86 > dmi.product.sku: To be filled by O.E.M. > dmi.product.version: 3.0 > dmi.sys.vendor: Micro-Star International Co., Ltd > version.compiz: compiz N/A > version.libdrm2: libdrm2
[Desktop-packages] [Bug 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned
you seem to have some problem with /usr/bin/deb-systemd-invoke, which is a perl script, but it seems to be getting called by /bin/sh. You should try reinstalling init-system-helpers to fix any problem with your script, and/or if you made any changes yourself manually that may be causing the problem. $ sudo apt --reinstall install init-system-helpers ** Package changed: fprintd (Ubuntu) => init-system-helpers (Ubuntu) ** Changed in: init-system-helpers (Ubuntu) Status: New => Incomplete -- 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/1933188 Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post- installation script subprocess returned error exit status 2 Status in init-system-helpers package in Ubuntu: Incomplete Bug description: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/1933188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned
** Package changed: systemd (Ubuntu) => fprintd (Ubuntu) -- 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/1933188 Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post- installation script subprocess returned error exit status 2 Status in fprintd package in Ubuntu: New Bug description: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fprintd/+bug/1933188/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933188] [NEW] package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returne
You have been subscribed to a public bug: Got this problem when doing a regular "Update/upgrade" from shell /usr/bin/deb-systemd-invoke: 32 =head1: not found /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected Endless loop of these two lines in bash before the crash. June 22 sentout uopdate ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114 Uname: Linux 5.4.0-74-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.18 AptOrdering: alsa-ucm-conf:amd64: Install libpam-fprintd:amd64: Install fprintd:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 22 06:52:05 2021 ErrorMessage: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-03-29 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 SourcePackage: fprintd Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fprintd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned error exit status 2 https://bugs.launchpad.net/bugs/1933188 You received this bug notification because you are a member of Desktop Packages, which is subscribed to fprintd in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()
Well, maybe or not but I don't understand how to install the patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871959 Title: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush() Status in Mesa: Unknown Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f --- nothing particular done to trigger this, just opening the lid apparently crashed the x server (ubuntu 20.04); then after reboot apport prompted me to report a crash ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: xserver-xorg-core 2:1.20.7-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Fri Apr 10 00:50:52 2020 DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56 DistroCodename: focal DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9] InstallationDate: Installed on 2019-11-27 (134 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0029 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5500 ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 __GI_abort () at abort.c:79 ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so Title: Xorg crashed with SIGABRT in __GI_raise() UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago) UserGroups: dmi.bios.date: 08/21/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0M14W7 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5500 dmi.product.sku: 08B9 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1871959/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
I can replicate the issue on a freshly flashed groovy image. However, once the image is fully upgraded (via a typical apt update+upgrade followed by a reboot), I'm unable to replicate the issue any more. Would be interested to hear if any one else can replicate the issue either on hirsute (fresh or upgraded), or on a fully upgraded groovy system. If not, I suspect this can be closed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: Confirmed Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
Hi @Daniel, I created a public bug in github/bluez, mp is sent by maintainer. https://github.com/bluez/bluez/issues/162 ** Bug watch added: github.com/bluez/bluez/issues #162 https://github.com/bluez/bluez/issues/162 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933340] Re: merge package with Debian
A merge with Debian packaging is done regularly already. https://git.launchpad.net/~libreoffice/ubuntu/+source/libreoffice/ ** Changed in: libreoffice (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1933340 Title: merge package with Debian Status in libreoffice package in Ubuntu: Invalid Bug description: while looking at LP: #1891623, I noticed that the LO packaging wasn't merged for a longer time, not importing some fixes from Debian. Please merge the package from Debian, and continue to do that on a regular basis. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1933340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933340] [NEW] merge package with Debian
Public bug reported: while looking at LP: #1891623, I noticed that the LO packaging wasn't merged for a longer time, not importing some fixes from Debian. Please merge the package from Debian, and continue to do that on a regular basis. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: rls-ii-incoming ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1933340 Title: merge package with Debian Status in libreoffice package in Ubuntu: New Bug description: while looking at LP: #1891623, I noticed that the LO packaging wasn't merged for a longer time, not importing some fixes from Debian. Please merge the package from Debian, and continue to do that on a regular basis. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1933340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4
@Sebastien, even identifying the exact change in gcc-9 won't be enough. It boils down to a miscompiled issue in two million lines of code. Already ten months ago, I asked to do proper debugging in LO, see LP: #1891623. However every bug I filed (comment #8) to get the debugging easier, or even possible was triaged as not affecting the user, and apparently delayed. There are two sides of the issue, one is to produce a test case below the two million line code mark, and below the 48 hour build mark. Helping yes, but doing that on my own, no. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1931701 Title: autopkgtests failures on armhf of 7.1.4 Status in gcc-9 package in Ubuntu: New Status in libreoffice package in Ubuntu: New Status in gcc-9 source package in Hirsute: New Status in libreoffice source package in Hirsute: New Status in gcc-9 source package in Impish: New Status in libreoffice source package in Impish: New Bug description: The autopkgtests for 7.1.4~rc2-0ubuntu1 on impish/armhf has started to fail reliably. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210610_121847_0ab56@/log.gz "/usr/lib/libreoffice/program/unopkg" add -f "/tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/bin/SampleDialog.oxt" # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0xf47474b8, pid=35616, tid=35643 # # JRE version: OpenJDK Runtime Environment (11.0.12+4) (build 11.0.12-ea+4-Ubuntu-0ubuntu2) # Java VM: OpenJDK Server VM (11.0.12-ea+4-Ubuntu-0ubuntu2, mixed mode, g1 gc, linux-) # Problematic frame: # C [libbootstraplo.so+0x1c4b8] stoc_impreg::mergeKeys(com::sun::star::uno::Reference const&, com::sun::star::uno::Reference const&, std::vector >&)+0xb # # Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport %p %s %c %d %P %E" (or dumping to /usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs/core.35616) # # An error report file with more information is saved as: # /tmp/hs_err_pid35616.log # # If you would like to submit a bug report, please visit: # https://bugs.launchpad.net/ubuntu/+source/openjdk-lts # ERROR: Exception occurred: Binary URP bridge disposed during call ./binaryurp/source/bridge.cxx:613 ERROR: unopkg failed. make[1]: Leaving directory '/usr/lib/libreoffice/sdk/examples/DevelopersGuide/BasicAndDialogs/CreatingDialogs' make[1]: *** [Makefile:112: /tmp/tmp.oOlP0i1pzN/out/sdk/LINUXexample.out/misc/devguide_basicanddialogs_creatingdialogs_register_component.flag] Error 1 make[1]: Target 'ALL' not remade because of errors. make: *** [/tmp/autopkgtest.U74TIg/build.myd/src/odk/CustomTarget_build-examples_java.mk:62: /tmp/autopkgtest.U74TIg/build.myd/src/workdir/CustomTarget/odk/build-examples_java.done] Error 2 make: Target 'CustomTarget_odk/build-examples_java' not remade because of errors. While a re-run of the test for 7.1.3-0ubuntu1 were successful it suggests it is binary problem. https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/armhf/libr/libreoffice/20210609_234830_1265b@/log.gz liberoffice is built with gcc-9/g++-9 on armhf to avoid https://bugs.launchpad.net/ubuntu/+source/gcc-10/+bug/1891623 A significant difference in the used toolchain points to the update of gcc-9 7.1.3-0ubuntu1 was built with gcc 9.3.0-24ubuntu1 https://launchpadlibrarian.net/537628130/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.3-0ubuntu1_BUILDING.txt.gz 7.1.4~rc2-0ubuntu1 was built with gcc 9.4.0-1ubuntu1 https://launchpadlibrarian.net/542492348/buildlog_ubuntu-impish-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu1_BUILDING.txt.gz Regarding 21.04/Hirsute 1:7.1.4~rc2-0ubuntu0.21.04.1~lo1 built and successfully ran autopkgtests, see https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1931272 If was using the gcc-9 9.3.0-23ubuntu2 available at the time. The no-change rebuild against 9.4.0-1ubuntu1~21.04 results in the same failure now. https://launchpadlibrarian.net/543392061/buildlog_ubuntu-hirsute-armhf.libreoffice_1%3A7.1.4~rc2-0ubuntu0.21.04.1~lo1_BUILDING.txt.gz https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-experimental/hirsute/armhf/libr/libreoffice/20210612_113218_f7f69@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1931701/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xwayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: Confirmed Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xwayland (Ubuntu Hirsute) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: Confirmed Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xwayland (Ubuntu Groovy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: Confirmed Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: Confirmed Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: Confirmed Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
Unable to replicate the problem on hirsute (either a fresh install from the image, or post all upgrades); currently flashing a groovy image for testing, but it looks like whatever's causing this in groovy *might* have been fixed by hirsute. If I can replicate the issue on the groovy image, I'll try running through the release upgrader to see if it goes away post-upgrade before marking hirsute as fixed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xwayland in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: Invalid Status in xwayland package in Ubuntu: New Status in linux-raspi source package in Groovy: Invalid Status in xwayland source package in Groovy: New Status in linux-raspi source package in Hirsute: Invalid Status in xwayland source package in Hirsute: New Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort
** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #2859
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
** Changed in: mesa (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: mesa (Ubuntu Hirsute)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1918855
Title:
Xorg xserver got signal 6 to abort
Status in OEM Priority Project:
In Progress
Status in Provider for Plainbox - Checkbox:
New
Status in mesa package in Ubuntu:
Fix Released
Status in mesa source package in Focal:
New
Status in mesa source package in Hirsute:
New
Bug description:
== SRU Justification ==
[Impact]
When the system is under memory pressure, the entire desktop session may
crash.
[Fix]
Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if
kernel can't allocate memory")
[Test]
Run memory stress and the session crashed in less than 5 minutes.
With the fix applied, run memory stress for 24 hours and the desktop session
is still alive.
[Where problems could occur]
Doing a reset might make the system even more sluggish when under memory
pressure.
== Original bug report ==
I run checkbox job com.canonical.certification::memory/memory_stress_ng on
focal, and the xserver stops unexpectedly with the following stacktrace:
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg
(OsLookupColor+0x13c) [0x5619f3a4d59c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 1:
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6
(gsignal+0xcb) [0x7fae476a418b]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6
(abort+0x12b) [0x7fae47683859]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 4:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 5:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec)
[0x7fae46529c9c]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 6:
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 7:
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150)
[0x7fae47007480]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind
info found [-10]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 8:
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg
(BlockHandler+0xa5) [0x5619f38f0995]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg
(WaitForSomething+0x122) [0x5619f3a46c12]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg
(SendErrorToClient+0x117) [0x5619f38ebcf7]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg
(InitFonts+0x3b4) [0x5619f38effc4]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6
(__libc_start_main+0xf3) [0x7fae476850b3]
/usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e)
[0x5619f38d9a2e]
More info:
I searched the Internet and got a bug with the same stacktrace:
https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1932291] Re: dhcp client resets IP address every few minutes
The reason why dhcp client reset connection was an ICMP message When the client send a REQUEST, the gateway replied with ICMP code 10 (Host administratively prohibited) Then dhcp server replied with ACK -- It happened because iptables on the server did not allow incoming connections to port 67 of the dhcp server and it responded with an ICMP (Host administratively prohibited). But it seems the requests came to the dhcp server anyway and dhcp server responded with ACK. I sent only dhcp packets in the dump file but there no ICMP messages were included. -- 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/1932291 Title: dhcp client resets IP address every few minutes Status in network-manager package in Ubuntu: New Bug description: Hello, Network manager resets IP address every 30 minutes (perhaps this time depends on default-lease-time) This issue affects at least the latest package Network Manager in Ubuntu 20.04.2 - network-manager 1.22.10-1ubuntu2.2. It seems this issue has been occuring more than a year (perhaps from release Ubuntu 20.04) and is not fixed yet. It is possible that this issue occurs only with our dhcp server. We have not checked if the issue occurs with other dhcp servers. lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy network-manager network-manager: Installed: 1.22.10-1ubuntu2.2 Candidate: 1.22.10-1ubuntu2.2 Version table: *** 1.22.10-1ubuntu2.2 500 500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.22.10-1ubuntu1 500 500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages - STR: Install Ubuntu 20.04.2 (update if needed) and connect to network with dhcp server. AR: Connection drops every few minutes, then NetworkManager reconnects again. On screen we can see message "Network disconnect" and right away "Network connect" ER: Connection should be stable. We have found the similar bug here - https://bugzilla.redhat.com/show_bug.cgi?id=1817788 It is possible that in my case the root of issue is the same and the isue is fixed in network manager 1.22.12 We need a new networkmanager package in Ubuntu 20.04 repository which has not got this bug. There is a part of /var/log/syslog Here we can see error "error -113 dispatching events" Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8092] dhcp4 (enp3s0): send REQUEST of 192.168.61.156 to 192.168.61.2 Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8225] dhcp4 (enp3s0): error -113 dispatching events Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8226] dhcp4 (enp3s0): state changed bound -> fail Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8226] device[5565e4c243c020e9] (enp3s0): new DHCPv4 client state 6 Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8227] device[5565e4c243c020e9] (enp3s0): DHCPv4 failed (ip_state done, was_active 0) Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8228] device (enp3s0): DHCPv4: trying to acquire a new lease within 90 seconds Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8228] dbus-object[cffc3e670403e5f9]: unexport: "/org/freedesktop/NetworkManager/DHCP4Config/8" Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]: [1623848500.8232] dbus-object[e4f7ca28a56cb5dc]: export: "/org/freedesktop/NetworkManager/DHCP4Config/9" Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]: [1623848538.4785] device[5565e4c243c020e9] (enp3s0): connectivity: [IPv6] periodic-check: re-scheduled in 299970 milliseconds (300 se conds interval) Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]: [1623848538.4787] device[5565e4c243c020e9] (enp3s0): connectivity: [IPv6] start check (seq:86, periodic-check) Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]: [1623848538.4790] connectivity: (enp3s0,IPv6,86) start request to 'http://connectivity-check.ubuntu.com/' (try resolving 'connectivit y-check.ubuntu.com' using systemd-resolved) Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]: [1623848538.4833] connectivity: (enp3s0,IPv6,86) can't resolve a name via systemd-resolved: GDBus.Error:org.freedesktop.resolve1.NoSu chRR: 'connectivity-check.ubuntu.com' does not have any RR of the requested type Jun 16 16:02:18 user-System-Product-Name systemd-resolved[549]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Jun 16 16:02:18 user-System-Product-Name systemd-resolved[549]: message repeated 2
[Desktop-packages] [Bug 1838720] Re: Power button action not working
Thank you for reporting this bug to Ubuntu. Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Tags added: disco ** Changed in: gnome-control-center (Ubuntu) Status: New => Won't Fix -- 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/1838720 Title: Power button action not working Status in gnome-control-center package in Ubuntu: Won't Fix Bug description: In the Power tab, the option "When the power button is pressed" is set to "Suspend". However, this action is not executed on power button press. It does nothing. This is always reproducible on Ubuntu 19.04, while on Ubuntu 18.04.2 it works as expected. gnome-control-center 3.32.2 Kernel 5.0.0-23-generic Ubuntu 19.04 Disco See attached logs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1838720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933310] Re: power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving
*** This bug is a duplicate of bug 1751954 *** https://bugs.launchpad.net/bugs/1751954 Sounds like bug 1751954 ** This bug has been marked a duplicate of bug 1751954 Bluetooth and Wi-Fi items in Power are worded ambiguously -- 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/1933310 Title: power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving Status in gnome-control-center package in Ubuntu: New Bug description: On the Settings window Power/Power Saving/Bluetooth there is a toggle button to turn off/on for power saving. but what it does, if its on the BT is on, if you toggle it to off, the BT gets turned off instantly. And if you go to Bluetooth devices and turn BT on, and you go back to power saving window, you see the toggle button turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 08:54:49 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-03-30 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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/1933310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933310] [NEW] power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving
Public bug reported: On the Settings window Power/Power Saving/Bluetooth there is a toggle button to turn off/on for power saving. but what it does, if its on the BT is on, if you toggle it to off, the BT gets turned off instantly. And if you go to Bluetooth devices and turn BT on, and you go back to power saving window, you see the toggle button turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 08:54:49 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-03-30 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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 focal third-party-packages -- 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/1933310 Title: power_saving_bluetooth_toggle_button disables Bluetooth instead of power saving Status in gnome-control-center package in Ubuntu: New Bug description: On the Settings window Power/Power Saving/Bluetooth there is a toggle button to turn off/on for power saving. but what it does, if its on the BT is on, if you toggle it to off, the BT gets turned off instantly. And if you go to Bluetooth devices and turn BT on, and you go back to power saving window, you see the toggle button turned on. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 23 08:54:49 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2021-03-30 (84 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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/1933310/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 875676] Re: Backing up fails with 'IOError CRC check failed'.
My workaround for this problem:
i went to the backupserver where our remote backups are located
ls -latr *.sigtar.gz
(pick the last one and gave it a "_" as prefix)
after that i could do a purge again.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to duplicity in Ubuntu.
https://bugs.launchpad.net/bugs/875676
Title:
Backing up fails with 'IOError CRC check failed'.
Status in Duplicity:
Incomplete
Status in duplicity package in Ubuntu:
Confirmed
Bug description:
For 4 days déjà dup hasn't been able to perform a backup. It fails
with the error
Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
0x3d503338L',), )
There is another similar bug #676767 where deleting ~/.cache/deja-dup
helps. In this case it doesn't.
I'm quite certain that my backup drive isn't corrupted. (It's a
raid5.) I'd be happy to provide any additional information needed.
--
System information:
Ubuntu 11.10
deja-dup 20.0-0ubuntu3
duplicity 0.6.15-0ubuntu2
Logs:
deja-dup.log: http://pastie.org/2705320
deja-dup.gsettings: http://pastie.org/2705322
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/875676/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Changed in: oem-priority Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in GNOME Bluetooth: Unknown Status in OEM Priority Project: New Status in bluez package in Ubuntu: Fix Committed Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in bluez source package in Focal: In Progress Status in bluez source package in Hirsute: In Progress Status in bluez source package in Impish: Fix Committed Status in gnome-settings-daemon source package in Impish: Fix Released Bug description: [Impact] On/off of Bluetooth in gnome-control-center will not work properly in kernels 5.11 (approximately) onward. Devices are not refreshed in the list anymore. [Test Plan] 1. Open gnome-control-center and select Bluetooth 2. Turn off Bluetooth via UI 3. Turn on Bluetooth via UI Expect: Device list appears, so Bluetooth really is on. [Where problems could occur] Since the fix involves the 'rfkill' logic it has the potential to affect any Bluetooth or Wifi on/off setting. [Other info] Upstream bug in gnome-bluetooth: https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38 Discussion in linux-bluetooth: https://marc.info/?t=16200475893=1=2 [Original bug report] When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS Bluetooth: hci0: HCI reset during shutdown failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
