[Desktop-packages] [Bug 1914007] [NEW] RT3290 Bluetooth not finding any device
Public bug reported: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1043 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 68.194380] audit: type=1400 audit(1611909043.887:65): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1102 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 68.194710] audit: type=1400 audit(1611909043.887:66): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=1102 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 81.668783] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 81.668785] Bluetooth: BNEP filters: protocol multicast [ 81.668791] Bluetooth: BNEP socket layer initialized [ 1965.556683] Bluetooth: RTBT_Tb: vendor=0x1814, device=0x3298 [ 1965.556685] Bluetooth: RTBT_Tb: vendor=0x0, device=0x0 [ 1965.556687] Bluetooth: DynamicAlloc pci_device_id table at
[Desktop-packages] [Bug 1914004] Re: gnome crashes after suspend, lenovo thinkpad t14s, amd ryzen 7
Also, next time the crash happens please: 1. Wait 10 seconds and then reboot. 2. Open a Terminal window and run: journalctl -b-1 > prevboot.txt 3. Attach the resulting text file here. -- 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/1914004 Title: gnome crashes after suspend, lenovo thinkpad t14s, amd ryzen 7 Status in gnome-shell package in Ubuntu: Incomplete Bug description: System crashes after suspend, lenovo thinkpad t14s, amd ryzen 7 Pro. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 Uname: Linux 5.11.0-051100rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 08:48:17 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-27 (4 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913963] Re: [Cherry Trail] [modeset] Cursor flickering on dual screen setup
Please try: * Selecting 'Ubuntu on Wayland' on the login screen, instead of Xorg; or * An older kernel series like https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.4.94/ ** Summary changed: - Cursor flickering on dual screen setup + [Cherry Trail] [modeset] Cursor flickering on dual screen setup ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Tags added: multimonitor ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu) ** Changed in: linux-signed-hwe-5.8 (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Package changed: linux-signed-hwe-5.8 (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1913963 Title: [Cherry Trail] [modeset] Cursor flickering on dual screen setup Status in linux package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914004] Re: gnome crashes after suspend, lenovo thinkpad t14s, amd ryzen 7
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (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/1914004 Title: gnome crashes after suspend, lenovo thinkpad t14s, amd ryzen 7 Status in gnome-shell package in Ubuntu: Incomplete Bug description: System crashes after suspend, lenovo thinkpad t14s, amd ryzen 7 Pro. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 Uname: Linux 5.11.0-051100rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 08:48:17 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-27 (4 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913934] Re: Wrong current option in Screen resolution window
Fixed upstream, in libhandy (!?) ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1133 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1133 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1133 Importance: Unknown Status: Unknown ** Also affects: libhandy (Ubuntu) Importance: Undecided Status: New ** Changed in: libhandy (Ubuntu) Status: New => Fix Committed ** Changed in: gnome-control-center (Ubuntu) Status: New => Invalid ** Tags added: fixed-upstream ** Package changed: libhandy (Ubuntu) => libhandy-1 (Ubuntu) -- 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/1913934 Title: Wrong current option in Screen resolution window Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Invalid Status in libhandy-1 package in Ubuntu: Fix Committed Bug description: The checkmark is on the wrong option. Current resolution is 1920x1080, not 1600x1200 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 10:41:49 2021 ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1913934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902801]
You'll want to follow bug 1686055. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902801]
>From https://www.thunderbird.net/en-US/#channel - 86 beta1 will be out in a day or two. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902801]
On https://bugzilla.mozilla.org/show_bug.cgi?id=1686055 I read: " status-thunderbird86: --- → fixed" When and where do we get TB86? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902801]
Issue still exists on TB 78.7.0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902801] Re: Encrypted attachments cannot be opened or saved as decrypted files
** Bug watch added: Mozilla Bugzilla #1686055 https://bugzilla.mozilla.org/show_bug.cgi?id=1686055 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1902801 Title: Encrypted attachments cannot be opened or saved as decrypted files Status in thunderbird package in Ubuntu: Fix Released Status in Arch Linux: Fix Released Bug description: I have been using enigmail in thunderbird until I upgraded Ubuntu and with it thunderbird to the latest version 1:78.3.2+build1-0ubuntu1 As enigmail is now integrated in thunderbird, I have gone through the painful upgrade process (it does not allow to look into passwordmanager for the pasphrase of the gpg keys it wants to import by blocking all other windows), and decryption of emails now works. But when looking at a decrypted email, fully being able to read the text content, when I want to use the Menu option "Decrypt and Open" by right clicking on an attachment (pdf in this case), nothing happens. What I expect to happen: The pdf file being shown to me in the pdf viewer. Or some error being displayed, or maybe I am asked for my gpg passphrase again for additional security. When trying the option "Decrypt and save as", next I can select a folder and filename, (the pdf name without .gpg) and chose "save" - but when looking into that folder, there is no decrypted file. (I tried this plenty of time, I am sure its not there, and I did this action before the upgrade many times successfully). What I would expect: the attached file without the .gpg suffix (the filename proposed when opening the dialog, which I did not change) in the selected directory. $ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.3.2+build1-0ubuntu1 Candidate: 1:78.3.2+build1-0ubuntu1 Version table: *** 1:78.3.2+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1902801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913947] Re: [CMT-SBT20, playback] Underruns, dropouts or crackling sound
Thanks for the bug report. It looks like you are using Bluetooth audio and also experiencing lots of kernel crashes in the rtw88_core module. Just in case the kernel crashes are not related, please check that you don't still have the Settings window open as that can cause some audio quality problems. Next, please try disabling wifi. Because 2.4GHz wifi networks can directly interfere with Bluetooth signal quality. Please also run: lspci > lspci.txt lsusb > lsusb.txt and attach the resulting text files here. ** Summary changed: - [CMT-SBT20, playback] Underruns, dropouts or crackling sound + Bluetooth audio underruns, dropouts or crackling sound ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete ** Tags added: a2dp ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- 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/1913947 Title: Bluetooth audio underruns, dropouts or crackling sound Status in linux package in Ubuntu: Incomplete Bug description: The audio isn't in sync with video (ex. with youtube). Sometimes the audio is missing ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: simone 2131 F pulseaudio /dev/snd/controlC0: simone 2131 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 15:56:52 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: CMT-SBT20 Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [CMT-SBT20, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DK.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DK.305:bd07/16/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DK_X512DK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DK_X512DK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1913947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913920] Re: 4k Panel issues
Thanks for the bug report. It appears you have GNOME's old integer scaling enabled at 200%, but not fractional scaling. Only enabling fractional scaling OR logging into 'Ubuntu on Wayland' will force scaling on apps that don't fully support it. So there does not appear to be any bug here. If you want more apps to scale then try logging into 'Ubuntu on Wayland' (option on the login screen) or enabling 'Fractional Scaling' in Settings. If neither of those are enough then you will need to report individual bugs against each application asking them to support scaling. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Invalid -- 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/1913920 Title: 4k Panel issues Status in Ubuntu: Invalid Bug description: Hello, I'm having a lot of problems with many apps, such as Spotify, Gimp, Kdenlive, Octave, Scilab, Matlab ... etc ... The problem is: All apps runs perfectly, but they aren't at 4k 200%, they are only 4K 100%, the mouse are very very tiny and all text in the apps are like it meant to be on a 4k screen with 100% scalling. Is a bug that belongs to ubuntu for about 2/3 years and never had a resolve update! All my intel graphics drivers are up to date and my system to! Please fix this bug, it's very annoying! Thank you very much for your work! Muito, muito obrigado do fundo do <3 Best Regards, Eduardo Barbosa eduardo.cm...@gmail.com ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 02:25:04 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Iris Plus Graphics G7 [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Iris Plus Graphics G7 [1028:096d] MachineType: Dell Inc. XPS 13 9300 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=fe8fc9b4-c320-4e0d-ad81-bb5c7f30cbd4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/23/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.1 dmi.board.name: 077Y9N dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.1:bd11/23/2020:br1.4:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn077Y9N:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1913920/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913859] Re: RT3290 Bluetooth not finding any device
Thanks for the bug report. Indeed if you installed the driver yourself then we can't support it via an Ubuntu task, so that makes it 'Invalid'. But it looks like Ubuntu 20.04.1 does have the 'rt2800pci' driver built-in if you install its latest 5.8 kernel. Please try that via: sudo apt update sudo apt install linux-generic-hwe-20.04 Reboot. Then if you still have any issues, please open a new bug by running: ubuntu-bug bluez ** No longer affects: ubuntu ** Tags added: focal ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1913859 Title: RT3290 Bluetooth not finding any device Status in bluez package in Ubuntu: Invalid Bug description: Ubuntu :- 20.04 Hello I have RT3290 bluetooth in built and it was not working so I installed its latest driver from github whose version is 3.9.6 . Now its working but its not discoverable to any other device and also not finding any other device. Outout of command :- service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor pre> Active: active (running) since Sat 2021-01-30 09:49:10 IST; 1h 0min ago Docs: man:bluetoothd(8) Main PID: 1389 (bluetoothd) Status: "Running" Tasks: 1 (limit: 4514) Memory: 2.0M CGroup: /system.slice/bluetooth.service └─1389 /usr/lib/bluetooth/bluetoothd Jan 30 09:49:07 Piyush-X55C systemd[1]: Starting Bluetooth service... Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth daemon 5.53 Jan 30 09:49:10 Piyush-X55C systemd[1]: Started Bluetooth service. Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Starting SDP server Jan 30 09:49:10 Piyush-X55C bluetoothd[1389]: Bluetooth management interface 1.> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> Jan 30 10:49:34 Piyush-X55C bluetoothd[1389]: Endpoint registered: sender=:1.66> lines 1-18/18 (END) Output of command :- sudo btmgmt info Index list with 1 item hci0: Primary controller addr A4:17:31:1D:65:54 version 4 manufacturer 91 class 0x00 supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr debug-keys current settings: powered bondable ssp br/edr name Piyush-X55C Output of command :- bluetoothctl Agent registered [bluetooth]# scan on [bluetooth]# discoverable on [bluetooth]# scan on Failed to start discovery: org.bluez.Error.InProgress [bluetooth]# discoverable on Changing discoverable on succeeded [bluetooth]# Output of command :- sudo btmgmt find Unable to start discovery. status 0x0c (Not Supported) Output of command :- lspci -knn | grep Net -A3; lsusb 02:00.0 Network controller [0280]: Ralink corp. RT3290 Wireless 802.11n 1T/1R PCIe [1814:3290] Subsystem: Foxconn International, Inc. RT3290 Wireless 802.11n 1T/1R PCIe [105b:e055] Kernel driver in use: rt2800pci Kernel modules: rt2800pci Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:2883 Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of command :-dmesg | grep -i bluetooth [ 12.851854] Bluetooth: Core ver 2.22 [ 12.851883] Bluetooth: HCI device and connection manager initialized [ 12.851888] Bluetooth: HCI socket layer initialized [ 12.851889] Bluetooth: L2CAP socket layer initialized [ 12.851893] Bluetooth: SCO socket layer initialized [ 67.399550] audit: type=1400 audit(1611909043.091:58): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=875 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.727240] audit: type=1400 audit(1611909043.419:60): apparmor="DENIED" operation="connect" profile="snap.bluez.bluez" name="/run/dbus/system_bus_socket" pid=875 comm="bluetoothd" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0 [ 67.929889] audit: type=1400 audit(1611909043.619:62): apparmor="DENIED" operation="create" profile="snap.bluez.bluez" pid=1043 comm="bluetoothd" family="bluetooth" sock_type="raw" protocol=1 requested_mask="create" denied_mask="create" [ 67.930261] audit: type=1400 audit(1611909043.623:63): apparmor="DENIED"
[Desktop-packages] [Bug 1914004] [NEW] gnome crashes after suspend, lenovo thinkpad t14s, amd ryzen 7
Public bug reported: System crashes after suspend, lenovo thinkpad t14s, amd ryzen 7 Pro. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 Uname: Linux 5.11.0-051100rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 08:48:17 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-27 (4 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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 groovy third-party-packages -- 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/1914004 Title: gnome crashes after suspend, lenovo thinkpad t14s, amd ryzen 7 Status in gnome-shell package in Ubuntu: New Bug description: System crashes after suspend, lenovo thinkpad t14s, amd ryzen 7 Pro. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.2-1ubuntu1~20.10.1 Uname: Linux 5.11.0-051100rc5-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 1 08:48:17 2021 DisplayManager: gdm3 InstallationDate: Installed on 2021-01-27 (4 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1~20.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/1914004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913855] Re: Failure to pass system check and present login screen
It would be useful to find out why gdm3 works for you but lightdm does not. It might be because gdm3 defaults to Wayland not Xorg, or it might be a difference in the greeter/login screen itself. To find out, please try editing /etc/gdm3/custom.conf and change: #WaylandEnable=false to WaylandEnable=false then reboot. Does gdm3 still work now it's using Xorg? ** Tags added: radeon ** Summary changed: - Failure to pass system check and present login screen + [radeon] Failure to pass system check and present login screen ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (Ubuntu) Status: New => Incomplete ** Also affects: unity-greeter (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-greeter (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/1913855 Title: [radeon] Failure to pass system check and present login screen Status in lightdm package in Ubuntu: Incomplete Status in unity-greeter package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: I'm reporting this against xorg, because of where the problem occurs, as indicated below, I can't tell if the problem is with xorg, lightdm or light-locker. The system is a Dell Optiplex 745 single-booting to Xubuntu 20.04 up-to-date as of today. I replaced one of 2 monitors, the one rotated to portrait orientation, with a higher resolution monitor. Started the system, logged in as another user and changed the desktop background however, when I then logged out and restarted the system, it behaved normally until it displayed the usual /dev/sda1: clean, x/x files, /x blocks on both monitors. The prompt remained for a few seconds, slowly blinked off and on 6 times, and then remained with no further activity. The system works fine if I boot from a Xubuntu 18.04 DVD (I didn't have a 20.04 DVD, and this is the only machine with a burner). On another machine, I determined that the system was booting, because the machine was visible on the network, and its shared folders were accessible. I could get to a login prompt and log on using Alt+F1 to F6. Alt-F7 returned me to the file system check prompt. I was able to start xorg after logging on with startx, and changing all settings for the new monitor, everything worked normally until logging out, which of course returned me to the command line where I had given the command startx. If I log out requesting a restart, the system reboots, but still stops at the same place every time. That behavior hadn't changed the next day. I can use the machine, but only by selecting a terminal, logging as myself or the other user and giving the startx command. I have been unable to find anything on the Internet that corrects the problem. Since the problem first started, two crashes have occurred and I allowed them to be reported; however, they were light-locker crashes. I reinstalled lightdm and light-locker, but that made no difference. I installed gdm3, which works fine, but switching back to lightdm with: sudo dpkg-reconfigure gdm3 sudo dpkg --configure lightdm resulted in: dpkg: error processing package lightdm (--configure): package lightdm is already installed and configured Errors were encountered while processing: lightdm So I can't really be sure if the problem is with xorg, lightdm or light-locker, but since there are no error messages and everything else works fine, it's clearly a bug, if a strange one. I do not relish the idea of having to reinstall Xubuntu; so for the time being, I'll use gdm3, though I prefer lightdm's ability to properly display backdrops and use the two monitors properly extended (with gdm3, the mouse moves down the left portrait monitor before moving onto the right monitor where gdm3 sees fit to put the logon dialog). The next thing I'll try is autoremoving lightdm rebooting a few times and then reinstalling it... Because of the absence of error messages and information even suggesting why X isn't starting, I have no idea what other information about my system might be useful to you, but if you need something additional, I'll try to provide it. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Fri Jan 29 22:12:37 2021 DistUpgraded: 2020-10-20
[Desktop-packages] [Bug 1913742] Re: Fractional scaling: bottom half of screen black on external monitor disconnect
Thanks for the bug report. Please run: lspci -kv > lspci.txt journalctl -b0 > journal.txt xrandr --verbose > xrandrv.txt apport-collect 1913742 both before and after the problem occurs. And attach the resulting text files here. In future, to save time you can report bugs using the 'ubuntu-bug' command which will do much of this automatically. ** Tags added: focal multimonitor xrandr-scaling ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1913742 Title: Fractional scaling: bottom half of screen black on external monitor disconnect Status in mutter package in Ubuntu: Incomplete Bug description: I'm using Ubuntu 20.04.1, on a Lenovo Thinkpad T14s. I've got fractional scaling enabled (125%) with Gnome. I regularly plug into an external monitor with an HDMI connection, and run both screens (the external monitor and the built-in laptop one) side-by-side. With that setup, I don't use fractional scaling, because my main external monitor is easier to read. When I unplug the HDMI cord from my external monitor to go back to working on the laptop, sometimes the bottom half of the laptop screen goes black. The mouse cursor is still visible if I move it to that region, but nothing is visible in the entire lower portion of my screen. I've been running 20.04 on this laptop since last August, and it didn't used to be a problem. The problem first occurred perhaps a month or two ago, but was rare and sporadic. It has been happening more and more frequently, and is now at the point that most of the time this problem occurs. Once I have unplugged the cable and I'm stuck with a black bottom half of the screen, I can resolve it by disabling fractional scaling, but of course, that disables fractional scaling. At that point, any attempts to reenable fractional scaling either bring the black region back again, or start causing all kinds of other instabilities. Restarting Gnome at this point contributes to the mess. The only stable workaround I've found (apart from rebooting) is to plug the laptop back into the external monitor again, switch the configuration to single display mode, and then unplug. This works but is of course cumbersome. Is there more information I can supply that would be useful? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1913742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Tags added: originate-from-1910630 sutton -- 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/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1881923] Re: No icons in file picker
[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/1881923 Title: No icons in file picker Status in chromium-browser package in Ubuntu: Expired Bug description: I installed chromium via snap on Ubuntu 20.04. When the file picker is opend (for example to upload some files) all icons are missing. Files and folders have no icon (see attached screenshot). Ubuntu 20.04 LTS Chromium Version 83.0.4103.61 (Official Build) snap (64-bit) Maybe it is a problem with the apparmor-profile? [27780.715573] audit: type=1400 audit(1591194917.741:3258): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/etc/fstab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [27780.737385] audit: type=1400 audit(1591194917.761:3259): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [27781.003139] audit: type=1400 audit(1591194918.029:3260): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 [27781.012869] audit: type=1107 audit(1591194918.037:3261): pid=1073 uid=100 auid=4294967295 ses=4294967295 msg='apparmor="DENIED" operation="dbus_method_call" bus="system" path="/org/freedesktop/hostname1" interface="org.freedesktop.DBus.Properties" member="GetAll" mask="send" name=":1.285" pid=5553 label="snap.chromium.chromium" peer_pid=156208 peer_label="unconfined" exe="/usr/bin/dbus-daemon" sauid=100 hostname=? addr=? terminal=?' [27784.173782] audit: type=1400 audit(1591194921.197:3262): apparmor="DENIED" operation="open" profile="snap.chromium.chromium" name="/run/mount/utab" pid=5553 comm="chrome" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1881923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906326] Re: package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: installed xcursor-themes package post-installation script subprocess returned error exit status 2
[Expired for xcursor-themes (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xcursor-themes (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xcursor-themes in Ubuntu. https://bugs.launchpad.net/bugs/1906326 Title: package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: installed xcursor-themes package post-installation script subprocess returned error exit status 2 Status in xcursor-themes package in Ubuntu: Expired Bug description: none ProblemType: Package DistroRelease: Ubuntu 20.04 Package: xcursor-themes 1.0.6-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73 Uname: Linux 5.4.0-56-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:02: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 455.38 Thu Oct 22 06:06:59 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.13 AptOrdering: gdm3:amd64: Install ubuntu-desktop-minimal:amd64: Install ubuntu-desktop:amd64: Install xcursor-themes:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Mon Nov 30 17:47:16 2020 Dependencies: DistUpgraded: 2020-11-09 22:11:21,286 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 455.38, 5.4.0-54-generic, x86_64: installed nvidia, 455.38, 5.4.0-56-generic, x86_64: installed ErrorMessage: installed xcursor-themes package post-installation script subprocess returned error exit status 2 GraphicsCard: NVIDIA Corporation GK208B [GeForce GT 710] [10de:128b] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK208B [GeForce GT 710] [1462:8c93] InstallationDate: Installed on 2017-04-02 (1338 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 8087:0a2a Intel Corp. Bus 002 Device 002: ID 050d:705c Belkin Components F5D7050 Wireless G Adapter v4000 [Zydas ZD1211B] Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/10p, 12M |__ Port 1: Dev 2, If 0, Class=Vendor Specific Class, Driver=zd1211rw, 12M |__ Port 7: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 7: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/10p, 480M MachineType: System manufacturer System Product Name PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-56-generic root=UUID=2cde2844-40c1-4e06-85a5-9ee53a38864a ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: xcursor-themes Title: package xcursor-themes 1.0.6-0ubuntu1 failed to install/upgrade: installed xcursor-themes package post-installation script subprocess returned error exit status 2 UpgradeStatus: Upgraded to focal on 2020-11-10 (20 days ago) dmi.bios.date: 01/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4N68T-M-V2 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0702:bd01/26/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4N68T-M-V2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.X11.cursors.core.theme: [deleted]
[Desktop-packages] [Bug 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s
** 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/1913977 Title: Bad sound quality (no bass) on Thinkpad T490s Status in alsa-driver package in Ubuntu: New Bug description: Sound works on with 20.04 on the Thinkpad T490s, but sound quality is noticeably worse than on Windows. It looks like the same bug here: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmahmood 1360 F pulseaudio /dev/snd/pcmC0D0p: hmahmood 1360 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 19:14:57 2021 InstallationDate: Installed on 2021-01-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2020 dmi.bios.release: 1.70 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET92W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS83800 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.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS83800 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1913977/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913977] [NEW] Bad sound quality (no bass) on Thinkpad T490s
You have been subscribed to a public bug: Sound works on with 20.04 on the Thinkpad T490s, but sound quality is noticeably worse than on Windows. It looks like the same bug here: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hmahmood 1360 F pulseaudio /dev/snd/pcmC0D0p: hmahmood 1360 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 19:14:57 2021 InstallationDate: Installed on 2021-01-30 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2020 dmi.bios.release: 1.70 dmi.bios.vendor: LENOVO dmi.bios.version: N2JET92W (1.70 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NYS83800 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.ec.firmware.release: 1.20 dmi.modalias: dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T490s dmi.product.name: 20NYS83800 dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s dmi.product.version: ThinkPad T490s dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Bad sound quality (no bass) on Thinkpad T490s https://bugs.launchpad.net/bugs/1913977 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1813441 Title: Can no longer drag and drop files between desktop and applications Status in gnome-shell-extension-desktop-icons: New Status in gnome-shell-extension-desktop-icons package in Ubuntu: Incomplete Bug description: In releases before 19.04, you could drag and drop files from the desktop into applications. This no longer works. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-desktop-icons 19.01-1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 21:47:14 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) PackageArchitecture: all SourcePackage: gnome-shell-extension-desktop-icons UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1813441/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913217] Re: [nvidia] Screen going black and not responding to input
If the problem started in a kernel update then you might be able to solve it by going back to a 5.4 kernel like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4.94/ You wouldn't be the first to find graphics problems in kernel 5.8. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Package changed: linux (Ubuntu) => linux-signed-hwe-5.8 (Ubuntu) ** Tags added: 5.8-gfx -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1913217 Title: [nvidia] Screen going black and not responding to input Status in linux-signed-hwe-5.8 package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-340 package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expecting: (usually after opening a new application): window to open Happened instead: Screen going black. System not responding to inputs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.108 Wed Dec 11 11:06:58 PST 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 25 21:49:05 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.108, 5.4.0-42-generic, x86_64: installed nvidia-340, 340.108, 5.8.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Several times a day GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) NVIDIA Corporation GT216M [GeForce GT 330M] [10de:0a29] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. GT216M [GeForce GT 330M] [106b:00c7] InstallationDate: Installed on 2021-01-24 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Apple Inc. MacBookPro6,2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic root=UUID=22238608-1c5f-40aa-a8f4-1fded14f6b84 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 99.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22586C8 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro6,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22586C8 dmi.modalias: dmi:bvnAppleInc.:bvr99.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro6,2:pvr1.0:rvnAppleInc.:rnMac-F22586C8:rvrMacBookPro6,2:cvnAppleInc.:ct10:cvrMac-F22586C8: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro6,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.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications
[Desktop-packages] [Bug 1906163] Re: Ubuntu 20.04 screen freezes when unlocking gnome session
> it isn't a good design to allow the gnome extensions to wreck the whole desktop. Yes I think most people agree about that. But since it's the only design gnome-shell has, and nobody is about to rewrite it all, the only options are: * Support extensions that might break things; or * Don't support extensions. Being able to break things is also a good sign in a way, because it demonstrates that extension authors are truly free to do anything. They just have to be very careful about the quality of their code. -- 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/1906163 Title: Ubuntu 20.04 screen freezes when unlocking gnome session Status in gnome-shell package in Ubuntu: Expired Bug description: since 2 days, gnome freezes after trying to unlock the screen. It happened already 3 times. I have ubuntu installed since April. I did not add anything through the last 5 days. I have a script running once a day to update everything what's available. Envornment: $ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 $ uname -a Linux G-Hibrid 5.4.0-54-generic #60-Ubuntu SMP Fri Nov 6 10:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ apt show gnome-settings-daemon Package: gnome-settings-daemon Version: 3.36.1-0ubuntu1 Priority: extra Section: gnome Origin: Ubuntu The packages recently updated: $ cat /var/og/apt/history.log Start-Date: 2020-11-25 08:12:14 Commandline: apt upgrade -y Upgrade: ruby2.7:amd64 (2.7.0-5ubuntu1.1, 2.7.0-5ubuntu1.2), megasync:amd64 (4.3.7-1.1, 4.3.8-1.1), qemu-system-x86:amd64 (1:4.2-3ubuntu6.8, 1:4.2-3ubuntu6.9), ruby2.7-dev:amd64 (2.7.0-5ubuntu1.1, 2.7.0-5ubuntu1.2), ruby2.7-doc:amd64 (2.7.0-5ubuntu1.1, 2.7.0-5ubuntu1.2), apport:amd64 (2.20.11-0ubuntu27.12, 2.20.11-0ubuntu27.13), busybox-static:amd64 (1:1.30.1-4ubuntu6.2, 1:1.30.1-4ubuntu6.3), libruby2.7:amd64 (2.7.0-5ubuntu1.1, 2.7.0-5ubuntu1.2), python3-apport:amd64 (2.20.11-0ubuntu27.12, 2.20.11-0ubuntu27.13), qemu-system-data:amd64 (1:4.2-3ubuntu6.8, 1:4.2-3ubuntu6.9), qemu-utils:amd64 (1:4.2-3ubuntu6.8, 1:4.2-3ubuntu6.9), qemu-kvm:amd64 (1:4.2-3ubuntu6.8, 1:4.2-3ubuntu6.9), apport-gtk:amd64 (2.20.11-0ubuntu27.12, 2.20.11-0ubuntu27.13), qemu-block-extra:amd64 (1:4.2-3ubuntu6.8, 1:4.2-3ubuntu6.9), python3-problem-report:amd64 (2.20.11-0ubuntu27.12, 2.20.11-0ubuntu27.13), qemu-system-common:amd64 (1:4.2-3ubuntu6.8, 1:4.2-3ubuntu6.9), qemu-system-gui:amd64 (1:4.2-3ubuntu6.8, 1:4.2-3ubuntu6.9), busybox-initramfs:amd64 (1:1.30.1-4ubuntu6.2, 1:1.30.1-4ubuntu6.3) End-Date: 2020-11-25 08:13:02 Start-Date: 2020-11-26 17:00:10 Commandline: apt upgrade -y Upgrade: xdg-utils:amd64 (1.1.3-2ubuntu1, 1.1.3-2ubuntu1.20.04.1), python3-distupgrade:amd64 (1:20.04.28, 1:20.04.29), ubuntu-release-upgrader-core:amd64 (1:20.04.28, 1:20.04.29), libwebkit2gtk-4.0-37:amd64 (2.28.4-0ubuntu0.20.04.1, 2.30.3-0ubuntu0.20.04.1), ubuntu-release-upgrader-gtk:amd64 (1:20.04.28, 1:20.04.29), gir1.2-webkit2-4.0:amd64 (2.28.4-0ubuntu0.20.04.1, 2.30.3-0ubuntu0.20.04.1), libjavascriptcoregtk-4.0-18:amd64 (2.28.4-0ubuntu0.20.04.1, 2.30.3-0ubuntu0.20.04.1), gir1.2-javascriptcoregtk-4.0:amd64 (2.28.4-0ubuntu0.20.04.1, 2.30.3-0ubuntu0.20.04.1) End-Date: 2020-11-26 17:00:16 one package is recently being kept back: The following packages have been kept back: libodbc1 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. The logs from today afternoon: $ sudo journalctl -S "2020-11-29 12:30:00" --no-pager -f Nov 29 12:37:30 hostname kernel: [UFW BLOCK] IN=eno1 OUT= MAC=30:85:a9:98:e9:99:80:7d:14:37:ff:a2:86:dd SRC=fe80::::827d:14ff:fe37:ffa2 DST=fd52:a81c:df85:0001:bc62:9628:e388:a759 LEN=264 TC=0 HOPLIMIT=255 FLOWLBL=0 PROTO=ICMPv6 TYPE=137 CODE=0 Nov 29 12:37:33 hostname kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:01:80:7d:14:37:ff:a2:08:00 SRC=192.168.1.1 DST=224.0.0.1 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Nov 29 12:37:40 hostname kernel: [UFW BLOCK] IN=eno1 OUT= MAC=01:00:5e:00:00:fb:b8:27:eb:e6:74:43:08:00 SRC=192.168.1.100 DST=224.0.0.251 LEN=32 TOS=0x00 PREC=0xC0 TTL=1 ID=0 DF PROTO=2 Nov 29 12:37:46 hostname /usr/lib/gdm3/gdm-x-session[2668]: (--) NVIDIA(GPU-0): ROW AAA (DFP-1): connected Nov 29 12:37:46 hostname /usr/lib/gdm3/gdm-x-session[2668]: (--) NVIDIA(GPU-0): ROW AAA (DFP-1): Internal TMDS Nov 29 12:37:46 hostname /usr/lib/gdm3/gdm-x-session[2668]: (--) NVIDIA(GPU-0): ROW AAA (DFP-1): 340.0 MHz maximum pixel clock Nov 29 12:37:46 hostname /usr/lib/gdm3/gdm-x-session[2668]: (--) NVIDIA(GPU-0): Nov 29 12:37:46 hostname /usr/lib/gdm3/gdm-x-session[2668]: (--) NVIDIA(GPU-0): ROW AAA (DFP-1): connected Nov 29 12:37:46 hostname /usr/lib/gdm3/gdm-x-session[2668]: (--) NVIDIA(GPU-0): ROW AAA (DFP-1): Internal TMDS
[Desktop-packages] [Bug 1913411] Re: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu.
If you need any further info then please ask the developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues -- 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/1913411 Title: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. Status in gnome-shell package in Ubuntu: Invalid Status in modemmanager package in Ubuntu: Invalid Bug description: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu. I just can see mobile broadband in network in system settings menu. OS: ubuntu20.04 Module: SDX55 ModemManager:1.14.2 iusse: 1.No mobile broadband in system status bar drop-down menu. 2.Every time I connect to the mobile broadband network in system settings menu, I need to add new connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913411/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
Alex, This bug is closed. You may find bug 1813441 relevant, or if you have a different concern then please open a new bug by running: ubuntu-bug gnome-shell-extension-desktop-icons -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Fix Released Status in gnome-shell-extension-desktop-icons source package in Groovy: Fix Released Status in gnome-shell-extension-desktop-icons source package in Hirsute: Fix Released Bug description: [Impact] Drag and drop files from Desktop to Nautilus freezes gnome-shell in Ubuntu 20.10. There is no way to recover without killing gnome-shell externally or rebooting. [Test Case] 1. Create a file in ~/Desktop 2. Open a nautilus (Files) window of a different directory. 3. Drag the new file from the desktop into the nautilus (Files) window. The shell should not become unresponsive. Also, the drag is expected to fail and snap back. That's a different issue (bug 1813441) not being fixed here. [Where problems could occur] An extension with syntax errors may fail to load leaving the user with reduced shell functionality. A more faulty extension might crash the entire shell after loading. [Other Info] Patch is in bug 1898005. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 12:19:26 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-03 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.0-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-10-03T01:41:41.633547 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890613] Re: Gnome unresponsive JS ERROR: TypeError: windowActor is null
See also bug 1880405 -- 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/1890613 Title: Gnome unresponsive JS ERROR: TypeError: windowActor is null Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: gnome-shell becomes unresponsive after about 1 day. I'm able to interact with the window that had focus when the problem appears (in this case it was Chrome), but I'm unable to select or otherwise interact with other windows, the shell, dock, or indicators. The logs are spammed with gnome-shell[2916]: JS ERROR: TypeError: windowActor is null#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 This looks similar to but different enough from https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1841774 I was using the i915 driver when this happened if that makes any difference ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 6 09:08:32 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-06-12 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200609) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1890613/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911921] Re: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-3.38.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1911921 Title: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) Status in GNOME Shell: Unknown Status in gnome-shell-extensions package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 --- As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1911921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913979] [NEW] settings plugin does not support adding connections
Public bug reported: As of a couple of days ago, I am unable to get network manager to connect to any wifi network. It looks like the groovy network manager packages have not received any updates since release, but since I can successfully use wpasupplicant directly I'm ruling out issues with my specific home wifi or wifi card. Though this might still ultimately be due to my specific setup, the error message logged by network manager is really insufficient for determining where the failure may lie, even when debug mode is turned on[0]. The Gnome UI doesn't display an error at all. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * no UI popup is produced when using the Gnome UI * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui * debug logs include slightly more information: Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: check-master-ready: not signalling (state deactivated, no master) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] device[fd0e531202f8924b] (wlp61s0): remove_pending_action (0): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8811] audit: op="connection-add-activate" pid=452187 uid=1000 result="fail" reason="failure adding connection: settings plugin does not support adding connections" Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8812] active-connection[0x55b6b9a25b50]: disposing Workaround: * connect to networks by using wpasupplicant directly[1] [0] https://wiki.gnome.org/Projects/NetworkManager/Debugging [1] https://shapeshed.com/linux-wifi/ ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1913979 Title: settings plugin does not support adding connections Status in network-manager package in Ubuntu: New Bug description: As of a couple of days ago, I am unable to get network manager to connect to any wifi network. It looks like the groovy network manager packages have not received any updates since release, but since I can successfully use wpasupplicant directly I'm ruling out issues with my specific home wifi or wifi card. Though this might still ultimately be due to my specific setup, the error message logged by network manager is really insufficient for determining where the failure may lie, even when debug mode is turned on[0]. The Gnome UI doesn't display an error at all. Versions: Ubuntu 20.10 network-manager 1.26.2-1ubuntu1 network-manager-gnome 1.18.0-1ubuntu2 How to reproduce: * select any wifi network via the Gnome UI, or * connect to a wifi network via nmcli, or * connect to a wifi network via nmtui Symptoms: * no UI popup is produced when using the Gnome UI * the message "failure adding connection: settings plugin does not support adding connections" is shown when using nmcli or nmtui * debug logs include slightly more information: Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8651] active-connection[0x55b6b9a25b50]: set device "wlp61s0" [0x55b6b9b62cb0] Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8652] device[fd0e531202f8924b] (wlp61s0): add_pending_action (1): 'activation-22' Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8653] active-connection[0x55b6b9a25b50]: constructed (NMActRequest, version-id 22, type managed) Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8807] active-connection[0x55b6b9a25b50]: Failed to activate '(null)': failure adding connection: settings plugin does not support adding connections Jan 31 20:32:57 laptop NetworkManager[3315]: [1612143177.8808] active-connection[0x55b6b9a25b50]: set state deactivated (was unknown) Jan 31 20:32:57 laptop
[Desktop-packages] [Bug 1913968] [NEW] [MacBookPro14, 1, Cirrus Logic Generic, Speaker, Internal] No sound at all
Public bug reported: New install of 20.04.1 on 1/31/2021 onto MacBookPro The "startup tone" plays when I start or re-start my computer. When I enter my password and login to my computer I expect to go to the audio settings, test the sound, and have the sound test work. I expect to hear media played back through my web browser. I expect to hear sound from my headphones or internal speakers. The actual behavior is that I am unable to hear sounds from my internal speakers or through headphones. Steps to troubleshoot (all cmd line steps performed as root): - checked sound not muted, system settings set correctly via cmd line - performed sound test with headphones and external speakers. - uninstall/reinstall/reload alsa - apt-get remove timidity - add snd-hda-intel.dmic_detect=0 setting to boot config I tried these steps using various tutorials from users having similar problems, and performed restarts after install/uninstall, reload of software, or config change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jess 1289 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 16:03:32 2021 InstallationDate: Installed on 2021-01-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jess 1289 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [MacBookPro14,1, Cirrus Logic Generic, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/03/2020 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 429.60.3.0.0 dmi.board.name: Mac-B4831CEBD52A0C4C dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro14,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-B4831CEBD52A0C4C dmi.modalias: dmi:bvnAppleInc.:bvr429.60.3.0.0:bd11/03/2020:br0.1:svnAppleInc.:pnMacBookPro14,1:pvr1.0:rvnAppleInc.:rnMac-B4831CEBD52A0C4C:rvrMacBookPro14,1:cvnAppleInc.:ct9:cvrMac-B4831CEBD52A0C4C: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro14,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** 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/1913968 Title: [MacBookPro14,1, Cirrus Logic Generic, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: New install of 20.04.1 on 1/31/2021 onto MacBookPro The "startup tone" plays when I start or re-start my computer. When I enter my password and login to my computer I expect to go to the audio settings, test the sound, and have the sound test work. I expect to hear media played back through my web browser. I expect to hear sound from my headphones or internal speakers. The actual behavior is that I am unable to hear sounds from my internal speakers or through headphones. Steps to troubleshoot (all cmd line steps performed as root): - checked sound not muted, system settings set correctly via cmd line - performed sound test with headphones and external speakers. - uninstall/reinstall/reload alsa - apt-get remove timidity - add snd-hda-intel.dmic_detect=0 setting to boot config I tried these steps using various tutorials from users having similar problems, and performed restarts after install/uninstall, reload of software, or config change. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jess 1289 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 16:03:32 2021 InstallationDate: Installed on 2021-01-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver
[Desktop-packages] [Bug 784055] Re: CPU usage increases dramatically (and visible stuttering) when running indicator-multiload
This is still an issue in a clean install, default config ubuntu 20.04 with all updates and indicator-multiload from the repo also in its absolute default config. This makes it basically impossible to use multiload with 20.04 right now. -- 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/784055 Title: CPU usage increases dramatically (and visible stuttering) 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 1913925] Re: gnome-control-center (Settings) Security is missing
Sorry, but I don't understand. If you found an issue, whether it affects security or not, please submit a bug describing that issue - just like you did with this one. What am I missing? -- 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/1913925 Title: gnome-control-center (Settings) Security is missing Status in gnome-control-center package in Ubuntu: Incomplete Bug description: For bug reporting in settings "security" supposed to be there but it is not found. I have reinstalled gnome control-center there is no change. In fact after brousing net some one suggested to remove and reinstall the package. I have removed the package but could not install. Finally I have reinstalled Ubuntu OS, but the problem remained same. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 10:12:43 2021 InstallationDate: Installed on 2021-01-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913963] [NEW] Cursor flickering on dual screen setup
Public bug reported: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210115) MachineType: BESSTAR (HK) LIMITED Z83-F ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-36-generic root=UUID=7152a6d1-67f7-4ca6-b813-98fa5685a28b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed with exit code 126: Error executing command as another user: Request dismissed dmi.bios.date: 08/13/2019 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: BLT-BI-MINIPC-X5R110-CC55B-BU-101-A dmi.board.asset.tag: Default string dmi.board.name: T3 MRD dmi.board.vendor: BESSTAR Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrBLT-BI-MINIPC-X5R110-CC55B-BU-101-A:bd08/13/2019:br5.11:svnBESSTAR(HK)LIMITED:pnZ83-F:pvrDefaultstring:rvnBESSTARTech:rnT3MRD:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z83-F dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: BESSTAR (HK) LIMITED version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.3.2-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug has-workaround hirsute reproducible ubuntu ** Attachment added: "VID_20210131_195227.mp4" https://bugs.launchpad.net/bugs/1913963/+attachment/5458573/+files/VID_20210131_195227.mp4 -- 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/1913963 Title: Cursor flickering on dual screen setup Status in xorg package in Ubuntu: New Bug description: When running on dual screen config, the cursor is heavily flickering. Makes it a very unpleasant experience, if not renders it unusable. If switched to only single screen, cursor is completely stable. When issuing xrandr --output HDMI-2 --scale 0.99x0.99 again cursor is stable. Switching to 200% scaling in the desktop settings, doesn't help. I tried to catch the effect in a movie. However, because of frame rate, it is not possible to show the effect. If if its helpful, let me know and I'll try harder. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu56 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: Budgie:GNOME Date: Sun Jan 31 19:55:12 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36)
[Desktop-packages] [Bug 844582] Re: "Invalid argument" when trying to scan
Hello,
I have the same problem:
gscan2pdf: sane_start: Invalid argument
I run from the command line with the "--log=log" option and create the log.xz
file that I attach.
My system is:
* Kubuntu 20.10 (Ubuntu + KDE)
* Scanner: Brother DCP-J562DW
I've been able to use this scanner in al ubuntu versions (I'm long linux user
and gscan2pdf too), but I'm not sure if I've used with the previous 20.04
version (I think that yes).
I have another PC with Windows 10 and the scanner works. So is something
with my system not with the device.
** Attachment added: "Log for gscan2pdf"
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+attachment/5458553/+files/log.xz
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to sane-backends in Ubuntu.
https://bugs.launchpad.net/bugs/844582
Title:
"Invalid argument" when trying to scan
Status in gscan2pdf package in Ubuntu:
Invalid
Status in sane-backends package in Ubuntu:
Opinion
Bug description:
I'm using a Fujitsu M3091DCd scanner with SANE. From the command line
it works more or less well with Ubuntu.
I can't use it with gscan2pdf v0.9.31, but gscan2pdf works with
another scanner.
All I get is a meaningless "Invalid argument" when I hit the scan
button.
When I start gscan2pdf from the command line I see these lines
appearing when I hit the scan button:
Error running process: Died at (eval 39) line 7.
$device->start;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
if ($Sane::STATUS != SANE_STATUS_GOOD) {
print "$prog_name: sane_start: $Sane::STATUS\n" if $debug;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
my $path = $shash{$sane_thread}{data};
if (not open($fh, ">", $path)) {
$device->cancel;
$shash{$sane_thread}{status} = SANE_STATUS_ACCESS_DENIED;
$shash{$sane_thread}{go} = 0;
die; # quickest way out of the eval block
}
scan_page($device, $fh);
$shash{$sane_thread}{status} = $Sane::STATUS+0;
close $fh;
printf "Scanned page %s.", $path if $debug;
printf " (scanner status = %d)\n", $Sane::STATUS if $debug;
$shash{$sane_thread}{status} = $Sane::STATUS+0;
$shash{$sane_thread}{go} = 0;
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: gscan2pdf 0.9.31-2
ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Thu Sep 8 09:44:25 2011
PackageArchitecture: all
ProcEnviron:
LANGUAGE=
PATH=(custom, no username)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: gscan2pdf
UpgradeStatus: Upgraded to natty on 2011-06-01 (98 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/844582/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910856] Re: Ubuntu 20.04.1 - network-manager instable with Centrino Advanced-N 6235 wifi
I think I'm having the exact same problem. My oldish dell xps 13 with this network controller has worked fine since ubuntu 12.04, but since installing 20.04, wifi keeps dropping out, bringing up an authentication dialog. Since the dialogue already has my credentials filled in, I would already be happy if it would reconnect without bothering me. -- 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/1910856 Title: Ubuntu 20.04.1 - network-manager instable with Centrino Advanced-N 6235 wifi Status in network-manager package in Ubuntu: New Bug description: Hello, I am facing an intermittent problem after upgrading to 20.04. I keep loosing the wifi connection and requested to put the wifi password again. I troubleshut the problem on forum.ubuntu-it.org (https://forum.ubuntu-it.org/viewtopic.php?f=9=643817=20=3100928dda5ea320e82d5db653e95611) but we could not figure it out. I am reporting here the same information provided to the forum and I am available to provide more. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 14:57:23 2021 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-12-18 (2213 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev wlan1 proto dhcp metric 600 169.254.0.0/16 dev wlan1 scope link metric 1000 192.168.1.0/24 dev wlan1 proto kernel scope link src 192.168.1.179 metric 600 SourcePackage: network-manager UpgradeStatus: Upgraded to focal on 2020-10-31 (70 days ago) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2019-01-14T23:22:39.355283 nmcli-dev: DEVICE TYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH wlan1 wifi connectedfull none /org/freedesktop/NetworkManager/Devices/3 TIM-18679861 817f1693-1daa-4c3e-b81f-46d576414c34 /org/freedesktop/NetworkManager/ActiveConnection/1 eth0ethernet unavailable none none /org/freedesktop/NetworkManager/Devices/2 ---- -- lo loopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1910856/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913947] [NEW] [CMT-SBT20, playback] Underruns, dropouts or crackling sound
Public bug reported: The audio isn't in sync with video (ex. with youtube). Sometimes the audio is missing ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: simone 2131 F pulseaudio /dev/snd/controlC0: simone 2131 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 15:56:52 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: CMT-SBT20 Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [CMT-SBT20, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DK.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DK.305:bd07/16/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DK_X512DK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DK_X512DK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1913947 Title: [CMT-SBT20, playback] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: New Bug description: The audio isn't in sync with video (ex. with youtube). Sometimes the audio is missing ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: simone 2131 F pulseaudio /dev/snd/controlC0: simone 2131 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 15:56:52 2021 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: CMT-SBT20 Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [CMT-SBT20, playback] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DK.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DK.305:bd07/16/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DK_X512DK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DK_X512DK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1913947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913940] Re: Wifi keeps disconnecting and reconnecting all the time
** Attachment added: "journalctl log" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+attachment/5458502/+files/journalctl_ubuntu -- 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/1913940 Title: Wifi keeps disconnecting and reconnecting all the time Status in wpa package in Ubuntu: New Bug description: I have a problem with WIFI not being stable, and disconnecting -> reconnecting, all the time (I have PC next to the router). It happens like every 10 seconds average (one time it happened twice in a row, and another time I got 30 seconds without disconnect). Specs: OS: Ubuntu 20.04.1 LTS (On 20.10 same issue) Wifi card: Qualcomm Atheros AR93xx Wireless Network Adapter (ath9k) Motherboard: MSI X470 Gaming Plus Max CPU: AMD Ryzen 5 3600 wpasupplicant: 2:2.9-1ubuntu4.1 I've tried so far: disabling IPV6, disabling powersave mode, creating ath9k.conf and adding parameters, setting manually BSSID and MAC adress, installing backport-iwlwifi-dkms, installing firmware-ath9k- htc, using 2,4G network. What I expect: Wifi network stable without single drop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-extra-440_440.100-0ubuntu0.20.04.1_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 12:09:00 2021 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913940] Re: Wifi keeps disconnecting and reconnecting all the time
** Attachment added: "dmesg log" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+attachment/5458503/+files/dmesg_ubuntu -- 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/1913940 Title: Wifi keeps disconnecting and reconnecting all the time Status in wpa package in Ubuntu: New Bug description: I have a problem with WIFI not being stable, and disconnecting -> reconnecting, all the time (I have PC next to the router). It happens like every 10 seconds average (one time it happened twice in a row, and another time I got 30 seconds without disconnect). Specs: OS: Ubuntu 20.04.1 LTS (On 20.10 same issue) Wifi card: Qualcomm Atheros AR93xx Wireless Network Adapter (ath9k) Motherboard: MSI X470 Gaming Plus Max CPU: AMD Ryzen 5 3600 wpasupplicant: 2:2.9-1ubuntu4.1 I've tried so far: disabling IPV6, disabling powersave mode, creating ath9k.conf and adding parameters, setting manually BSSID and MAC adress, installing backport-iwlwifi-dkms, installing firmware-ath9k- htc, using 2,4G network. What I expect: Wifi network stable without single drop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-extra-440_440.100-0ubuntu0.20.04.1_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 12:09:00 2021 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913940] [NEW] Wifi keeps disconnecting and reconnecting all the time
Public bug reported: I have a problem with WIFI not being stable, and disconnecting -> reconnecting, all the time (I have PC next to the router). It happens like every 10 seconds average (one time it happened twice in a row, and another time I got 30 seconds without disconnect). Specs: OS: Ubuntu 20.04.1 LTS (On 20.10 same issue) Wifi card: Qualcomm Atheros AR93xx Wireless Network Adapter (ath9k) Motherboard: MSI X470 Gaming Plus Max CPU: AMD Ryzen 5 3600 wpasupplicant: 2:2.9-1ubuntu4.1 I've tried so far: disabling IPV6, disabling powersave mode, creating ath9k.conf and adding parameters, setting manually BSSID and MAC adress, installing backport-iwlwifi-dkms, installing firmware-ath9k-htc, using 2,4G network. What I expect: Wifi network stable without single drop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-extra-440_440.100-0ubuntu0.20.04.1_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 12:09:00 2021 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (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 wpa in Ubuntu. https://bugs.launchpad.net/bugs/1913940 Title: Wifi keeps disconnecting and reconnecting all the time Status in wpa package in Ubuntu: New Bug description: I have a problem with WIFI not being stable, and disconnecting -> reconnecting, all the time (I have PC next to the router). It happens like every 10 seconds average (one time it happened twice in a row, and another time I got 30 seconds without disconnect). Specs: OS: Ubuntu 20.04.1 LTS (On 20.10 same issue) Wifi card: Qualcomm Atheros AR93xx Wireless Network Adapter (ath9k) Motherboard: MSI X470 Gaming Plus Max CPU: AMD Ryzen 5 3600 wpasupplicant: 2:2.9-1ubuntu4.1 I've tried so far: disabling IPV6, disabling powersave mode, creating ath9k.conf and adding parameters, setting manually BSSID and MAC adress, installing backport-iwlwifi-dkms, installing firmware-ath9k- htc, using 2,4G network. What I expect: Wifi network stable without single drop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: wpasupplicant 2:2.9-1ubuntu4.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-440/libnvidia-extra-440_440.100-0ubuntu0.20.04.1_amd64.deb CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 12:09:00 2021 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1913940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913934] Re: Wrong current option in Screen resolution window
** Attachment added: "ubuntu_bug_report_2021-01-31_10-44.png" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913934/+attachment/5458488/+files/ubuntu_bug_report_2021-01-31_10-44.png -- 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/1913934 Title: Wrong current option in Screen resolution window Status in gnome-control-center package in Ubuntu: New Bug description: The checkmark is on the wrong option. Current resolution is 1920x1080, not 1600x1200 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 10:41:49 2021 ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913934] [NEW] Wrong current option in Screen resolution window
Public bug reported: The checkmark is on the wrong option. Current resolution is 1920x1080, not 1600x1200 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 10:41:49 2021 ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1913934 Title: Wrong current option in Screen resolution window Status in gnome-control-center package in Ubuntu: New Bug description: The checkmark is on the wrong option. Current resolution is 1920x1080, not 1600x1200 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-control-center 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 10:41:49 2021 ExecutablePath: /usr/bin/gnome-control-center ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-control-center UpgradeStatus: Upgraded to groovy on 2020-10-29 (93 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913934/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Thanks all for this thread!
I have the legion 5 with a MSFT0001:00 04F3:3186 Touchpad
graphics: 0NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] (rev a1)
I got this error message when trying to do what Eamon (342) said (upgrade the
kernel), as I too am new to kernel patching:
ERROR (dkms apport): kernel package linux-headers-5.11.0-051100rc2-generic is
not supported
Error! Bad return status for module build on kernel: 5.11.0-051100rc2-generic
(x86_64)
It said to consult this log:
/var/lib/dkms/nvidia/460.32.03/build/make.log
which is attached.
It seems like maybe this isn't compatible with my nvidia graphics card (1660)
for some reason?
Has anyone else has this problem?
So instead I tried to solve my touchpad issues by upgrading to 5.9.16
like Koen said in 325, but my it did not fix things :/
If there are no other "quick fixes" I supposed I will embark on the
journey of applying #189. But just wondering -- will #189 work with the
kernel I just installed: 5.9.16 or would I have to install
5.9.0-rc7-MANJARO+ ?
** Attachment added: "error log from trying to install kernel 5.11.0 rc2"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5458483/+files/make.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Oh, I understand Nicolas' message now: maybe there is a patched 5.8
kernel I can just install?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Status in Pop!_OS:
New
Status in linux package in Ubuntu:
Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
Confirmed
Status in linux package in Arch Linux:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
Hello
The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at
all (pointer and click never move when touchpad is touched). This has been
reported by other users in various websites, with various linux systems
including other Ubuntu systems, but I saw no launchpad bug so I post one.
Example of websites covering the issue :
- https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly
the same laptop)
- https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar
laptop)
xinput indentifies it as MSFT0001:00 04F3:3140
Virtual core pointer id=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer
(2)]
⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer
(2)]
⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave
pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Ideapad extra buttons id=15 [slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave
keyboard (3)]
↳ Power Buttonid=9[slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
keyboard (3)]
↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=18 [slave
keyboard (3)]
↳ Video Bus id=8[slave
keyboard (3)]
Thanks a lot for your time. It does not help, but I can confirm what
was reported on askubuntu by another user : the touchpad does work on
Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-40-generic 5.4.0-40.44
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: nicolas1567 F pulseaudio
/dev/snd/controlC1: nicolas1567 F pulseaudio
/dev/snd/controlC2: nicolas1567 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jul 10 20:14:25 2020
InstallationDate: Installed on 2020-07-02 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 82B5
ProcEnviron:
[Desktop-packages] [Bug 1913925] Re: gnome-control-center (Settings) Security is missing
I wanted bug reporting. It seems we can go for it with security tab in settings. I have searched the web and I found suggestion to remove it and reinstall. Reinstall failed due to dependencies ect. -- 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/1913925 Title: gnome-control-center (Settings) Security is missing Status in gnome-control-center package in Ubuntu: Incomplete Bug description: For bug reporting in settings "security" supposed to be there but it is not found. I have reinstalled gnome control-center there is no change. In fact after brousing net some one suggested to remove and reinstall the package. I have removed the package but could not install. Finally I have reinstalled Ubuntu OS, but the problem remained same. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jan 31 10:12:43 2021 InstallationDate: Installed on 2021-01-31 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1913925/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
