[Touch-packages] [Bug 1923377] Re: Automatically installed systemd:i386 makes graphical boot hang
[Expired for systemd (Ubuntu) because there has been no activity for 60 days.] ** Changed in: systemd (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1923377 Title: Automatically installed systemd:i386 makes graphical boot hang Status in systemd package in Ubuntu: Expired Bug description: 1) Description: Ubuntu 20.04.2 LTS Release: 20.04 2) systemd:i386 (245.4-4ubuntu3.6, automatic) systemd:amd64 (245.4-4ubuntu3.6, automatic) 3) I expected that letting the system install/upgrade packages it suggested would cause no harm. 4) Harm was caused. Graphical boot got stuck after the grub menu. But I could access virtual console be pressing alt-F1. I accepted the upgrade on Saturday, on Sunday, when tried to boot the machine, the machine hung up. I suspect that one of the problematic packages was systemd:i386. I have no idea why a 32bit version of this got installed, and other 32bit versions as well. I attached an excerpt from /var/log/apt/history.log showing the problematic upgrade. One of the results was that the binaries /usr/bin/systemctl and /lib/systemd/systemd were 32bit executables, and they could not load appropriate the pam modules (which were still 64bit). But as I could log in from the virtual terminal just fine, this showed that pam itself was working, systemd was the problem. After long struggle I managed to fix this by reinstalling systemd, which overwrote the above binaries with their 64bit versions. Removing systemd:i386 would have deleted systemd altogether. After that I purged various 32bit packages I suspected were causing problems. And I installed the packages removed by the upgrade on Saturday, such as snapd. Now the system boots up in graphical mode just fine. But why did the 32bit versions of systemd etc got installed automatically? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1923377/+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 1936769] Re: [Braswell] HDMI not working properly
Although I don't fully understand the bug description, I do wonder if there's a Braswell regression given bug 1935901 also. ** Summary changed: - HDMI not working properly + [Braswell] HDMI not working properly ** Package changed: xorg (Ubuntu) => mutter (Ubuntu) ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-hwe-5.8 (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/1936769 Title: [Braswell] HDMI not working properly Status in linux-hwe-5.8 package in Ubuntu: New Status in mutter package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: HP Pavillion desktop 2015 ufei date. Never turned off because boot takes too long. Screens (2) turned off system left on when not in use. Up to Ubuntu 19 and early versions of 20 both screens came back on. With latest update HDMI does not restart. If boot from power off both screens, HDMI and VGA are ok. Turn screens off and HDMI will not display. I note that Windows (horrible) has a switch that allows the HDMI to be controlled but Ubuntu did it automatically but won't now. Suspend has always killed the HDMI but there is not much difference in power consumption between on with suspend and on with screens off. Hope you can help, booting from full power off takes too long. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 13:09:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] InstallationDate: Installed on 2020-11-05 (255 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP 510-a112a ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2018 dmi.bios.release: 5.11 dmi.bios.vendor: AMI dmi.bios.version: F.33 dmi.board.asset.tag: CNV7380P8W dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV7380P8W dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-a112a dmi.product.sku: W2S68AA#ABG dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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/linux-hwe-5.8/+bug/1936769/+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 1936769] [NEW] HDMI not working properly
Public bug reported: HP Pavillion desktop 2015 ufei date. Never turned off because boot takes too long. Screens (2) turned off system left on when not in use. Up to Ubuntu 19 and early versions of 20 both screens came back on. With latest update HDMI does not restart. If boot from power off both screens, HDMI and VGA are ok. Turn screens off and HDMI will not display. I note that Windows (horrible) has a switch that allows the HDMI to be controlled but Ubuntu did it automatically but won't now. Suspend has always killed the HDMI but there is not much difference in power consumption between on with suspend and on with screens off. Hope you can help, booting from full power off takes too long. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 13:09:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [103c:821d] InstallationDate: Installed on 2020-11-05 (255 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP 510-a112a ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-59-generic root=UUID=45ef6758-d850-46bc-b01b-ff1d33b61a32 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2018 dmi.bios.release: 5.11 dmi.bios.vendor: AMI dmi.bios.version: F.33 dmi.board.asset.tag: CNV7380P8W dmi.board.name: 821D dmi.board.vendor: HP dmi.board.version: 00 dmi.chassis.asset.tag: CNV7380P8W dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.33:bd01/17/2018:br5.11:svnHP:pn510-a112a:pvr:rvnHP:rn821D:rvr00:cvnHP:ct3:cvr: dmi.product.family: 103C_53316J G=D dmi.product.name: 510-a112a dmi.product.sku: W2S68AA#ABG dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 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 -- 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/1936769 Title: HDMI not working properly Status in xorg package in Ubuntu: New Bug description: HP Pavillion desktop 2015 ufei date. Never turned off because boot takes too long. Screens (2) turned off system left on when not in use. Up to Ubuntu 19 and early versions of 20 both screens came back on. With latest update HDMI does not restart. If boot from power off both screens, HDMI and VGA are ok. Turn screens off and HDMI will not display. I note that Windows (horrible) has a switch that allows the HDMI to be controlled but Ubuntu did it automatically but won't now. Suspend has always killed the HDMI but there is not much difference in power consumption between on with suspend and on with screens off. Hope you can help, booting from full power off takes too long. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jul 19 13:09:23 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 35) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom/Celeron/Pentium Processor
[Touch-packages] [Bug 1935884] Re: avahi-daemon segfaults when a txt-record has no value
** Changed in: avahi Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1935884 Title: avahi-daemon segfaults when a txt-record has no value Status in Avahi: Fix Released Status in avahi package in Ubuntu: New Status in focal package in Ubuntu: New Bug description: This bug is reported upstream( https://github.com/lathiat/avahi/issues/247 ) but ubuntu focal did not fix it. Version: avahi-daemon (0.7-4ubuntu7.1) on Focal Fossa Service XML causing the segfault: ``` Printer _ipp._tcp. printer.local 631 note= ``` The line `note=` causes avahi to segfault. The Workaround I found was: `note=""` I.e. setting the `note` to an empty string. It can fix to merge this ( https://github.com/lathiat/avahi/pull/226 ). This bug fixed on upstream version 0.8, so this bug remains on bionic and focal. To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1935884/+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 1936716] Re: video glitch
Obviously GRUB and YouTube shouldn't be sharing the same screen. That looks like a driver/browser chroma-key bug. What browser were you using? I'm also not totally confident that's even the main issue you were describing. If it's not then please be sure to open a second bug about the other issue. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-465 (Ubuntu) ** Summary changed: - video glitch + YouTube video still visible (hardware chroma key) after reboot on the GRUB screen -- 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/1936716 Title: YouTube video still visible (hardware chroma key) after reboot on the GRUB screen Status in nvidia-graphics-drivers-465 package in Ubuntu: New Bug description: There was a glitch as I was watching a youtube video that imprinted a still image on the screen with transparent vertical stripes. Restarted the computer and the same image was imprinted behind the GRUB boot- loader menu during start up. Unusual behavior that continued 2-3 times after resets including removing all power sources for a while before restarting. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 465.27 Thu Apr 22 23:21:03 UTC 2021 GCC version: gcc version 10.3.0 (Ubuntu 10.3.0-1ubuntu1) ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: GNOME Date: Sat Jul 17 23:57:09 2021 DistUpgraded: 2021-05-08 18:27:26,605 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: nvidia, 465.27, 5.11.0-22-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1080] [10de:1b80] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1080] [1458:3717] InstallationDate: Installed on 2021-02-02 (165 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Gigabyte Technology Co., Ltd. Z370 AORUS Gaming 5 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to hirsute on 2021-05-08 (70 days ago) dmi.bios.date: 10/30/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F11 dmi.board.asset.tag: Default string dmi.board.name: Z370 AORUS Gaming 5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF11:bd10/30/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGaming5-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z370 AORUS Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1936716/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1935884] Re: avahi-daemon segfaults when a txt-record has no value
** Bug watch added: github.com/lathiat/avahi/issues #247 https://github.com/lathiat/avahi/issues/247 ** Also affects: avahi via https://github.com/lathiat/avahi/issues/247 Importance: Unknown Status: Unknown ** Also affects: focal (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1935884 Title: avahi-daemon segfaults when a txt-record has no value Status in Avahi: Unknown Status in avahi package in Ubuntu: New Status in focal package in Ubuntu: New Bug description: This bug is reported upstream( https://github.com/lathiat/avahi/issues/247 ) but ubuntu focal did not fix it. Version: avahi-daemon (0.7-4ubuntu7.1) on Focal Fossa Service XML causing the segfault: ``` Printer _ipp._tcp. printer.local 631 note= ``` The line `note=` causes avahi to segfault. The Workaround I found was: `note=""` I.e. setting the `note` to an empty string. It can fix to merge this ( https://github.com/lathiat/avahi/pull/226 ). This bug fixed on upstream version 0.8, so this bug remains on bionic and focal. To manage notifications about this bug go to: https://bugs.launchpad.net/avahi/+bug/1935884/+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 1894046] Re: Bluetooth keyboard has lag
Thanks for the bug report. Please: 1. Run this command to send us more system info: apport-collect 1894046 2. If you have 'tlp' installed then try uninstalling it. It is known to cause bugs like this. 3. Install 'powertop' and try using that to disable power savings mode for the affected devices. ** Tags added: focal ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1894046 Title: Bluetooth keyboard has lag Status in bluez package in Ubuntu: Incomplete Bug description: For some days, I observe an annoying lag with my Logitech K380 keyboard and Ubuntu 20.04. After a couple of seconds not typing, new keystrokes are registered only after 1–2 seconds lag. From there on, I can type without lag, until the next typing pause. I seems that the Bluetooth component switches Bluetooth in some sort of hibernate after a couple of seconds of not typing, and then it needs 1–2 seconds to wake up again and process the keystrokes. No keys are missing – they just arrive with a lag. Probably the keyboard buffers them. Important: If I listen to music with a Bluetooth headset, I can type without *any* problems because the Bluetooth module remains awake due to the music transmission. The keyboard does not exhibit this issues at my Android tablet. Furthermore, I am sometimes lucky can work with the keyboard without any lag (and without music). In the BIOS settings of the computer, I do not find anything Bluetooth-related. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1894046/+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 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok
@Alex, Download 3 deb files, then run 'sudo dpkg -i *.deb'; 'reboot', and check if the running kernel is the testing kernel through 'uname -a' -- 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/1918458 Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok Status in alsa-driver package in Ubuntu: Confirmed Bug description: Expect : sound from speaker Instead, obtain : no sound. Tried various configuration of /etc/modprobe.d/alsa-conf with : options snd-hda-intel model= and options snd-intel-dspcfg dsp_driver=3 or 1 and systematic reboot. Either I get dummy output, or I get proper output detection, alsamixer and pavucontrol seems 100% ok, but no sound comes from the speakers. I'm under a dualboot with Windows 10, BIOS fast boot disabled. Ubuntu 20.04.2 LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thibauts 1522 F pulseaudio /dev/snd/pcmC0D0p: thibauts 1522 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 18:10:30 2021 InstallationDate: Installed on 2021-03-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp Symptom_Jack: Grey Speaker, Internal Symptom_Type: Only some of outputs are working Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/24/2019 dmi.bios.release: 1.4 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.04 dmi.board.asset.tag: Default string dmi.board.name: Guinness_WL dmi.board.vendor: WL dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 5 dmi.product.name: Swift SF515-51T dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1936751] Re: disabling "turn wifi off to save power" turns off wifi
** Package changed: ubuntu => network-manager (Ubuntu) -- 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/1936751 Title: disabling "turn wifi off to save power" turns off wifi Status in network-manager package in Ubuntu: New Bug description: I wanted to disable the "Wifi can be turned off to save power" in the power settings. But, doing this turns off the wifi! :-/ I was doing so because my wifi is unstable, it seems to turn off on its own. definitely some issue with wifi turn on/off by the system. Thanks for any help. Note: I tried putting a 2 instead of a 3 in /etc/NetworkManager/conf.d/default-wifi-powersave-on.conf Same buggy behavior, and wifi not more stable. JL ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 18 20:27:20 2021 InstallationDate: Installed on 2021-06-26 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.103 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1936751/+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 1936751] [NEW] disabling "turn wifi off to save power" turns off wifi
You have been subscribed to a public bug: I wanted to disable the "Wifi can be turned off to save power" in the power settings. But, doing this turns off the wifi! :-/ I was doing so because my wifi is unstable, it seems to turn off on its own. definitely some issue with wifi turn on/off by the system. Thanks for any help. Note: I tried putting a 2 instead of a 3 in /etc/NetworkManager/conf.d /default-wifi-powersave-on.conf Same buggy behavior, and wifi not more stable. JL ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 18 20:27:20 2021 InstallationDate: Installed on 2021-06-26 (22 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) IpRoute: default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.103 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- disabling "turn wifi off to save power" turns off wifi https://bugs.launchpad.net/bugs/1936751 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager 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 1780677] Re: X session crash after resuming from suspend
Still no fix ? I have just installed clean Ubuntu 20.04 an this exact thing is happening to me. It took me hours just to find this bug report... 沈 ** Also affects: xorg (Ubuntu) Importance: Undecided Status: New ** No longer affects: 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/1780677 Title: X session crash after resuming from suspend Status in xorg-server package in Ubuntu: Confirmed Bug description: Description: Ubuntu 18.04 LTS Release: 18.04 xorg: Installed: 1:7.7+19ubuntu7 First I suspended my laptop, while a few applications were running (Firefox, Chrome and some others much smaller). A couple of hours later, I opened the lid and expected the Gnome session would resume. What happened instead was a crash of the X server, then the login page was shown again and a new Gnome session started: the old session got killed! In the Xorg.0.log.old file I found this, not sure if related: [ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0 [ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error [ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error [ 21189.338] (II) Server terminated successfully (0). Closing log file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Jul 8 23:03:30 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidia, 390.48, 4.15.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05cc] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc] InstallationDate: Installed on 2018-06-21 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Precision M4800 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/02/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0T3YTY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 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 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1780677/+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 1936750] [NEW] package python3-xdg 0.25-4ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 139
Public bug reported: i don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-xdg 0.25-4ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Sun Jul 18 14:24:21 2021 Dependencies: ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 139 InstallationDate: Installed on 2016-12-02 (1689 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: pyxdg Title: package python3-xdg 0.25-4ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 139 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pyxdg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pyxdg in Ubuntu. https://bugs.launchpad.net/bugs/1936750 Title: package python3-xdg 0.25-4ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 139 Status in pyxdg package in Ubuntu: New Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-xdg 0.25-4ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 Date: Sun Jul 18 14:24:21 2021 Dependencies: ErrorMessage: sub-processo script post-installation instalado retornou estado de saída de erro 139 InstallationDate: Installed on 2016-12-02 (1689 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: pyxdg Title: package python3-xdg 0.25-4ubuntu0.16.04.1 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 139 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pyxdg/+bug/1936750/+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
