[Desktop-packages] [Bug 1368147] Re: Lenovo Thinkpad Twist: Mobile Broadbad not working any more
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1368147 Title: Lenovo Thinkpad Twist: Mobile Broadbad not working any more Status in network-manager package in Ubuntu: Incomplete Bug description: It seems that something has changed and now the functionality for mobile broadband support got completely lost. I can create a new connection, enteringtheoperator and so on, but I cannot establish a connection. First, I click "Enable Mobile Broadband" in the network manager menu. Then I open the meu again and click the entry for my operator. Then I get a pop-up window saying "Connection activation failed, (32) The connection was not supportedby oFono". I am using Utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1368147/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1274857] Re: wi-fi continually fails to connect (after previous success)
Is this still a problem on bionic or later? ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- 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/1274857 Title: wi-fi continually fails to connect (after previous success) Status in network-manager package in Ubuntu: Incomplete Bug description: Wi-fi had been working fine, but this morning, nothing doing. syslog shows many instances of: Activation (wlan0/wireless): association took too long, failing activation. Some info which may or may not be relevant: Removing the network and adding it made no difference. Deactivating, then reactivating the hardware wi-fi network switch made no difference. This was happening on two independent wi-fi networks (my hotel and the bluefin office) Rebooting fixed the issue. Closing the laptop did not reliably send it to sleep last night. Two competent Canonical engineers were unable to diagnose the problem. % lsb_release -rd Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 % uname -a Linux rog-ThinkPad-X220 3.13.0-2-generic #17-Ubuntu SMP Fri Jan 10 12:14:30 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux % lspci 00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 04) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 04) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b4) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b4) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b4) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b4) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 04) 00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC Controller (rev 04) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 04) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 04) 03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000 [Condor Peak] 0d:00.0 System peripheral: Ricoh Co Ltd MMC/SD Host Controller (rev 07) % I have attached my syslog starting just before the most recent successful connection until just before I rebooted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1274857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867496] [NEW] Thinkpad X220 internal ethernet identified as T520
Public bug reported: This is a very minor bug, only cosmetic in nature, but likely easy to fix. The internal ethernet adapter on my Thinkpad X220 is identified as from the T520 by network-manager. See attached screenshot. This is on an up-to-date bionic system. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "screenshot demonstrating the problem" https://bugs.launchpad.net/bugs/1867496/+attachment/5337120/+files/misidentified-ethernet.png -- 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/1867496 Title: Thinkpad X220 internal ethernet identified as T520 Status in network-manager package in Ubuntu: New Bug description: This is a very minor bug, only cosmetic in nature, but likely easy to fix. The internal ethernet adapter on my Thinkpad X220 is identified as from the T520 by network-manager. See attached screenshot. This is on an up-to-date bionic system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1867496/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867337] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1867337/+attachment/5337116/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) NonfreeKernelModules: wl Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867337] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1867337/+attachment/5337118/+files/ShellJournal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) NonfreeKernelModules: wl Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867337] Re: even after login the login page was displaying everywhere.
apport information ** Tags added: apport-collected third-party-packages ** Description changed: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu20 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-03-14 (0 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) + NonfreeKernelModules: wl + Package: gnome-shell 3.35.91-1ubuntu2 + PackageArchitecture: amd64 + ProcEnviron: + LANGUAGE=en_IN:en + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_IN + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 + RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 + Tags: focal third-party-packages + Uname: Linux 5.4.0-18-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1867337/+attachment/5337115/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
Re: [Desktop-packages] [Bug 1867337] Re: even after login the login page was displaying everywhere.
Hello, Thanks for contacting me i have successfully executed the command and have send the bug report to the developer. using the prompts available. Hope to see the fix asap Thanks. SHUBHAM KALE On Saturday, 14 March, 2020, 02:25:45 pm IST, Daniel van Vugt wrote: Please run this command (sorry I know you already used ubuntu-bug but it collected info for the wrong package): apport-collect 1867337 Also, if there are any files in /var/crash then please follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867337/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed
[Desktop-packages] [Bug 1867337] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1867337/+attachment/5337117/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) NonfreeKernelModules: wl Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6
The silence regarding this problem is a bit disconcerting. After jumping through many hoops, I managed to resolve this with the help of this answer: https://forum.manjaro.org/t/weird-dns-issue-over-vpn/78092/11 I deleted the /etc/resolv.conf symlink and disabled systemd-resolved as instructed, then rebooted. After start up, NetworkManager re-created a file at /etc/resolv.conf (not a symlink this time). Although I could connect to the Internet, I coulnd't access any website. I inferred some DNS issues and I simply re-enabled systemd-resolved. $ sudo systemctl enable systemd-resolved.service I recreated the symlink pointing /etc/resolv.conf to /run/resolvconf/resolv.conf $ sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf then I rebooted once again. Next time I connected to the VPN, I could access its resources with no further issues. -- 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/1688018 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6 Status in network-manager package in Ubuntu: Triaged Status in network-manager source package in Xenial: In Progress Status in network-manager source package in Yakkety: Won't Fix Bug description: This was initially opened as #1671606 then later duped to #1639776. Discussion in #1639776 indicate that we need new bug for this so I am opening one ... Please don't mark this as duplicate to #1639776 or other similar bug report. We already lost several months and we are again at beginning ... TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from DHCP instead of one defined by VPN (wrong). DNS resolver should query only DNS servers defined by VPN while connection is active. = Test steps / result: - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 (dnsmasq-base-2.75-1ubuntu0.16.04.2) - restated my laptop to ensure clean start - connected to VPN using openconnect / network-manager-openconnect-gnome Observed results -> DNS queries are forwarded only to DNS servers defined by LAN connection (this is wrong / connection not working at all) - "killall dnsmasq" - dnsmasq get automatically restarted by system Observed results -> most of the the queries are forwarded to DNS servers defined by VPN, but lot of queries get forwarded to DNS servers defined by LAN connection (this is still wrong / DNS leaks, attacker can hijack connection even if VPN is enabled) - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base stay same) - restated my laptop to ensure clean test - connected to same VPN using openconnect Observed results -> DNS queries are forwarded only to DNS servers defined by VPN connection. There are no leaks to LAN DNS server (this is correct behavior). = Paul Smith requested additional details in #1639776. Here are: * If you're using IPv4 vs. IPv6 -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi /vpn) * If you have checked or unchecked the "Use this connection only for resources on its network" -> unchecked on all nw definition * If you have this checked, try unchecking it and see if that makes a difference -> no change if I toggle this option. Behavior is same. * When you say "DNS lookups" please be clear about whether the hostnames being looked up are public (e.g., www.google.com or whatever), on your local LAN, or in the network accessed via the VPN. Does it make a difference which one you choose? -> No difference. * Are you using fully-qualified hostnames, or relying on the DNS domain search path? Does it make a difference if you do it differently? -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see difference when I try same using hostname + domain search. = I am using openconnect (cisco) and openvpn. Test result are by using openconnect but I saw same behaviour also while using openvpn. = Thanks Lukas To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867337] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1867337/+attachment/5337119/+files/monitors.xml.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) NonfreeKernelModules: wl Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Ubuntu MATE 20.04 2020315 QEMU: crash VirtualBox VBoxVGA crash VirtualBox VMSVGA: no crash In this case VirtualBox 6.1.4 (version shipping in 20.04) -- 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/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: New Status in gstreamer-vaapi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1859294] Re: Cannot type capital letters with accents: pressing Shift cancels the accent key action
[Expired for chromium-browser (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1859294
Title:
Cannot type capital letters with accents: pressing Shift cancels the
accent key action
Status in chromium-browser package in Ubuntu:
Expired
Bug description:
This is a weird quirk:
When typing Spanish accented capital letters, one presses the Accent
key (') and then the letter (e.g. "a"), so the sequence " ' + a "
results in "á".
Expected: Pressing Accent + Letter = Accented Letter.
What happens: When one presses Accent + Shift + letter, Shift cancels
the Accent action (with an audible system alert if activated).
It is possible, however, to press Caps Lock and do Accent + letter,
with the expected result (an accented letter).
This only happens within Chromium. It is possible to press Accent +
Letter and get the accented letter anywhere else.
OS: Ubuntu 18.04
Chromium Build version: 79.0.3945.79
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1859294/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1859437] Re: gnome-software crashed with SIGSEGV in as_app_add_provide()
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1859437 Title: gnome-software crashed with SIGSEGV in as_app_add_provide() Status in gnome-software package in Ubuntu: Expired Bug description: I don't know what happened. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-software 3.30.6-2ubuntu11 Uname: Linux 5.4.10-050410-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 10 07:52:49 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2018-12-02 (406 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InstalledPlugins: gnome-software-plugin-flatpak 3.30.6-2ubuntu11 gnome-software-plugin-snap3.30.6-2ubuntu11 ProcCmdline: /usr/bin/gnome-software --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 SegvAnalysis: Segfault happened at: 0x7f0fdeeb2c84 :mov (%rdx,%rax,8),%r14 PC (0x7f0fdeeb2c84) ok source "(%rdx,%rax,8)" (0x2e70) not located in a known VMA region (needed readable region)! destination "%r14" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: as_app_add_provide () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 as_store_add_apps () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8 () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so Title: gnome-software crashed with SIGSEGV in as_app_add_provide() UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1859437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586528] Re: Avahi-daemon withdraws address record
I am also seeing this same problem on a Raspberry Pi4 4GB. I purchased the Pi last November and installed from the then-available 2019-09-26-raspbian-buster.zip but routinely keep it updated (apt update / apt upgrade). The Pi was rock solid and did not exhibit any problems until 2020-02-24 when I applied some updates followed by a "sudo reboot" but the boot process did not complete. The Pi runs headless so I don't know whether it never actually completed the shutdown, or failed to reboot. I power- cycled the device and it came back OK. Another set of updates were applied on 2020-03-11 and the subsequent reboot completed without incident so I assumed the earlier problem was a one-off. Then, on 2020-03-14 the Pi froze. Wouldn't respond to pings, ssh or vnc. It is Ethernet-connected but the WiFi interface is active and it did not occur to me to try connecting via WiFi. I just did another power-cycle and then started nosing around through the logs. Which brought me to: Mar 14 12:48:16 iot-hub avahi-daemon[361]: Withdrawing address record for 192.168.132.60 on eth0. Mar 14 12:48:16 iot-hub avahi-daemon[361]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.132.60. Mar 14 12:48:16 iot-hub avahi-daemon[361]: Interface eth0.IPv4 no longer relevant for mDNS. and, from there, to this post. The main reasons I'm adding a comment to this post are (a) as a "me too" as of March 2020, and (b) in case the pattern of the RPi being perfectly OK until 2020-02-24 causes someone to say "ahah!" The updates in question were (from the history log): Upgrade: libpython3.7-minimal:armhf (3.7.3-2, 3.7.3-2+deb10u1), libraspberrypi- bin:armhf (1.20200114-1, 1.20200212-1), libopenjp2-7:armhf (2.3.0-2, 2.3.0-2+deb10u1), rc-gui:armhf (1.34, 1.36), libcom-err2:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), libcups2:armhf (2.2.10-6+deb10u1, 2.2.10-6+deb10u2), libraspberrypi-dev:armhf (1.20200114-1, 1.20200212-1), libraspberrypi-doc:armhf (1.20200114-1, 1.20200212-1), python3.7-venv:armhf (3.7.3-2, 3.7.3-2+deb10u1), raspberrypi-ui- mods:armhf (1.20200127, 1.20200218), qt5-gtk-platformtheme:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libfm4:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), libsystemd0:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), raspi-config:armhf (20200205, 20200207), libfm- modules:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), libfm-extra4:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), mariadb-common:armhf (1:10.3.17-0+deb10u1, 1:10.3.22-0+deb10u1), binutils:armhf (2.31.1-16+rpi1, 2.31.1-16+rpi2), e2fsprogs:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), sudo:armhf (1.8.27-1+deb10u1, 1.8.27-1+deb10u2), libqt5dbus5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libqt5sql5-sqlite:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), python3-pil:armhf (5.4.1-2, 5.4.1-2+deb10u1), libpython3.7:armhf (3.7.3-2, 3.7.3-2+deb10u1), python3.7:armhf (3.7.3-2, 3.7.3-2+deb10u1), openssh-sftp-server:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), libqt5widgets5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libfm-gtk4:armhf (1.3.1-1+rpt12, 1.3.1-1+rpt13), udev:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), python3.7-dev:armhf (3.7.3-2, 3.7.3-2+deb10u1), binutils-arm-linux-gnueabihf:armhf (2.31.1-16+rpi1, 2.31.1-16+rpi2), libpython3.7-stdlib:armhf (3.7.3-2, 3.7.3-2+deb10u1), libudev1:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), python3.7-minimal:armhf (3.7.3-2, 3.7.3-2+deb10u1), libqt5xml5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libqt5printsupport5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), raspberrypi- kernel:armhf (1.20200114-1, 1.20200212-1), libss2:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), libqt5concurrent5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libext2fs2:armhf (1.44.5-1+deb10u2, 1.44.5-1+deb10u3), raspberrypi-bootloader:armhf (1.20200114-1, 1.20200212-1), libexif12:armhf (0.6.21-5.1, 0.6.21-5.1+deb10u1), libqt5gui5:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), libimobiledevice6:armhf (1.2.1~git20181030.92c5462-1, 1.2.1~git20181030.92c5462-2), gldriver- test:armhf (0.4, 0.5), ssh:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), systemd-sysv:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), guile-2.2-libs:armhf (2.2.4+1-2, 2.2.4+1-2+deb10u1), realvnc-vnc-server:armhf (6.6.0.41949, 6.7.1.42348), libpython3.7-dev:armhf (3.7.3-2, 3.7.3-2+deb10u1), libpam-systemd:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), libmatroska6v5:armhf (1.4.9-1, 1.4.9-1+deb10u1), systemd:armhf (241-7~deb10u2+rpi1, 241-7~deb10u3+rpi1), libwebkit2gtk-4.0-37:armhf (2.26.3-1~deb10u1+rpi1, 2.26.4-1~deb10u1+rpi1), libqt5core5a:armhf (5.11.3+dfsg1-1+rpi1, 5.11.3+dfsg1-1+rpi1+deb10u3), piwiz:armhf (0.8, 0.9), libraspberrypi0:armhf (1.20200114-1, 1.20200212-1), openssh-server:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), openssh-client:armhf (1:7.9p1-10+deb10u1, 1:7.9p1-10+deb10u2), libmysofa0:armhf (0.6~dfsg0-3, 0.6~dfsg0-3+deb10u1), rpi-chromium-mods:armhf
[Desktop-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1867474 *** https://bugs.launchpad.net/bugs/1867474 Solution given in https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1867474/comments/3 does not resolve issue on my install. I've attached the dmesg ** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+attachment/5337110/+files/dmesg -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867492] [NEW] Sync geocode-glib 3.26.2-1 (main) from Debian unstable (main)
Public bug reported: Please sync geocode-glib 3.26.2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Make autopkgtests cross-test-friendly. Steve's patch was merged into Debian. Builds successfully in a Focal chroot. From a feature freeze perspective, all bug fixes in the new patch version: ~/geocode-glib (master)> git log 3.26.0..3.26.1 --oneline 8280732 (tag: 3.26.1) 3.26.1 72e3ba3 build: Remove unused autotools test helpers 254182e Merge branch 'wip/hadess/place_rank-crasher' into 'master' 0d4f1ba tests: Fix missing installed-tests file e721658 geocode-nominatim: Fix possible crash with missing place_rank 24d8423 tests: Add test for issue #6 5fb1cbc Merge branch 'wip/hadess/nominatim-crasher' into 'master' ada9522 tests: Add test for issue #5 e1a6b06 geocode-nominatim: Fix parsing of integer JSON values 1321af7 Merge branch 'meson-docs' into 'master' 0fc6eeb Remove in DOAP file (a repository is not a homepage) a1f532a Merge branch 'wip/hadess/zero-distance-test-case' into 'master' f6c09dc ci: Add CI bb7807d tests: Add a zero distance test f8f1271 Fix meson docs building Changelog entries since current focal version 3.26.1-1ubuntu1: geocode-glib (3.26.2-1) unstable; urgency=medium [ Simon McVittie ] * d/tests/build: Mark as superficial * Bump Standards-Version to 4.4.1 * d/tests/build: Remove support for ancient autopkgtest versions. AUTOPKGTEST_TMP is now required to be set, and we do not fall back to the deprecated ADTTMP. * d/tests/build: Fix a shellcheck warning * d/tests/build: Make autopkgtest cross-test-friendly. Thanks to Steve Langasek. (Closes: #946377) * Use debhelper-compat 12 * Disable gtk-doc for architecture-only builds. This should speed them up a bit, and is generally preferred when cross-building. * Remove migration path from libgeocode-glib-dbg. It was removed in Debian 9 'stretch' (oldstable). * Remove Breaks on ancient versions of empathy. 3.4.2.3 is considerably older than Debian 8 'jessie' (oldoldstable). [ Laurent Bigonville ] * New upstream release * debian/control.in: Bump Standards-Version to 4.5.0 (no further changes) * debian/control.in: Mark libgeocode-glib-doc with Build-Profile: and add libglib2.0-doc to the BDI -- Laurent Bigonville Fri, 13 Mar 2020 23:52:45 +0100 ** Affects: geocode-glib (Ubuntu) Importance: Wishlist Status: New ** Changed in: geocode-glib (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geocode-glib in Ubuntu. https://bugs.launchpad.net/bugs/1867492 Title: Sync geocode-glib 3.26.2-1 (main) from Debian unstable (main) Status in geocode-glib package in Ubuntu: New Bug description: Please sync geocode-glib 3.26.2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * Make autopkgtests cross-test-friendly. Steve's patch was merged into Debian. Builds successfully in a Focal chroot. From a feature freeze perspective, all bug fixes in the new patch version: ~/geocode-glib (master)> git log 3.26.0..3.26.1 --oneline 8280732 (tag: 3.26.1) 3.26.1 72e3ba3 build: Remove unused autotools test helpers 254182e Merge branch 'wip/hadess/place_rank-crasher' into 'master' 0d4f1ba tests: Fix missing installed-tests file e721658 geocode-nominatim: Fix possible crash with missing place_rank 24d8423 tests: Add test for issue #6 5fb1cbc Merge branch 'wip/hadess/nominatim-crasher' into 'master' ada9522 tests: Add test for issue #5 e1a6b06 geocode-nominatim: Fix parsing of integer JSON values 1321af7 Merge branch 'meson-docs' into 'master' 0fc6eeb Remove in DOAP file (a repository is not a homepage) a1f532a Merge branch 'wip/hadess/zero-distance-test-case' into 'master' f6c09dc ci: Add CI bb7807d tests: Add a zero distance test f8f1271 Fix meson docs building Changelog entries since current focal version 3.26.1-1ubuntu1: geocode-glib (3.26.2-1) unstable; urgency=medium [ Simon McVittie ] * d/tests/build: Mark as superficial * Bump Standards-Version to 4.4.1 * d/tests/build: Remove support for ancient autopkgtest versions. AUTOPKGTEST_TMP is now required to be set, and we do not fall back to the deprecated ADTTMP. * d/tests/build: Fix a shellcheck warning * d/tests/build: Make autopkgtest cross-test-friendly. Thanks to Steve Langasek. (Closes: #946377) * Use debhelper-compat 12 * Disable gtk-doc for architecture-only builds. This should speed them up a bit, and is generally preferred when cross-building. * Remove migration path from libgeocode-glib-dbg. It was removed in Debian 9 'stretch' (oldstable). * Remove Breaks on ancient versions of empathy. 3.4.2.3 is considerably older than Debian 8 'jessie' (oldoldstable). [ Laurent Bigonville ] * New
[Desktop-packages] [Bug 1864001] Re: Dialog windows of Chromium with unprintable characters
** Summary changed: - "Save as" in chromium with unprintable characters + Dialog windows of Chromium with unprintable characters -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1864001 Title: Dialog windows of Chromium with unprintable characters Status in chromium-browser package in Ubuntu: New Bug description: In Chromium with the following version numbers (output of “snap list”): chromium 80.0.3987.100 1026 stable canonical✓ - (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable characters, i.e., I see only small boxes instead of letters. I don’t observe this in comparable dialogs of other programs, e.g. Inkscape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: PCI/internal sound card not detected
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
*** This bug is a duplicate of bug 1867474 *** https://bugs.launchpad.net/bugs/1867474 Please refer to https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1867474/comments/3 ** This bug has been marked a duplicate of bug 1867474 PCI/internal sound card not detected -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867491] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1867491/+attachment/5337109/+files/ThreadStacktrace.txt ** Tags added: apport-failed-retrace ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1867491 Title: info assert failure: free(): double free detected in tcache 2 Status in texinfo package in Ubuntu: New Bug description: Program did not open ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AssertionMessage: free(): double free detected in tcache 2 CurrentDesktop: KDE Date: Sat Mar 14 18:49:03 2020 ExecutablePath: /usr/bin/info ProcCmdline: /usr/bin/info Signal: 6 SourcePackage: texinfo StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected in tcache 2") at malloc.c:5347 _int_free (av=av@entry=0x7f239f8c5b80 , p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201 _int_realloc (av=av@entry=0x7f239f8c5b80 , oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at malloc.c:4618 __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226 Title: info assert failure: free(): double free detected in tcache 2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1867491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867491] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1867491/+attachment/5337107/+files/Stacktrace.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1867491 Title: info assert failure: free(): double free detected in tcache 2 Status in texinfo package in Ubuntu: New Bug description: Program did not open ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AssertionMessage: free(): double free detected in tcache 2 CurrentDesktop: KDE Date: Sat Mar 14 18:49:03 2020 ExecutablePath: /usr/bin/info ProcCmdline: /usr/bin/info Signal: 6 SourcePackage: texinfo StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected in tcache 2") at malloc.c:5347 _int_free (av=av@entry=0x7f239f8c5b80 , p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201 _int_realloc (av=av@entry=0x7f239f8c5b80 , oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at malloc.c:4618 __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226 Title: info assert failure: free(): double free detected in tcache 2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1867491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867491] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1867491/+attachment/5337108/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1867491 Title: info assert failure: free(): double free detected in tcache 2 Status in texinfo package in Ubuntu: New Bug description: Program did not open ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AssertionMessage: free(): double free detected in tcache 2 CurrentDesktop: KDE Date: Sat Mar 14 18:49:03 2020 ExecutablePath: /usr/bin/info ProcCmdline: /usr/bin/info Signal: 6 SourcePackage: texinfo StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected in tcache 2") at malloc.c:5347 _int_free (av=av@entry=0x7f239f8c5b80 , p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201 _int_realloc (av=av@entry=0x7f239f8c5b80 , oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at malloc.c:4618 __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226 Title: info assert failure: free(): double free detected in tcache 2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1867491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867491] info assert failure: free(): double free detected in tcache 2
StacktraceTop: raise () from /tmp/apport_sandbox__7eb1p71/lib/x86_64-linux-gnu/libc.so.6 abort () from /tmp/apport_sandbox__7eb1p71/lib/x86_64-linux-gnu/libc.so.6 ?? () from /tmp/apport_sandbox__7eb1p71/lib/x86_64-linux-gnu/libc.so.6 ?? () from /tmp/apport_sandbox__7eb1p71/lib/x86_64-linux-gnu/libc.so.6 ?? () from /tmp/apport_sandbox__7eb1p71/lib/x86_64-linux-gnu/libc.so.6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1867491 Title: info assert failure: free(): double free detected in tcache 2 Status in texinfo package in Ubuntu: New Bug description: Program did not open ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AssertionMessage: free(): double free detected in tcache 2 CurrentDesktop: KDE Date: Sat Mar 14 18:49:03 2020 ExecutablePath: /usr/bin/info ProcCmdline: /usr/bin/info Signal: 6 SourcePackage: texinfo StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected in tcache 2") at malloc.c:5347 _int_free (av=av@entry=0x7f239f8c5b80 , p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201 _int_realloc (av=av@entry=0x7f239f8c5b80 , oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at malloc.c:4618 __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226 Title: info assert failure: free(): double free detected in tcache 2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1867491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867491] [NEW] info assert failure: free(): double free detected in tcache 2
Public bug reported: Program did not open ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AssertionMessage: free(): double free detected in tcache 2 CurrentDesktop: KDE Date: Sat Mar 14 18:49:03 2020 ExecutablePath: /usr/bin/info ProcCmdline: /usr/bin/info Signal: 6 SourcePackage: texinfo StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected in tcache 2") at malloc.c:5347 _int_free (av=av@entry=0x7f239f8c5b80 , p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201 _int_realloc (av=av@entry=0x7f239f8c5b80 , oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at malloc.c:4618 __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226 Title: info assert failure: free(): double free detected in tcache 2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Affects: texinfo (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash focal need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to texinfo in Ubuntu. https://bugs.launchpad.net/bugs/1867491 Title: info assert failure: free(): double free detected in tcache 2 Status in texinfo package in Ubuntu: New Bug description: Program did not open ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: info 6.7.0.dfsg.2-5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AssertionMessage: free(): double free detected in tcache 2 CurrentDesktop: KDE Date: Sat Mar 14 18:49:03 2020 ExecutablePath: /usr/bin/info ProcCmdline: /usr/bin/info Signal: 6 SourcePackage: texinfo StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f239f894285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 malloc_printerr (str=str@entry=0x7f239f8965f0 "free(): double free detected in tcache 2") at malloc.c:5347 _int_free (av=av@entry=0x7f239f8c5b80 , p=p@entry=0x564299291f90, have_lock=have_lock@entry=1) at malloc.c:4201 _int_realloc (av=av@entry=0x7f239f8c5b80 , oldp=oldp@entry=0x564299291f90, oldsize=oldsize@entry=336, nb=496) at malloc.c:4618 __GI___libc_realloc (oldmem=0x564299291fa0, bytes=488) at malloc.c:3226 Title: info assert failure: free(): double free detected in tcache 2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/texinfo/+bug/1867491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711801] Re: Packages in both Snap and .deb form show twice (e.g. GIMP)
*** This bug is a duplicate of bug 1790814 *** https://bugs.launchpad.net/bugs/1790814 ** This bug has been marked a duplicate of bug 1790814 Duplicate entries caused by debs and snaps offering the same application -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1711801 Title: Packages in both Snap and .deb form show twice (e.g. GIMP) Status in gnome-software package in Ubuntu: Triaged Bug description: Gimp appears twice in gnome-software in french : one description is in english, the other on in french. Ubuntu 17.04. Probably a problem in appstream description (?) See image. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-12 (160 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: gnome-software 3.22.7-0ubuntu3.17.04.6 PackageArchitecture: amd64 ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Tags: zesty package-from-proposed third-party-packages Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 CurrentDesktop: XFCE DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-12 (162 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Package: gnome-software 3.22.7-0ubuntu3.17.04.6 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17 Tags: zesty package-from-proposed third-party-packages Uname: Linux 4.10.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1711801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1739869] Re: Chromium appears twice in Ubuntu Software
*** This bug is a duplicate of bug 1790814 ***
https://bugs.launchpad.net/bugs/1790814
** This bug is no longer a duplicate of bug 1711801
Packages in both Snap and .deb form show twice (e.g. GIMP)
** This bug has been marked a duplicate of bug 1790814
Duplicate entries caused by debs and snaps offering the same application
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1739869
Title:
Chromium appears twice in Ubuntu Software
Status in gnome-software package in Ubuntu:
Confirmed
Bug description:
Searching for "chromium" in Ubuntu Software shows both "Chromium" and
"Chromium Web Browser".
This can confuse users, or raise paranoid alarms ("is the other
Chromium malware?").
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-software 3.20.5-0ubuntu0.16.04.6
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.14
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Dec 23 01:38:00 2017
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/gnome-software
InstallationDate: Installed on 2017-10-06 (78 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
SourcePackage: gnome-software
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1739869/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867479] Re: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: Confirmed Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866722] Re: Packaging type should appear in app's name
*** This bug is a duplicate of bug 1790814 *** https://bugs.launchpad.net/bugs/1790814 ** This bug has been marked a duplicate of bug 1790814 Duplicate entries caused by debs and snaps offering the same application -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1866722 Title: Packaging type should appear in app's name Status in gnome-software package in Ubuntu: New Bug description: Hi, for years now, Ubuntu Software show snap in priority. Hence for a given app' it appears many times in the list. Packaging type should be part of the app' name in the list to help users know where they're going. Thunderbird [ deb ] Thunderbird [ snap ] ( and why not ? ) Thunderbird [ flatpak ] Thunderbird [ appimage ] Another way to deal with this would be ⋅ to have only one entry by app'name ⋅ and have some clear labels for available packaging type Thunderbird app' description Available as : [ deb | snap | flatpak | appimage | from source | whatever ] here tabbed suggestions and info matching selected packaging type just above and eventually options like sandboxing, connect or plug interfaces, authorizations when relevant. [ install button ] Nowadays users may not be conscious of « how » they install an app, leading to bitter surprises ( slowness, no access to removable medias, used disk space ) because all users don't have SSD nor thousands Gb free disk space. All LTS Ubuntu are concerned by this bug : Software-center should show benefits, use-case, requirements and limits for each available packaging type, it should be more « teaching » instead of confusing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1866722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1840612] Re: Software Center offers multiple version without explanation
*** This bug is a duplicate of bug 1790814 *** https://bugs.launchpad.net/bugs/1790814 ** This bug has been marked a duplicate of bug 1790814 Duplicate entries caused by debs and snaps offering the same application -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1840612 Title: Software Center offers multiple version without explanation Status in gnome-software package in Ubuntu: Confirmed Bug description: Ubuntu 19.04 Gnome-software: 3.30.6-2ubuntu4.19.04.1 By default Ubuntu Software offers applications both from the ubuntu repos and the snap store. that's fine but confusing. The two packages can have different versions and descriptions, or the same version and the same descriptions. This is all very confusing for anyone who doesn't understand the difference. I'm not going to suggest a specific solution, but here are some thoughts. - some key differences could be highlighted in tool-tip text - the 'snap-store' text could be made into a button like the 'channel and 'license buttons. An explanatory text could be kept there. - if Canonical thinks it's unimportant which source is used (which is implied by not giving any caveats) then why not just roll the multiple packages into one entry (like the current multiple versions available) and make the 'source' text into an 'any' button which offers a choice of source. The newest version (regardless of source) could be offered by default. PS. it's inconsistent that the option to include snappy is a setting in the Gnome-software package and cannot be set in the Software & Updates package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1840612/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749085] Re: Applications packaged as snap and deb appear twice in the search results.
*** This bug is a duplicate of bug 1790814 *** https://bugs.launchpad.net/bugs/1790814 ** This bug is no longer a duplicate of bug 1711801 Packages in both Snap and .deb form show twice (e.g. GIMP) ** This bug has been marked a duplicate of bug 1790814 Duplicate entries caused by debs and snaps offering the same application -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1749085 Title: Applications packaged as snap and deb appear twice in the search results. Status in gnome-software package in Ubuntu: Triaged Bug description: Searching for "VLC" in Ubuntu Software shows two results. The first is "vlc" and has the same description as VideoLAN. However, installing the first entry doesn't create a VLC shortcut. What is the first "vlc" entry? Is it malware? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1749085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790814] Re: Duplicate entries caused by debs and snaps offering the same application
** Changed in: gnome-software (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Triaged ** Also affects: gnome-software via https://gitlab.gnome.org/GNOME/gnome-software/issues/645 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1790814 Title: Duplicate entries caused by debs and snaps offering the same application Status in GNOME Software: Unknown Status in gnome-software package in Ubuntu: Triaged Bug description: As a user, when I search for a software package, I want to see either one, canonical option, or I want to see clear visual cues why a software piece is listed multiple times, So that I either don't have to choose, Or that I have enough visual information to make a choice. As can be seen in the screenshot, when searching for Gimp, I get two, slightly different options. As a software engineer, I know the different sources: snaps and debs. And I know the reason for having two options. However, this is confusing, even when the cause is known. We need either: * An opinionated choice to be made: the "software" package should prefer one over the other. And list only that one. Commandline tools (apt, deb) still offer the choice to install the other option. * A visual cue why there are two. Information lacking is: the source: "Ubuntu Repository (deb)" or "Snap Store". Additional information is the version: often one or the other is newer, or preferred. Note that after clicking the through to the details, this information is made avaialble, albeit small and tucked away at the bottom. It also does not explain much there, either. Additionally, for sysadmins, an option to disable one or the other entirely would be useful. This may be in place in some way already, but I cannot find this in the configuration of the gnome-software. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1790814/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867469] Re: Update failed on allmost all Ubuntu 20.04 systems
*** This bug is a duplicate of bug 1867431 *** https://bugs.launchpad.net/bugs/1867431 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1867431, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1867431 ERROR got an error from dpkg for pkg: 'libc6' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867490] [NEW] Persistent GNOME Application Platform update that won't install
Public bug reported: I've had a persistent available update in GNOME Software for a while now that doesn't actually install when I hit Update (although it doesn't have any obvious failures either). It's for GNOME Application Platform version 3.34. When I hit the Update button, it briefly changes to Installing and then goes back to showing as an update again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 21:34:13 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-02-14 (29 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak 3.35.91-0ubuntu1 gnome-software-plugin-snap3.35.91-0ubuntu1 ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867490 Title: Persistent GNOME Application Platform update that won't install Status in gnome-software package in Ubuntu: New Bug description: I've had a persistent available update in GNOME Software for a while now that doesn't actually install when I hit Update (although it doesn't have any obvious failures either). It's for GNOME Application Platform version 3.34. When I hit the Update button, it briefly changes to Installing and then goes back to showing as an update again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 21:34:13 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2020-02-14 (29 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) InstalledPlugins: gnome-software-plugin-flatpak 3.35.91-0ubuntu1 gnome-software-plugin-snap3.35.91-0ubuntu1 ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867490/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867000] Re: Clicking "Open in Software" in GNOME Settings does not open Snap Store
Related upstream issue: https://gitlab.gnome.org/GNOME/gnome-control- center/issues/417 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #417 https://gitlab.gnome.org/GNOME/gnome-control-center/issues/417 -- 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/1867000 Title: Clicking "Open in Software" in GNOME Settings does not open Snap Store Status in snap-store: New Status in gnome-control-center package in Ubuntu: Invalid Bug description: This happens on latest Ubuntu Focal (without deb gnome-software /ubuntu-software packages installed, only Snap Store snap). When clicking the "Open in Software" button on Applications tab of GNOME Settings, nothing happens. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1867000/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] Re: PCI/internal sound card not detected
enabled the -proposed. Then install the latest kernel (maybe 5.4.0-18), latest linux-firmware and latest pulseaudio, then install alsa-ucm-conf manually, reboot. your audio should work, if not please upload the dmesg. thx. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1855514] Re: ibus preferences do not show up in search or indicator bar
Thanks for your report! It's not a bug, though. $ cat /usr/share/applications/org.freedesktop.IBus.Setup.desktop | grep '# GNOME' -A 1 # GNOME uses its own "input source" settings instead NotShowIn=GNOME;Unity; IBus is integrated into the GNOME desktop, and normally the UI provided by Settings -> Region & Language is sufficient. Closing. ** Changed in: ibus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1855514 Title: ibus preferences do not show up in search or indicator bar Status in ibus package in Ubuntu: Invalid Bug description: This might be two separate bugs. But I feel like they have the same root, so I reported them as one. Remarks: [1] This report is *not* related to bug 1854610 in ibus-anthy (Ubuntu) "No Japanese input possible after upgrade from 19.04 to 19.10" [Undecided,New] https://launchpad.net/bugs/1854610 [2] This report might be related to https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1580463, but I'm not sure. Someone with more technical knowledge should look into this. 1 --- steps to reproduce: 1) Have a fresh ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) press windows key to open all applications 4) type in ibus Actual: 5) ibus settings will not show up Expected: 5) ibus settings show up Workaround: 6) open Software center 7) search for ibus 8) click "launch there" 2 -- steps to reproduce: 1) Have a fresh Ubuntu 19.10 installation 2) install ibus and ibus-anthy 3) Set input method to "ibus" 4) restart Actual: 5) ibus preferences do not show up in the top bar at the indicators Expected 6) "ibus preferences" is visible at the top bar inside the indicators area. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ibus 1.5.21-1~exp2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 13:10:27 2019 SourcePackage: ibus UpgradeStatus: no upgrade log present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1855514/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867479] [NEW] PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake
Public bug reported: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET21W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1S05A00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET21W(1.15):bd02/25/2020:svnLENOVO:pn20R1S05A00:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1S05A00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1S05A00 dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1867479 Title: PCI/internal sound card not detected. Lenovo X1 Carbon Gen 7 Comet Lake Status in alsa-driver package in Ubuntu: New Bug description: It looks like 20.04 is now using sound open firmware (sof), however, sof does not have a driver(?) for Intel Comet Lake processors (which my Lenovo X1 Carbon Gen 7 laptop has). Here is the relevant output of dmesg: [3.272336] sof-audio-pci :00:1f.3: warning: No matching ASoC machine driver found [3.272343] sof-audio-pci :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040380 [3.272485] sof-audio-pci :00:1f.3: use msi interrupt mode [3.323370] sof-audio-pci :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.355159] sof-audio-pci :00:1f.3: hda codecs found, mask 5 [3.355161] sof-audio-pci :00:1f.3: using HDA machine driver skl_hda_dsp_generic now [3.377802] sof-audio-pci :00:1f.3: Direct firmware load for intel/sof/sof-cnl.ri failed with error -2 [3.377805] sof-audio-pci :00:1f.3: error: request firmware intel/sof/sof-cnl.ri failed err: -2 [3.377808] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2 [3.377809] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 18:22:42 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected
[Desktop-packages] [Bug 1867474] Re: PCI/internal sound card not detected
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1867474 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1867474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867474] [NEW] PCI/internal sound card not detected
You have been subscribed to a public bug: Problem with detecting audio input/output device. Device: Dell Vostro 5590 Tested earlier also on Ubuntu 18.04 and 19.10. On older systems with some configurations output device was working, but I never succeeded making build-in microphone to work (be properly detected). On current Ubuntu 20.04 (14.03.2020) both input and output audio devices are not visible at all. Devices are work without any issues on Windows 10 originally installed on the device. Let me know if I can provide any additional information that will help solving the issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 23:45:55 2020 InstallationDate: Installed on 2020-03-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 051P23 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn051P23:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5590 dmi.product.sku: 095A dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- PCI/internal sound card not detected https://bugs.launchpad.net/bugs/1867474 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1867469] Re: Update failed on allmost all Ubuntu 20.04 systems
There is nothing wrong with my keyboard layout. Typing sudo -s without touching the keyboard for any additional input, gives those password error messages, as explaned in the original report. Like I said my system is working again due to snapshots, I will wait for a new corrected update. On Sat, 2020-03-14 at 21:55 +, Matthias Klumpp wrote: > @lammert-nijhof: Your locale/keyboard layout is likely messed up - > type > your password without sudo, to see which password you are actually > typing for your account (and then adjust to the keyboard layout you > currently have for repair) > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867472] Re: nautilus crashed with SIGSEGV
*** This bug is a duplicate of bug 1857539 *** https://bugs.launchpad.net/bugs/1857539 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1857539, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1867472/+attachment/5337014/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1867472/+attachment/5337016/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1867472/+attachment/5337021/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1867472/+attachment/5337022/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1867472/+attachment/5337023/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1867472/+attachment/5337024/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1867472/+attachment/5337025/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1857539 nautilus crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1867472 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: New Bug description: nautilus crashed in background seconds after login ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 22:39:15 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2020-03-12 (2 days ago) InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200311) ProcCmdline: /usr/bin/nautilus --gapplication-service SegvAnalysis: Segfault happened at: 0x7f066b982ae2:mov0x380(%rax),%rax PC (0x7f066b982ae2) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1867472/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867471] Re: FFe: Sync appstream 0.12.10-2 (main) from Debian unstable (main)
** Patch added: "appstream_0.12.10-1_to_0.12.10-2.debdiff" https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1867471/+attachment/5337013/+files/appstream_0.12.10-1_to_0.12.10-2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1867471 Title: FFe: Sync appstream 0.12.10-2 (main) from Debian unstable (main) Status in appstream package in Ubuntu: New Bug description: Please sync appstream 0.12.10-2 (main) from Debian unstable (main) Explanation of FeatureFreeze exception: This revision pulls in a few changes from upstream to fix issues or prevent future annoyances: fix-free-license-check.patch A plain bugfix to the "is this a free license?" check of AppStream, which was introduced in this release. In the current version, licenses which are non-free may incorrectly be considered free. There isn't much stuff using this feature yet, but when it does we may as well give a correct result. ascli-explain-in-manpage.patch A simple non-functional manual page addition, since people apparently had a hard time to find the "--explain" switch for the AppStream validator. There is no potential for regression in this patch. ignore-control-relation-in-validator.patch Control relations are defined in the upcoming version of the AppStream specification and define how an application is controlled (keyboard, touch, ...). This feature is potentially used *a lot* and the current validator in Ubuntu will consider the usage of this tag invalid. With this patch, this tag isn't considered an error anymore, which should annoy users and developers much less when they are working with AppStream data on the LTS release. update-static-data.patch This just updates the license ID list to what is current in the SPDX registry. The regression potential of all of these changes is very low. Having them will greatly improve the experience of users with AppStream metadata in Ubuntu, and hopefully may lead to less bug reports upstream ;-) A full debdiff of the changes is attached. The biggest change is the non-free-licenses fix, all the other changes are simple few-line changes or just update static data or help text. Thanks for considering! Changelog entries since current focal version 0.12.10-1: appstream (0.12.10-2) unstable; urgency=medium * Add fix-free-license-check.patch: Non-free licenses were previously considered free software, this patch fixes that * Add ascli-explain-in-manpage.patch: Explain the `--explain` flag for `appstreamcli validate` in the manual page as well * Add ignore-control-relation-in-validator.patch: Don't fail validation if control relations exists. This is an upcoming AppStream feature that will potentially be used quite a lot. * Add update-static-data.patch: Update the license and TLD lists to validate newer licenses correctly. * Bump standards version: No changes needed -- Matthias Klumpp Sat, 14 Mar 2020 16:40:14 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1867471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867471] [NEW] FFe: Sync appstream 0.12.10-2 (main) from Debian unstable (main)
Public bug reported: Please sync appstream 0.12.10-2 (main) from Debian unstable (main) Explanation of FeatureFreeze exception: This revision pulls in a few changes from upstream to fix issues or prevent future annoyances: fix-free-license-check.patch A plain bugfix to the "is this a free license?" check of AppStream, which was introduced in this release. In the current version, licenses which are non-free may incorrectly be considered free. There isn't much stuff using this feature yet, but when it does we may as well give a correct result. ascli-explain-in-manpage.patch A simple non-functional manual page addition, since people apparently had a hard time to find the "--explain" switch for the AppStream validator. There is no potential for regression in this patch. ignore-control-relation-in-validator.patch Control relations are defined in the upcoming version of the AppStream specification and define how an application is controlled (keyboard, touch, ...). This feature is potentially used *a lot* and the current validator in Ubuntu will consider the usage of this tag invalid. With this patch, this tag isn't considered an error anymore, which should annoy users and developers much less when they are working with AppStream data on the LTS release. update-static-data.patch This just updates the license ID list to what is current in the SPDX registry. The regression potential of all of these changes is very low. Having them will greatly improve the experience of users with AppStream metadata in Ubuntu, and hopefully may lead to less bug reports upstream ;-) A full debdiff of the changes is attached. The biggest change is the non-free-licenses fix, all the other changes are simple few-line changes or just update static data or help text. Thanks for considering! Changelog entries since current focal version 0.12.10-1: appstream (0.12.10-2) unstable; urgency=medium * Add fix-free-license-check.patch: Non-free licenses were previously considered free software, this patch fixes that * Add ascli-explain-in-manpage.patch: Explain the `--explain` flag for `appstreamcli validate` in the manual page as well * Add ignore-control-relation-in-validator.patch: Don't fail validation if control relations exists. This is an upcoming AppStream feature that will potentially be used quite a lot. * Add update-static-data.patch: Update the license and TLD lists to validate newer licenses correctly. * Bump standards version: No changes needed -- Matthias Klumpp Sat, 14 Mar 2020 16:40:14 +0100 ** Affects: appstream (Ubuntu) Importance: Wishlist Status: New ** Changed in: appstream (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1867471 Title: FFe: Sync appstream 0.12.10-2 (main) from Debian unstable (main) Status in appstream package in Ubuntu: New Bug description: Please sync appstream 0.12.10-2 (main) from Debian unstable (main) Explanation of FeatureFreeze exception: This revision pulls in a few changes from upstream to fix issues or prevent future annoyances: fix-free-license-check.patch A plain bugfix to the "is this a free license?" check of AppStream, which was introduced in this release. In the current version, licenses which are non-free may incorrectly be considered free. There isn't much stuff using this feature yet, but when it does we may as well give a correct result. ascli-explain-in-manpage.patch A simple non-functional manual page addition, since people apparently had a hard time to find the "--explain" switch for the AppStream validator. There is no potential for regression in this patch. ignore-control-relation-in-validator.patch Control relations are defined in the upcoming version of the AppStream specification and define how an application is controlled (keyboard, touch, ...). This feature is potentially used *a lot* and the current validator in Ubuntu will consider the usage of this tag invalid. With this patch, this tag isn't considered an error anymore, which should annoy users and developers much less when they are working with AppStream data on the LTS release. update-static-data.patch This just updates the license ID list to what is current in the SPDX registry. The regression potential of all of these changes is very low. Having them will greatly improve the experience of users with AppStream metadata in Ubuntu, and hopefully may lead to less bug reports upstream ;-) A full debdiff of the changes is attached. The biggest change is the non-free-licenses fix, all the other changes are simple few-line changes or just update static data or help text. Thanks for considering! Changelog entries since current focal version 0.12.10-1: appstream (0.12.10-2) unstable; urgency=medium * Add
[Desktop-packages] [Bug 1867469] Re: Update failed on allmost all Ubuntu 20.04 systems
@lammert-nijhof: Your locale/keyboard layout is likely messed up - type your password without sudo, to see which password you are actually typing for your account (and then adjust to the keyboard layout you currently have for repair) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://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 1867469] Re: Update failed on allmost all Ubuntu 20.04 systems
Thank you, but I run VMs on top of ZFS, so I restored the Virtualbox vdi file from the last snapshot and blocked futher updates. I'll wait for the correction. If needed, I can easily try-out something, using this time the VBox snapshots. On Sat, 2020-03-14 at 21:35 +, Manfred Hampl wrote: > This is a known problem. > > See Bug #1866844 comment #12 for an emergency repair. > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864001] Re: "Save as" in chromium with unprintable characters
I installed Chromium directly using Snap, so apport said “Package chromium-browser not installed and no hook available, ignoring”. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1864001 Title: "Save as" in chromium with unprintable characters Status in chromium-browser package in Ubuntu: New Bug description: In Chromium with the following version numbers (output of “snap list”): chromium 80.0.3987.100 1026 stable canonical✓ - (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable characters, i.e., I see only small boxes instead of letters. I don’t observe this in comparable dialogs of other programs, e.g. Inkscape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864001] Re: "Save as" in chromium with unprintable characters
I attached a screenshot showing the problem. ** Attachment added: "The “open file“ dialog as opened with Ctrl+o." https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864001/+attachment/5337011/+files/Bildschirmfoto%20von%202020-03-14%2022-33-50.png ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1864001 Title: "Save as" in chromium with unprintable characters Status in chromium-browser package in Ubuntu: New Bug description: In Chromium with the following version numbers (output of “snap list”): chromium 80.0.3987.100 1026 stable canonical✓ - (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable characters, i.e., I see only small boxes instead of letters. I don’t observe this in comparable dialogs of other programs, e.g. Inkscape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1864001] Re: "Save as" in chromium with unprintable characters
I found out that a workaround is to remove ~/snap/chromium/common/.cache/fontconfig before starting Chromium. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1864001 Title: "Save as" in chromium with unprintable characters Status in chromium-browser package in Ubuntu: New Bug description: In Chromium with the following version numbers (output of “snap list”): chromium 80.0.3987.100 1026 stable canonical✓ - (Ubuntu 19.10) the “Save as” dialog box consists only of unprintable characters, i.e., I see only small boxes instead of letters. I don’t observe this in comparable dialogs of other programs, e.g. Inkscape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867469] Re: Update failed on allmost all Ubuntu 20.04 systems
Of course the proposed apt correction did not work since sudo fails. I don't use any ppa! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867469] Re: Update failed on allmost all Ubuntu 20.04 systems
This is a known problem. See Bug #1866844 comment #12 for an emergency repair. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867469] Re: Update failed on allmost all Ubuntu 20.04 systems
See the error message that had been displayed .?field.comment=See the error message that had been displayed . ** Attachment added: "Screenshot from 2020-03-14 17-25-57.png" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+attachment/5337010/+files/Screenshot%20from%202020-03-14%2017-25-57.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867469] [NEW] Update failed on allmost all Ubuntu 20.04 systems
Public bug reported: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1867469 Title: Update failed on allmost all Ubuntu 20.04 systems Status in gnome-software package in Ubuntu: New Bug description: Today the update of almost all Ubuntu 20.04 systems failed. Afterwards the system can't be rebooted and even the recovery mode does not work. This is one of the symptons and I even did not touch the keyboard. bertadmin@VM-Budgie:~$ sudo -s Sorry, try again. Sorry, try again. sudo: 3 incorrect password attempts bertadmin@VM-Budgie:~$ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.35.91-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Sat Mar 14 17:16:04 2020 InstallationDate: Installed on 2020-01-13 (61 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Alpha amd64 (20200113) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.35.91-0ubuntu1 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1867469/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867466] [NEW] Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the
Public bug reported: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the bar nor turn off the computer, only the open tabs work. Even some app icons that I closed don't show up and if I click on all apps it doesn't work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 21:33:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867466 Title: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the bar nor turn off the computer, only the open tabs work Status in gnome-shell package in Ubuntu: New Bug description: Practically if I try to drag in the taskbar on the left an application freezes everything and you cannot make squares in the desk nor click on other apps in the bar nor turn off the computer, only the open tabs work. Even some app icons that I closed don't show up and if I click on all apps it doesn't work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 21:33:57 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-09 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867466/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867462] Re: Desktop icons extension does not work properly
Worth nothing, as a workaround I issued `dpkg -r --force-depends gnome- shell-extension-desktop-icons' followed by 'apt-mark hold gnome-shell- extension-desktop-icons` to be able to get rid of the extension. Once done, logging out and back in will give you a clean desktop with no icons. -- 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/1867462 Title: Desktop icons extension does not work properly Status in gnome-control-center package in Ubuntu: New Bug description: First, I am unable to find any way of disabling/hiding desktop icons in Gnome settings. Is this intended behavior? Second, when using Gnome tweaks, there is currently no way of disabling/hiding desktop icons via the extension, clicking the settings button for it renders no result and disabling it will not hide desktop icons. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 20:23:41 2020 InstallationDate: Installed on 2020-03-06 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) 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/1867462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867462] [NEW] Desktop icons extension does not work properly
Public bug reported: First, I am unable to find any way of disabling/hiding desktop icons in Gnome settings. Is this intended behavior? Second, when using Gnome tweaks, there is currently no way of disabling/hiding desktop icons via the extension, clicking the settings button for it renders no result and disabling it will not hide desktop icons. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 20:23:41 2020 InstallationDate: Installed on 2020-03-06 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) 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 -- 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/1867462 Title: Desktop icons extension does not work properly Status in gnome-control-center package in Ubuntu: New Bug description: First, I am unable to find any way of disabling/hiding desktop icons in Gnome settings. Is this intended behavior? Second, when using Gnome tweaks, there is currently no way of disabling/hiding desktop icons via the extension, clicking the settings button for it renders no result and disabling it will not hide desktop icons. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 20:23:41 2020 InstallationDate: Installed on 2020-03-06 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) 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/1867462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867444] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) using PCA backend
Thanks for the bug reports!
** Also affects: duplicity
Importance: Undecided
Status: New
** Changed in: duplicity
Importance: Undecided => Medium
** Changed in: duplicity
Status: New => Fix Committed
** Changed in: duplicity
Milestone: None => 0.8.12
--
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/1867444
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) using PCA backend
Status in Duplicity:
Fix Committed
Status in duplicity package in Ubuntu:
New
Bug description:
Sorry but after last fix, I have another error.
I am using duplicity 0.8.11.1606 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200314T160021Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(source_path.name))
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py", line
520, in request
resp = self.send(prep, **send_kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py", line
630, in send
r = adapter.send(request, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/requests/adapters.py", line
460, in send
for i in request.body:
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/utils.py", line
279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/84/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1867444/+subscriptions
--
Mailing list: https://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 1866933] Re: Gnome Shell freeze
I tried to but was unable to replicate. There were several extensions which gave me an error when I tried to reinstall them. On Sat, Mar 14, 2020 at 4:50 AM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Thanks. If you can figure out which extension was causing the problem > then we can possibly reopen and reassign this bug to just that > extension. > > ** Changed in: gnome-shell (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1866933 > > Title: > Gnome Shell freeze > > Status in gnome-shell package in Ubuntu: > Invalid > > Bug description: > when I click on the Activities button and try to start an application > my X session freezes. I can move the mouse around and bring up the > dock on the side of the screen, but no windows will come up. This > problem does not come up if I open applications from the applications > menu, dock, or terminal. I can only solve it by logging out and > logging back in. > > Description: Ubuntu Focal Fossa (development branch) > Release: 20.04 > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > BootLog: > > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Mar 10 20:12:16 2020 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > DkmsStatus: >virtualbox, 6.1.4, 5.4.0-14-generic, x86_64: installed >virtualbox-guest, 6.1.4, 5.4.0-14-generic, x86_64: installed > EcryptfsInUse: Yes > ExtraDebuggingInterest: Yes, including running git bisection searches > GpuHangFrequency: Several times a day > GpuHangReproducibility: Yes, I can easily reproduce it > GpuHangStarted: Within the last few days > GraphicsCard: >Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 > [VGA controller]) > Subsystem: Intel Corporation Iris Graphics 540 [8086:2063] > InstallationDate: Installed on 2017-10-19 (873 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic > root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/24/2019 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: SYSKLi35.86A.0071.2019.0524.1102 > dmi.board.asset.tag: >� [� > dmi.board.name: NUC6i5SYB > dmi.board.vendor: Intel corporation > dmi.board.version: H81131-505 > dmi.chassis.type: 3 > dmi.modalias: > dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0071.2019.0524.1102:bd05/24/2019:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-505:cvn:ct3:cvr: > version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 > version.libdrm2: libdrm2 2.4.100-4 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-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 > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu20 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > DisplayManager: gdm3 > DistroRelease: Ubuntu 20.04 > EcryptfsInUse: Yes > InstallationDate: Installed on 2017-10-19 (875 days ago) > InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) > Package: gnome-shell 3.35.91-1ubuntu2 > PackageArchitecture: amd64 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 > Tags: focal > Uname: Linux 5.4.0-14-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers video > _MarkForUpload: True > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866933/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in
[Desktop-packages] [Bug 1866698] Re: gnome shell takes 35% of cpu when system load indicator is run in default configuration
*** This bug is a duplicate of bug 784055 *** https://bugs.launchpad.net/bugs/784055 Thank you -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1866698 Title: gnome shell takes 35% of cpu when system load indicator is run in default configuration Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged Status in indicator-multiload package in Ubuntu: Incomplete Bug description: Problems started 10 days ago or so after update and restart of OS. Cpu load is 35 percent constantly after start of the system. No other process is started - I just login and that's it. I see cpu load. See attached file "Top". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 20:26:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-12-27 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191223) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Still happens with Ubuntu MATE 20.04 LTS (20200313) using VirtualBox 5.1. -- 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/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: New Status in gstreamer-vaapi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745345] Re: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
Still happens with Ubuntu MATE 20.04 LTS (20200413) using VirtualBox 5.1. -- 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/1745345 Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. Status in X.Org X server: New Status in gstreamer-vaapi package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: It happened after upgrade to bionic, in the first login, after logon screen. Instead of opening the desktop area, gave the error. I had to do hard reset to be able to use X. After hard reset showed the same error but after a while it entered desktop. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 AssertionMessage: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Thu Jan 25 10:09:41 2018 DistUpgraded: 2018-01-25 02:34:06,581 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] Ficheiro ou directoria inexistente: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems HD Graphics 5500 [1179:f920] Subsystem: Toshiba America Info Systems Radeon R7 M260 [1179:f923] InstallationDate: Installed on 2018-01-07 (17 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: TOSHIBA SATELLITE L50-B ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcEnviron: LANGUAGE=pt:pt_BR:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_PT.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic root=UUID=7985a6e4-e304-4f48-97b5-9111dc373a81 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51 __GI_abort () at abort.c:90 __assert_fail_base (fmt=, assertion=assertion@entry=0x7f549469ed25 "key->initialized", file=file@entry=0x7f549469ed08 "/usr/include/xorg/privates.h", line=line@entry=122, function=function@entry=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:92 __GI___assert_fail (assertion=0x7f549469ed25 "key->initialized", file=0x7f549469ed08 "/usr/include/xorg/privates.h", line=122, function=0x7f549469fd00 "dixGetPrivateAddr") at assert.c:101 ?? () from /usr/lib/xorg/modules/drivers/amdgpu_drv.so Title: Xorg assert failure: Xorg: /usr/include/xorg/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: Upgraded to bionic on 2018-01-25 (0 days ago) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 2.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Type2 - Board Vendor Name1 dmi.board.version: Type2 - Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis ManuFacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr2.10:bd01/21/2015:svnTOSHIBA:pnSATELLITEL50-B:pvrPSKTNE-01U011EP:rvnType2-BoardVendorName1:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnOEMChassisManuFacturer:ct10:cvrOEMChassisVersion: dmi.product.family: INVALID dmi.product.name: SATELLITE L50-B dmi.product.version: PSKTNE-01U011EP dmi.sys.vendor: TOSHIBA version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1745345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1796437] Re: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()
*** This bug is a duplicate of bug 1745345 *** https://bugs.launchpad.net/bugs/1745345 Still happens with Ubuntu MATE 20.04 LTS (20200413) using VirtualBox 5.1. -- 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/1796437 Title: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate() Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 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 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1796437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1796437] Re: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate()
*** This bug is a duplicate of bug 1745345 *** https://bugs.launchpad.net/bugs/1745345 Still happens with Ubuntu MATE 20.04 LTS (20200313) using VirtualBox 5.1. -- 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/1796437 Title: [nouveau] Xorg crashes with assertion failure "key->initialized" in dixGetPrivateAddr() from dixLookupPrivate() from DRI2Authenticate() Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: Went to the menu button in upper left corner. Attempted to open Budgie Welcome and the X11 session crashed. About 4 lines of error code were displayed for a few seconds then the login screen appeared. Description: Ubuntu Cosmic Cuttlefish (development branch) Release: 18.10 budgie-welcome: Installed: (none) Candidate: 0.6.1 Version table: 0.6.1 500 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages 500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages Seems to not be installed on a fresh install. So solved but needs fixing? ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: xserver-xorg-core 2:1.20.1-3ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AssertionMessage: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. BootLog: [[0;32m OK [0m] Stopped Snappy daemon. Starting Snappy daemon... CompositorRunning: None CrashCounter: 1 Date: Fri Oct 5 20:36:30 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2018-10-06 (0 days ago) InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 (20181005) MachineType: System manufacturer System Product Name ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1 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 __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=) at assert.c:92 __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101 ?? () Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: dixGetPrivateAddr: Assertion `key->initialized' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/14/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS IX FORMULA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx: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 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1796437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1867406] Re: Ubuntu 20.04 Dock/Taskbar icons
Video showing the problem ** Attachment added: "Video showing the problem" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867406/+attachment/5336904/+files/Ubuntu%2020.04.webm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867406 Title: Ubuntu 20.04 Dock/Taskbar icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When the taskbar/dock is located at the bottom of the screen it is near impossible to rearrange the icons within it. I posted to a forum and one other user confirmed he has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867442] Re: settings dialog for extension "desktop icons" doesn't launch
*** This bug is a duplicate of bug 1866146 *** https://bugs.launchpad.net/bugs/1866146 ** This bug has been marked a duplicate of bug 1866146 GNOME Shell 3.35.91 extension's preferences doesn't load -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867442 Title: settings dialog for extension "desktop icons" doesn't launch Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installiert: 3.35.91-1ubuntu2 Installationskandidat: 3.35.91-1ubuntu2 Versionstabelle: *** 3.35.91-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I clicked the settings icon of Desktop Icons to change the settings of this extension. Instead no settings dialog appeared, no indication of any activity. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 16:21:27 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2020-03-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867444] [NEW] UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0: ordinal not in range(128) using PCA backend
Public bug reported:
Sorry but after last fix, I have another error.
I am using duplicity 0.8.11.1606 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200314T160021Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(source_path.name))
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files, **self.requests_args)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
422, in _request
return self.request_session.request(*arg, **kwarg)
File "/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py",
line 520, in request
resp = self.send(prep, **send_kwargs)
File "/snap/duplicity/84/usr/lib/python3/dist-packages/requests/sessions.py",
line 630, in send
r = adapter.send(request, **kwargs)
File "/snap/duplicity/84/usr/lib/python3/dist-packages/requests/adapters.py",
line 460, in send
for i in request.body:
File "/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/utils.py",
line 279, in __next__
chunk = self.content.read(self.chunk_size)
File "/snap/duplicity/84/usr/lib/python3.6/encodings/ascii.py", line 26, in
decode
return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position 0:
ordinal not in range(128)
** Affects: duplicity (Ubuntu)
Importance: Undecided
Status: New
--
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/1867444
Title:
UnicodeDecodeError: 'ascii' codec can't decode byte 0x85 in position
0: ordinal not in range(128) using PCA backend
Status in duplicity package in Ubuntu:
New
Bug description:
Sorry but after last fix, I have another error.
I am using duplicity 0.8.11.1606 from snap edge channel.
I am trying to use multi backend with one of them being the OVH PCA.
It fails when trying to write to the PCA with the following error :
MultiBackend: _put: write to store #0 (pca://backupPortableX-cold)
Writing cold_duplicity-full.20200314T160021Z.vol1.difftar.gpg
Backtrace of previous error: Traceback (innermost last):
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 376, in inner_retry
return fn(self, *args)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 547, in put
self.__do_put(source_path, remote_filename)
File "/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backend.py",
line 533, in __do_put
self.backend._put(source_path, remote_filename)
File
"/snap/duplicity/84/lib/python3.6/site-packages/duplicity/backends/pcabackend.py",
line 154, in _put
open(source_path.name))
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1842, in put_object
response_dict=response_dict)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1691, in _retry
service_token=self.service_token, **kwargs)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
1320, in put_object
conn.putrequest(path, headers=headers, data=data)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
449, in putrequest
return self.request('PUT', full_path, data, headers, files)
File
"/snap/duplicity/84/usr/lib/python3/dist-packages/swiftclient/client.py", line
439, in request
files=files,
[Desktop-packages] [Bug 1867442] [NEW] settings dialog for extension "desktop icons" doesn't launch
Public bug reported: Description:Ubuntu Focal Fossa (development branch) Release:20.04 gnome-shell: Installiert: 3.35.91-1ubuntu2 Installationskandidat: 3.35.91-1ubuntu2 Versionstabelle: *** 3.35.91-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I clicked the settings icon of Desktop Icons to change the settings of this extension. Instead no settings dialog appeared, no indication of any activity. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 16:21:27 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2020-03-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867442 Title: settings dialog for extension "desktop icons" doesn't launch Status in gnome-shell package in Ubuntu: New Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 gnome-shell: Installiert: 3.35.91-1ubuntu2 Installationskandidat: 3.35.91-1ubuntu2 Versionstabelle: *** 3.35.91-1ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I clicked the settings icon of Desktop Icons to change the settings of this extension. Instead no settings dialog appeared, no indication of any activity. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 14 16:21:27 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell-extension-prefs InstallationDate: Installed on 2020-03-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867442/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867406] Re: Ubuntu 20.04 Dock/Taskbar icons
My experience with that matter and how to reproduce: Ubuntu 20.04 (development) installed. Ubuntu dock bar at the left (or right): You can easily re-arrange the icons by dragging one of them up or down with your mouse and pressed left mouse button. When hovering between two icons, they slide up and down to create space for dropping the icon that you want to move. Now relocate the dock bar to the bottom edge of the screen with Settings - appearance - position of the dock: bottom Now when attempting to move an icon, the other icons do not leave space for dropping the moving icon, but they move somewhat in groups. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867406 Title: Ubuntu 20.04 Dock/Taskbar icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When the taskbar/dock is located at the bottom of the screen it is near impossible to rearrange the icons within it. I posted to a forum and one other user confirmed he has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867435] Re: TypeError: must be str, not bytes using PCA backend
** Also affects: duplicity Importance: Undecided Status: New ** Changed in: duplicity Importance: Undecided => Medium ** Changed in: duplicity Status: New => Fix Committed ** Changed in: duplicity Milestone: None => 0.8.12 -- 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/1867435 Title: TypeError: must be str, not bytes using PCA backend Status in Duplicity: Fix Committed Status in duplicity package in Ubuntu: New Bug description: I am using duplicity 0.8.11.1604 from snap edge channel. I am trying to use multi backend with one of them being the OVH PCA. It fails when trying to write to the PCA with the following error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200314T135032Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backends/pcabackend.py", line 153, in _put self.conn.put_object(self.container, self.prefix + remote_filename, TypeError: must be str, not bytes To manage notifications about this bug go to: https://bugs.launchpad.net/duplicity/+bug/1867435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867406] Re: Ubuntu 20.04 Dock/Taskbar icons
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867406 Title: Ubuntu 20.04 Dock/Taskbar icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When the taskbar/dock is located at the bottom of the screen it is near impossible to rearrange the icons within it. I posted to a forum and one other user confirmed he has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867406] Re: Ubuntu 20.04 Dock/Taskbar icons
** Package changed: ubuntu => gnome-shell-extension-ubuntu-dock (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1867406 Title: Ubuntu 20.04 Dock/Taskbar icons Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When the taskbar/dock is located at the bottom of the screen it is near impossible to rearrange the icons within it. I posted to a forum and one other user confirmed he has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1867406/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867406] [NEW] Ubuntu 20.04 Dock/Taskbar icons
You have been subscribed to a public bug: When the taskbar/dock is located at the bottom of the screen it is near impossible to rearrange the icons within it. I posted to a forum and one other user confirmed he has the same issue. ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 20.04 Dock/Taskbar icons https://bugs.launchpad.net/bugs/1867406 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock 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 1826159] Re: gsd-print-notifications assert failure: free(): invalid pointer
May be related to this bug as printing issues started with it.
https://bugs.launchpad.net/ubuntu/+source/ippusbxd/+bug/1866838
--
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/1826159
Title:
gsd-print-notifications assert failure: free(): invalid pointer
Status in gnome-settings-daemon package in Ubuntu:
Confirmed
Bug description:
This problem occurs since upgrade to disco dingo. Have not seen this
in earlier releases. It seems to be related to printers in the gnome
settings.
janw-LIFEBOOK-AH532-G21{janw}(79)% lsb_release -rd
Description: Ubuntu 19.04
Release: 19.04
apt-cache policy gnome-settings-daemon
gnome-settings-daemon:
Installerad: 3.32.0-1ubuntu1
Kandidat:3.32.0-1ubuntu1
Versionstabell:
*** 3.32.0-1ubuntu1 500
500 http://se.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
ProblemType: Crash
DistroRelease: Ubuntu 19.04
Package: gnome-settings-daemon 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AssertionMessage: free(): invalid pointer
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 22:16:13 2019
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-print-notifications
InstallationDate: Installed on 2018-02-20 (427 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-print-notifications
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=sv_SE.UTF-8
SHELL=/bin/tcsh
Signal: 6
SourcePackage: gnome-settings-daemon
StacktraceTop:
__libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f247b810952
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
malloc_printerr (str=str@entry=0x7f247b80ea9b "free(): invalid pointer") at
malloc.c:5352
_int_free (av=, p=, have_lock=)
at malloc.c:4181
()
g_list_foreach () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gsd-print-notifications assert failure: free(): invalid pointer
UpgradeStatus: Upgraded to disco on 2019-04-19 (4 days ago)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo
mtime.conffile..etc.apport.crashdb.conf: 2019-04-24T11:16:47.806271
separator:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1826159/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741074] Re: [snap] chrome-gnome-shell extension fails to detect native host connector
This is still an issue on 20.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1741074 Title: [snap] chrome-gnome-shell extension fails to detect native host connector Status in chromium-browser package in Ubuntu: Triaged Bug description: (initially reported at https://forum.snapcraft.io/t/chrome-gnome- shell-does-not-work-with-chromium-snap/3377) See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1797734] Re: slow calculator startup
I'm not sure why the "is 2s too slow to start" is the question being asked. Who starts and stops their calculator multiple times in a row? That's not a realistic use-case for the vast majority. Most people need a calculator once a day or every few days, and a desktop calculator is not an application people tend to leave running for long periods like a browser or word processor. They need to do a quick bit of computation so they open the app, work in it for a few minutes, then close it again. Startup speed is, after correctness, probably THE most important aspect of a utility like this. The interesting number for gnome-calculator is the FIRST number: how long it takes to be able to use the application from a cold start. 15s is much closer to what I see, EVERY TIME I start gnome-calculator. That's just... close to unusable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1797734 Title: slow calculator startup Status in gnome-calculator package in Ubuntu: Confirmed Bug description: The calculator starts very slowly. It's a tiny program, but it runs like a very big one. In previous versions of Ubuntu, the launch was normal, very fast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-calculator (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 14 08:40:06 2018 InstallationDate: Installed on 2018-05-06 (160 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: gnome-calculator UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1797734/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867435] [NEW] TypeError: must be str, not bytes using PCA backend
Public bug reported: I am using duplicity 0.8.11.1604 from snap edge channel. I am trying to use multi backend with one of them being the OVH PCA. It fails when trying to write to the PCA with the following error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200314T135032Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backends/pcabackend.py", line 153, in _put self.conn.put_object(self.container, self.prefix + remote_filename, TypeError: must be str, not bytes ** Affects: duplicity (Ubuntu) Importance: Undecided Status: New -- 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/1867435 Title: TypeError: must be str, not bytes using PCA backend Status in duplicity package in Ubuntu: New Bug description: I am using duplicity 0.8.11.1604 from snap edge channel. I am trying to use multi backend with one of them being the OVH PCA. It fails when trying to write to the PCA with the following error : MultiBackend: _put: write to store #0 (pca://backupPortableX-cold) Writing cold_duplicity-full.20200314T135032Z.vol1.difftar.gpg Backtrace of previous error: Traceback (innermost last): File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 376, in inner_retry return fn(self, *args) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 547, in put self.__do_put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backend.py", line 533, in __do_put self.backend._put(source_path, remote_filename) File "/snap/duplicity/83/lib/python3.6/site-packages/duplicity/backends/pcabackend.py", line 153, in _put self.conn.put_object(self.container, self.prefix + remote_filename, TypeError: must be str, not bytes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1867435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1363277] Re: Indicator not shown in fallback mode when a subdir/file with the same name of icon exists in current work dir
** Bug watch added: github.com/pwr-Solaar/Solaar/issues #698
https://github.com/pwr-Solaar/Solaar/issues/698
** Also affects: solaar-unifying via
https://github.com/pwr-Solaar/Solaar/issues/698
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libappindicator in Ubuntu.
https://bugs.launchpad.net/bugs/1363277
Title:
Indicator not shown in fallback mode when a subdir/file with the same
name of icon exists in current work dir
Status in libappindicator:
New
Status in Solaar:
Unknown
Status in libappindicator package in Ubuntu:
Confirmed
Bug description:
Take the attached python script and execute it in a non-unity desktop
which does not support appindicators but can show gtk_status_icon (see
at the end of the post under the "Tested on" paragraph).
The attached script will fallback correctly to the old gtk_status_icon
and will show the "battery-good" indicator icon on the system tray.
Now exit from the script (with ^C).
In your current directory create a subdir named "battery-good".
Do not change directory and relaunch the script.
The fallback mechanism will be unable to find the icon, and now the
indicator will not be shown.
The problem could be in app-indicator.c, near line 1641
if (g_file_test(icon_name, G_FILE_TEST_EXISTS)) {
gtk_status_icon_set_from_file(icon, icon_name);
}
This code will find the subdir "battery-good" you created, and it will
try to load it as a icon. But if it fails, as it does, it will never
load an icon for your indicator.
Tested on xubuntu 14.04.1 64bit without indicator panel element and
with indicator application removed from autostart. Tested also on
Fedora 20 64bit with XFCE.
To manage notifications about this bug go to:
https://bugs.launchpad.net/libappindicator/+bug/1363277/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867320] Re: bad kerning
evince vs qpdfview on ubuntu, incorrect kerning in evince (left) ** Description changed: Evince exhibits incorrect/bad kerning on 20.04. - This occurs in 19.10 as well, but not on Arch Linux. + This occurs in 19.10 as well. + It does *not* occur in qpdfview (also poppler-based) on the same system, or in Evince on Arch Linux. - Could this be a poppler bug? + I'm stumped. Seeing as this doesn't occur in Evince on Arch, it has to + be some kind of dependency/packaging/lib problem? ** Attachment added: "evince vs qpdfview on ubuntu, incorrect kerning in evince (left)" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1867320/+attachment/5336791/+files/Screenshot%20from%202020-03-14%2013-15-35.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1867320 Title: bad kerning Status in evince package in Ubuntu: New Bug description: Evince exhibits incorrect/bad kerning on 20.04. This occurs in 19.10 as well. It does *not* occur in qpdfview (also poppler-based) on the same system, or in Evince on Arch Linux. I'm stumped. Seeing as this doesn't occur in Evince on Arch, it has to be some kind of dependency/packaging/lib problem? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1867320/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867429] [NEW] libreoffice-base pre-depends issue
Public bug reported: It seems libreoffice-base 1:6.4.0-0ubuntu7 is missing "Pre-Depends: dpkg (>= 1.19.1)". dpkg 1.19.1 introduced the --no-rename option. Error log : Preparing to unpack .../libreoffice-base_1%3a6.4.0-0ubuntu7_amd64.deb ... dpkg-divert: error: unknown option --no-rename Use --help for help about diverting files. dpkg: error processing archive /var/cache/apt/archives/libreoffice-base_1%3a6.4.0-0ubuntu7_amd64.deb (--unpack): new libreoffice-base package pre-installation script subprocess returned error exit status 2 ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- 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/1867429 Title: libreoffice-base pre-depends issue Status in libreoffice package in Ubuntu: New Bug description: It seems libreoffice-base 1:6.4.0-0ubuntu7 is missing "Pre-Depends: dpkg (>= 1.19.1)". dpkg 1.19.1 introduced the --no-rename option. Error log : Preparing to unpack .../libreoffice-base_1%3a6.4.0-0ubuntu7_amd64.deb ... dpkg-divert: error: unknown option --no-rename Use --help for help about diverting files. dpkg: error processing archive /var/cache/apt/archives/libreoffice-base_1%3a6.4.0-0ubuntu7_amd64.deb (--unpack): new libreoffice-base package pre-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1867429/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1405452] Re: Typo in man page ("introduce a much improvement mechanism")
** Tags removed: utopic vivid
** Tags added: bionic focal
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1405452
Title:
Typo in man page ("introduce a much improvement mechanism")
Status in One Hundred Papercuts:
Triaged
Status in wpa package in Ubuntu:
Triaged
Status in wpa package in Debian:
New
Bug description:
"introduce a much improvement mechanism" should be "introduce a much
improved mechanism".
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: wpasupplicant 2.1-0ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1
Uname: Linux 3.16.0-28-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Wed Dec 24 16:19:30 2014
InstallationDate: Installed on 2014-12-19 (4 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64
(20141022.1)
SourcePackage: wpa
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1405452/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
** Changed in: hundredpapercuts Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: New Status in chrome-gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867345] Re: Do not ship "Extensions" application with gnome-shell
** Changed in: hundredpapercuts Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867345 Title: Do not ship "Extensions" application with gnome-shell Status in One Hundred Papercuts: Opinion Status in gnome-shell package in Ubuntu: Opinion Bug description: Consider not shipping the "Extensions" application with gnome-shell in Ubuntu 20.04. This application is intended to be a standalone application and is not much useful in Ubuntu at the moment since new extensions can't be installed (because of https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1866841). To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1867345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867425] [NEW] Update tracker to 2.3.4 and tracker-miners to 2.3.3
Public bug reported: The 2.3.x branch receives bug fixes only since big, new development now goes to the master branch. tracker https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS NEW in 2.3.4 - 2020-03-10 = * Brown paper bag release, fix NULL check. NEW in 2.3.3 - 2020-03-09 = * Fix race condition during tracker-store shutdown maybe leading to warnings and missed writeback events. * Made fts:offsets stronger against corrupt FTS tables Translations: ja tracker-miners https://gitlab.gnome.org/GNOME/tracker-miners/-/blob/tracker-miners-2.3/NEWS NEW in 2.3.3 - 2020-03-09 = * The secure sandbox for tracker-extract now permits clock_nanosleep() calls, fixing crashes on some systems. * Miners now set nice/scheduler priorities in a way that placates glib. The sched_setscheduler syscall is as a side effect also allowed by the tracker-extract sandbox. Translations: ja NEW in 2.3.2 - 2020-02-18 = * Blocked parsing of image/x-dds image files, which were previously being passed to GStreamer and triggering system lockups for some people * Fixed incorrect MIME type for .raw images, which were previously being passed to GStreamer and triggering system lockups for some people * Improved how the MP3 extractor calculates durations of variable bitrate MP3s, which fixes incorrect durations being shown in GNOME Music. * Fixed a bug in the GStreamer writeback module. * Fix race condition that might leave tracker-miner-fs paused after a writeback operation. Translations: ms ** Affects: tracker (Ubuntu) Importance: Undecided Status: New ** Affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Tags: focal upgrade-software-version ** Also affects: tracker-miners (Ubuntu) Importance: Undecided Status: New ** Description changed: - The 2.3.x branch receives bug-fixes only since big, new development now + The 2.3.x branch receives bug fixes only since big, new development now goes to the master branch. tracker https://gitlab.gnome.org/GNOME/tracker/-/blob/tracker-2.3/NEWS NEW in 2.3.4 - 2020-03-10 = - * Brown paper bag release, fix NULL check. + * Brown paper bag release, fix NULL check. NEW in 2.3.3 - 2020-03-09 = - * Fix race condition during tracker-store shutdown maybe leading to - warnings and missed writeback events. - * Made fts:offsets stronger against corrupt FTS tables + * Fix race condition during tracker-store shutdown maybe leading to warnings and missed writeback events. + * Made fts:offsets stronger against corrupt FTS tables Translations: ja - tracker-miners https://gitlab.gnome.org/GNOME/tracker-miners/-/blob/tracker-miners-2.3/NEWS NEW in 2.3.3 - 2020-03-09 = - - * The secure sandbox for tracker-extract now permits clock_nanosleep() calls, - fixing crashes on some systems. - * Miners now set nice/scheduler priorities in a way that placates glib. The - sched_setscheduler syscall is as a side effect also allowed by the - tracker-extract sandbox. + * The secure sandbox for tracker-extract now permits clock_nanosleep() calls, fixing crashes on some systems. + * Miners now set nice/scheduler priorities in a way that placates glib. The sched_setscheduler syscall is as a side effect also allowed by the tracker-extract sandbox. Translations: ja NEW in 2.3.2 - 2020-02-18 = - - * Blocked parsing of image/x-dds image files, which were previously - being passed to GStreamer and triggering system lockups for some people - * Fixed incorrect MIME type for .raw images, which were previously - being passed to GStreamer and triggering system lockups for some people - * Improved how the MP3 extractor calculates durations of variable bitrate - MP3s, which fixes incorrect durations being shown in GNOME Music. - * Fixed a bug in the GStreamer writeback module. - * Fix race condition that might leave tracker-miner-fs paused after a - writeback operation. + * Blocked parsing of image/x-dds image files, which were previously being passed to GStreamer and triggering system lockups for some people + * Fixed incorrect MIME type for .raw images, which were previously being passed to GStreamer and triggering system lockups for some people + * Improved how the MP3 extractor calculates durations of variable bitrate MP3s, which fixes incorrect durations being shown in GNOME Music. + * Fixed a bug in the GStreamer writeback module. + * Fix race condition that might leave tracker-miner-fs paused after a writeback operation. Translations: ms -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1867425 Title: Update tracker to 2.3.4 and
[Desktop-packages] [Bug 1867405] Re: gdm3 loads very slowly with newer kernels
Please reboot again and then run this command to collect a fresh log of a slow boot: dmesg > dmesg.txt And then attach the resulting file 'dmesg.txt' here. ** Package changed: gdm3 (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete ** Tags added: performance -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1867405 Title: gdm3 loads very slowly with newer kernels Status in Ubuntu: Incomplete Bug description: After updating to the latest kernel (5.3 general/lowlatency) my W510 Thinkpad is taking forever to load gdm3. After some reading I installed haveged as some issues indicated this as a possible fix. No dice, still have the issue, no improvement. On average it takes about 40 seconds to a minute between plymouth switching and the mouse cursor being drawn, about a minute and a half to two minutes for the greeter to launch. I've disabled Wayland which seems to speed up the latter process slightly but its barely noticeable. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-24 (294 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Package: gdm3 3.28.3-0ubuntu18.04.4 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-lowlatency 5.3.18 Tags: bionic Uname: Linux 5.3.0-40-lowlatency x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2020-03-13T17:07:44.727975 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1867405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867352] Re: Xorg freeze after boot if use xorg.conf generated by nvidia-xconfig
Please reproduce the crash/freeze again, and then on the very next reboot collect a log of the previous boot where it was happening: journalctl -b-1 > prevboot.txt And then attach the file 'prevboot.txt' here. Please also check /var/crash/ for any files and if you find some then follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-440 (Ubuntu) ** Changed in: nvidia-graphics-drivers-440 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1867352 Title: Xorg freeze after boot if use xorg.conf generated by nvidia-xconfig Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: Hello! I have constant X crash if use xorg.conf generated by nvidia-xconfig. Currently my xorg.conf is absent. Only if I have an empty conf file or it is absent I can start X. The problem exists in 19.10 and 20.04 development version Also I have strange messages if I run nvidia-xconfig: $ sudo nvidia-xconfig WARNING: Unable to locate/open X configuration file. Package xorg-server was not found in the pkg-config search path. Perhaps you should add the directory containing `xorg-server.pc' to the PKG_CONFIG_PATH environment variable No package 'xorg-server' found New X configuration file written to '/etc/X11/xorg.conf' Here is my xorg.conf generated by nvidia: # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 440.64 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice"Keyboard0" "CoreKeyboard" InputDevice"Mouse0" "CorePointer" EndSection Section "Files" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/psaux" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor"Monitor0" DefaultDepth24 SubSection "Display" Depth 24 EndSubSection EndSection ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Это каталог: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.2.1 20200304 (Ubuntu 9.2.1-31ubuntu1) ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 16:44:45 2020 DistUpgraded: 2020-03-13 00:50:36,699 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed nvidia, 440.64, 5.4.0-14-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: I don't know GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation 3rd Gen Core processor Graphics Controller [104d:90b7] Subsystem: Sony Corporation GK208M [GeForce GT 735M] [104d:90b7] MachineType: Sony Corporation SVF15A1S9RB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=UUID=81c8a442-a191-4c83-b415-ee0f1f2b0b81 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal
[Desktop-packages] [Bug 1866841] Re: Add chrome-gnome-shell to ubuntu-desktop recommends
** Changed in: chrome-gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1866841 Title: Add chrome-gnome-shell to ubuntu-desktop recommends Status in One Hundred Papercuts: New Status in chrome-gnome-shell package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Bug description: Please, consider adding the chrome-gnome-shell package as a recommended dependency for ubuntu-desktop package in Ubuntu 20.04. The chrome-gnome-shell package provides GNOME Shell integration (connector) for Firefox, Chrome, Chromium and other web browsers that is necessary for users to be able to manage GNOME Shell extensions using a extensions.gnome.org website. Since the Shell Extensions support was removed from gnome-software since 3.36 and the replacement Extensions application cannot be used to find and install new extensions, there is not any user friendly way to install new Shell Extensions without having the chrome-gnome-shell package installed. More information: https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1866841/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 784055] Re: compiz CPU usage increases dramatically when running indicator-multiload
** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - compiz CPU usage increases dramatically when running indicator-multiload + CPU usage increases dramatically when running indicator-multiload ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed ** Project changed: indicator-multiload => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/784055 Title: CPU usage increases dramatically when running indicator-multiload Status in libindicator: Fix Committed Status in The Ubuntu Power Consumption Project: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Status in indicator-multiload package in Ubuntu: Confirmed Status in libindicator package in Ubuntu: Fix Released Bug description: using 0.1-0~5~natty1 on mostly up to date natty system, when running the indicator-multiload with with just cpu monitor and the default update interval of 500 milliseconds, I see (via top) that compiz usage when generally idle goes from either 0 or 1% of CPU to 3 or 4% of CPU. Reducing the update interval does seem to have an affect. I realize that a.) top is not scientific b.) there could be something I'm missing here c.) saying "300%" (in the subject) is not scientific To manage notifications about this bug go to: https://bugs.launchpad.net/libindicator/+bug/784055/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867337] Re: even after login the login page was displaying everywhere.
Please run this command (sorry I know you already used ubuntu-bug but it collected info for the wrong package): apport-collect 1867337 Also, if there are any files in /var/crash then please follow: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867337 Title: even after login the login page was displaying everywhere. Status in gnome-shell package in Ubuntu: Incomplete Bug description: I logged into Ubuntu and the system crashed and the login screen was a frozen screen with login page on it. All the apps were not as responsive as the expected login screen won't go. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 13 17:20:00 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-14-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-18-generic, x86_64: installed GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller [106b:00fa] InstallationDate: Installed on 2020-03-11 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) MachineType: Apple Inc. MacBookPro9,2 ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=70f5287a-ef7d-48fd-a479-01244bc3fecf ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 229.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-6F01561E16C75D06 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro9,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-6F01561E16C75D06 dmi.modalias: dmi:bvnAppleInc.:bvr229.0.0.0.0:bd07/24/2019:svnAppleInc.:pnMacBookPro9,2:pvr1.0:rvnAppleInc.:rnMac-6F01561E16C75D06:rvrMacBookPro9,2:cvnAppleInc.:ct10:cvrMac-6F01561E16C75D06: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro9,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867337/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867345] Re: Do not ship "Extensions" application with gnome-shell
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Wishlist ** Changed in: hundredpapercuts Status: New => Opinion ** Changed in: gnome-shell (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867345 Title: Do not ship "Extensions" application with gnome-shell Status in One Hundred Papercuts: Opinion Status in gnome-shell package in Ubuntu: Opinion Bug description: Consider not shipping the "Extensions" application with gnome-shell in Ubuntu 20.04. This application is intended to be a standalone application and is not much useful in Ubuntu at the moment since new extensions can't be installed (because of https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1866841). To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1867345/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866933] Re: Gnome Shell freeze
Thanks. If you can figure out which extension was causing the problem then we can possibly reopen and reassign this bug to just that extension. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866933 Title: Gnome Shell freeze Status in gnome-shell package in Ubuntu: Invalid Bug description: when I click on the Activities button and try to start an application my X session freezes. I can move the mouse around and bring up the dock on the side of the screen, but no windows will come up. This problem does not come up if I open applications from the applications menu, dock, or terminal. I can only solve it by logging out and logging back in. Description: Ubuntu Focal Fossa (development branch) Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Mar 10 20:12:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.4, 5.4.0-14-generic, x86_64: installed virtualbox-guest, 6.1.4, 5.4.0-14-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: Intel Corporation Iris Graphics 540 [8086:1926] (rev 0a) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Iris Graphics 540 [8086:2063] InstallationDate: Installed on 2017-10-19 (873 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0071.2019.0524.1102 dmi.board.asset.tag: � [� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-505 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0071.2019.0524.1102:bd05/24/2019:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-505:cvn:ct3:cvr: version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.0-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 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-19 (875 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: gnome-shell 3.35.91-1ubuntu2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Tags: focal Uname: Linux 5.4.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866933/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867416] Re: /usr/bin/gnome-shell:11:wl_resource_get_version:data_offer_choose_action:data_offer_update_action:create_and_send_dnd_offer:meta_wayland_drag_grab_set_focus
*** This bug is a duplicate of bug 1866368 *** https://bugs.launchpad.net/bugs/1866368 ** This bug has been marked a duplicate of bug 1866368 gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867416 Title: /usr/bin/gnome- shell:11:wl_resource_get_version:data_offer_choose_action:data_offer_update_action:create_and_send_dnd_offer:meta_wayland_drag_grab_set_focus Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.35.91-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866698] Re: gnome shell takes 35% of cpu when system load indicator is run in default configuration
*** This bug is a duplicate of bug 784055 *** https://bugs.launchpad.net/bugs/784055 Thanks. Since it's the same root cause I will merge this into bug 784055... ** This bug has been marked a duplicate of bug 784055 CPU usage increases dramatically when running indicator-multiload -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1866698 Title: gnome shell takes 35% of cpu when system load indicator is run in default configuration Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell-extension-appindicator package in Ubuntu: Triaged Status in indicator-multiload package in Ubuntu: Incomplete Bug description: Problems started 10 days ago or so after update and restart of OS. Cpu load is 35 percent constantly after start of the system. No other process is started - I just login and that's it. I see cpu load. See attached file "Top". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 9 20:26:58 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-12-27 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191223) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866698/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866851] Re: lock screen scaled down backgound image in top left corner
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866851 Title: lock screen scaled down backgound image in top left corner Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: The new lock screen in gnome 3.36 looks strange, as if the blurred background image is being scaled down to the top left corner of the screen. background image being used is 1920x1440 pixel jpeg, display size is 3840x2160, with fractional scaling enabled and set to 175% on wayland. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu19 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 10 07:38:52 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (206 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-06 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866851/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866368] Re: gnome-shell crashed with SIGSEGV in wl_resource_get_version()
Tracking in: https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c ** Information type changed from Private to Public ** Summary changed: - gnome-shell crashed with SIGSEGV in wl_resource_get_version() + gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) ** Description changed: + https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c + + --- + I had two crashes in a row, in both instances I was moving a Firefox tab from one window out to a new window with drag and drop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 16:16:03 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version() UpgradeStatus: Upgraded to focal on 2019-08-24 (195 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1866368 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version(resource=0x0) Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c --- I had two crashes in a row, in both instances I was moving a Firefox tab from one window out to a new window with drag and drop. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-17.21-generic 5.4.22 Uname: Linux 5.4.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 16:16:03 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 Signal: 11 SourcePackage: gnome-shell StacktraceTop: wl_resource_get_version () from /usr/lib/x86_64-linux-gnu/libwayland-server.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGSEGV in wl_resource_get_version() UpgradeStatus: Upgraded to focal on 2019-08-24 (195 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867304] Re: LG OLED TV screen resolution not properly detected
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1867304 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1867304 Title: LG OLED TV screen resolution not properly detected Status in xorg-server package in Ubuntu: Incomplete Bug description: When I connect my LG OLED B9 TV to my computer, black bars appear at the top and bottom. The desktop won't scale to the full screen. Here's some basic info: Ubuntu 19.10 AMD 560 graphics card LG OLED B9 TV I tried changing the display settings, but the black bars won't go away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1867304/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1867416] [NEW] /usr/bin/gnome-shell:11:wl_resource_get_version:data_offer_choose_action:data_offer_update_action:create_and_send_dnd_offer:meta_wayland_drag_grab_set_focus
*** This bug is a duplicate of bug 1866368 *** https://bugs.launchpad.net/bugs/1866368 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.35.91-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1867416 Title: /usr/bin/gnome- shell:11:wl_resource_get_version:data_offer_choose_action:data_offer_update_action:create_and_send_dnd_offer:meta_wayland_drag_grab_set_focus Status in gnome-shell package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.35.91-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/d34d7337a4c810ce28fed5c01b0caf7ac53f8b8c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1867416/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856884] Re: When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand.
Thanks. Please also ensure the bug title and description describes the problem you are facing. And to log a new separate bug for each different problem. ** Summary changed: - not proper sound device + When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1856884 Title: When I insert or take out my headphones the system doesn't send signal on my headphones, I need to switch by hand. Status in pulseaudio package in Ubuntu: New Bug description: when i insert or take out my headphones , the system doesn't send signal on my headphones, i need to switch by hand. it worked in ubuntu 18.10 correct. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rob1929 F pulseaudio /dev/snd/controlC1: rob1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (326 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (43 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-01-26 (411 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:13.0-1ubuntu1.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Tags: eoan Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-05 (128 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856516] Re: Excessive memory usage by gnome-shell in 19.10
Anyone other than Chris please be sure to log your own bugs about memory usage. Don't subscribe to this bug as it is incomplete and intended to be just about whatever issue Chris is facing. ** Bug watch removed: gitlab.gnome.org/GNOME/gjs/issues #52 https://gitlab.gnome.org/GNOME/gjs/issues/52 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1856516 Title: Excessive memory usage by gnome-shell in 19.10 Status in gnome-shell package in Ubuntu: Incomplete Bug description: The gnome-shell process on my system is currently at 5473M VIRT 1224M RSS 566M SHR; this seems a bit excessive. This session has been up for >4 days with a number of suspend/resume cycles in there, so this might be a slow leak? ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic 5.3.10 Uname: Linux 5.3.0+bcachefs.git20191120.71cdaa7a-1-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 16 16:50:10 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2019-08-29 (109 days ago) InstallationMedia: Ubuntu 19.10 bcachefs (20190828) ProcEnviron: LANG=en_AU.UTF-8 LANGUAGE=en_AU:en PATH=(custom, user) SHELL=/usr/bin/fish XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1856516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1525628] Re: tracker needs to be killed on every boot
To update: Per the Gnome team this is finally fixed in version 2.3.2, https://gitlab.gnome.org/GNOME/tracker/issues/95 I cannot verify as as this version is not avialable for any current version of Ubuntu, including Focal. Please update the tracker version in supported channels. ** Bug watch added: gitlab.gnome.org/GNOME/tracker/issues #95 https://gitlab.gnome.org/GNOME/tracker/issues/95 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1525628 Title: tracker needs to be killed on every boot Status in tracker package in Ubuntu: Confirmed Bug description: At every boot, tacker-miner-fs and tracker-extract uses all of the processor and needs to be killed manually for computer to work. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: tracker 1.6.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.3.0-2.11-generic 4.3.0 Uname: Linux 4.3.0-2-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Dec 13 13:02:58 2015 InstallationDate: Installed on 2015-04-24 (232 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: tracker UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1525628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1866681] Re: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+)
So, I ran `uname -or` on my Ubuntu 18.04, which gave: `5.3.0-40-generic GNU/Linux` I find this strange because it doesn't do it on this edition. The problem is definitely somehow connected to the Ubuntu/Debian layer on top of the kernel, and not the actual kernel itself. I'm certain of this now. -- 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/1866681 Title: [HP Pavilion dv9000] Mute toggles on/off while plugged into the headphone/speaker jack (19.04+) Status in alsa-driver package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: I'm on an HP Pavilion dv9000 (https://www.cnet.com/products/hp- pavilion-dv9000/specs/) built many years ago. Whenever I'm using any distro that's based on Ubuntu which was published from Version 19.04 onwards, I've been having a major issue with the mute button toggling on and off whenever I have something plugged into the audio out jack. I know that it's not the fault of XFCE, because I also use the latest version of Manjaro with XFCE on this same computer, and it works fine. I also know it's not any Red Hat-based distro, because I use Stella (which is a remix of CentOS 6) also on this exact same computer, and it also works fine. Qubes, Mageia, and Fedora 31 also work perfectly fine and don't have this issue. My "lsb-release" is: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=19.10 DISTRIB_CODENAME=eoan DISTRIB_DESCRIPTION="Ubuntu 19.10" and "apt-cache policy pulseaudio" outputs: pulseaudio: Installed: 1:13.0-1ubuntu1.1 Candidate: 1:13.0-1ubuntu1.1 Version table: *** 1:13.0-1ubuntu1.1 500 500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:13.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages I've uploaded a short video of the problem that I recorded with my phone here: https://www.youtube.com/watch?v=GXaHXQA-5uQ The problem appears with Kali 2019 and 2020, Peppermint 19.04, Lubuntu 19.04, Xubuntu 19.04, and Sparky 5.10 and 2020.02. I've checked pretty much everything I can think of. There's a log for my ALSA help diagnostics results on my current computer (which works properly with 18.04) at: http://alsa-project.org/db/?f=4859b85cd7fc32e7f01f8df63591b5a43dbf6829 the result output of lspci is: [code]00:00.0 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.1 RAM memory: NVIDIA Corporation C51 Memory Controller 0 (rev a2) 00:00.2 RAM memory: NVIDIA Corporation C51 Memory Controller 1 (rev a2) 00:00.3 RAM memory: NVIDIA Corporation C51 Memory Controller 5 (rev a2) 00:00.4 RAM memory: NVIDIA Corporation C51 Memory Controller 4 (rev a2) 00:00.5 RAM memory: NVIDIA Corporation C51 Host Bridge (rev a2) 00:00.6 RAM memory: NVIDIA Corporation C51 Memory Controller 3 (rev a2) 00:00.7 RAM memory: NVIDIA Corporation C51 Memory Controller 2 (rev a2) 00:02.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:03.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:04.0 PCI bridge: NVIDIA Corporation C51 PCI Express Bridge (rev a1) 00:09.0 RAM memory: NVIDIA Corporation MCP51 Host Bridge (rev a2) 00:0a.0 ISA bridge: NVIDIA Corporation MCP51 LPC Bridge (rev a3) 00:0a.1 SMBus: NVIDIA Corporation MCP51 SMBus (rev a3) 00:0a.3 Co-processor: NVIDIA Corporation MCP51 PMU (rev a3) 00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3) 00:0d.0 IDE interface: NVIDIA Corporation MCP51 IDE (rev f1) 00:0e.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:0f.0 IDE interface: NVIDIA Corporation MCP51 Serial ATA Controller (rev f1) 00:10.0 PCI bridge: NVIDIA Corporation MCP51 PCI Bridge (rev a2) 00:10.1 Audio device: NVIDIA Corporation MCP51 High Definition Audio (rev a2) 00:14.0 Bridge: NVIDIA Corporation MCP51 Ethernet Controller (rev a3) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control 03:00.0 Network controller: Broadcom Inc. and subsidiaries BCM4311 802.11b/g WLAN (rev 01) 05:00.0 VGA compatible controller: NVIDIA Corporation G73M [GeForce Go 7600] (rev a1) 07:05.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller 07:05.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19) 07:05.2 System peripheral: Ricoh Co Ltd
