[Bug 1896110] Re: Ubuntu Dock has no icons when logged in with USB storage plugged in
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Ubuntu Dock has no icons when logged in with USB storage plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898186] Re: Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting
lspci has: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) [168c:002b] (rev 01) Subsystem: XAVi Technologies Corp. WB214E 802.11bgn Wireless Half-size Mini PCIe Card [AR9002WB-1NGCD] [1b9a:0c03] Maybe a AR5BWB222 precisely: https://www.notebookcheck.net/Review-Acer- Aspire-V5-571G-Notebook.78314.0.html#toc-connectivity Syslog has: bluetoothd[901]: Failed to set mode: Blocked through rfkill (0x12) Can you execute `rfkill list` and paste the result? You may want to try `rfkill unblock all` if you find anything listed as blocked. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: hwe-bluetooth ** Summary changed: - Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting + Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898186 Title: Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898426] Re: Favourites missing when booting with a smartphone connected
*** This bug is a duplicate of bug 1896110 *** https://bugs.launchpad.net/bugs/1896110 Let's assume this is the same as bug 1896110. ** Tags added: focal ** This bug has been marked a duplicate of bug 1896110 Ubuntu Dock has no icons when logged in with USB storage plugged in -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898426 Title: Favourites missing when booting with a smartphone connected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1898426/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896110] Re: Ubuntu Dock has no icons when logged in with USB storage plugged in
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896110 Title: Ubuntu Dock has no icons when logged in with USB storage plugged in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1896110/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898186] Re: Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting
I was wrong. You're referring to AR3011 connected to usb bus. But please still try the rfkill command above. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898186 Title: Qualcomm Atheros Communications AR3011 USB 0cf3:3005 Bluetooth headset stopped connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898404] Re: The keyboard overlay slides up the screen even though touch screen is not in use
Which onscreen keyboard is it (there are multiple)? Can you provide a screenshot? Also, can you please test a live boot of 20.04.1 and tell us if the problem is still there? https://ubuntu.com/download/desktop ** Tags added: osk ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898404 Title: The keyboard overlay slides up the screen even though touch screen is not in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898186] Re: Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting
** Summary changed: - [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting + Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898186 Title: Qualcomm Atheros AR9285 [168c:002b] Subsystem [1b9a:0c03] [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
Not much chance unless AMD GFX folks spend sometime to fix this old bug... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873128] Re: calamares wants to install to 3.5" 1.44MB floppy (& boot loader will get written to /dev/fd0 if sda selected)
Lubuntu groovy (daily) QA-test (simulated) install dell [optiplex] 755 (c2d-e6850, 5gb, amd/ati radeon rv516/x1300/x1550) I didn't complete install; the purpose is to look for https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1873128 which doesn't require the install to complete.. (floppy is readable, containing monopoly.com & associated files; if floppy is unreadable the bug doesn't appear to occur) Install is going to sda9, but boot loaded to /dev/fd0 (despite selecting /dev/sda for boot loader) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873128 Title: calamares wants to install to 3.5" 1.44MB floppy (& boot loader will get written to /dev/fd0 if sda selected) To manage notifications about this bug go to: https://bugs.launchpad.net/calamares/+bug/1873128/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898501] Re: lubuntu qa-test install with internet, calamares is selecting new york
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1898501 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898501 Title: lubuntu qa-test install with internet, calamares is selecting new york To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1898501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898505] [NEW] weird screen display
Public bug reported: Hi, After Resuming my system after sleep mode,display shows overlapping of multiple pages.Initially it shows black screen after that when I try to switch to different tab it shows partial display of previous tabs as well. This issue is also happening with Slack and other software as well. ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Screenshot from 2020-10-05 10-19-21.png" https://bugs.launchpad.net/bugs/1898505/+attachment/5417682/+files/Screenshot%20from%202020-10-05%2010-19-21.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898505 Title: weird screen display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852747] Re: mdcheck_start.service trying to start unexisting file
The "natural start" succeeded on all 4 of my systems. The start times were 01:41, 10:50, 18:11, and 21:43. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852747 Title: mdcheck_start.service trying to start unexisting file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1852747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
** No longer affects: mutter -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1820832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890384] Re: Crash
[Expired for Ubuntu because there has been no activity for 60 days.] ** Changed in: ubuntu Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890384 Title: Crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1890384/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890512] Re: bluetooth stopped working after recent apt updates
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890512 Title: bluetooth stopped working after recent apt updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890512/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1826786] Re: High CPU usage of the Xorg process
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1826786 Title: High CPU usage of the Xorg process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1826786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890321] Re: package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890321 Title: package chromium-browser 83.0.4103.97-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting a removal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890321/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890062] Re: speed mismatch trying to attach xbox sensor to windows 10 guest vm
[Expired for libvirt (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libvirt (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890062 Title: speed mismatch trying to attach xbox sensor to windows 10 guest vm To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1890062/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890390] Re: [nouveau] Xorg freeze
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890390 Title: [nouveau] Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1890390/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890446] Re: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127
[Expired for firefox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: firefox (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890446 Title: package firefox 78.0.1+build1-0ubuntu0.20.04.1 failed to install/upgrade: new firefox package pre-installation script subprocess returned error exit status 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1890446/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890047] Re: Sessions crash, all X11 remote users disconnected
[Expired for glib-networking (Ubuntu) because there has been no activity for 60 days.] ** Changed in: glib-networking (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890047 Title: Sessions crash, all X11 remote users disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1890047/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890055] Re: Brightness control does not work with 5.4.0-42.26
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890055 Title: Brightness control does not work with 5.4.0-42.26 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890055/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888090] Re: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888090 Title: Frequent Kernel panic in 5.4.0-40 but not 5.4.0-29 on Gemini Lake cpu and r8169r To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888090/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890365] Re: [snap] Web Serial fails to access local device
[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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890365 Title: [snap] Web Serial fails to access local device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1890365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898442] Re: Center new windows
** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Changed in: mutter (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898442 Title: Center new windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1898442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898495] Re: Grub loader installer crash upgrading 20.04 to 20.10
** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898495 Title: Grub loader installer crash upgrading 20.04 to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1898495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
I'm not sure we should treat the freeze as a separate issue since dragging and dropping isn't expected to work (bug 1813441). Can you find any reports of a crash in /var/crash ? ** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension- desktop-icons (Ubuntu) ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: New => Incomplete ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell-extension-desktop-icons (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898462] Re: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome-shell
Confirmed, but see also bug 1813441. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898462 Title: [groovy] Drag and drop files from Desktop to Nautilus freezes gnome- shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1898462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898154] Re: Broadcom BCM4352 [14e4:43b1] Subsystem [1028:0019] No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency
Hi, could you confirm dkms modules have been built and installed? Looks good for me from my side except I don't have this bcm chip: $ dkms status bcmwl, 6.30.223.271+bdcom, 5.4.0-45-lowlatency, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-47-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-47-lowlatency, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-48-lowlatency, x86_64: installed Besides, it seems stable patch broke OEM kernel interface again. Build failure on bcmwl version 6.30.223.271+bdcom against at least 5.6.0-1028-oem. ** Attachment added: "bcmwl_6.30.223.271+bdcom.make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1898154/+attachment/5417680/+files/bcmwl_6.30.223.271+bdcom.make.log ** Changed in: bcmwl (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: Broadcom BCM4352 [14e4:43b1] Subsystem [1028:0019] No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898393] Re: Gnome Magnifier does track mouse cursor.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898393 Title: Gnome Magnifier does track mouse cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898393] Re: Gnome Magnifier does track mouse cursor.
** Tags added: regression ** Tags added: a11y ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => High ** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898393 Title: Gnome Magnifier does track mouse cursor. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1898393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898186] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898186 Title: [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898395] Re: Problem with external monitor
** Tags added: amdgpu hybrid multi-gpu multimonitor nvidia ** Summary changed: - Problem with external monitor + [nvidia] [amdgpu] Problem with external monitor ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-450 (Ubuntu) ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898395 Title: [nvidia] [amdgpu] Problem with external monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1898395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898501] [NEW] lubuntu qa-test install with internet, calamares is selecting new york
Public bug reported: Firefox search reports my location as "203.214.60.52 AU St Kilda, Victoria, Australia, Oceania 203.214.60.0/24 3182-37.8661, 144.981 10" however calamares has selected 'New York' as my location, Region:America Zone: New York I exited calamares, used firefox to check geoip location as noted before & restarted calamares and again it had me as New York. (My prior test today was without internet, thus new york was expected) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: calamares 3.2.24-0ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 .etc.calamares.modules.finished.conf: --- restartNowMode: user-checked restartNowCommand: "systemctl -i reboot" .etc.calamares.modules.partition.conf: efiSystemPartition: "/boot/efi" enableLuksAutomatedPartitioning: true userSwapChoices: none drawNestedPartitions: true defaultFileSystemType: "ext4" .etc.calamares.modules.shellprocess_logs.conf: --- dontChroot: true timeout: 30 script: - calamares-logs-helper @@ROOT@@ .etc.calamares.modules.unpackfs.conf: --- unpack: - source: "/cdrom/casper/filesystem.squashfs" sourcefs: "squashfs" destination: "" ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: LXQt Date: Sun Oct 4 23:45:48 2020 LiveMediaBuild: Lubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201004) RelatedPackageVersions: calamares-settings-ubuntu-common 1:20.10.9 calamares-settings-lubuntu 1:20.10.9 xfsprogs 5.6.0-1ubuntu4 btrfs-progs 5.7-1 SourcePackage: calamares UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: calamares (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898501 Title: lubuntu qa-test install with internet, calamares is selecting new york To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calamares/+bug/1898501/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898324] Re: Different thickness title bars between gtk3 / gtk2 applications
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: yaru-theme (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898324 Title: Different thickness title bars between gtk3 / gtk2 applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1898324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898204] Re: sound
It seems this bug was reported against the wrong component so we have the wrong attachments. Please run this command to send us more information about the machine's sound: apport-collect 1898204 ** Package changed: xorg (Ubuntu) => pulseaudio (Ubuntu) ** Summary changed: - sound + [Gigabyte Z170-HD3P] No sound ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898204 Title: [Gigabyte Z170-HD3P] No sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1898204/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898324] Re: [groovy] Different thickness title bars between gtk3 / gtk2 applications
It's not a new problem. I can see the same issue in 20.04 right now. I'm not sure it's a bug though... GTK3 titlebars are functionally different to GTK2 titlebars. ** Package changed: gnome-shell (Ubuntu) => yaru-theme (Ubuntu) ** Summary changed: - [groovy] Different thickness title bars between gtk3 / gtk2 applications + Different thickness title bars between gtk3 / gtk2 applications ** Changed in: yaru-theme (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898324 Title: Different thickness title bars between gtk3 / gtk2 applications To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1898324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898154] Re: No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352
Please install proprietary driver bcmwl-kernal-source. See https://askubuntu.com/questions/590442/how-can-i-install-broadcom- wireless-adapter-bcm4352-802-11ac-pcid-14e443b1-r ** Summary changed: - No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency - Broadcom BCM4352 + Broadcom BCM4352 [14e4:43b1] Subsystem [1028:0019] No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898154 Title: Broadcom BCM4352 [14e4:43b1] Subsystem [1028:0019] No Wi-Fi Adapter Found Ubuntu 20.04 after updated Linux kernel to version 5.4.0-47-lowlatency 5.4.0-48-lowlatency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1898154/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1541392] Re: AR3011 Bluetooth not starting after being stoped (but detected)
Thank you for reporting this bug to Ubuntu. Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1541392 Title: AR3011 Bluetooth not starting after being stoped (but detected) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1541392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814120] Re: Troubles w/ Bluetooth @ usb device 04ca:3002
Thank you for reporting this bug to Ubuntu. Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814120 Title: Troubles w/ Bluetooth @ usb device 04ca:3002 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814120/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898186] Re: [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting
** Summary changed: - the stereo headset stopped connecting + [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898186 Title: [Qualcomm Atheros Communications AR3011] Bluetooth headset stopped connecting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1898186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891100] Re: hp notebook 15-da0001nk sound mute led not working
@kaihengfeng Why the bug status is still incomplete even though I added all the necessary information, and it also affected other users. Is there any development or news around it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891100 Title: hp notebook 15-da0001nk sound mute led not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891100/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898153] Re: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time.
Rick, what do you get if you run this command? gsettings get org.gnome.desktop.lockdown disable-lock-screen ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898153 Title: I upgraded from 18.04 to 20.04.1 and the screen doesn't lock or go blank at the set time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1898153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898210] Re: X11 applications do not refresh in a timely fashion, resulting in screen corruption, when using custom xrandr scaling
Filed: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1084 ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1084 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1084 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898210 Title: X11 applications do not refresh in a timely fashion, resulting in screen corruption, when using custom xrandr scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1898210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898287] Re: srt-tools version 1.4.2
this package has been upgraded in Debian Sid to the request version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898287 Title: srt-tools version 1.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/srt/+bug/1898287/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897553] Re: [ALPS i2c Touchpads] Palm detect pressure is too easy to trigger so that the cursor stalled
Verify on device SPT4-DVT1-C1, CID: 202008-28141. Touchpad hid: 0488:101A. $ sudo apt install libinput-tools $ sudo libinput measure touchpad-pressure See the threshold become 180 by default. Try to move finger on the touchpad. It won't exceed 180 by normal movement and usage. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897553 Title: [ALPS i2c Touchpads] Palm detect pressure is too easy to trigger so that the cursor stalled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1897553/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897934] Re: [HP 14-ac100na] The initial sound level is set to zero (mute)
** Summary changed: - The initial sound level is set to zero (mute) + [HP 14-ac100na] The initial sound level is set to zero (mute) ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [HP 14-ac100na] The initial sound level is set to zero (mute) + [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897934 Title: [HP 14-ac100na N9S73EA#ABU] The initial sound level is set to zero (mute) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1897934/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1897959] Re: Audio Shuts Down with Screen Blanking
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897959 Title: Audio Shuts Down with Screen Blanking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1897959/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898210] Re: X11 applications do not refresh in a timely fashion, resulting in screen corruption, when using custom xrandr scaling
Thanks for the bug report. Please also report it to the Xorg developers at: https://gitlab.freedesktop.org/xorg/xserver/-/issues and then tell us the new issue ID. ** Summary changed: - X11 applications do not refresh in a timely fashion, resulting in screen corruption + X11 applications do not refresh in a timely fashion, resulting in screen corruption, when using custom xrandr scaling ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898210 Title: X11 applications do not refresh in a timely fashion, resulting in screen corruption, when using custom xrandr scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1898210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890141] Re: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling
Yes disabling fullscreen window "unredirection" should work, and was discussed in the previous bug too (bug 1862081). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890141 Title: Can't fullscreen, or windows get automatically un-fullscreened, when using fractional scaling To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1890141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898498] [NEW] Attempted upgrade from 18.04 LTS to 20.04 LTS
Public bug reported: Attempted the automated upgrade from 18.04 to 20.04 and hit failure. └──> $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 └──> $ sudo apt-cache policy pkgname N: Unable to locate package pkgname Gui popped up with upgrade to 20.04,exception thrown stating to remove snap. No snap found with issues that I see. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu Date: Sun Oct 4 20:10:46 2020 InstallationDate: Installed on 2019-01-31 (612 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-05 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898498 Title: Attempted upgrade from 18.04 LTS to 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898498/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1897477] Re: Trying to install 18.04.5 on Dell optlplex 7010
I came to that conclusion myself, I successfully installed 20.04. I also failed installing 16.04 for the same reason. Thank you -Original Message- >From: Paul White <1897...@bugs.launchpad.net> >Sent: Oct 4, 2020 2:43 AM >To: s...@sprynet.com >Subject: [Bug 1897477] Re: Trying to install 18.04.5 on Dell optlplex 7010 > >The following errors can be found in UbiquitySyslog.txt which was >automatically attached to this bug report: > >Sep 27 20:09:53 ubuntu kernel: [ 857.891206] SQUASHFS error: zlib >decompression failed, data probably corrupt >Sep 27 20:09:53 ubuntu kernel: [ 857.891211] SQUASHFS error: >squashfs_read_data failed to read block 0x1d49c21e > >It's possible you have a bad write to your media. If you're still having >problems please try the option to check the integrity of the image from >the installer boot menu, and if this confirms that the media is corrupt, >try re-writing and/or re-downloading it. > > >** Changed in: ubiquity (Ubuntu) > Status: New => Incomplete > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1897477 > >Title: > Trying to install 18.04.5 on Dell optlplex 7010 > >Status in ubiquity package in Ubuntu: > Incomplete > >Bug description: > 3) I expected an n nstall to occurr > 4) I got an disk error, will try again > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: ubiquity 18.04.14.15 > ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 > Uname: Linux 5.4.0-42-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.16 > Architecture: amd64 > CasperVersion: 1.394.3 > CurrentDesktop: ubuntu:GNOME > Date: Sun Sep 27 13:12:44 2020 > InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper > initrd=/casper/initrd quiet splash --- maybe-ubiquity > LiveMediaBuild: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 > (20200806.1) > ProcEnviron: > LANGUAGE=en_US.UTF-8 > PATH=(custom, no user) > XDG_RUNTIME_DIR= > LANG=en_US.UTF-8 > LC_NUMERIC=C.UTF-8 > SourcePackage: ubiquity > UpgradeStatus: No upgrade log present (probably fresh install) > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897477/+subscriptions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897477 Title: Trying to install 18.04.5 on Dell optlplex 7010 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1897477/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
** Changed in: mutter (Ubuntu) Status: Opinion => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1430 https://gitlab.gnome.org/GNOME/mutter/-/issues/1430 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1430 Importance: Unknown Status: Unknown ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1820832/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898497] [NEW] upgrade to "20.04" crashes due to: "python-is-python2"
Public bug reported: MarkInstall python-is-python2:amd64 < none -> 2.7.17-4 @un uN Ib > FU=1 Installing python2 as Depende of python-is-python2 MarkInstall python2:amd64 < none -> 2.7.17-2ubuntu4 @un uN Ib > FU=0 Installing python2-minimal as PreDepende of python2 MarkInstall python2-minimal:amd64 < none -> 2.7.17-2ubuntu4 @un uN Ib > FU=0 Removing: python-minimal MarkDelete python-minimal:amd64 < 2.7.15~rc1-1 @ii mK > FU=0 Installing libpython2-stdlib as Depende of python2 MarkInstall libpython2-stdlib:amd64 < none -> 2.7.17-2ubuntu4 @un uN Ib > FU=0 Removing: libpython-stdlib MarkDelete libpython-stdlib:amd64 < 2.7.15~rc1-1 @ii mK > FU=0 Removing: python MarkDelete python:amd64 < 2.7.15~rc1-1 @ii mK Ib > FU=0 Starting pkgProblemResolver with broken count: 1 Starting 2 pkgProblemResolver with broken count: 1 Investigating (0) nodejs:amd64 < 12.18.4-1nodesource1 @ii mK Ib > Broken nodejs:amd64 Depende on python-minimal:amd64 < 2.7.15~rc1-1 @ii gR > Considering python-minimal:amd64 1 as a solution to nodejs:amd64 92 Added python-minimal:amd64 to the remove list Fixing nodejs:amd64 via keep of python-minimal:amd64 MarkKeep python-minimal:amd64 < 2.7.15~rc1-1 @ii gR > FU=0 Investigating (0) python2-minimal:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > Broken python2-minimal:amd64 Rompe on python-minimal:amd64 < 2.7.15~rc1-1 @ii gK > (< 2.7.15-2) Considering python-minimal:amd64 1 as a solution to python2-minimal:amd64 1 MarkKeep python2-minimal:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > FU=0 Holding Back python2-minimal:amd64 rather than change python-minimal:amd64 Investigating (0) python2:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > Broken python2:amd64 PreDepende on python2-minimal:amd64 < none | 2.7.17-2ubuntu4 @un umH > (= 2.7.17-2ubuntu4) Considering python2-minimal:amd64 1 as a solution to python2:amd64 1 MarkKeep python2:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > FU=0 Holding Back python2:amd64 rather than change python2-minimal:amd64 Investigating (1) python-is-python2:amd64 < none -> 2.7.17-4 @un pumN Ib > Broken python-is-python2:amd64 Depende on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Considering python2:amd64 1 as a solution to python-is-python2:amd64 Re-Instated python2-minimal:amd64 Re-Instated python2:amd64 Investigating (1) python2-minimal:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > Broken python2-minimal:amd64 Rompe on python-minimal:amd64 < 2.7.15~rc1-1 @ii gK > (< 2.7.15-2) Considering python-minimal:amd64 1 as a solution to python2-minimal:amd64 1 MarkKeep python2-minimal:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > FU=0 Holding Back python2-minimal:amd64 rather than change python-minimal:amd64 Investigating (1) python2:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > Broken python2:amd64 PreDepende on python2-minimal:amd64 < none | 2.7.17-2ubuntu4 @un umH > (= 2.7.17-2ubuntu4) Considering python2-minimal:amd64 1 as a solution to python2:amd64 1 MarkKeep python2:amd64 < none -> 2.7.17-2ubuntu4 @un umN Ib > FU=0 Holding Back python2:amd64 rather than change python2-minimal:amd64 Investigating (2) python-is-python2:amd64 < none -> 2.7.17-4 @un pumN Ib > Broken python-is-python2:amd64 Depende on python2:amd64 < none | 2.7.17-2ubuntu4 @un umH > Considering python2:amd64 1 as a solution to python-is-python2:amd64 Done Log time: 2020-10-05 03:55:54.164121 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 [origin: unknown] ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-lowlatency 5.4.60 Uname: Linux 5.4.0-48-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu Date: Mon Oct 5 03:52:26 2020 InstallationDate: Installed on 2018-09-21 (744 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-10-05 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-10-05 03:51:15.481933 Log time: 2020-10-05 03:52:02.935666 VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages ** Attachment added: "apt.log and main.log in one file" https://bugs.launchpad.net/bugs/1898497/+attachment/5417644/+files/bug.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898497 Title: upgrade to "20.04" crashes due to: "python-is-python2" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com
[Bug 1898495] [NEW] Grub loader installer crash upgrading 20.04 to 20.10
Public bug reported: Term error installing grub! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.10 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 21:49:52 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-20-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898495 Title: Grub loader installer crash upgrading 20.04 to 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898495/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
Which Nvidia driver you use probably isn't very important here. I suggest we don't start a new conversation about that. This is a bug in the 'mutter' package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898494] [NEW] ubiquity in Ubuntu 20.04 Deprecation warning
Public bug reported: Running ubiquity after an upgrade fom 18.04 to 20.04 LTS ubuntu: /usr/bin/ubiquity:74: DeprecationWarning: the imp module is deprecated in favour of importlib; see the module's documentation for alternative uses import imp Note: Replacing "imp" by "importlib" in /usr/bin/ubiquity does NOT work. ubiquity appears to succeed, are there any latent issues which might crop up following this warning? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.2 [modified: usr/lib/ubiquity/user-setup/user-setup-apply usr/share/ubiquity/apt-setup] ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperVersion: 1.445.1 CurrentDesktop: GNOME-Flashback:GNOME Date: Mon Oct 5 04:22:22 2020 InstallCmdLine: BOOT_IMAGE=(hd0,gpt4)/casper/vmlinuz file=/cdrom/preseed/custom.seed boot=casper iso-scan/filename= quiet splash fsck.mode=skip persistent -- LiveMediaBuild: Backup_mike2_Oct_2020 20.04 - Release amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IL SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug custom focal ubiquity-20.04.15.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898494 Title: ubiquity in Ubuntu 20.04 Deprecation warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1898494/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898493] [NEW] /dev/dri/card0 not closed when plasmashell forks
Public bug reported: plasmashell forks xterm. xterm inherits /dev/dri/card0 open on fd 15. Working as designed? Or forgot to close it/mark it as CLOEXEC? # lsof -p 2624 | grep /dev/dri plasmashe 2624 kaos 12u CHR 226,0 0t0347 /dev/dri/card0 plasmashe 2624 kaos 13u CHR 226,0 0t0347 /dev/dri/card0 plasmashe 2624 kaos 14u CHR 226,0 0t0347 /dev/dri/card0 plasmashe 2624 kaos 15u CHR 226,0 0t0347 /dev/dri/card0 xterm child on pid 3659 # lsof -p 3659 | grep /dev/dri xterm 3659 kaos 15u CHR 226,0 0t0 347 /dev/dri/card0 strace 2624 shows no close for fd 12, 13, 14 but they are not inherited by 3659. So they are probably marked CLOEXEC. But fd 15 is left open and is inherited by all children of plasmashell. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plasma-workspace 4:5.18.5-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Oct 5 12:24:05 2020 InstallationDate: Installed on 2017-07-12 (1180 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) SourcePackage: plasma-workspace UpgradeStatus: Upgraded to focal on 2020-06-21 (105 days ago) ** Affects: plasma-workspace (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898493 Title: /dev/dri/card0 not closed when plasmashell forks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/1898493/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886534] Re: [SRU] This message is shown once once a day.
I can verify that it is fixed: https://sgp1.digitaloceanspaces.com/pkwu- personal/garage/screenshots/Screenshot%202020-10-05%20at%209.18.46%20AM.png ** Tags removed: verification-needed-focal ** Tags added: verification-done-foical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886534 Title: [SRU] This message is shown once once a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuwsl/+bug/1886534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
i have already added some pr_err to the kernel source , then the dmesg say : the touchpad work 1 time,during the system boot. the dmesg output like : ``` [1.766437] in handle_fasteoi_irq for irq:7,starting... [1.766440] in handle_irq_event start for :7 [1.766440] in __handle_irq_event_percpu :7 starting... [1.766441] in __handle_irq_event_percpu :7,in for_each_action_of_desc [1.766442] in amd_gpio_irq_handler,irq:7 start... [1.766500] in amd_gpio_irq_handler,(!(regval & PIN_IRQ_PENDING) ||!(regval & BIT(INTERRUPT_MASK_OFF))) continue: 0 [1.766502] in amd_gpio_irq_handler,(!(regval & PIN_IRQ_PENDING) ||!(regval & BIT(INTERRUPT_MASK_OFF))) continue: 0 [1.766504] in amd_gpio_irq_handler, generic_handle_irq :55,start... [1.766510] in amd_gpio_irq_handler, generic_handle_irq :55,end [1.766512] in amd_gpio_irq_handler,(!(regval & PIN_IRQ_PENDING) ||!(regval & BIT(INTERRUPT_MASK_OFF))) continue: 0 [1.766514] in amd_gpio_irq_handler,irq:55 end [1.766515] in __handle_irq_event_percpu :7,in switch IRQ_HANDLED break [1.766516] in __handle_irq_event_percpu :7 ending... [1.766516] in handle_irq_event end for :7 [1.766517] cond_unmask_eoi_irq irq:7 [1.766519] in handle_fasteoi_irq for irq:7, end [1.841153] input: MSFT0001:00 04F3:3140 Mouse as /devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:04F3:3140.0001/input/input6 [1.841250] input: MSFT0001:00 04F3:3140 Touchpad as /devices/platform/AMDI0010:03/i2c-0/i2c-MSFT0001:00/0018:04F3:3140.0001/input/input7 [1.841312] hid-generic 0018:04F3:3140.0001: input,hidraw0: I2C HID v1.00 Mouse [MSFT0001:00 04F3:3140] on i2c-MSFT0001:00 ``` and today ,i run the script: ``` [root@localhost ra]# cd /sys/class/gpio/ [root@localhost gpio]# echo 386 > export [root@localhost gpio]# cd gpio386 ``` then ``` [root@localhost gpio386]# cat direction in ``` so, there is some bug code set the direction to in ,or missing code to set the direction to out ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898492] [NEW] mosquitto broker websockets no longer work
Public bug reported: Ubuntu 20.04.1 LTS mosquitto 1.6.9-1 I have a MQTT-brokered weather station, which sends realtime updates to a webpage using paho to do MQTT over websockets Everything worked fine until upgrade from bionic to focal The mosquitto broker continued to work fine, but the websocket component stopped functioning The relevant config section for mosquitto is like this: listener 4 ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH certfile /etc/nginx/ssl/acme/site.crt cafile /etc/nginx/ssl/acme/site.fullchain keyfile /etc/nginx/ssl/acme/site.key protocol websockets --- The first issue, netstat confirmed that mosquitto was NOT listening on IPv4, but only on IPv6. IPv6 is not routed to the internet in my installation, so that was an undesirable change in functionality. Adding this stanza: socket_domain ipv4 ...at least got netstat to report IPv4 listening on the websocket port But the websocket server was not reachable from the Internet. It just didn't work, on either Chrome or Firefox, on ubuntu or Windows, though strangely it worked with Mobile Safari on iOS. I made some discoveries... focal uses mosquitto 1.6.9, on top of libwebsockets 3.2.1 [libwebsockets15] bionic used mosquitto 1.4.15, on top of libwebsockets 2.0.3 [libwebsockets8] I pulled down mosquitto 1.6.9 source and the source for both libwebsockets versions from packages.ubuntu.com mosquitto 1.6.9 built against libwebsockets 3.2.1 misbehaved exactly as stock Ubuntu focal builds, which was reassuring mosquitto 1.6.9 built against libwebsockets 2.0.3 functioned properly, as 1.4.15 did on bionic Everything else was left identical. you may note in this report that /usr/sbin/mosquitto is altered - I have replaced it with my hand-built frankenversion, to get my server back in business Cheers ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mosquitto 1.6.9-1 [modified: usr/sbin/mosquitto] ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 4 17:07:46 2020 InstallationDate: Installed on 2018-03-07 (942 days ago) InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: mosquitto UpgradeStatus: Upgraded to focal on 2020-10-04 (0 days ago) ** Affects: mosquitto (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898492 Title: mosquitto broker websockets no longer work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mosquitto/+bug/1898492/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
so may be there is some bug with the :direction, because ,i run echo out > direction,then it start to work. and may be just like #130 or #133 ,but in drivers related to this touchpad . -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898491] [NEW] STARTTIME is incorrect in 2.2.0
Public bug reported: I have several up-to-date instances of Ubuntu 20.04 and one of them consistently shows incorrect STARTTIME. The column often shows the same timestamp for most processes with only a handful of top level exceptions like /sbin/init and /lib/systemd/systemd. In the same instance the old issue of process name not being completely refreshed is back. This is very noticeable with postrgesql processes that change process name according to the command they execute. E.g. when a process changes state from running a SELECT to idle the process name changes from SELECT to idleCT keeping the last 2 characters "CT" of SELECT. As a reference top when run with -o lstart produces correct process start timestamp. This issue is discussed here: https://github.com/htop- dev/htop/issues/202. It also states that installing a DEB from debian testing (ver 3.0.2-1) fixes the issue. ** Affects: htop (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898491 Title: STARTTIME is incorrect in 2.2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/htop/+bug/1898491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
and the dmesg has some output related: ``` [ 138.233653] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1831348] Re: The Progress Bar for emptying the Trash stuck at 0
Why don't you just flag all new bugs as "ignored", since I have never seen any activity to actually fix any bugs. When my company bought a system with Unix System V on it, I got a book of known bugs. There were over 500 pages with two pages/page of known bugs. The catch is that AT never attempted to actually FIX any of these bugs. Nor were there any workarounds. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1831348 Title: The Progress Bar for emptying the Trash stuck at 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pluma/+bug/1831348/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
no touch test: i run :sudo hid-recorder ``` [ra@localhost ~]$ sudo hid-recorder [sudo] password for ra: Available devices: /dev/hidraw0: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw1: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw2: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw3: MSFT0001:00 04F3:3140 /dev/hidraw4: ITE Tech. Inc. ITE Device(8910) Select the device event number [0-4]: 3 # MSFT0001:00 04F3:3140 # 0x05, 0x01,// Usage Page (Generic Desktop)0 # 0x09, 0x02,// Usage (Mouse) 2 # 0xa1, 0x01,// Collection (Application)4 # 0x85, 0x01,// Report ID (1) 6 # 0x09, 0x01,// Usage (Pointer)8 # 0xa1, 0x00,// Collection (Physical) 10 # 0x05, 0x09,// Usage Page (Button) 12 # 0x19, 0x01,// Usage Minimum (1) 14 # 0x29, 0x02,// Usage Maximum (2) 16 # 0x15, 0x00,// Logical Minimum (0) 18 # 0x25, 0x01,// Logical Maximum (1) 20 # 0x75, 0x01,// Report Size (1) 22 # 0x95, 0x02,// Report Count (2) 24 # 0x81, 0x02,// Input (Data,Var,Abs) 26 # 0x95, 0x06,// Report Count (6) 28 # 0x81, 0x03,// Input (Cnst,Var,Abs) 30 # 0x05, 0x01,// Usage Page (Generic Desktop) 32 # 0x09, 0x30,// Usage (X) 34 # 0x09, 0x31,// Usage (Y) 36 # 0x09, 0x38,// Usage (Wheel) 38 # 0x15, 0x81,// Logical Minimum (-127)40 # 0x25, 0x7f,// Logical Maximum (127) 42 # 0x75, 0x08,// Report Size (8) 44 # 0x95, 0x03,// Report Count (3) 46 # 0x81, 0x06,// Input (Data,Var,Rel) 48 # 0x05, 0x0c,// Usage Page (Consumer Devices) 50 # 0x0a, 0x38, 0x02, // Usage (AC Pan)52 # 0x95, 0x01,// Report Count (1) 55 # 0x81, 0x06,// Input (Data,Var,Rel) 57 # 0x75, 0x08,// Report Size (8) 59 # 0x95, 0x03,// Report Count (3) 61 # 0x81, 0x03,// Input (Cnst,Var,Abs) 63 # 0xc0, // End Collection 65 # 0x06, 0x00, 0xff, // Usage Page (Vendor Defined Page 1) 66 # 0x85, 0x0d,// Report ID (13) 69 # 0x09, 0xc5,// Usage (Vendor Usage 0xc5) 71 # 0x15, 0x00,// Logical Minimum (0)73 # 0x26, 0xff, 0x00, // Logical Maximum (255) 75 # 0x75, 0x08,// Report Size (8)78 # 0x95, 0x04,// Report Count (4) 80 # 0xb1, 0x02,// Feature (Data,Var,Abs) 82 # 0x85, 0x0c,// Report ID (12) 84 # 0x09, 0xc6,// Usage (Vendor Usage 0xc6) 86 # 0x96, 0x10, 0x04, // Report Count (1040)88 # 0x75, 0x08,// Report Size (8)91 # 0xb1, 0x02,// Feature (Data,Var,Abs) 93 # 0x85, 0x0b,// Report ID (11) 95 # 0x09, 0xc7,// Usage (Vendor Usage 0xc7) 97 # 0x95, 0x42,// Report Count (66) 99 # 0x75, 0x08,// Report Size (8)101 # 0xb1, 0x02,// Feature (Data,Var,Abs) 103 # 0x09, 0x01,// Usage (Vendor Usage 1) 105 # 0x85, 0x5d,// Report ID (93) 107 # 0x95, 0x1f,// Report Count (31) 109 # 0x75, 0x08,// Report Size (8)111 # 0x81, 0x06,// Input (Data,Var,Rel) 113 # 0xc0, // End Collection 115 # 0x05, 0x0d,// Usage Page (Digitizers) 116 # 0x09, 0x05,// Usage (Touch Pad) 118 # 0xa1, 0x01,// Collection (Application)120 # 0x85, 0x04,//
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
touch test: follow the no touch test, i touch the touchpad: then the output are: ``` # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2249 | Y: 1233 | Scan Time: 59692 | Contact Count:1 | Button: 0 | # | # E: 000215.550028 12 04 03 c9 08 d1 04 2c e9 01 80 19 43 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2249 | Y: 1233 | Scan Time: 59782 | Contact Count:1 | Button: 0 | # | # E: 000215.558929 12 04 03 c9 08 d1 04 86 e9 01 80 19 43 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2249 | Y: 1233 | Scan Time: 59872 | Contact Count:1 | Button: 0 | # | # E: 000215.567472 12 04 03 c9 08 d1 04 e0 e9 01 80 19 43 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2249 | Y: 1232 | Scan Time: 59992 | Contact Count:1 | Button: 0 | # | # E: 000215.578906 12 04 03 c9 08 d0 04 58 ea 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2246 | Y: 1226 | Scan Time: 60112 | Contact Count:1 | Button: 0 | # | # E: 000215.590708 12 04 03 c6 08 ca 04 d0 ea 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2243 | Y: 1219 | Scan Time: 60222 | Contact Count:1 | Button: 0 | # | # E: 000215.601795 12 04 03 c3 08 c3 04 3e eb 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2243 | Y: 1219 | Scan Time: 60332 | Contact Count:1 | Button: 0 | # | # E: 000215.611951 12 04 03 c3 08 c3 04 ac eb 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2243 | Y: 1219 | Scan Time: 60442 | Contact Count:1 | Button: 0 | # | # E: 000215.622699 12 04 03 c3 08 c3 04 1a ec 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2243 | Y: 1219 | Scan Time: 60512 | Contact Count:1 | Button: 0 | # | # E: 000215.629600 12 04 03 c3 08 c3 04 60 ec 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2243 | Y: 1219 | Scan Time: 60582 | Contact Count:1 | Button: 0 | # | # E: 000215.636408 12 04 03 c3 08 c3 04 a6 ec 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2243 | Y: 1219 | Scan Time: 60672 | Contact Count:1 | Button: 0 | # | # E: 000215.646507 12 04 03 c3 08 c3 04 00 ed 01 80 19 34 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2228 | Y: 1171 | Scan Time: 60752 | Contact Count:1 | Button: 0 | # | # E: 000215.653875 12 04 03 b4 08 93 04 50 ed 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2227 | Y: 1165 | Scan Time: 60832 | Contact Count:1 | Button: 0 | # | # E: 000215.661588 12 04 03 b3 08 8d 04 a0 ed 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2227 | Y: 1165 | Scan Time: 60922 | Contact Count:1 | Button: 0 | # | # E: 000215.669600 12 04 03 b3 08 8d 04 fa ed 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2224 | Y: 1152 | Scan Time: 61002 | Contact Count:1 | Button: 0 | # | # E: 000215.678954 12 04 03 b0 08 80 04 4a ee 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2223 | Y: 1146 | Scan Time: 61082 | Contact Count:1 | Button: 0 | # | # E: 000215.686412 12 04 03 af 08 7a 04 9a ee 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2223 | Y: 1146 | Scan Time: 61152 | Contact Count:1 | Button: 0 | # | # E: 000215.693151 12 04 03 af 08 7a 04 e0 ee 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2223 | Y: 1133 | Scan Time: 61222 | Contact Count:1 | Button: 0 | # | # E: 000215.700738 12 04 03 af 08 6d 04 26 ef 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2223 | Y: 1133 | Scan Time: 61292 | Contact Count:1 | Button: 0 | # | # E: 000215.706789 12 04 03 af 08 6d 04 6c ef 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2223 | Y: 1133 | Scan Time: 61382 | Contact Count:1 | Button: 0 | # | # E: 000215.715586 12 04 03 af 08 6d 04 c6 ef 01 80 1c 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2224 | Y: 1100 | Scan Time: 61492 | Contact Count:1 | Button: 0 | # | # E: 000215.727195 12 04 03 b0 08 4c 04 34 f0 01 80 1b 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2226 | Y: 1091 | Scan Time: 61562 | Contact Count:1 | Button: 0 | # | # E: 000215.733150 12 04 03 b2 08 43 04 7a f0 01 80 1b 44 # ReportID: 4 / Confidence: 1 | Tip Switch: 1 | # | Contact Id: 0 | X: 2226 | Y: 1091 | Scan Time: 61752 | Contact Count:1 | Button: 0 | # | # E: 000215.752795 12 04 03 b2 08 43 04 38 f1 01 80 1b 44 # ReportID: 4 / Confidence: 1 |
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) #144 i now test it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@@wangjun Good to know that! What's the result of "echo value"? And what's the output of hdi-recorder with and without fingers on the touchpad? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@coiby xu ,many thanks to you you find another way to solve the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
i reboot ,and test it again. only run this script: ``` [ra@localhost ~]$ su Password: [root@localhost ra]# cd /sys/class/gpio/ [root@localhost gpio]# echo 386 > export [root@localhost gpio]# cd gpio386 [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# ``` then cursor start move ,and two figure scroll is ok too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
after i run the line in the terminal windows 2: echo out > direction terminal window 1 has output and the cursor start move. no need to run the line echo 0 > value -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1896250] Re: SDL support is missing while virglrenderer has problems with GTK
Hi Christian, Fairly easy to reproduce. I just tried with current qemu (version 4.2.1 (Debian 1:4.2-3ubuntu6.6)). You need to download the Android 9.0r2 ISO image from the Android-x86 project. Here's a link for the 64-bit image (I chose the non k49 one) : https://www.fosshub.com/Android-x86.html?dwl=android-x86_64-9.0-r2.iso Then boot the image in Qemu : qemu-system-x86_64 -machine q35,vmport=off -cpu host -accel kvm -smp 2 -m 4G -audiodev pa,id=pasound,timer-period=5000 -device ES1370,audiodev=pasound -device virtio-vga,virgl=on -device virtio-mouse -device virtio-keyboard -drive file=android-x86_64-9.0-r2.iso,if=virtio,media=cdrom,format=raw,readonly=on -display gtk,gl=on -usb -nodefaults -monitor vc -nic user,hostfwd=tcp:127.0.0.1:-: It shouldn't take long before the screen freezes. Here's the associated log entry : - LOG START - 10-05 01:00:18.548 1147 1259 F libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xe8 in tid 1259 (frame-worker), pid 1147 (surfaceflinger) 10-05 01:00:18.565 4406 4406 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 10-05 01:00:18.565 4406 4406 F DEBUG : Build fingerprint: 'Android-x86/android_x86_64/x86_64:9/PI/lh03251128:userdebug/test-keys' 10-05 01:00:18.565 4406 4406 F DEBUG : Revision: '0' 10-05 01:00:18.565 4406 4406 F DEBUG : ABI: 'x86_64' 10-05 01:00:18.565 4406 4406 F DEBUG : pid: 1147, tid: 1259, name: frame-worker >>> /system/bin/surfaceflinger <<< 10-05 01:00:18.565 4406 4406 F DEBUG : signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xe8 10-05 01:00:18.565 4406 4406 F DEBUG : Cause: null pointer dereference 10-05 01:00:18.565 4406 4406 F DEBUG : rax rbx 7eb0cc0585b0 rcx rdx 7eb0d2a9cc08 10-05 01:00:18.565 4406 4406 F DEBUG : r8 r9 r10 r11 0246 10-05 01:00:18.565 4406 4406 F DEBUG : r12 0001 r13 7eb0d30d7050 r14 001e r15 7eb0d30d7100 10-05 01:00:18.565 4406 4406 F DEBUG : rdi rsi fff0 10-05 01:00:18.565 4406 4406 F DEBUG : rbp 7eb0ccf01400 rsp 7eb0ccf01310 rip 7eb0cd2892ac 10-05 01:00:18.566 4406 4406 F DEBUG : 10-05 01:00:18.566 4406 4406 F DEBUG : backtrace: 10-05 01:00:18.566 4406 4406 F DEBUG : #00 pc 000202ac /system/vendor/lib64/hw/hwcomposer.drm.so (android::DrmDisplayCompositor::CommitFrame(android::DrmDisplayComposition*, bool)+668) 10-05 01:00:18.566 4406 4406 F DEBUG : #01 pc 0001e72b /system/vendor/lib64/hw/hwcomposer.drm.so (android::DrmDisplayCompositor::ApplyFrame(std::__1::unique_ptr>, int)+27) 10-05 01:00:18.566 4406 4406 F DEBUG : #02 pc 0001e68e /system/vendor/lib64/hw/hwcomposer.drm.so (android::DrmDisplayCompositor::FrameWorker::Routine()+318) 10-05 01:00:18.566 4406 4406 F DEBUG : #03 pc 000372e8 /system/vendor/lib64/hw/hwcomposer.drm.so (android::Worker::InternalRoutine()+72) 10-05 01:00:18.566 4406 4406 F DEBUG : #04 pc 00037466 /system/vendor/lib64/hw/hwcomposer.drm.so (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ptrINS_15__thread_structENS_14default_deleteIS3_MN7android6WorkerEFvvEPS8_EPvSD_+54) 10-05 01:00:18.566 4406 4406 F DEBUG : #05 pc 00092bfb /system/lib64/libc.so (__pthread_start(void*)+27) 10-05 01:00:18.566 4406 4406 F DEBUG : #06 pc 0002af0d /system/lib64/libc.so (__start_thread+61) - LOG END - It seems the problem doesn't happen when using the Android 8.1-r3 image, or I didn't try long enough. As I said, using SDL "solves" the problem. One could argue the problem is with Android itself, but then why would it react differently depending on which frontend, GTK or SDL, is used ? Shouldn't it be transparent to the emulated system ? I saw other people reporting the problem on a russian forum (don't remember which one), not anywhere else (I searched only for Android problems with virglrenderer). I had to translate since I'm not russian myself (I'm french). Interestingly, shortly after reporting the bug here, I was contacted by a Russian who confirmed he had the same problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896250 Title: SDL support is missing while virglrenderer has problems with GTK To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1896250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
(For those who read # 132, please ignore it and this is re-written version.) For the Synaptics touchpad, the following experiment would make the touchpad work. Could you share the result with the ELAN touchpad? 1. Install hid-tools and start hid-recorder as the root user ```bash # install hid-tools # If it's not provided by your distribution's package manager, you can install it by pip # sudo pip install hid-tools # run hid-recorder and choose the device having name "MSFT*" $ sudo hid-recorder Available devices: /dev/hidraw0: MSFT0001:00 06CB:7F28 ``` 2. Run the following sh script as a root ```bash # now open another terminal window # go to gpio's sysfs cd /sys/class/gpio/ # export the pin used by the touchpad echo 386 > export # now you will see a folder named gpio386 created cd gpio386 # change the pin as an output echo out > direction # write 0 to the pin echo 0 > value ``` Now move your finger on the touchpad. See if your cursor moves now and if there is any output from hid-recorder. And then don't touch the touchpad. See if there is any output from hid- recorder. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Affects me as well on Kubuntu 20.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi wangjun, Thank you for testing the script. Sorry I notice there's some problems with the instructions in # 132. And those instructions can't be executed as a single shell script. If you go to /sys/class/gpio, do you see a folder named gpio386? - If yes, cd to gpio386. "echo out > direction". Then "echo 0 > value". Then you check the output from hid-recorder. - If no, please checck another re-written version of # 132 as follows. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@coiby xu, terminal window 1: - [ra@localhost ~]$ uname -r 5.8.13-301.fc33.x86_64 [ra@localhost ~]$ sudo hid-recorder [sudo] password for ra: Available devices: /dev/hidraw0: MSFT0001:00 04F3:3140 /dev/hidraw1: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw2: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw3: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw4: ITE Tech. Inc. ITE Device(8910) Select the device event number [0-4]: 0 # MSFT0001:00 04F3:3140 # 0x05, 0x01,// Usage Page (Generic Desktop)0 # 0x09, 0x02,// Usage (Mouse) 2 # 0xa1, 0x01,// Collection (Application)4 # 0x85, 0x01,// Report ID (1) 6 # 0x09, 0x01,// Usage (Pointer)8 # 0xa1, 0x00,// Collection (Physical) 10 # 0x05, 0x09,// Usage Page (Button) 12 # 0x19, 0x01,// Usage Minimum (1) 14 # 0x29, 0x02,// Usage Maximum (2) 16 # 0x15, 0x00,// Logical Minimum (0) 18 # 0x25, 0x01,// Logical Maximum (1) 20 # 0x75, 0x01,// Report Size (1) 22 # 0x95, 0x02,// Report Count (2) 24 # 0x81, 0x02,// Input (Data,Var,Abs) 26 # 0x95, 0x06,// Report Count (6) 28 # 0x81, 0x03,// Input (Cnst,Var,Abs) 30 # 0x05, 0x01,// Usage Page (Generic Desktop) 32 # 0x09, 0x30,// Usage (X) 34 # 0x09, 0x31,// Usage (Y) 36 # 0x09, 0x38,// Usage (Wheel) 38 # 0x15, 0x81,// Logical Minimum (-127)40 # 0x25, 0x7f,// Logical Maximum (127) 42 # 0x75, 0x08,// Report Size (8) 44 # 0x95, 0x03,// Report Count (3) 46 # 0x81, 0x06,// Input (Data,Var,Rel) 48 # 0x05, 0x0c,// Usage Page (Consumer Devices) 50 # 0x0a, 0x38, 0x02, // Usage (AC Pan)52 # 0x95, 0x01,// Report Count (1) 55 # 0x81, 0x06,// Input (Data,Var,Rel) 57 # 0x75, 0x08,// Report Size (8) 59 # 0x95, 0x03,// Report Count (3) 61 # 0x81, 0x03,// Input (Cnst,Var,Abs) 63 # 0xc0, // End Collection 65 # 0x06, 0x00, 0xff, // Usage Page (Vendor Defined Page 1) 66 # 0x85, 0x0d,// Report ID (13) 69 # 0x09, 0xc5,// Usage (Vendor Usage 0xc5) 71 # 0x15, 0x00,// Logical Minimum (0)73 # 0x26, 0xff, 0x00, // Logical Maximum (255) 75 # 0x75, 0x08,// Report Size (8)78 # 0x95, 0x04,// Report Count (4) 80 # 0xb1, 0x02,// Feature (Data,Var,Abs) 82 # 0x85, 0x0c,// Report ID (12) 84 # 0x09, 0xc6,// Usage (Vendor Usage 0xc6) 86 # 0x96, 0x10, 0x04, // Report Count (1040)88 # 0x75, 0x08,// Report Size (8)91 # 0xb1, 0x02,// Feature (Data,Var,Abs) 93 # 0x85, 0x0b,// Report ID (11) 95 # 0x09, 0xc7,// Usage (Vendor Usage 0xc7) 97 # 0x95, 0x42,// Report Count (66) 99 # 0x75, 0x08,// Report Size (8)101 # 0xb1, 0x02,// Feature (Data,Var,Abs) 103 # 0x09, 0x01,// Usage (Vendor Usage 1) 105 # 0x85, 0x5d,// Report ID (93) 107 # 0x95, 0x1f,// Report Count (31) 109 # 0x75, 0x08,// Report Size (8)111 # 0x81, 0x06,// Input (Data,Var,Rel) 113 # 0xc0, // End Collection 115 # 0x05, 0x0d,// Usage Page (Digitizers) 116 # 0x09, 0x05,// Usage (Touch Pad) 118 # 0xa1, 0x01,// Collection (Application)
[Bug 1887312] Re: [SRU] Cinnamon session doesn't shutdown until all apps close regardless if they act to Cinnamon's logout request
Alright-I see some activity so I'll go through these: "Joshua, there are some unnecessary changes in your debdiff (trailing white space), e.g. - case CSM_MANAGER_LOGOUT_SHUTDOWN_INTERACT: + case CSM_MANAGER_LOGOUT_SHUTDOWN_INTERACT:" Most of the time I blame Linux Mint. Atom automatically deletes trailing white spaces-so I'll check the diff to see if it removed the whitespace or added whitespaces. But if you really want I can manually remove it. "Also, this: Bug: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1887312 Bug-: https://github.com/linuxmint/cinnamon/issues/3752 should be: Bug-Ubuntu: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1887312 Bug: https://github.com/linuxmint/cinnamon/issues/3752; Okay. I'll fix that ASAP -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887312 Title: [SRU] Cinnamon session doesn't shutdown until all apps close regardless if they act to Cinnamon's logout request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon-session/+bug/1887312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1866471] Re: no se actuliza ubuntu 18.04 a 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1866471 Title: no se actuliza ubuntu 18.04 a 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1866471/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
sorry, default fedora kernel with the option CONFIG_GPIO_SYSFS is not set. i will set it and build new kernel to test the above script. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@coiby xu, with my elan touchpad , [ra@localhost ~]$ sudo pip install hid-tools [sudo] password for ra: WARNING: Running pip install with root privileges is generally not a good idea. Try `pip install --user` instead. Collecting hid-tools Using cached hid-tools-0.2.tar.gz (51 kB) Collecting parse Downloading parse-1.18.0.tar.gz (30 kB) Collecting pyudev Using cached pyudev-0.22.0.tar.gz (85 kB) Requirement already satisfied: six in /usr/lib/python3.9/site-packages (from pyudev->hid-tools) (1.15.0) Using legacy 'setup.py install' for hid-tools, since package 'wheel' is not installed. Using legacy 'setup.py install' for parse, since package 'wheel' is not installed. Using legacy 'setup.py install' for pyudev, since package 'wheel' is not installed. Installing collected packages: parse, pyudev, hid-tools Running setup.py install for parse ... done Running setup.py install for pyudev ... done Running setup.py install for hid-tools ... done Successfully installed hid-tools-0.2 parse-1.18.0 pyudev-0.22.0 [ra@localhost ~]$ sudo hid-recorder Available devices: /dev/hidraw0: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw1: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw2: Microsoft Microsoft® Nano Transceiver v1.0 /dev/hidraw3: MSFT0001:00 04F3:3140 /dev/hidraw4: ITE Tech. Inc. ITE Device(8910) Select the device event number [0-4]: 3 # MSFT0001:00 04F3:3140 # 0x05, 0x01,// Usage Page (Generic Desktop)0 # 0x09, 0x02,// Usage (Mouse) 2 # 0xa1, 0x01,// Collection (Application)4 # 0x85, 0x01,// Report ID (1) 6 # 0x09, 0x01,// Usage (Pointer)8 # 0xa1, 0x00,// Collection (Physical) 10 # 0x05, 0x09,// Usage Page (Button) 12 # 0x19, 0x01,// Usage Minimum (1) 14 # 0x29, 0x02,// Usage Maximum (2) 16 # 0x15, 0x00,// Logical Minimum (0) 18 # 0x25, 0x01,// Logical Maximum (1) 20 # 0x75, 0x01,// Report Size (1) 22 # 0x95, 0x02,// Report Count (2) 24 # 0x81, 0x02,// Input (Data,Var,Abs) 26 # 0x95, 0x06,// Report Count (6) 28 # 0x81, 0x03,// Input (Cnst,Var,Abs) 30 # 0x05, 0x01,// Usage Page (Generic Desktop) 32 # 0x09, 0x30,// Usage (X) 34 # 0x09, 0x31,// Usage (Y) 36 # 0x09, 0x38,// Usage (Wheel) 38 # 0x15, 0x81,// Logical Minimum (-127)40 # 0x25, 0x7f,// Logical Maximum (127) 42 # 0x75, 0x08,// Report Size (8) 44 # 0x95, 0x03,// Report Count (3) 46 # 0x81, 0x06,// Input (Data,Var,Rel) 48 # 0x05, 0x0c,// Usage Page (Consumer Devices) 50 # 0x0a, 0x38, 0x02, // Usage (AC Pan)52 # 0x95, 0x01,// Report Count (1) 55 # 0x81, 0x06,// Input (Data,Var,Rel) 57 # 0x75, 0x08,// Report Size (8) 59 # 0x95, 0x03,// Report Count (3) 61 # 0x81, 0x03,// Input (Cnst,Var,Abs) 63 # 0xc0, // End Collection 65 # 0x06, 0x00, 0xff, // Usage Page (Vendor Defined Page 1) 66 # 0x85, 0x0d,// Report ID (13) 69 # 0x09, 0xc5,// Usage (Vendor Usage 0xc5) 71 # 0x15, 0x00,// Logical Minimum (0)73 # 0x26, 0xff, 0x00, // Logical Maximum (255) 75 # 0x75, 0x08,// Report Size (8)78 # 0x95, 0x04,// Report Count (4) 80 # 0xb1, 0x02,// Feature (Data,Var,Abs) 82 # 0x85, 0x0c,// Report ID (12) 84 # 0x09, 0xc6,// Usage (Vendor Usage 0xc6) 86 # 0x96, 0x10, 0x04, // Report Count (1040)88 # 0x75, 0x08,// Report Size (8)91 # 0xb1, 0x02,// Feature (Data,Var,Abs) 93 # 0x85, 0x0b,// Report ID (11) 95 # 0x09, 0xc7,// Usage (Vendor Usage
[Bug 1871306] Re: No sound from internal card chtmax98090 - missing UCM2 files in alsa-ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3
thanks for working on this @Hui and @Gabirele Today i added ppa:hui.wang/pa-testing and installed alsa-ucm-conf followed by an "apt update; apt upgrade" when i rebooted the system after that, i was so happy to have the sound working. sound worked from browser (while watching youtube videos) and also from media players. But when I opened the pulse audio volume control, i noticed a strange behavior. Suddenly the sound became garbled. I could still hear the sound but it was very garbled. Same behavior observed when i tried to do a zoom conference. The sound on zoom was also very much garbled. Is there a way to fix this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1871306 Title: No sound from internal card chtmax98090 - missing UCM2 files in alsa- ucm-conf 1.2.2, available in alsa-ucm-conf 1.2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1871306/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1886148] Re: failure to boot groovy daily
On Sun, Oct 04, 2020 at 01:14:43PM -, Marcos Nascimento wrote: > In previous version images the /isolinux folder existed. Isn't it the > case that it's necessary for systems that are experiencing problems? No. The isolinux directory is an internal implementation detail of using the isolinux bootloader, which was only ever used for BIOS booting. We are not using the isolinux bootloader anymore, and the remaining boot failures reported are not with BIOS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898484] [NEW] During release-update is old version 20.04 shown instead of 20.10
Public bug reported: I did update from 20.04 to 20.10. There are some steps (preparing, configuration, download, installation, cleaning up, restart). While doing the download in "system-update-window" the old version ist shown: Ubuntu is updated to 20.04 (instead of 20.10). I have a screenshot, which i will attach below. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.11 ProcVersionSignature: Ubuntu 5.8.0-20.21-generic 5.8.10 Uname: Linux 5.8.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu48 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun Oct 4 23:10:14 2020 InstallationDate: Installed on 2020-03-21 (196 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) PackageArchitecture: all ProcEnviron: LANGUAGE=de_AT:de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to groovy on 2020-10-03 (1 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy ** Attachment added: "Ubuntu update to Groovy => wrong (old) version is shown in update window" https://bugs.launchpad.net/bugs/1898484/+attachment/5417596/+files/Ubuntu_Groovy_falsche_Version_wird_angezeigt.png ** Summary changed: - During releas-update is old version 20.04 shown instead 20.10 + During release-update is old version 20.04 shown instead 20.10 ** Summary changed: - During release-update is old version 20.04 shown instead 20.10 + During release-update is old version 20.04 shown instead of 20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898484 Title: During release-update is old version 20.04 shown instead of 20.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898484/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
No Matter now. Thank you. I simpl complete installation without chosing no option and let the program start by itself and tell not to do download updates during installation. Now installation is complete, system works and tomorrow i do all the updates and let you know. Thanks for support. Bye ! > Il 04/10/2020 21:57 Curtis Schroeder <1871...@bugs.launchpad.net> ha scritto: > > > Well, I see the 20.04.1 live image still has a problem installing > (NVIDIA?) drivers during the initial install that was in the original > 20.04 release. I shall try again without the drivers install option. I > was trying a minimal clean install this time if that makes any > difference for the analysis. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871268 > > Title: > Installation fails when "Install Third-Party Drivers" is selected > > Status in GLibC: > New > Status in Ubuntu CD Images: > Fix Released > Status in apt package in Ubuntu: > Confirmed > Status in glibc package in Ubuntu: > Invalid > Status in apt source package in Bionic: > Confirmed > Status in glibc source package in Bionic: > Fix Released > Status in apt source package in Focal: > Confirmed > Status in glibc source package in Focal: > Invalid > > Bug description: > Please use the latest daily installer images if you would like to enable > third-party drivers during installation: > http://www.cdimage.ubuntu.com/focal/daily-live/current/ > > [Original Bug Text] > > Test Case > 1. Install Ubuntu Desktop on hardware with an nVidia card and select to > install 3rd party drivers > 2. Proceed with installation > > The following error message is displayed in /var/log/syslog > /plugininstall.py: Verifying downloads ... > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: > "Version: '4.4.10-10ubuntu4' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: > '1.2.11.dfsg-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: > '1.0.9-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: > '1.1.3-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: > '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: > '1.3.4-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: > '3.6.0-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: > '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: > '1.1.5-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: > '5.0.3-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: > "Version: '1.1.4-1build1' not found." > /plugininstall.py: Downloads verified successfully > ubiquity: Error in function: install > /plugininstall.py: Exception during installation: > /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , > E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see > man 5 apt.conf under APT::Immediate-Configure for details. (2) > /plugininstall.py: > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubiquity 20.04.9 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu22 > Architecture: amd64 > CasperVersion: 1.442 > Date: Mon Apr 6 20:17:07 2020 > InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity > initrd=/casper/initrd quiet splash --- > LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) > ProcEnviron: > LANGUAGE=es_EC.UTF-8 >
[Bug 1898473] Re: canonical-livepatch snap not working
** Package changed: ubuntu => canonical-livepatch-client -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898473 Title: canonical-livepatch snap not working To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-livepatch-client/+bug/1898473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
No Matter now. Thank you. I simpl complete installation without chosing no option and let the program start by itself and tell not to do download updates during installation. Now installation is complete, system works and tomorrow i do all the updates and let you know. Thanks for support. Bye ! > Il 04/10/2020 13:15 Jon Brase <1871...@bugs.launchpad.net> ha scritto: > > > ** Attachment added: "The attachment for my comment above does not seem to > have taken. This is /var/log/syslog for a failed ground-up Kubuntu 20.04 > installation" > > https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417422/+files/syslog > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1871268 > > Title: > Installation fails when "Install Third-Party Drivers" is selected > > Status in GLibC: > New > Status in Ubuntu CD Images: > Fix Released > Status in apt package in Ubuntu: > Confirmed > Status in glibc package in Ubuntu: > Invalid > Status in apt source package in Bionic: > Confirmed > Status in glibc source package in Bionic: > Fix Released > Status in apt source package in Focal: > Confirmed > Status in glibc source package in Focal: > Invalid > > Bug description: > Please use the latest daily installer images if you would like to enable > third-party drivers during installation: > http://www.cdimage.ubuntu.com/focal/daily-live/current/ > > [Original Bug Text] > > Test Case > 1. Install Ubuntu Desktop on hardware with an nVidia card and select to > install 3rd party drivers > 2. Proceed with installation > > The following error message is displayed in /var/log/syslog > /plugininstall.py: Verifying downloads ... > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: > "Version: '4.4.10-10ubuntu4' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: > '9.3.0-1ubuntu2' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: > '1.2.11.dfsg-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: > '1.0.9-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: > '1.1.3-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: > '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: > '1.3.4-0ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: > '3.6.0-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: > '1.6.9-2ubuntu1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: > '1.1.5-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: > '5.0.3-1' not found." > /plugininstall.py: Failed to find package object for > /cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: > "Version: '1.1.4-1build1' not found." > /plugininstall.py: Downloads verified successfully > ubiquity: Error in function: install > /plugininstall.py: Exception during installation: > /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , > E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see > man 5 apt.conf under APT::Immediate-Configure for details. (2) > /plugininstall.py: > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubiquity 20.04.9 > ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 > Uname: Linux 5.4.0-21-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu22 > Architecture: amd64 > CasperVersion: 1.442 > Date: Mon Apr 6 20:17:07 2020 > InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity > initrd=/casper/initrd quiet splash --- > LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) > ProcEnviron: > LANGUAGE=es_EC.UTF-8 > PATH=(custom, no user) > XDG_RUNTIME_DIR= >
[Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
** Tags added: alsa audio no-sound volume -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898482] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898482 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1898482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898483] [NEW] [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
Public bug reported: The volume bars in sound settings react to what sound is played correctly but I can't hear any sounds ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65 Uname: Linux 5.4.0-49-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 02:22:25 2020 InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Lake PCH cAVS - sof-hda-dsp Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: paramvir 1924 F pulseaudio /dev/snd/pcmC0D0p: paramvir 1924 F...m pulseaudio /dev/snd/pcmC0D6c: paramvir 1924 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.0 dmi.board.name: 0K1VDX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.0:bd07/22/2019:svnDellInc.:pnInspiron7591:pvr:rvnDellInc.:rn0K1VDX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7591 dmi.product.sku: 0923 dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-10-04T03:10:08.906233 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898483] Re: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected
#New Changes options snd-hda-intel model=dell-inspiron-7559 options snd-hda-intel probe_mask=0x1 I added this to alsa-base.conf.txt following this forum https://ubuntuforums.org/showthread.php?t=2421187 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898483 Title: [Inspiron 7591, Realtek ALC3254, Speaker, Internal] No sound at all despite the sound bars moving fine and device detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1898483/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898482] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Public bug reported: do-release-upgrade said it would need 1.5G free diskspace, used 1.7G and the disk was then full. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 4.15.0-118.119-generic 4.15.18 Uname: Linux 4.15.0-118-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Oct 4 20:45:27 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-04 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898482 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1898482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898296] Re: FFe: Please accept sshguard 2.3.1-1ubuntu3
Thanks, uploaded to Unapproved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898296 Title: FFe: Please accept sshguard 2.3.1-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sshguard/+bug/1898296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898473] Re: canonical-livepatch snap not working
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1898473/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898473 Title: canonical-livepatch snap not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898473/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898476] Re: Updating from 16.04 to 18.04 craches
** Tags added: xenial2bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898476 Title: Updating from 16.04 to 18.04 craches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898476] Re: Updating from 16.04 to 18.04 craches
** Package changed: ubuntu => ubuntu-release-upgrader (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898476 Title: Updating from 16.04 to 18.04 craches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1898476/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1426216] Re: pci driver messages - BAR 13: no space for
I'm on Debian sid with a T470 Thinkpad (Linux t470 5.8.0-1-amd64 #1 SMP Debian 5.8.7-1 (2020-09-05) x86_64 GNU/Linux) and this same bug affects me too. I know, my system is not Ubuntu, but I think it's important to let you know that this might be a problem with the upstream kernel code, as opposed to the Ubuntu or Debian packaged kernel. Maybe it's related to something Lenovo specific. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1426216 Title: pci driver messages - BAR 13: no space for To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1426216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
Well, I see the 20.04.1 live image still has a problem installing (NVIDIA?) drivers during the initial install that was in the original 20.04 release. I shall try again without the drivers install option. I was trying a minimal clean install this time if that makes any difference for the analysis. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876991] Re: Touchpad started appearing both as a touchpad and as a mouse input devices after upgrade to 20.04
I am also having a very similar problem on my Dell Inspiron 5390 runnin ubuntu 20.04.1 LTS. The output from running xinput reads: ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ DELL091F:00 27C6:01F0 Mouse id=10 [slave pointer (2)] ⎜ ↳ DELL091F:00 27C6:01F0 Touchpadid=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Video Bus id=6[slave keyboard (3)] ↳ Power Button id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=9[slave keyboard (3)] ↳ Intel HID events id=12 [slave keyboard (3)] ↳ Intel HID 5 button array id=13 [slave keyboard (3)] ↳ Dell WMI hotkeys id=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=15 [slave keyboard (3)] After booting the laptop up I have no problems with the touchpad, I also noticed that after a cold boot if i run "xinput test 11" and "xinput test 10" only device 11 (touchpad) registers any inputs. However, once i suspend the laptop and then wake it the touchpad loses lots of functions (basically functions like a mouse no gestures work) and right click also becomes middle click. If i again run both of the xinput tests again the only device that registers inputs is now device ID 10 (the one labelled mouse) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876991 Title: Touchpad started appearing both as a touchpad and as a mouse input devices after upgrade to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1876991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
