[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
@jweede Hm. And is the instance booted with or without initramfs? -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 124440] Re: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed
Get money to fix this bug or raise the bounty so it will get more tempting for someone to get it done: https://www.bountysource.com/issues/3848890-enhancement-ubuntu-needs-a -way-to-set-mouse-wheel-scrolling-speed -- 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/124440 Title: [enhancement] Ubuntu needs a way to set mouse wheel scrolling speed Status in gnome-control-center: Unknown Status in GTK+: Unknown Status in Mir: Fix Released Status in Unity: Invalid Status in gnome-control-center package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Status in mir package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: Triaged Bug description: This has been driving me nuts for a while now. The scroll wheel on my desktop mouse (it's an MS wireless optical mouse model 1008) scrolls rather fast. Instead of moving a few lines, it scrolls half a page or more with a very gentle scroll. The bluetooth mouse I use with my laptop does not do this so it's probably somewhat hardware specific. However, I'm wondering if there is a way to modify the speed or sensitivity. I found an answer here from about a year ago (https://answers.launchpad.net/ubuntu/+question/1339) that suggests there isn't a way but I'm wondering if anything has changed since then. I've also skimmed through synaptic but didn't see anything promising (like gsynaptic for touchpads). Thanks. See https://answers.launchpad.net/ubuntu/+question/9200 for more information. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/124440/+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 1814371] Re: package linux-image-4.15.0-45-generic 4.15.0-45.48 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/1814371 Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 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: after fresh install the message about some error in system soft is reported. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1020 F pulseaudio arkady 1449 F pulseaudio Date: Thu Jan 31 18:09:39 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=13962fc0-9198-4027-b39f-12bc4c03aded InstallationDate: Installed on 2019-01-17 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 RfKill: SourcePackage: initramfs-tools StagingDrivers: vboxvideo Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814371/+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 1814373] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1814373 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in udisks package in Ubuntu: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1814373] [NEW] storage / luks / dmsetup regressed (or got better) on ppc64le
Public bug reported: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: udisks (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: udisks (Ubuntu) Importance: Undecided Status: New -- 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/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Status in udisks package in Ubuntu: New Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+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 1814072] Re: software-properties-gtk does not recognize https mirrors under Ubuntu Software
Main source is https://code.launchpad.net/software-properties (I thought upstream was Debian due to versioning) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1814072 Title: software-properties-gtk does not recognize https mirrors under Ubuntu Software Status in software-properties package in Ubuntu: Confirmed Bug description: How to reproduce: 1. Change main Ubuntu mirrors to https in /etc/apt/sources.list and do "apt update" 2. Run software-properties-gtk 3. Go to "Ubuntu Software" tab What happens: The tab "Ubuntu Software" does not list https mirrors. The corresponding boxes are not checked, the correct "Download from" entry is not selected and falls back to "Main server". The correct sources are just listed under "Other Software". What should happen: The tab "Ubuntu Software" should recognize the https mirrors from apt and tick the corresponding boxes and select the correct server in the "Download from" list. Ubuntu 18.04 software-properties-gtk 0.96.24.32.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1814072/+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 1814371] [NEW] package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: after fresh install the message about some error in system soft is reported. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1020 F pulseaudio arkady 1449 F pulseaudio Date: Thu Jan 31 18:09:39 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=13962fc0-9198-4027-b39f-12bc4c03aded InstallationDate: Installed on 2019-01-17 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 RfKill: SourcePackage: initramfs-tools StagingDrivers: vboxvideo Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic staging -- 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/1814371 Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 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: after fresh install the message about some error in system soft is reported. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-45-generic 4.15.0-45.48 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1020 F pulseaudio arkady 1449 F pulseaudio Date: Thu Jan 31 18:09:39 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=13962fc0-9198-4027-b39f-12bc4c03aded InstallationDate: Installed on 2019-01-17 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash 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.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 RfKill: SourcePackage: initramfs-tools StagingDrivers: vboxvideo Title: package linux-image-4.15.0-45-generic 4.15.0-45.48 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias:
[Touch-packages] [Bug 1450838] Re: lightdm fails to unlock with serial console configured
Is this still the case when testing with a currently supported Ubuntu release? ** Changed in: light-locker (Ubuntu) Status: New => Incomplete ** Changed in: lightdm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1450838 Title: lightdm fails to unlock with serial console configured Status in light-locker package in Ubuntu: Incomplete Status in lightdm package in Ubuntu: Incomplete Bug description: With /etc/default/grub configured for serial console output as follows (seehttps://help.ubuntu.com/community/SerialConsoleHowto): GRUB_DEFAULT=0 GRUB_TIMEOUT=3 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="" GRUB_CMDLINE_LINUX="" GRUB_CMDLINE_LINUX="console=tty0 console=ttyS0,9600n8" #GRUB_TERMINAL=console GRUB_TERMINAL="serial console" GRUB_SERIAL_COMMAND="serial --speed=9600 --unit=0 --word=8 --parity=no --stop=1" Lightdm fails to unlock a locked screen. Initial login works fine. But, when the screen locks, the correct password is accepted, but the screen does not unlock. If I disable serial console with the default "GRUB_TERMINAL=console", lightdm screen unlock seems to work fine. I don't know if this is a problem with lightdm or light-locker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1450838/+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 1717796] Re: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle
Dear Ubuntu dev Team DON'T MAKE "UPGRADES" WHICH CHANGE PERMISSIONS!!! It is a permission problem with my home folder and pulseaudio. I've had 2 issues: - bluetoothd operating at 100% of one CPU core - no way to connect ANY bt device If happened after one of your "upgrades", so please test it MORE THOROUGHLY next time. Yes, I'm certain it happened after an upgrade cause I made backup 2 days prior to this extremely frustrating issue and no software other than "ubuntu upgrade" was installed in the meantime. After having researched internet twice and having already made my mind to switch to another linux distro if the solution does't come up till the end of the day - I came across this: Run the following command to fix the $HOME directory permissions for the current $USER: sudo chown -R $USER:$USER $HOME/ I used http://www.linuxquestions.org/questions/linux-software-2/problem-with-pulse-audio-834041/ and http://ubuntuforums.org/showthread.php?p=6208727 as sources. The solution for me was to fix the permissions using the following command: sudo chown -R lionel:lionel /home/lionel and then using pavucontrol to unmute the output. The gnome indicator is still greyed but music is back, and that's a good thing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1717796 Title: Bluetoothd fills 100% CPU when bluetooth keyboard goes in idle Status in The Ubuntu Power Consumption Project: Confirmed Status in bluez package in Ubuntu: Confirmed Bug description: When bluetooth keyboard goes in idle bluetoothd fills 100% CPU. At this point you have to press any key to reconnect the device and let bluetoothd to return to work normally. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5.1 ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Sun Sep 17 19:02:40 2017 ExecutablePath: /usr/lib/bluetooth/bluetoothd InstallationDate: Installed on 2016-08-06 (406 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: GIGABYTE GB-BXBT-2807 ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic.efi.signed root=UUID=8931ead4-8d43-4aef-8946-c7845c63c7d3 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MZBAYAP-00 dmi.board.vendor: GIGABYTE dmi.board.version: 1.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd10/22/2015:svnGIGABYTE:pnGB-BXBT-2807:pvr1.x:rvnGIGABYTE:rnMZBAYAP-00:rvr1.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: GB-BXBT-2807 dmi.product.version: 1.x dmi.sys.vendor: GIGABYTE hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: DC:85:DE:FD:2F:BC ACL MTU: 820:8 SCO MTU: 255:16 UP RUNNING PSCAN ISCAN RX bytes:528225 acl:32183 sco:0 events:1134 errors:0 TX bytes:33849 acl:338 sco:0 commands:388 errors:1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1717796/+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 311029] Re: curl and pycurl is not compiled with sftp support
> Could someone describe a test case using the backend which we could use to > test that the feature is working if we enable it to bionic (the 'curl > --version' output tells us that the backend is enabled but it would be > good to also check that it's actually correctly working) Not sure what you mean by test case using the backend. But I compiled version 7.63.0 and it looks like it works find. Though I just used git- ftp to upload via sftp, but that worked smooth. Here is what I did to install it with ubuntu 18.04. I had to compile debhelper too. git clone https://git.launchpad.net/ubuntu/+source/debhelper cd debhelper/ sudo apt-get install build-essential po4a dpkg-buildpackage -uc -us cd .. sudo apt-get install dwz sudo dpkg -i debhelper_12ubuntu1_all.deb git clone https://git.launchpad.net/ubuntu/+source/curl cd curl/ sudo apt-get install build-essential libssh-dev dpkg-buildpackage -b -rfakeroot -us -uc cd .. sudo dpkg -i libcurl*.deb sudo dpkg -i curl*.deb Here the versions output: # curl --version curl 7.63.0 (x86_64-pc-linux-gnu) libcurl/7.63.0 OpenSSL/1.1.0g zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) libssh/0.7.0/openssl/zlib nghttp2/1.30.0 librtmp/2.3 Release-Date: 2018-12-12 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL -- 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/311029 Title: curl and pycurl is not compiled with sftp support Status in curl package in Ubuntu: Fix Released Status in curl package in Debian: Fix Released Bug description: Binary package hint: curl Running curl --version, I see: Protocols: tftp ftp telnet dict ldap ldaps http file https ftps SFTP is obviously missing, although it is supported by curl upstream The SFTP is also missing from python-pycurl, probably because libcurl doesn't have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/311029/+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 1730035] Re: Needs to depend on Python3
For those who really don't want python3-apport and apport installed, despite what Ubuntu maintainers say: Create a new package with "Provides: python3-apport" that is otherwise empty. Then python3-apport and apport can be uninstalled. Warning: This might break your system. -- 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/1730035 Title: Needs to depend on Python3 Status in xorg package in Ubuntu: Fix Released Status in xorg source package in Artful: Won't Fix Bug description: [Impact] source_xorg.py apport hook does not work if python3 is not installed. [Test case] install on a clean system, check that apport-bug xorg does the right thing. [Regression potential] Minimal, just adds the correct dependencies that were missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1730035/+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 1605861] Re: apt-key output should not be parsed (stdout is not a terminal)
*** This bug is a duplicate of bug 1754075 *** https://bugs.launchpad.net/bugs/1754075 ** This bug has been marked a duplicate of bug 1754075 apt-setup uses apt-key but probably should not anymore ** Bug watch removed: Debian Bug tracker #851774 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1605861 Title: apt-key output should not be parsed (stdout is not a terminal) Status in software-properties package in Ubuntu: Invalid Bug description: Got that warning logged after registering two ppas and updating them: com.ubuntu.SoftwareProperties[2113]: gpg: keyring `/tmp/tmp58u008j4/secring.gpg' created com.ubuntu.SoftwareProperties[2113]: gpg: keyring `/tmp/tmp58u008j4/pubring.gpg' created com.ubuntu.SoftwareProperties[2113]: gpg: requesting key F59EAE4D from hkp server keyserver.ubuntu.com com.ubuntu.SoftwareProperties[2113]: gpg: /tmp/tmp58u008j4/trustdb.gpg: trustdb created com.ubuntu.SoftwareProperties[2113]: gpg: key F59EAE4D: public key "Launchpad PPA for NoobsLab" imported com.ubuntu.SoftwareProperties[2113]: gpg: no ultimately trusted keys found com.ubuntu.SoftwareProperties[2113]: gpg: Total number processed: 1 com.ubuntu.SoftwareProperties[2113]: gpg: imported: 1 (RSA: 1) com.ubuntu.SoftwareProperties[2113]: Warning: apt-key output should not be parsed (stdout is not a terminal) com.ubuntu.SoftwareProperties[2113]: OK com.ubuntu.SoftwareProperties[2113]: gpg: keyring `/tmp/tmpjwlat63e/secring.gpg' created com.ubuntu.SoftwareProperties[2113]: gpg: keyring `/tmp/tmpjwlat63e/pubring.gpg' created com.ubuntu.SoftwareProperties[2113]: gpg: requesting key E2D0EBE9 from hkp server keyserver.ubuntu.com com.ubuntu.SoftwareProperties[2113]: gpg: /tmp/tmpjwlat63e/trustdb.gpg: trustdb created com.ubuntu.SoftwareProperties[2113]: gpg: key E2D0EBE9: public key "Launchpad PPA for RAVEfinity Project" imported com.ubuntu.SoftwareProperties[2113]: gpg: Total number processed: 1 com.ubuntu.SoftwareProperties[2113]: gpg: imported: 1 (RSA: 1) com.ubuntu.SoftwareProperties[2113]: Warning: apt-key output should not be parsed (stdout is not a terminal) com.ubuntu.SoftwareProperties[2113]: OK ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: software-properties-gtk 0.96.24.1 ProcVersionSignature: Ubuntu 4.6.0-9.11-generic 4.6.4 Uname: Linux 4.6.0-9-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.2-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Jul 23 13:37:35 2016 PackageArchitecture: all SourcePackage: software-properties UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1605861/+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 1814389] Re: Second extend of second lvmraid mirror does not sync
** Description changed: This is a weird corner case. Extending an lvmraid(7) type1 mirror for the second time seems to result in the mirror legs not getting synced, *if* there is another type1 mirror in the vg. This reliably reproduces for me: # quickly fill two 10G files with random data openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv1.img iflag=fullblock openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv2.img iflag=fullblock # change loop devices if you have loads of snaps in use losetup /dev/loop10 pv1.img losetup /dev/loop11 pv2.img pvcreate /dev/loop10 pvcreate /dev/loop11 vgcreate testvg /dev/loop10 /dev/loop11 lvcreate --type raid1 -L2G -n test testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync lvcreate --type raid1 -L2G -n test2 testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync - # this will sync OK, observe kernel message for output from md subsys noting time taken - # + # the following will sync OK, observe kernel message for output from md subsys noting time taken + # lvextend -L+2G testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync - # this will FAIL to sync, the sync will seem to complete instantly, e.g: + # the following will FAIL to sync, the sync will seem to complete instantly, e.g: # Feb 02 15:22:50 asr-host kernel: md: resync of RAID array mdX # Feb 02 15:22:50 asr-host kernel: md: mdX: resync done. # lvextend -L+2G testvg/test2 lvchange --syncaction check testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # observe error count This may cause administrator alarm unnecessarily ... :/ For some reason the precise sizes with which the LVs are created, and are then extended by, do appear to matter. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Feb 2 15:33:16 2019 ProcEnviron: - TERM=screen - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + TERM=screen + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lvm.lvm.conf: 2018-07-22T18:30:15.470358 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1814389 Title: Second extend of second lvmraid mirror does not sync Status in lvm2 package in Ubuntu: New Bug description: This is a weird corner case. Extending an lvmraid(7) type1 mirror for the second time seems to result in the mirror legs not getting synced, *if* there is another type1 mirror in the vg. This reliably reproduces for me: # quickly fill two 10G files with random data openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv1.img iflag=fullblock openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv2.img iflag=fullblock # change loop devices if you have loads of snaps in use losetup /dev/loop10 pv1.img losetup /dev/loop11 pv2.img pvcreate /dev/loop10 pvcreate /dev/loop11 vgcreate testvg /dev/loop10 /dev/loop11 lvcreate --type raid1 -L2G -n test testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync lvcreate --type raid1 -L2G -n test2 testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will sync OK, observe kernel message for output from md subsys noting time taken # lvextend -L+2G testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will FAIL to sync, the sync will seem to complete instantly, e.g: # Feb 02 15:22:50 asr-host kernel: md: resync of RAID array mdX # Feb 02 15:22:50 asr-host kernel: md: mdX: resync done. # lvextend -L+2G testvg/test2 lvchange --syncaction check testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # observe error count This may cause administrator alarm unnecessarily ... :/ For some reason the precise sizes with which the LVs are created, and are then extended by, do appear to matter. ProblemType: Bug DistroRelease:
[Touch-packages] [Bug 1814262] Re: Wired interface gets impossibly high metric 20100
k, it could also be a bug in the new 1.15 serie with is new/still unstable so not likely used anywhere in 'production' and having little users at the moment -- 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/1814262 Title: Wired interface gets impossibly high metric 20100 Status in network-manager package in Ubuntu: New Bug description: Actually this might be a heisenbug. I've had an issue with this all morning since network-manager got an update this morning, but just now *while this bug was being submitted* it decided to correct itself. What I was getting was, on a machine (Dell XPS 13 9370) with WiFi and a (Caldigit) Thunderbolt 3 dock with an ethernet port: After the network-manager update I noticed everything was slower than I was used to, and in gnome-shell the network icon showing was the WiFi one, not the wired one. Looking at the output of route, or route -n for simplicity, I would see this: rachel@rainbow:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG60000 wlp2s0 0.0.0.0 192.168.1.254 0.0.0.0 UG20100 00 enp63s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlp2s0 192.168.1.0 0.0.0.0 255.255.255.0 U 10000 enp63s0 192.168.1.0 0.0.0.0 255.255.255.0 U 60000 wlp2s0 So the metric on the default route on enp63s0 had 20,000 mysteriously added to it, which would obviously make it extremely low-priority. The system was choosing the wifi connection instead, which isn't that great in my office, hence observable slowness. Now, this morning, this seemed to be the sticky situation. It didn't show any sign of changing, whatever I did, after restarts of network- manager, undock/redock, reboots, etc. I could change it manually with ifmetric (and it would work), but that was about it. I would have reported the bug then, but I had to go out. When I got back I plugged in and initially saw the same thing again (that's where the above snippet was pasted from). But *while* the ubuntu-bug network-manager command was running, I noticed the gnome-shell network icon switch to wired, checked again, and saw: rachel@rainbow:~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 192.168.1.254 0.0.0.0 UG10000 enp63s0 0.0.0.0 192.168.1.254 0.0.0.0 UG20600 00 wlp2s0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 00 wlp2s0 192.168.1.0 0.0.0.0 255.255.255.0 U 10000 enp63s0 192.168.1.0 0.0.0.0 255.255.255.0 U 60000 wlp2s0 So now the wifi connection has 20,000 added to it, which may still be wrong? But I wouldn't otherwise have noticed it because the system is again *behaving* as expected. This all seemed to happen after the network-manager upgrade (from 1.12.6-0ubuntu4 to 1.15.2-0ubuntu1) this morning. I can't say if these metric+20,000 values were present before then, because I didn't have any cause to go looking at it, it always just worked. Could it be some issue with how the newer network-manager, or one of its associated packages, is figuring out the metrics on new connections? Like it's running some new heuristic to determine which one should really be the preferred? If it's like it was just now, when it fixed itself after a minute or so, that's not really a problem, but if it's like it was this morning when it just seemed to be stuck with the ethernet connection at 20100, it is. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.15.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 1 13:15:06 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-09-11 (142 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) IpRoute: default via 192.168.1.254 dev wlp2s0 proto dhcp metric 600 default via 192.168.1.254 dev enp63s0 proto dhcp metric 20100 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev enp63s0 proto kernel scope link src 192.168.1.106 metric 100 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: 1: phy0: Wireless LAN
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: - update to openjdk 11 in 18.04 LTS + Transition OpenJDK 11 to 18.04 LTS. + + This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: + - openjdk-lts 11 needs newer build dependencies + - various packages have runtime failures when run with openjdk-11 + + A few packages *must* be updated/patched before openjdk-11 itself is uploaded: + TBD -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - openjdk-lts 11 needs newer build dependencies - various packages have runtime failures when run with openjdk-11 A few packages *must* be updated/patched before openjdk-11 itself is uploaded: TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+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 1814384] Re: update-initramfs: failed for with 1.
** Project changed: launchpad => initramfs-tools (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/1814384 Title: update-initramfs: failed for with 1. Status in initramfs-tools package in Ubuntu: New Bug description: lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic Within installation linux kernel 4.15.0.45 error occurred: !!! x86_64-linux-gnu_EGL.conf is not an issue here !!! Setting up linux-image-4.15.0-45-generic (4.15.0-45.48) ... Setting up linux-headers-4.15.0-45 (4.15.0-45.48) ... Setting up linux-headers-4.15.0-45-generic (4.15.0-45.48) ... Processing triggers for linux-image-4.15.0-45-generic (4.15.0-45.48) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-4.15.0-45-generic mkinitramfs: for device none missing /sys/dev/block/0:0 mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-4.15.0-45-generic (--configure): installed linux-image-4.15.0-45-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-4.15.0-45-generic E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1814384/+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 1814387] [NEW] swithching workspace by scrolling on edge of Dock (left side bar)
Public bug reported: If you position the mouse corsor on the edge of Dock and scroll, you can switch the workspace, which behaves equivalent to the scrolling on the "Show Applications" button in the corner. I've reproduced it on other Ubuntu 18 installations of friends (all 3 I tested, at least one was a fresh installation from the official iso). It is not important where Dock is or whether a window or the desktop is next to it. Program shortcuts have also no effect, because they end before it. It works with a single or 2 monitors on all instances of Dock. I use Ubuntu 18.04.1 LTS with all updates (via apt upgrade) installed and observed it for several months now. (After starting apport for this I updated again and nothing changed, no restart) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 2 16:10:48 2019 DistUpgraded: 2018-10-01 14:59:21,229 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:2300] Subsystem: CLEVO/KAPOK Computer GM107M [GeForce GTX 860M] [1558:2300] InstallationDate: Installed on 2017-03-18 (685 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Notebook W230SS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=907d4e48-c148-454e-aa8a-7adb74d51fb2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-01 (124 days ago) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 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.2 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: Mon Oct 1 13:12:45 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dock ubuntu ui -- 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/1814387 Title: swithching workspace by scrolling on edge of Dock (left side bar) Status in xorg package in Ubuntu: New Bug description: If you position the mouse corsor on the edge of Dock and scroll, you can switch the workspace, which behaves equivalent to the scrolling on the "Show Applications" button in the corner. I've reproduced it on other Ubuntu 18 installations of friends (all 3 I tested, at least one was a fresh installation from the official iso). It is not important where Dock is or whether a window or the desktop is next to it. Program shortcuts have also no effect, because they end before it. It works with a single or 2 monitors on all instances of Dock. I use Ubuntu 18.04.1 LTS with all updates (via apt upgrade) installed and observed it for several months now. (After starting apport for this I updated again and nothing changed, no restart) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
[Touch-packages] [Bug 1814284] Re: зависает всё
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- 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/1814284 Title: зависает всё Status in xorg package in Ubuntu: Incomplete Bug description: компьютер зависает на долго или прихода пере запускатькомпютер ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 1 21:48:54 2019 DistUpgraded: 2019-01-28 16:16:38,613 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Palit Microsystems Inc. GF108 [GeForce GT 630] [1569:0f00] InstallationDate: Installed on 2019-01-03 (29 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-01-28 (4 days ago) dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H61M-VG3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 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: Fri Feb 1 21:29:29 2019 xserver.configfile: default xserver.errors: [drm] Failed to open DRM device for pci::01:00.0: -19 open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814284/+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 1814389] [NEW] Second extend of second lvmraid mirror does not sync
Public bug reported: This is a weird corner case. Extending an lvmraid(7) type1 mirror for the second time seems to result in the mirror legs not getting synced, *if* there is another type1 mirror in the vg. This reliably reproduces for me: # quickly fill two 10G files with random data openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv1.img iflag=fullblock openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv2.img iflag=fullblock # change loop devices if you have loads of snaps in use losetup /dev/loop10 pv1.img losetup /dev/loop11 pv2.img pvcreate /dev/loop10 pvcreate /dev/loop11 vgcreate testvg /dev/loop10 /dev/loop11 lvcreate --type raid1 -L2G -n test testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync lvcreate --type raid1 -L2G -n test2 testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # this will sync OK, observe kernel message for output from md subsys noting time taken # lvextend -L+2G testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # this will FAIL to sync, the sync will seem to complete instantly, e.g: # Feb 02 15:22:50 asr-host kernel: md: resync of RAID array mdX # Feb 02 15:22:50 asr-host kernel: md: mdX: resync done. # lvextend -L+2G testvg/test2 lvchange --syncaction check testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # observe error count This may cause administrator alarm unnecessarily ... :/ For some reason the precise sizes with which the LVs are created, and are then extended by, do appear to matter. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Feb 2 15:33:16 2019 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lvm.lvm.conf: 2018-07-22T18:30:15.470358 ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Summary changed: - Second extent of second lvmraid mirror does not sync + Second extend of second lvmraid mirror does not sync -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1814389 Title: Second extend of second lvmraid mirror does not sync Status in lvm2 package in Ubuntu: New Bug description: This is a weird corner case. Extending an lvmraid(7) type1 mirror for the second time seems to result in the mirror legs not getting synced, *if* there is another type1 mirror in the vg. This reliably reproduces for me: # quickly fill two 10G files with random data openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv1.img iflag=fullblock openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv2.img iflag=fullblock # change loop devices if you have loads of snaps in use losetup /dev/loop10 pv1.img losetup /dev/loop11 pv2.img pvcreate /dev/loop10 pvcreate /dev/loop11 vgcreate testvg /dev/loop10 /dev/loop11 lvcreate --type raid1 -L2G -n test testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync lvcreate --type raid1 -L2G -n test2 testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # this will sync OK, observe kernel message for output from md subsys noting time taken # lvextend -L+2G testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # this will FAIL to sync, the sync will seem to complete instantly, e.g: # Feb 02 15:22:50 asr-host kernel: md: resync of RAID array mdX # Feb 02 15:22:50 asr-host kernel: md: mdX: resync done. # lvextend -L+2G testvg/test2 lvchange --syncaction check testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # observe error count This may cause administrator alarm unnecessarily ... :/ For some reason the precise sizes with which the LVs are created, and are then extended by, do appear to matter. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion:
[Touch-packages] [Bug 1814384] [NEW] update-initramfs: failed for with 1.
You have been subscribed to a public bug: lsb_release -a LSB Version: core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic Within installation linux kernel 4.15.0.45 error occurred: !!! x86_64-linux-gnu_EGL.conf is not an issue here !!! Setting up linux-image-4.15.0-45-generic (4.15.0-45.48) ... Setting up linux-headers-4.15.0-45 (4.15.0-45.48) ... Setting up linux-headers-4.15.0-45-generic (4.15.0-45.48) ... Processing triggers for linux-image-4.15.0-45-generic (4.15.0-45.48) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic /sbin/ldconfig.real: Warning: ignoring configuration file that cannot be opened: /etc/ld.so.conf.d/x86_64-linux-gnu_EGL.conf: No such file or directory /etc/kernel/postinst.d/kdump-tools: kdump-tools: Generating /var/lib/kdump/initrd.img-4.15.0-45-generic mkinitramfs: for device none missing /sys/dev/block/0:0 mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug update-initramfs: failed for with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 dpkg: error processing package linux-image-4.15.0-45-generic (--configure): installed linux-image-4.15.0-45-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-4.15.0-45-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New -- update-initramfs: failed for with 1. https://bugs.launchpad.net/bugs/1814384 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754075] Re: apt-setup uses apt-key but probably should not anymore
** Also affects: apt-setup (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851774 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Status in apt-setup source package in Bionic: Confirmed Status in gnupg source package in Bionic: Confirmed Status in gnupg2 source package in Bionic: Confirmed Status in apt-setup package in Debian: Unknown Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
** Changed in: linux (Ubuntu Cosmic) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: In Progress Status in gnome-shell source package in Bionic: Fix Committed Status in linux source package in Bionic: New Status in upower source package in Bionic: Fix Committed Status in gnome-control-center source package in Cosmic: Fix Committed Status in gnome-shell source package in Cosmic: Fix Committed Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Committed Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK 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/gnome-control-center/+bug/1745032/+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 1814387] Re: swithching workspace by scrolling on edge of Dock (left side bar)
Thank you for your bug report, what's the output of the command? - dpkg -l | grep dock the bug is similar to bug #1719706 but that was fixed, do you use the ubuntu dock or did you install dash to dock? ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- 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/1814387 Title: swithching workspace by scrolling on edge of Dock (left side bar) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Incomplete Bug description: If you position the mouse corsor on the edge of Dock and scroll, you can switch the workspace, which behaves equivalent to the scrolling on the "Show Applications" button in the corner. I've reproduced it on other Ubuntu 18 installations of friends (all 3 I tested, at least one was a fresh installation from the official iso). It is not important where Dock is or whether a window or the desktop is next to it. Program shortcuts have also no effect, because they end before it. It works with a single or 2 monitors on all instances of Dock. I use Ubuntu 18.04.1 LTS with all updates (via apt upgrade) installed and observed it for several months now. (After starting apport for this I updated again and nothing changed, no restart) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Feb 2 16:10:48 2019 DistUpgraded: 2018-10-01 14:59:21,229 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics Controller [1558:2300] Subsystem: CLEVO/KAPOK Computer GM107M [GeForce GTX 860M] [1558:2300] InstallationDate: Installed on 2017-03-18 (685 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Notebook W230SS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=907d4e48-c148-454e-aa8a-7adb74d51fb2 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2018-10-01 (124 days ago) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 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.2 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: Mon Oct 1 13:12:45 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1814387/+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 1803743] Re: Sometimes the sound disappears
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- 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/1803743 Title: Sometimes the sound disappears Status in pulseaudio package in Ubuntu: Expired Bug description: Здравствуйте! С переходом на 16.04 lts на моем компьютере иногда стал пропадать звук. Определить по какой причине так и не получилось. Если звук пропадает то помогает только перезагрузка. Обращался на форум, но безрезультатно https://forum.ubuntu.ru/index.php?topic=278602.0 Пару раз переустанавливал Убунту 16.04 и один раз Убунту 18.04 - но проблема осталась. Востанавливал по инструкции https://help.ubuntu.com/community/SoundTroubleshootingProcedure. Первых два шага не помогают. Проблема остается и звук появляется только при перезагрузке. Третий шаг это задать вопрос здесь, что я собственно и делаю. В третьем шаге предлагается специальный скрипт, который собирает всю необходимую информацию о системе и публикует ее на сайте. вот ссылка на отчет о моей системе в момент когда звук отсутствует http://www.alsa-project.org/db/?f=e3512ce403985434442eb1d4b4905e5bcab76ac8 Помогите, пожалуйста. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: a 1288 F pulseaudio /dev/snd/controlC0: a 1288 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 NonfreeKernelModules: nvidia_modeset nvidia Package: pulseaudio 1:11.1-1ubuntu7.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 Tags: bionic third-party-packages Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 11/02/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: None dmi.board.name: H61MLV2 dmi.board.vendor: BIOSTAR Group dmi.board.version: 6.0 dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.chassis.version: 6.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd11/02/2012:svnBIOSTARGroup:pnH61MLV2:pvr6.0:rvnBIOSTARGroup:rnH61MLV2:rvr6.0:cvnBIOSTARGroup:ct3:cvr6.0: dmi.product.family: None dmi.product.name: H61MLV2 dmi.product.version: 6.0 dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803743/+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 1666203] Re: pam_tty_audit failed in pam_open_session
The attachment "bionic-fix-for-lp-1666203.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Status in pam package in Debian: New Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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 1563110]
*** Bug 200431 has been marked as a duplicate of this bug. *** -- 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/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+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 1327041] Re: gdebi won't display content of gzip compressed files
[Expired for gdebi (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdebi (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdebi in Ubuntu. https://bugs.launchpad.net/bugs/1327041 Title: gdebi won't display content of gzip compressed files Status in gdebi package in Ubuntu: Expired Bug description: When I open a .deb file in gdebi and go to the "Included files" tab and click on a gzip compressed file, it should normally show its content on the right side. Instead it displays this error message: Error reading file content 'initial_value must be str or None, not bytes' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1327041/+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 145604]
It was nice to get update on the patch for LCD filtering from SuSE builds shared by David Turner, one of the freetype2 upstream developers that means a lot for users to refer his concern about regarding the LCD filtering and the Cairo patch are all on a public. Caroline, http://www.personalstatementfolks.co.uk/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/145604 Title: VRGB sub-pixel hinting causes black-on-black text rendering Status in libcairo: Unknown Status in cairo package in Ubuntu: Triaged Status in compiz package in Ubuntu: Invalid Status in compiz-fusion-plugins-main package in Ubuntu: Invalid Bug description: Binary package hint: libcairo2 There is a long-standing problem (Gutsy, Hardy, Intrepid - possibly Jaunty too) with sub-pixel rendering which affects metacity or compiz composition (see the images attached to this bug) when VRGB is chosen as the sub-pixel format. Comment #15 by MoMaT demonstrates a non- compiz scenario. My comments #2 and #10 demonstrate the issue with Compiz enabled. The underlying issue essentially seems to be: where should sub-pixel rendering should be done - in libcairo or in the font renderer (FreeType in this case) ? There have been two versions of the Ubuntu patch in libcairo/libcairo2. Reports seem to suggest that both versions may be responsible for the VRGB problem (however, that supposition needs checking - see Bob McElrath's comment #19). We need to be aware that libcairo (libcairo 1.5.4 in Universe) and libcairo2 (cairo 1.6.0 in Main) are similarly patched and will need similar fixes. To manage notifications about this bug go to: https://bugs.launchpad.net/libcairo/+bug/145604/+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 1813131] Re: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbo
Fixed in 2.4.0-1. ** Changed in: libva (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1813131 Title: i965_drv_video.so doesn't load any more if a Wayland server is present [failed to resolve wl_drm_interface(): /lib/x86_64-linux- gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface] Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in libva package in Ubuntu: Fix Released Bug description: If a Wayland server is present (anywhere on the system including even the gdm3 login screen) then i965_drv_video.so fails to initialize: $ vainfo libva info: VA-API version 1.3.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_2 error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit $ mpv bbb_sunflower_2160p_60fps_normal.mp4 Playing: bbb_sunflower_2160p_60fps_normal.mp4 (+) Video --vid=1 (*) (h264 3840x2160 60.000fps) (+) Audio --aid=1 (*) (mp3 2ch 48000Hz) Audio --aid=2 (*) (ac3 6ch 48000Hz) File tags: Artist: Blender Foundation 2008, Janus Bager Kristensen 2013 Comment: Creative Commons Attribution 3.0 - http://bbb3d.renderfarming.net Composer: Sacha Goedegebure Genre: Animation Title: Big Buck Bunny, Sunflower version error: failed to resolve wl_drm_interface(): /lib/x86_64-linux-gnu/libEGL_mesa.so.0: undefined symbol: wl_drm_interface [vaapi] libva: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed Meanwhile, it continues to work after you have logged into a Xorg session. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: i965-va-driver 2.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 Date: Thu Jan 24 16:54:21 2019 InstallationDate: Installed on 2018-12-04 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181203) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-vaapi-driver/+bug/1813131/+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 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
@xnox The grub config makes me believe the aws image is booted with initramfs. Thanks for responding, I wasn't sure if this was the right spot to report this bug. -- 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/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Fix Committed Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. * When a generator started to be provided by systemd, it was recognized that $PATH is not correctly set, nonetheless, due to an environment bug that systemd generators run in. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin Output should contain a complete and a valid PATH, i.e. PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin" or similar. [Regression Potential] * snapd generator was already fixed separately to cause no harm, when running under a broken systemd. With the corrected environment, generators will now run with a correct PATH out of the box. A slight change of PATH will be observed by all generators, when running in containers/initramfs-less boots. However most generators will not be affected as they typically do not execute external binaries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+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 1814391] [NEW] package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error
Public bug reported: i dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Feb 2 12:40:06 2019 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2018-04-23 (285 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: avahi Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: avahi (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1814391 Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in avahi package in Ubuntu: New Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Feb 2 12:40:06 2019 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2018-04-23 (285 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: avahi Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1814391/+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 1754075] Re: apt-setup uses apt-key but probably should not anymore
** Bug watch removed: Debian Bug tracker #886473 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886473 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/1754075 Title: apt-setup uses apt-key but probably should not anymore Status in apt-setup package in Ubuntu: Confirmed Status in gnupg package in Ubuntu: Confirmed Status in gnupg2 package in Ubuntu: Confirmed Status in apt-setup source package in Bionic: Confirmed Status in gnupg source package in Bionic: Confirmed Status in gnupg2 source package in Bionic: Confirmed Status in apt-setup package in Debian: Unknown Bug description: In di if the kernel is in a private PPA we seed di using d-i apt-setup/local0/key string http://keyserver.ubuntu.com:11371/pks/lookup?op=get= this used to work in xenial, but in bionic this fails and therefore apt update fails in base-installer. May be because add-apt-key is not installed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-setup/+bug/1754075/+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 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11
** No longer affects: freetype (Ubuntu) ** No longer affects: freetype (Ubuntu Bionic) ** No longer affects: freetype (Ubuntu Cosmic) ** Changed in: openjdk-lts (Ubuntu) Importance: Undecided => Medium ** Changed in: openjdk-lts (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: openjdk-lts (Ubuntu Cosmic) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to freetype in Ubuntu. https://bugs.launchpad.net/bugs/1799014 Title: bold font rendeing in Java is broken in Cosmic with OpenJDK 11 Status in openjdk-lts package in Ubuntu: Fix Released Status in openjdk-lts source package in Bionic: New Status in openjdk-lts source package in Cosmic: New Status in openjdk-11 package in Debian: Fix Released Bug description: Since update to Cosmic, I see that bold fonts in Java have broken rendering. See attached 400% scaled PNG for illustration. The 'r' in bold rendering of "Hello World" shows basically a vertical line from the end of the hook end. I am not entirely sure this is freetype issue but some sources (https://github.com/adobe/brackets/issues/14290) suggest there is a bug in the 2.8.1 version that Cosmic seems to install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-lts/+bug/1799014/+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 1814389] Re: Second extend of second lvmraid mirror does not sync
** Bug watch added: Red Hat Bugzilla #1671964 https://bugzilla.redhat.com/show_bug.cgi?id=1671964 ** Also affects: lvm2 via https://bugzilla.redhat.com/show_bug.cgi?id=1671964 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1814389 Title: Second extend of second lvmraid mirror does not sync Status in lvm2: Confirmed Status in lvm2 package in Ubuntu: New Bug description: This is a weird corner case. Extending an lvmraid(7) type1 mirror for the second time seems to result in the mirror legs not getting synced, *if* there is another type1 mirror in the vg. This reliably reproduces for me: # quickly fill two 10G files with random data openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv1.img iflag=fullblock openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv2.img iflag=fullblock # change loop devices if you have loads of snaps in use losetup /dev/loop10 pv1.img losetup /dev/loop11 pv2.img pvcreate /dev/loop10 pvcreate /dev/loop11 vgcreate testvg /dev/loop10 /dev/loop11 lvcreate --type raid1 -L2G -n test testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync lvcreate --type raid1 -L2G -n test2 testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will sync OK, observe kernel message for output from md subsys noting time taken # lvextend -L+2G testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will FAIL to sync, the sync will seem to complete instantly, e.g: # Feb 02 15:22:50 asr-host kernel: md: resync of RAID array mdX # Feb 02 15:22:50 asr-host kernel: md: mdX: resync done. # lvextend -L+2G testvg/test2 lvchange --syncaction check testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # observe error count This may cause administrator alarm unnecessarily ... :/ For some reason the precise sizes with which the LVs are created, and are then extended by, do appear to matter. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Sat Feb 2 15:33:16 2019 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.lvm.lvm.conf: 2018-07-22T18:30:15.470358 To manage notifications about this bug go to: https://bugs.launchpad.net/lvm2/+bug/1814389/+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 1763870] Re: openssl: After symbol versioning, distributed pkgs are missing API symbols (e.g. EVP_PKEY_asn1_set_item)
** Changed in: openssl (Ubuntu) Importance: Undecided => Medium ** Project changed: openssl => ubuntu ** No longer affects: ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1763870 Title: openssl: After symbol versioning, distributed pkgs are missing API symbols (e.g. EVP_PKEY_asn1_set_item) Status in openssl package in Ubuntu: New Status in openssl package in Debian: Fix Released Bug description: I'm developing an ENGINE for OpenSSL, and close to release, I noticed that in Ubuntu 16.04 LTS and in Debian oldstable-backports the build fails with the following output: ``` /usr/bin/cc -fPIC -g -shared -Wl,-soname,liblibsuola.so -o liblibsuola.so CMakeFiles/suola.dir/suola.c.o CMakeFiles/suola.dir/suola_keypair.c.o CMakeFiles/suola.dir/debug/debug.c.o CMakeFiles/suola.dir/meths/X25519_meth.c.o CMakeFiles/suola.dir/meths/ed25519_meth.c.o CMakeFiles/suola.dir/meths/suola_asn1_meth.c.o CMakeFiles/suola.dir/meths/suola_md_identity_meth.c.o CMakeFiles/suola.dir/ossl/ossl_compat.c.o CMakeFiles/suola.dir/ossl/suola_err.c.o CMakeFiles/suola.dir/ossl/suola_objects.c.o CMakeFiles/suola.dir/providers/libsodium/base.c.o CMakeFiles/suola.dir/providers/libsodium/curve25519.c.o CMakeFiles/suola.dir/providers/libsodium/ed25519.c.o -lssl -lcrypto /opt/libsodium-stable/lib/libsodium.so -Wl,-z,defs -Wl,-rpath,/opt/libsodium-stable/lib: CMakeFiles/suola.dir/meths/suola_asn1_meth.c.o: In function `suola_register_asn1_meth': /usr/local/src/libsuola/meths/suola_asn1_meth.c:505: undefined reference to `EVP_PKEY_asn1_set_item' collect2: error: ld returned 1 exit status make[2]: *** [liblibsuola.so] Error 1 CMakeFiles/suola.dir/build.make:412: recipe for target 'liblibsuola.so' failed make[2]: Leaving directory '/usr/local/src/libsuola/build' make[1]: *** [CMakeFiles/suola.dir/all] Error 2 make: *** [all] Error 2 ``` This does not happen linking against the same exact release of openssl compiled from source on the same system. I then learned that one of the patches applied by Debian and inherited also by Ubuntu has the goal of versioning library symbols to avoid conflicts. Unfortunately said patch is not updated regularly with each release of OpenSSL, resulting, like in my case, in symbols available in the public header files but masked through versioning in the shared library binary. The attached patch fixes my need by adding `EVP_PKEY_asn1_set_item` to the list, but you might consider an internal review of your release process to make sure that the list of symbols is updated whenever a new upstream releases makes new functions publicly available. I believe this bug is important, as it stops everyone using official packages from using third-party ENGINEs that require to use that function to set special handling of ASN.1 format, which basically includes every ENGINE that would add support for cryptosystems that upstream OpenSSL does not support (defying the purpose of using some ENGINEs). The patch I propose covers my use case, but basically the package as is results unusable to any user of any application that may require functions available in the public headers but accidentally masked in the symbol versioning step. The ideal outcome of fixing this issue would consist in making the versioning patch dynamic, checking when symbols are added (or removed) in newer releases and updating the list accordingly. You might have the same versioning patch applied in other releases, so it's worth tagging this bug also for those to make the handling of the exposed symbols consistent. Finally I also opened a similar bug against the equivalent Debian oldstable-backports package, but I opened an Ubuntu-specific bug report because 16.04 ships a more recent version of the package and the inherited symbol versioning patch has already been modified compared with the original Debian one. For reference this is the Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895547 -- System information -- # lsv_release -rd Description:Ubuntu 16.04.4 LTS Release:16.04 # apt-cache policy libssl-dev libssl-dev: Installed: 1.0.2g-1ubuntu4.11 Candidate: 1.0.2g-1ubuntu4.11 Version table: *** 1.0.2g-1ubuntu4.11 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 1.0.2g-1ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libssl-dev 1.0.2g-1ubuntu4.11 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16
[Touch-packages] [Bug 1814391] Re: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1
** Changed in: avahi (Ubuntu) Importance: Undecided => Low ** Changed in: avahi (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1814391 Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 Status in avahi package in Ubuntu: Invalid Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162 Uname: Linux 4.4.0-141-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sat Feb 2 12:40:06 2019 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 1 InstallationDate: Installed on 2018-04-23 (285 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: avahi Title: package avahi-daemon 0.6.32~rc+dfsg-1ubuntu2.3 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1814391/+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 1814389] Re: Second extend of second lvmraid mirror does not sync
Launchpad has imported 1 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1671964. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2019-02-02T20:36:33+00:00 steved424 wrote: Description of problem: Extending an lvmraid(7) type1 mirror for the second time seems to result in the mirror legs not getting synced, *if* there is another type1 mirror in the vg. Version-Release number of selected component (if applicable): 2.02.176 (4.1ubuntu3) How reproducible: Seems to be reliably reproducible here on Ubuntu 18.04 at least. Steps to Reproduce: # quickly fill two 10G files with random data openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv1.img iflag=fullblock openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv2.img iflag=fullblock # change loop devices if you have loads of snaps in use losetup /dev/loop10 pv1.img losetup /dev/loop11 pv2.img pvcreate /dev/loop10 pvcreate /dev/loop11 vgcreate testvg /dev/loop10 /dev/loop11 lvcreate --type raid1 -L2G -n test testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync lvcreate --type raid1 -L2G -n test2 testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will sync OK, observe kernel message for output from md subsys noting time taken # lvextend -L+2G testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will FAIL to sync, the sync will seem to complete instantly, e.g: # Feb 02 15:22:50 asr-host kernel: md: resync of RAID array mdX # Feb 02 15:22:50 asr-host kernel: md: mdX: resync done. # lvextend -L+2G testvg/test2 lvchange --syncaction check testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # observe error count Actual results: The sync after the final lvextend completes instantly, and a subsequent lvchange --syncaction check reports a high number for raid_mismatch_count Expected results: The sync after the final lvextend should take at least a few seconds, and a subsequent lvchange --syncaction check should not report any errors for raid_mismatch_count (unless the underlying hardware has failed.) Additional info: Launchpad bug: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1814389 Reply at: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1814389/comments/2 ** Changed in: lvm2 Status: Unknown => Confirmed ** Changed in: lvm2 Importance: Unknown => Undecided -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1814389 Title: Second extend of second lvmraid mirror does not sync Status in lvm2: Confirmed Status in lvm2 package in Ubuntu: New Bug description: This is a weird corner case. Extending an lvmraid(7) type1 mirror for the second time seems to result in the mirror legs not getting synced, *if* there is another type1 mirror in the vg. This reliably reproduces for me: # quickly fill two 10G files with random data openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv1.img iflag=fullblock openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | dd bs=$((1024*1024*1024)) count=10 of=pv2.img iflag=fullblock # change loop devices if you have loads of snaps in use losetup /dev/loop10 pv1.img losetup /dev/loop11 pv2.img pvcreate /dev/loop10 pvcreate /dev/loop11 vgcreate testvg /dev/loop10 /dev/loop11 lvcreate --type raid1 -L2G -n test testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync lvcreate --type raid1 -L2G -n test2 testvg watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will sync OK, observe kernel message for output from md subsys noting time taken # lvextend -L+2G testvg/test2 watch lvs -o +raid_sync_action,sync_percent,raid_mismatch_count testvg # wait for sync # the following will FAIL to sync, the sync will seem to complete instantly, e.g: # Feb 02 15:22:50 asr-host kernel: md: resync of RAID array mdX # Feb 02 15:22:50 asr-host kernel: md: mdX: resync done. # lvextend -L+2G testvg/test2 lvchange --syncaction check testvg/test2 watch lvs -o
[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
** Bug watch removed: github.com/systemd/systemd/issues #5882 https://github.com/systemd/systemd/issues/5882 -- 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/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Committed Bug description: [Impact] Mounting manually a network share (NFS) and masking it breaks the state of other units (and their dependencies). Casper is masking a mounted NFS share, blocking the normal boot process as described in the original description, but the issue comes from systemd. [Test Case] - NFS mount point at /media root@iscsi-bionic:/home/ubuntu# mount | grep media 10.230.56.72:/tmp/mnt on /media type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=192.168.122.127,local_lock=none,addr=10.230.56.72) - Test mount point (/test) defined in /etc/fstab: root@iscsi-bionic:/home/ubuntu# cat /etc/fstab |grep test tmpfs /test tmpfs nosuid,nodev 0 0 1. If media.mount is not masked, everything works fine: root@iscsi-bionic:/home/ubuntu# mount | grep test root@iscsi-bionic:/home/ubuntu# systemctl status media.mount | grep Active Active: active (mounted) since Thu 2018-11-15 16:03:59 UTC; 3 weeks 6 days ago root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:33:52 UTC; 4min 11s ago root@iscsi-bionic:/home/ubuntu# systemctl start test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: active (mounted) since Thu 2018-12-13 10:38:13 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: inactive (dead) since Thu 2018-12-13 10:38:32 UTC; 3s ago root@iscsi-bionic:/home/ubuntu# mount | grep test 2. If media.mount is masked, other mounts are failing: root@iscsi-bionic:/home/ubuntu# systemctl mask media.mount Created symlink /etc/systemd/system/media.mount → /dev/null. root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 10s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# systemctl status test.mount | grep Active Active: failed (Result: protocol) since Thu 2018-12-13 10:40:06 UTC; 25s ago root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl start test.mount Job for test.mount failed. See "systemctl status test.mount" and "journalctl -xe" for details. root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) root@iscsi-bionic:/home/ubuntu# systemctl stop test.mount root@iscsi-bionic:/home/ubuntu# mount | grep test tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) tmpfs on /test type tmpfs (rw,nosuid,nodev,relatime) [Regression potential] Minimal. Originally, one failing mount point blocked the processing of the rest due to how the return codes were handled for every line in /proc/self/mountinfo. This patch removes this "dependency" and keeps the failure local to the affected mount point, allowing the rest to be processed normally. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10874 Fixed upstream with commit: https://github.com/systemd/systemd/commit/c165888426ef99440418592a8cdbaff4b7c319b3 [Original Description] netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating
[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
** Also affects: gtk+3.0 (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=899147
Importance: Unknown
Status: Unknown
--
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/1714518
Title:
GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
shares in file chooser
Status in GTK+:
Fix Released
Status in gtk+3.0 package in Ubuntu:
Fix Released
Status in gtk+3.0 source package in Trusty:
Triaged
Status in gtk+3.0 source package in Xenial:
Triaged
Status in gtk+3.0 source package in Artful:
Won't Fix
Status in gtk+3.0 package in Debian:
Unknown
Bug description:
Steps to reproduce:
1. Install any Gtk3 application such as Firefox or Chromium which use modern
file-chooser dialog.
2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS,
"sftp://; = SFTP/SSH and so on)
3. Try to save/open file to/from the remote location from Gtk3 application.
Expected results:
* user is able to find network folder and save/open file to/from it with
GtkFileChooser dialog
Actual results:
* user is unable to find network folder and save/open file to/from it with
GtkFileChooser dialog and many user applications are affected
-
Original bug description is below:
GTK+3 doesn't show FUSE network shares in file chooser - it used to do
so in GTK+2, and the GTK+3 documentation still mentions it should do
it.
In the mean time, every user of every application switching to GTK+3
-- including Chromium, at some point between 58 and 60 -- (a change
which happened in 16.04 LTS!!), loses the functionality to open or
save directly to a network share.
I had chosen 16.04 LTS for deploying our workstations at work, and my 50
users have been suddenly unable to do a simple operation they have to do dozens
of times a day.
They now have to "buffer" these files to their local filesystem when saving
them and before uploading them, and then copy them to the company's network
shares.
They were already a little bit grumpy when it stopped working with Firefox,
and are now really side-eyeing me when they apply updates and find Chromium
broken.
I have reported the bug upstream and provided a patch to fix this. I
hope you'll be able and willing to include it to Ubuntu's GTK+3
package.
Thanks in advance.
Colin
To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1714518/+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 1814413] [NEW] Whatever I try to get a printer set up, I get a CUPS problem
Public bug reported: This is really not new, but it is frustrating that Ubuntu has not been able to fix this over the years. Just reinstalled 18.04 because I was getting graphics driver problems which were preventing me even updating software due to broken dependencies, and what should be an easy restore is driving me crazy. I had problems initially with my earlier installation of 18.04 but it sorted itself out I don't know how. Here is the information gathered from the Ubuntu DebuggingPrintingProblems link: john@john-ThinkCentre-M910t:~$ lsmod | grep lp glue_helper16384 1 aesni_intel lp 20480 0 parport49152 3 parport_pc,lp,ppdev drm_kms_helper172032 1 nouveau syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper drm 401408 6 drm_kms_helper,ttm,nouveau john@john-ThinkCentre-M910t:~$ lsmod | grep ppdev ppdev 20480 0 parport49152 3 parport_pc,lp,ppdev john@john-ThinkCentre-M910t:~$ lsmod | grep parport_pc parport_pc 36864 0 parport49152 3 parport_pc,lp,ppdev john@john-ThinkCentre-M910t:~$ dmesg | grep par [0.00] Booting paravirtualized kernel on bare hardware [0.00] vt handoff: transparent VT on vt#1 [0.03] evm: security.apparmor [0.229026] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.788589] Asymmetric key parser 'x509' registered [0.943520] xhci_hcd :00:14.0: hcc params 0x200077c1 hci version 0x100 quirks 0x9810 [1.566866] ahci :00:17.0: flags: 64bit ncq sntf pm led clo only pio slum part ems deso sadm sds apst [8.975011] ppdev: user-space parallel port driver [ 24.508038] audit: type=1400 audit(1549115193.742:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/ippusbxd" pid=778 comm="apparmor_parser" [ 24.508210] audit: type=1400 audit(1549115193.742:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=774 comm="apparmor_parser" [ 24.508212] audit: type=1400 audit(1549115193.742:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=774 comm="apparmor_parser" [ 24.508213] audit: type=1400 audit(1549115193.742:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=774 comm="apparmor_parser" [ 24.508374] audit: type=1400 audit(1549115193.742:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/cups-browsed" pid=776 comm="apparmor_parser" [ 24.508892] audit: type=1400 audit(1549115193.742:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/sbin/tcpdump" pid=780 comm="apparmor_parser" [ 24.513516] audit: type=1400 audit(1549115193.746:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince" pid=772 comm="apparmor_parser" [ 24.513517] audit: type=1400 audit(1549115193.746:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince//sanitized_helper" pid=772 comm="apparmor_parser" [ 24.513519] audit: type=1400 audit(1549115193.746:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer" pid=772 comm="apparmor_parser" [ 24.513534] audit: type=1400 audit(1549115193.746:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/evince-previewer//sanitized_helper" pid=772 comm="apparmor_parser" [ 7395.196639] audit: type=1400 audit(1549122564.441:35): apparmor="STATUS" operation="profile_load" profile="unconfined" name="snap-update-ns.vidcutter" pid=5626 comm="apparmor_parser" [ 7395.250076] audit: type=1400 audit(1549122564.497:36): apparmor="STATUS" operation="profile_load" profile="unconfined" name="snap.vidcutter.vidcutter" pid=5627 comm="apparmor_parser" [ 7396.667922] audit: type=1400 audit(1549122565.913:37): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/6350/usr/lib/snapd/snap-confine" pid=5999 comm="apparmor_parser" [ 7396.667924] audit: type=1400 audit(1549122565.913:38): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="/snap/core/6350/usr/lib/snapd/snap-confine//mount-namespace-capture-helper" pid=5999 comm="apparmor_parser" [ 7396.669940] audit: type=1400 audit(1549122565.917:39): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined" name="snap-update-ns.core" pid=6001 comm="apparmor_parser" [ 7396.670521] audit: type=1400 audit(1549122565.917:40): apparmor="STATUS" operation="profile_replace" info="same as current profile, skipping" profile="unconfined"
[Touch-packages] [Bug 1782535] Re: cifs - poor upload speed with nautilus compared to rsync
Thank you for the detail, if 'gio' also has the issue then it's a lower level issue and not a nautilus problem, reassigning. That's also probably an upstream issue and would be worth reporting on https://gitlab.gnome.org/GNOME/glib ** Package changed: nautilus (Ubuntu) => glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Status: Incomplete => New -- 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/1782535 Title: cifs - poor upload speed with nautilus compared to rsync Status in glib2.0 package in Ubuntu: New Bug description: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1782535/+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 991360] Re: isc-dhcp-client does not send hostnames in DHCPv6 by default
The opening line is somewhat misleading, even if in some sense it may be technically correct. > DHCPv6 does not have a host-name option to send the client hostname to register with the DHCP server. See option 39 OPTION_CLIENT_FQDN, and RFC 4704 "The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/991360 Title: isc-dhcp-client does not send hostnames in DHCPv6 by default Status in isc-dhcp package in Ubuntu: Fix Released Bug description: DHCPv6 does not have a host-name option to send the client hostname to register with the DHCP server. There are several potential options here: 1) Use the same "magic" to insert the hostname via fqdn.fqdn (i.e. "send fqdn.fqdn "";" This should work with DHCPv4 as well. 2) Backport the gethostname() functionality from DHCP 4.2. 3) Upgrade to isc-dhcp-client 4.2. Perhaps some of these are more appropriate to consider for the Q cycle. Personally, I think option 1 (implementing "" magic) for fqdn.fqdn would be the least intrusive. As issues go, this is admittedly minor. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: isc-dhcp-client 4.1.ESV-R4-0ubuntu5 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 CheckboxSubmission: 014d169fc2d78562c156088c6ab6adc0 CheckboxSystem: c69722ecac764861be52925fa50b4dcc Date: Sun Apr 29 13:19:49 2012 DhclientLeases: ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: isc-dhcp UpgradeStatus: Upgraded to precise on 2012-04-15 (14 days ago) mtime.conffile..etc.dhcp.dhclient.conf: 2011-09-26T21:03:34.986111 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/991360/+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 1781746] Re: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap
** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => Medium ** No longer affects: zram-config (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/1781746 Title: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled (for example zram-config installed) or swap is encrypted. Today lots of users have SSD instead of HDD disk drives and use zram swap instead of swap partition or swap file, but if initrd is generated when zram swap is enabled then system can become "unbootable" from the user's perspective (Users with SSD storage doesn't wait 2 or more minutes...) This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d [Test Case] Install zram-config package and regenerate and initrd, for example with sudo update-initramfs -u When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. [Regression Potential] None, patch simply adds case for /dev/zram*: 60case "$resume_auto" in 61/dev/zram*) 62ephemeral=true 63;; 64esac [Other Info] Manual method to disable this (as resuming from swap is not possible with an encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add (or change) line RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. and run sudo update-initramfs -u to apply the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+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 1782535] [NEW] cifs - poor upload speed with nautilus compared to rsync
You have been subscribed to a public bug: I'm mounting folders from my NAS on my computer (Ubuntu 18.04) with cifs. Copying an 8 GB file... Upload (local -> mounted) - Nautilus/Nemo -> 6 MB/s - rsync -> 50-60 MB/s Download performance is also strange, but not my biggest concern. Download (mounted -> local) - Nautilus/Nemo -> 90 MB/s - rsync -> 50-60 MB/s rsync command (upload): rsync --progress /home/me/file.iso /mnt/cifs_media/ fstab entry: //nas/media /mnt/cifs_media cifs vers=3.0,uid=me,gid=me,credentials=/home/me/.smbcredentials,dir_mode=0700,file_mode=0700 0 0 Any idea, why Nautilus is uploading up to 10 times more slowly than rsync, although both using the same cifs, os, hardware, network etc.? PS: Further info for bug report 1) The release of Ubuntu: Ubuntu 18.04 LTS 2) The version of the package: Nautilus 3.26.3 3) What you expected to happen: At least same speed as with using rsync 4) What happened instead: See above ** Affects: glib2.0 (Ubuntu) Importance: Low Status: New ** Tags: bionic -- cifs - poor upload speed with nautilus compared to rsync https://bugs.launchpad.net/bugs/1782535 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812095] Re: console login loop after entering username followed by RETURN
I'm have the same problem. Not even the update to linux-image-4.15.0-45-generic solved this. Like @lokkoze, I'm still using (choosing) linux-image-4.15.0-43-generic where the problem not exist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1812095 Title: console login loop after entering username followed by RETURN Status in shadow package in Ubuntu: Confirmed Bug description: login: password: Just do nothing. About two seconds later ... login: password: login: password: login: password: After this being displayed three times: "Too many failure" or so and login is restarting. You cant login at all. Only solution: clear the password for the account you want to login with. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20 Uname: Linux 4.18.0-14-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 16 19:34:30 2019 InstallationDate: Installed on 2011-10-19 (2645 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: shadow UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
** No longer affects: cups-filters (Ubuntu) -- 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/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in gtk+3.0 package in Ubuntu: In Progress Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET97WW (2.57 ) dmi.board.asset.tag: Not Available dmi.board.name: 2306CTO dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information
[Touch-packages] [Bug 1666203] Re: pam_tty_audit failed in pam_open_session
Attached patch (which is based on pam_1.1.8-3.6ubuntu2) fixes the issue for Ubuntu 18.04/Bionic Following fix was implemented as mentioned by the reporter of the LP bug: https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee I tested the patch and it indeed resolves the issue: pam_tty_audit now works as expected and users are still able to login after adding: session required pam_tty_audit.so enable=root to /etc/pam.d/common-session "aureport --tty" shows the expected output. * Fix: pam_tty_audit failed in pam_open_session (LP: #1666203) The patch has also been submitted to Debian. ** Patch added: "bionic-fix-for-lp-1666203.debdiff" https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+attachment/5235473/+files/bionic-fix-for-lp-1666203.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1666203 Title: pam_tty_audit failed in pam_open_session Status in pam package in Ubuntu: Triaged Status in pam package in Debian: New Bug description: Dear Maintainer. I found a bug in pam_tty_audit. When Using the pam_tty_audit with other pam modules(ex, pam_ldap), it failed in pam_open_session. It was triggared by use uninitialized variable in pam_tty_audit.c::pam_open_session. * Enviroments Ubuntu 14.04.4 LTS linux-image-3.16.0-71-generic3.16.0-71.92~14.04.1 libpam-ldap:amd64184-8.5ubuntu3 libpam-modules:amd641.1.8-1ubuntu2.2 Ubuntu 16.04.2 TLS linux-image-4.4.0-62-generic4.4.0-62.83 libpam-ldap:amd64184-8.7ubuntu1 libpam-modules:amd641.1.8-3.2ubuntu2 * Reproduction method 1. Install libpam-ldap. 2. Add the following to the end of /etc/pam.d/common-sessions session required pam_tty_audit.so enable=* open_only 3. When logging in with ssh etc., pam_tty_audit will fail and login fails * Solution (== 2018/04/16 Link updated ==) apply upstream patch https://github.com/linux-pam/linux-pam/commit/c5f829931a22c65feffee16570efdae036524bee * Logs (on Ubuntu14.04) -- auth.log -- May 18 14:47:03 vm sshd[2272]: Accepted publickey for test from 10.99.0.1 port 51398 ssh2: RSA 8f:39:1c:3a:f4:9d:ca:99:67:fc:e3:fd:1e:0c:5b:a8 May 18 14:47:03 vm sshd[2272]: pam_unix(sshd:session): session opened for user test by (uid=0) May 18 14:47:03 vm sshd[2272]: pam_tty_audit(sshd:session): error setting current audit status: Invalid argument May 18 14:47:03 vm sshd[2272]: error: PAM: pam_open_session(): Cannot make/remove an entry for the specified session May 18 14:47:03 vm sshd[2297]: Received disconnect from 10.99.0.1: 11: disconnected by user -- syslog -- May 18 14:47:03 vm audispd: node=vm type=USER_ACCT msg=audit(1463550423.399:58): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.403:59): pid=2272 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=LOGIN msg=audit(1463550423.403:60): pid=2272 uid=0 old-auid=4294967295 auid=20299 old-ses=4294967295 ses=3 res=1 May 18 14:47:03 vm audispd: node=vm type=CONFIG_CHANGE msg=audit(1463550423.403:61): pid=2272 uid=0 auid=20299 ses=3 op=tty_set old-enabled=0 new-enabled=1 old-log_passwd=0 new-log_passwd=32743 res=0 May 18 14:47:03 vm audispd: node=vm type=USER_START msg=audit(1463550423.447:62): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:session_open acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=failed' May 18 14:47:03 vm audispd: node=vm type=CRED_ACQ msg=audit(1463550423.447:63): pid=2297 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' May 18 14:47:03 vm audispd: node=vm type=CRED_DISP msg=audit(1463550423.451:64): pid=2272 uid=0 auid=20299 ses=3 msg='op=PAM:setcred acct="test" exe="/usr/sbin/sshd" hostname=10.99.0.1 addr=10.99.0.1 terminal=ssh res=success' Thanks regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1666203/+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
