[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1844426 Title: Impossible to set up Livepatch on Ubuntu MATE Status in Ubuntu MATE: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: In Ubuntu MATEE 18.04, in the Software Properties window (available from Software Boutique > Preferences > Show Software Sources > Manage Repositories, among other places), there is a Livepatch tab. This tab says "To use Livepatch, you need to sign in" and provides a "Sign In..." button. This button launches an empty version of gnome-control-center with no icons in it. If one is technically adept, it is possible to do what (I think) that button is trying to do by launching g-c-c directly in a terminal and overriding the desktop, thus: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts This online accounts window permits attempting to add an Ubuntu One account. However, when one tries, a window pops up with a place to add one's Ubuntu One username and password, but the window has no Submit button; there is no way to actually initiate sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1844426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: software-properties (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1844426 Title: Impossible to set up Livepatch on Ubuntu MATE Status in Ubuntu MATE: Confirmed Status in software-properties package in Ubuntu: Confirmed Bug description: In Ubuntu MATEE 18.04, in the Software Properties window (available from Software Boutique > Preferences > Show Software Sources > Manage Repositories, among other places), there is a Livepatch tab. This tab says "To use Livepatch, you need to sign in" and provides a "Sign In..." button. This button launches an empty version of gnome-control-center with no icons in it. If one is technically adept, it is possible to do what (I think) that button is trying to do by launching g-c-c directly in a terminal and overriding the desktop, thus: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts This online accounts window permits attempting to add an Ubuntu One account. However, when one tries, a window pops up with a place to add one's Ubuntu One username and password, but the window has no Submit button; there is no way to actually initiate sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1844426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1844426] Re: Impossible to set up Livepatch on Ubuntu MATE
** Also affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1844426 Title: Impossible to set up Livepatch on Ubuntu MATE Status in Ubuntu MATE: Confirmed Status in software-properties package in Ubuntu: New Bug description: In Ubuntu MATEE 18.04, in the Software Properties window (available from Software Boutique > Preferences > Show Software Sources > Manage Repositories, among other places), there is a Livepatch tab. This tab says "To use Livepatch, you need to sign in" and provides a "Sign In..." button. This button launches an empty version of gnome-control-center with no icons in it. If one is technically adept, it is possible to do what (I think) that button is trying to do by launching g-c-c directly in a terminal and overriding the desktop, thus: env XDG_CURRENT_DESKTOP=GNOME gnome-control-center online-accounts This online accounts window permits attempting to add an Ubuntu One account. However, when one tries, a window pops up with a place to add one's Ubuntu One username and password, but the window has no Submit button; there is no way to actually initiate sign in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1844426/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298
Related problem: (Headphones work, no speaker volume whatsoever) w/ Notebook Pen 9 (Nvidia) #NP950SBE-X01US on Ubuntu 0.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1834566 Title: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298 Status in alsa-driver package in Ubuntu: Confirmed Bug description: Unable to get system speakers working running 19.04. At max volume, sound is barely perceptible through headphones. Pavucontrol shows sounds is present, but no amount of adjustments makes a difference. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 3355 F pulseaudio CurrentDesktop: KDE Date: Fri Jun 28 00:44:13 2019 InstallationDate: Installed on 2019-06-05 (22 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P02AHK.029.190425.PS dmi.board.asset.tag: No Asset Tag dmi.board.name: NP930MBE-K04US dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A: dmi.product.family: Notebook 9 Series dmi.product.name: 930MBE dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK dmi.product.version: P02AHK dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1834566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1869981] Re: Printer notification every day at midnight
[Expired for cups (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cups (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1869981 Title: Printer notification every day at midnight Status in cups package in Ubuntu: Expired Bug description: Every day, all my 20.04 machines get a notification that the printer in my house has been detected. The printer works fine and is already added. So not sure why I need to be told repeatedly that I have a printer on the network? (see screenshot) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups 2.3.1-9ubuntu1 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-0ubuntu21 Architecture: amd64 CupsErrorLog: CurrentDesktop: ubuntu:GNOME Date: Wed Apr 1 00:00:31 2020 InstallationDate: Installed on 2020-03-01 (30 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301) Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/ MachineType: LENOVO 20BV001BUK Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: JBET73WW (1.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV001BUK dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV001BUK dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1869981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Oh and it can be a bug in X, please give Wayland a try. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mesa-utils package in Ubuntu: New Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with noveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Let's suppose it doesn't use reverse prime, please test latest drm-tip kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mesa-utils package in Ubuntu: New Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with noveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Thank you Yevhen (yevhen.b). It works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1746582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)
This bug was fixed in the package initramfs-tools - 0.137ubuntu9 --- initramfs-tools (0.137ubuntu9) groovy; urgency=medium * Document add_mountroot_fail_hook correctly. initramfs-tools (0.137ubuntu8) groovy; urgency=medium * Partially revert 0.133ubuntu12 upload: "* scripts/functions: Fix args in the add_mountroot_fail_check function." The arguments were correct, as used by lvm2 hook. LP: #1871154 initramfs-tools (0.137ubuntu7) groovy; urgency=medium * Fix copying libgcc_s when there is optimized pthreads installed. LP: #1880853 -- Dimitri John Ledkov Sat, 30 May 2020 16:33:08 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: In Progress Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
This bug was fixed in the package initramfs-tools - 0.137ubuntu9 --- initramfs-tools (0.137ubuntu9) groovy; urgency=medium * Document add_mountroot_fail_hook correctly. initramfs-tools (0.137ubuntu8) groovy; urgency=medium * Partially revert 0.133ubuntu12 upload: "* scripts/functions: Fix args in the add_mountroot_fail_check function." The arguments were correct, as used by lvm2 hook. LP: #1871154 initramfs-tools (0.137ubuntu7) groovy; urgency=medium * Fix copying libgcc_s when there is optimized pthreads installed. LP: #1880853 -- Dimitri John Ledkov Sat, 30 May 2020 16:33:08 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1880853 Title: libc6-lse lets update-initramfs fail on AWS m6g instances Status in cloud-images: New Status in btrfs-progs package in Ubuntu: Invalid Status in glibc package in Ubuntu: Invalid Status in initramfs-tools package in Ubuntu: Fix Released Status in btrfs-progs source package in Focal: Invalid Status in glibc source package in Focal: Invalid Status in initramfs-tools source package in Focal: In Progress Bug description: [Impact] * update-initramfs -u fails on arm64 m6g instances in AWS [Test Case] * launch m6g instance in AWS * install libc6-lse (if not installed) * run $ update-initramfs -u * It should suceed [Regression Potential] * Adding one more path to libgcc_s1 resolution. This will still fail if something compiles libc6 for _two_ optimisations like /lib/$arch/foo/bar/libpthread. [Other Info] * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the initrd libgcc_s1 must be copied in too. However the logic to find matching libgcc_s1 is broken for optimizied builds of libc6 without optimized build of libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these issues. * Original bug report With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor : 0 BogoMIPS : 243.75 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer: 0x41 CPU architecture: 8 CPU variant: 0x3 CPU part : 0xd0c CPU revision : 1 ProcEnviron: LANG=C.UTF-8 TERM=screen-256color PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30 SourcePackage: glibc Tags: focal ec2-images Uname: Linux 5.4.0-1009-aws aarch64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions -- Mailin
[Touch-packages] [Bug 1871154] Re: Error message displayed during boot (mountroot hook, premount)
This bug was fixed in the package lvm2 - 2.03.07-1ubuntu3 --- lvm2 (2.03.07-1ubuntu3) groovy; urgency=medium * Revert "Fix incorrect path to mountroot fail hook. LP: #1871154" regression is in the initramfs-tools package. lvm2 (2.03.07-1ubuntu2) groovy; urgency=medium * Fix incorrect path to mountroot fail hook. LP: #1871154 -- Dimitri John Ledkov Sat, 30 May 2020 15:02:01 +0100 ** Changed in: lvm2 (Ubuntu) Status: Invalid => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1871154 Title: Error message displayed during boot (mountroot hook, premount) Status in initramfs-tools package in Ubuntu: Fix Committed Status in lvm2 package in Ubuntu: Fix Released Status in initramfs-tools source package in Focal: In Progress Status in lvm2 source package in Focal: Invalid Bug description: [Impact] * People using lvm2 on ubuntu focal are getting a strange and weird message due to a wrong path [Test Case] * Install lvm2 on Ubuntu 20.04 [Regression Potential] * Low, the fix is already part of groovy [Other info] Hi, my Ubuntu system uses LVM2 for its root file system. It boots correctly, but an ugly error message is displayed during boot. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lvm2 2.03.07-1ubuntu1 Uname: Linux 5.6.2-050602-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: KDE Date: Mon Apr 6 17:59:03 2020 SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Update: If I adjust the minimum resolution, sometimes appears the second desktop, but instantly disappear then. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in mesa-utils package in Ubuntu: New Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: New Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with noveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881498] Re: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
** Attachment added: "The screens, how I order them before I click apply." https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881498/+attachment/5379186/+files/Screenshot%20from%202020-05-31%2017-22-04.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
[Touch-packages] [Bug 1720693] Re: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all
** Changed in: alsa-driver (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1720693 Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all Status in alsa-driver package in Ubuntu: Fix Released Bug description: There is no sound from the front jack. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Sun Oct 1 17:49:29 2017 InstallationDate: Installed on 2017-06-08 (115 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: Error: command ['pkexec', 'fuser', '-v', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/by-path', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Symptom_Jack: Black Headphone Out, Front Symptom_Type: No sound at all Symptom_amixerStderr: a m i x e r : M i x e r h w : P C H l o a d e r r o r : I n v a l i d a r g u m e n t Title: [10MVCTO1WW, Realtek ALC294, Black Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: M1AKT17A dmi.board.name: 310B dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN 3259612472445 dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrM1AKT17A:bd04/13/2017:svnLENOVO:pn10MVCTO1WW:pvrThinkCentreM910q:rvnLENOVO:rn310B:rvrSDK0J40709WIN3259612472445:cvnLENOVO:ct3:cvrNone: dmi.product.name: 10MVCTO1WW dmi.product.version: ThinkCentre M910q dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1720693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881504] [NEW] cross-testing essential packages fails
Public bug reported: Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz ... autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1 autopkgtest [19:51:38]: build not needed autopkgtest [19:51:38]: test simple-gzip: preparing testbed Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages will be REMOVED: gzip The following NEW packages will be installed: build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0 libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22 libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1 linux-libc-dev WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! gzip 0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. E: Failed to process build dependencies ... ** Affects: autopkgtest (Ubuntu) Importance: Undecided Status: New ** Affects: gzip (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse ** Also affects: gzip (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1881504 Title: cross-testing essential packages fails Status in autopkgtest package in Ubuntu: New Status in gzip package in Ubuntu: New Bug description: Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz ... autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1 autopkgtest [19:51:38]: build not needed autopkgtest [19:51:38]: test simple-gzip: preparing testbed Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get the build dependencies Reading package lists... Building dependency tree... Reading state information... Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done The following packages will be REMOVED: gzip The following NEW packages will be installed: build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0 libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22 libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1 linux-libc-dev WARNING: The following essential packages will be removed. This should NOT be done unless you know exactly what you are doing! gzip 0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded. E: Essential packages were removed and -y was used without --allow-remove-essential. E: Failed to process build dependencies ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1881504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881502] [NEW] package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/shar
Public bug reported: Errors created when trying to install TeamViewer on Jetson Nano ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] Uname: Linux 4.9.140-tegra aarch64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: arm64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 31 14:35:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf GraphicsCard: ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,0 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1125 core_edp_ma=4000 tegra_fbmem=0x14@0x92cb4000 is_hdmi_initialised=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: mesa Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf UpgradeStatus: No upgrade log present (probably fresh install) version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package arm64 bionic compiz-0.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1881502 Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] failed to install/upgrade: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf Status in mesa package in Ubuntu: New Bug description: Errors created when trying to install TeamViewer on Jetson Nano ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libegl-mesa0 19.2.8-0ubuntu0~18.04.3 [modified: usr/share/glvnd/egl_vendor.d/50_mesa.json] Uname: Linux 4.9.140-tegra aarch64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: arm64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Sun May 31 14:35:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ErrorMessage: trying to overwrite shared '/usr/share/glvnd/egl_vendor.d/50_mesa.json', which is different from other instances of package libegl-mesa0:armhf GraphicsCard: ProcKernelCmdLine: tegraid=21.1.2.0.0 ddr_die=4096M@2048M section=512M memtype=0 vpr_resize usb_port_owner_info=0 lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb no_console_suspend=1 console=ttyS0,115200n8 debug_uartport=lsport,0 earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 lp0_vec=0x1000@0xff78 core_edp_mv=1125 core_edp_ma=4000 tegra_fbmem=0x14@0x92cb4000 is_hdmi_initialised=1 root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0root=/dev/mmcblk0p1 rw rootwait rootfstype=ext4 console=ttyS0,115200n8 console=tty0 fbcon=map:0 net.ifnames=0 quiet Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.12ubuntu0.1 SourcePackage: mesa Title: package libegl-mesa0 19.2.8-0ubuntu0~18.04
[Touch-packages] [Bug 1881494] Re: suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
** Description changed: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. + Also the computer never really goes into standby. The cpu fan is running + all the time and the power button is fully lighted up. Nevertheless, I + need to press CTRL to "wake" it, so I can access it via SSH. + I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB + Tested EFI and BIOS bootmode. Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: - Enable hibernation (suspend to disk) and use instead of suspend to ram. + Enable hibernation (suspend to disk) and use instead of suspend to ram (standby). - What didn't helped: - Kernel parameters (some actually prevented the system from booting): no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush + What didn't help: + Kernel parameters: no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async + Upgrading kernel from 5.4 to: 5.6.0-1010-oem + + Using the kernel parameters + no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 + idle=nowait amd_iommu=flush + and doing + echo mem > /sys/power/state + before suspend made the system acutally not crash. + Nevertheless, the cpu fan and the power button stay full on/lighted. So the system doesn't really go to standby either. + + I'll try to find the minimal combination of kernel parameters. + nomodeset seems to be essential, but not sufficient. + Without nomodeset the system wakes again for a few seconds, but freezes a moment later (ssh still accessible). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: Hewlett-Packard Company Picasso [103c:85de] + Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 9YN58EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu
[Touch-packages] [Bug 1881498] [NEW] Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04
Public bug reported: Since I upgraded from Ubuntu 19.10 to 20.04 my multi monitor setup is broken. I put the screens into the shape of an H. The center screen is in landscape and to each side one screen in portrait/pivot orientation. I expected to rotate the virtual screens of the outer monitors into portrait mode as it was possible before. Instead the smallest (middle) screen gets scaled extremely in, the virtual screens overlap and just everything about the monitor setup breaks. The resolutions are from left to right 1440p, 1080p, 2160p. I could configure the outer screens to portrait mode over Nvidia X Server, but it doesn't survive a reboot. Also it breaks if I touch the screens over the gnome-control-center. == > apt-cache policy gnome-control-center gnome-control-center: Installed: 1:3.36.2-0ubuntu1 Candidate: 1:3.36.2-0ubuntu1 Version table: *** 1:3.36.2-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 17:29:17 2020 DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-55-generic, x86_64: installed nvidia, 435.21, 5.4.0-33-generic, x86_64: installed virtualbox, 6.1.6, 5.3.0-55-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM204 [GeForce GTX 970] [19da:2370] InstallationDate: Installed on 2019-11-26 (186 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-29 (2 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3802 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII RANGER dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3802:bd03/15/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIRANGER:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Attachment added: "After putting orienting the screens how I want them to be and click apply it gets scrambled like that" https://bugs.launchpad.net/bugs/1881498/+attachment/5379099/+files/Screenshot%20from%202020-05-31%2017-21-31.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881498 Title: Three monitor setup breaks if one+ screen rotated into portrait mode since Ubuntu 20.04 Status in xorg package in Ubuntu: New Bug description: S
[Touch-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
autoconnection works. Besides the auto-connection bug is just with redmi+ubuntu, manual connections (and disconnections) are also useful if you use the same headphone in more than one device. ** Attachment added: "autoconnection after turn phone on" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5379076/+files/philipsSHB3075-autoconnect-good.cap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
I tested a third headphone, Philips SHB3075, in my acer laptop, and autoconnection works, but manual reconnections not. For manual connections is the same than for redmi, i had to try connect a lot of times than it works. ** Attachment added: "Philips SHB3075 cap, manual connection bad" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5379075/+files/philipsSHB3075-manualConnect-bad.cap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881494] [NEW] suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360)
Public bug reported: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram. What didn't helped: Kernel parameters (some actually prevented the system from booting): no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 31 18:43:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Picasso [103c:85de] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ENVY x360 Convertible 13-ar0xxx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1010-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/26/2019 dmi.bios.vendor: AMI dmi.bios.version: F.19 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 85DE dmi.board.vendor: HP dmi.board.version: 41.36 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.19:bd12/26/2019:svnHP:pnHPENVYx360Convertible13-ar0xxx:pvr:rvnHP:rn85DE:rvr41.36:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Envy dmi.product.name: HP ENVY x360 Convertible 13-ar0xxx dmi.product.sku: 9YN58EA#ABD dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 amdgpu apport-bug focal freeze ubuntu ** Summary changed: - suspend to ram (standby) crashes amdgpu + suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881494 Title: suspend to ram (standby) crashes amdgpu (Ryzen-7 Vega - HP Envy x360) Status in xorg package in Ubuntu: New Bug description: suspend to ram crashes amdgpu. System is still accessible via SSH after resume from standby. Happens when X is running (gdm/gnome with 3d acceleration) and also when X is stopped. I'll attach the dmesg output of several attempts. This is the hardware: https://store.hp.com/GermanyStore/Merch/Product.aspx?id=9YN58EA&opt=ABD&sel=NTB Please let me know if I can help tracking this down. I'm a software developer (sadly not a kernel developer), so you can ask dirty technical questions ;-) Workaround: Enable hibernation (suspend to disk) and use instead of suspend to ram. What didn't helped: Kernel parameters (some actually prevented the system from booting): no_console_suspend nomodeset amdgpu.gpu_recovery=1 init_on_free=0 idle=nowait amd_iommu=flush echo mem > /sys/power/state systemctl start suspend.target echo 0 > /sys/power/pm_async ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Uname: Linux 5.6.0-1010-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.2
[Touch-packages] [Bug 1741045] Re: Change the default resample-method to speex-float-N (N > 1) in daemon.conf
I changed the resample-method to soxr-hq, and I'll be testing it for some time. According to the manpage of pulse-daemon.conf "the Soxr resamplers generally offer better quality at less CPU compared to other resamplers, such as speex". So far I think it gives better sound quality than speex-float-1 and auto. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1741045 Title: Change the default resample-method to speex-float-N (N > 1) in daemon.conf Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Bug description: I suggest changing the default resample-method to speex-float-10, instead of speex-float-1, which is the current default now, in /etc/pulse/daemon.conf. It would look like this in daemon.conf: resample-method = speex-float-10 I have always done that since at least 12.04 LTS. I was not satisfied with the sound quality in Ubuntu compared to Windows, so I changed the resample-method. In my day-to-day usage, it gives better sound quality without sacrificing CPU power. I have not tried other resample methods. Maybe there are better options I don't know about. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1696 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 14:37:25 2018 InstallationDate: Installed on 2017-10-02 (92 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1741045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881490] Re: Onboard sound not detected for Zenith ROG after upgrade to 20.04
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1881490 Title: Onboard sound not detected for Zenith ROG after upgrade to 20.04 Status in alsa-driver package in Ubuntu: New Bug description: After upgrading to 20.04, my onboard sound no longer seems to work. The motherboard is ROG Zenith. dmesg shows the following: [9.266092] snd_hda_intel :09:00.1: dmic_detect option is deprecated, pass snd-intel-dspcfg.dsp_driver=1 option instead [9.266556] snd_hda_intel :09:00.1: Disabling MSI [9.266586] snd_hda_intel :09:00.1: Handle vga_switcheroo audio client [9.267181] snd_hda_intel :0b:00.3: Skipping the blacklisted device After searching for this message in kernel source, I happened upon this line: https://github.com/torvalds/linux/blob/052c467cb58748e302a95546925928e637025acc/sound/pci/hda/hda_intel.c#L2082 static const struct pci_device_id driver_blacklist[] = { { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1043, 0x874f) }, /* ASUS ROG Zenith II / Strix */ { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb59) }, /* MSI TRX40 Creator */ { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb60) }, /* MSI TRX40 */ {} }; Which led me to this bug report: https://lore.kernel.org/alsa- devel/20200424061222.19792-1-ti...@suse.de/ I confirmed that the PCI device that is not working appears to match the vendor ID: $ lspci | grep 0b:00.3 0b:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller $ lspci -n | grep 0b:00.3 0b:00.3 0403: 1022:1457 Unfortunately, I am unsure how to test a Ubuntu compatible kernel with these changes but it appears there has been some jiggery pokery in Linux kernel land in this regard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sohail 4693 F pulseaudio /dev/snd/pcmC1D0p: sohail 4693 F...m pulseaudio /dev/snd/controlC0: sohail 4693 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 11:14:39 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-16 (1049 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to focal on 2020-05-24 (6 days ago) dmi.bios.date: 07/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1304 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1304:bd07/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1881490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881490] [NEW] Onboard sound not detected for Zenith ROG after upgrade to 20.04
You have been subscribed to a public bug: After upgrading to 20.04, my onboard sound no longer seems to work. The motherboard is ROG Zenith. dmesg shows the following: [9.266092] snd_hda_intel :09:00.1: dmic_detect option is deprecated, pass snd-intel-dspcfg.dsp_driver=1 option instead [9.266556] snd_hda_intel :09:00.1: Disabling MSI [9.266586] snd_hda_intel :09:00.1: Handle vga_switcheroo audio client [9.267181] snd_hda_intel :0b:00.3: Skipping the blacklisted device After searching for this message in kernel source, I happened upon this line: https://github.com/torvalds/linux/blob/052c467cb58748e302a95546925928e637025acc/sound/pci/hda/hda_intel.c#L2082 static const struct pci_device_id driver_blacklist[] = { { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1043, 0x874f) }, /* ASUS ROG Zenith II / Strix */ { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb59) }, /* MSI TRX40 Creator */ { PCI_DEVICE_SUB(0x1022, 0x1487, 0x1462, 0xcb60) }, /* MSI TRX40 */ {} }; Which led me to this bug report: https://lore.kernel.org/alsa-devel/20200424061222.19792-1-ti...@suse.de/ I confirmed that the PCI device that is not working appears to match the vendor ID: $ lspci | grep 0b:00.3 0b:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller $ lspci -n | grep 0b:00.3 0b:00.3 0403: 1022:1457 Unfortunately, I am unsure how to test a Ubuntu compatible kernel with these changes but it appears there has been some jiggery pokery in Linux kernel land in this regard. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sohail 4693 F pulseaudio /dev/snd/pcmC1D0p: sohail 4693 F...m pulseaudio /dev/snd/controlC0: sohail 4693 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 31 11:14:39 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-07-16 (1049 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: Upgraded to focal on 2020-05-24 (6 days ago) dmi.bios.date: 07/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1304 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1304:bd07/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Onboard sound not detected for Zenith ROG after upgrade to 20.04 https://bugs.launchpad.net/bugs/1881490 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
The distorted audio problem just came back. I think it has something to do with this system being dual boot (Windows 10 and Ubuntu 20.04). When I only use Ubuntu there is no problem. As soon as I stop using Windows and reboot to Ubuntu the noise comes back. It's almost like a turntable loses power and the playback slows down and stops. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860930] Re: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio
** Changed in: alsa-driver (Ubuntu) Status: Fix Released => New ** Changed in: pulseaudio (Ubuntu) Status: Fix Released => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1860930 Title: [Asus GX531GX] Internal speakers are sometimes noisy - bad audio Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: I have an Asus Zephyrus S GX531GX laptop and a pair of Asus Delta USB headphones. When the headphones are plugged in during boot the internal speakers won't work. There is only crackling sound coming from them. It doesn't help in I unplug the headphones. There is no problem if they are not plugged in during boot. I'm using Ubuntu 19.10. Please let me know if you need more information. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Jan 26 19:26:35 2020 InstallationDate: Installed on 2019-12-19 (38 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=hu_HU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GX531GXR.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GX531GXR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGX531GXR.304:bd06/28/2019:svnASUSTeKCOMPUTERINC.:pnZephyrusSGX531GXR_GX531GXR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGX531GXR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: Zephyrus S dmi.product.name: Zephyrus S GX531GXR_GX531GXR dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1860930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881437] Re: IBus right click on system tray shows in top left corner hindering screen edges on KDE desktop
Thanks for your report. It does not sound as an ibus bug to me, though, but rather a KDE one. Or sddm. Or a support request.. On KDE you should be able to add the "Input Method Panel" widget and relogin. That will replace the IBus icon with a better-loooking KDE one. Can you try that and let us know if it helps? ** Package changed: ibus (Ubuntu) => kde-runtime (Ubuntu) ** Changed in: kde-runtime (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1881437 Title: IBus right click on system tray shows in top left corner hindering screen edges on KDE desktop Status in kde-runtime package in Ubuntu: Incomplete Bug description: Right-clicking IBus on system tray shows options on the top left corner of the desktop taking up space and hindering screen edges to be executed on KDE desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-runtime/+bug/1881437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881462] Re: Brightness settings don't work on Lenovo Ideapad 5 15ARE05
Solved this (and some other issues) for me by installing the mainline kernel Used the "mainline" script for that e.g. with instructions from https://www.linuxuprising.com/2018/10/2-utilities-to-install-latest-kernel-in.html ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881462 Title: Brightness settings don't work on Lenovo Ideapad 5 15ARE05 Status in xorg package in Ubuntu: Invalid Bug description: After installation, the notebook brighness buttons change brightness settings, but settings are not applied on the screen. In the log files I can see something like this: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address Failed to get backlight or LED device 'backlight:acpi_video0': No such device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sun May 31 10:43:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev ce) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=94ab3768-11c5-4582-9374-578128353e38 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
@JamesH, my only involvement in this bug report was to inform you that you were using an "End of Line" Ubuntu release and to ensure that the report was assigned to the correct project/package/Ubuntu release so that others who have a much better knowledge and experience of such issues could look at your report. Anyone looking at the bug reports that you raise may not have the level of expertise that can actually fix issues. Several people may look at or change the report before it reaches someone who might be able to suggest a fix. Comments such as yours will only drive Ubuntu users/volunteers such as myself away from helping to assign bug reports to users and teams that can actually help. As you have not replied to Kai-Heng's request in comment #21 I'm closing this report as "Invalid". If you still have an issue with the problem that you reported then perhaps issuing the following command in a terminal window ubuntu-bug linux when your connection is working would probably be the best way forward. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: Invalid Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881462] Re: Brightness settings don't work on Lenovo Ideapad 5 15ARE05
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1881462 Title: Brightness settings don't work on Lenovo Ideapad 5 15ARE05 Status in xorg package in Ubuntu: New Bug description: After installation, the notebook brighness buttons change brightness settings, but settings are not applied on the screen. In the log files I can see something like this: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address Failed to get backlight or LED device 'backlight:acpi_video0': No such device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sun May 31 10:43:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev ce) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=94ab3768-11c5-4582-9374-578128353e38 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1881462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881462] [NEW] Brightness settings don't work on Lenovo Ideapad 5 15ARE05
You have been subscribed to a public bug: After installation, the notebook brighness buttons change brightness settings, but settings are not applied on the screen. In the log files I can see something like this: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0. amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address Failed to get backlight or LED device 'backlight:acpi_video0': No such device ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Sun May 31 10:43:17 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev ce) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:381b] InstallationDate: Installed on 2020-05-29 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=94ab3768-11c5-4582-9374-578128353e38 ro quiet splash amdgpu.exp_hw_support=1 vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- Brightness settings don't work on Lenovo Ideapad 5 15ARE05 https://bugs.launchpad.net/bugs/1881462 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
** Attachment added: "btmon cap from lenovo bug" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5378974/+files/lenovo.cap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1879582] Re: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again
well, i had done both tests (redmi in other laptop and same laptop with another phone), and the result was quite confusing. Seems the bug occurs with the combination of ubuntu+redmi 1 - Testing Redmi In an old laptop Lenovo G470, autoconnection (after turn phone on again) not works at all (just as in my acer, on status blinks when i turn phone on, but it immediately change to off again). Manual connection fails kind of 50% of times, in a different way than in my acer (here it keeps loading for some seconds and then fail, while in acer it just become of immediactly). 2 - In MS Windows, in the same lenovo laptop (i had tested just for discard a hardware problem), redmi works fine both, manual and auto connection (also in my android tablet and android phone). 3 - With an old and cheap bluetooth phone, called "fitphone", in my acer, works both, auto-connection after turn phone on and manual connection in gnome. I had noticed that when i try to manual connect in my acer, i get in btmon a status "bluetoothd: connect error: Device or resource busy", while in lenovo, the fails status are When lenovo auto-connection blinks, it printed in btmon: "= bluetoothd: connect error: Operation already in progress" (while it's not) ** Attachment added: "btmon cap from acer bug" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+attachment/5378973/+files/acer.cap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1879582 Title: [Redmi AirDots Bluetooth] I need to remove device in settings every time i want to connect again Status in alsa-driver package in Ubuntu: New Bug description: I can connect to my bluetooth phone only the first time after pair the device. It works until disconnecting, (whether by turning off the phone, or putting into the case, or disconnecting in ubuntu settings), and then i turn on the phone again (or remove from the case), i cannot connect until I manually remove from bluetooth devices list in Ubuntu Settings, and then pair it again.. If the Ubuntu/Gnome Settings is opened, i can see the status "connected" blinks, and fastly change to "disconnected". My bluetooth phone works fine with another devices. Ubuntu 20.04 LTS Laptop Acer Aspire Nitro 5 (AN515-52-5771). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: felipe 2149 F pulseaudio /dev/snd/controlC0: felipe 2149 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 19 19:10:35 2020 InstallationDate: Installed on 2020-04-29 (20 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Redmi AirDots_R Symptom_Type: None of the above Title: [Redmi AirDots_R, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.28 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.28 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.28 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.28:bd08/05/2019:svnAcer:pnNitroAN515-52:pvrV1.28:rvnCFL:rnFreed_CFS:rvrV1.28:cvnAcer:ct10:cvrV1.28: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.28 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp