[Touch-packages] [Bug 1839589] [NEW] pulseaudio FTBFS on eoan 12.2-2ubuntu4
Public bug reported: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1839589 Title: pulseaudio FTBFS on eoan 12.2-2ubuntu4 Status in pulseaudio package in Ubuntu: New Bug description: pulseaudio fails to build from source on Eoan I was attempting to put together a patchset for LP#1839580, but it appears as if the packages are currently failing to build from source. Not sure how they built the first time around. Here's my ppa's buildlog, for a source package with my patch commented out of the series file. https://launchpadlibrarian.net/436626918/buildlog_ubuntu-eoan-amd64.pulseaudio_1%3A12.2-2ubuntu4+lp1839580b2_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839589/+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 1839586] Re: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839586 Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cups package in Ubuntu: New Bug description: error at the start of the pc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 AptOrdering: cups-filters:amd64: Install NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Wed Aug 7 06:58:27 2019 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-07-30 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_400_M401dn_817E04_: ipp://ZXDSL83C1II.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3050 Papersize: letter PpdFiles: HP_LaserJet_400_M401dn_817E04_: LaserJet 400 M401dn ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0W0CHX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd05/08/2017:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0W0CHX:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839586/+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 1839586] [NEW] package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: error at the start of the pc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 AptOrdering: cups-filters:amd64: Install NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Wed Aug 7 06:58:27 2019 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-07-30 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_400_M401dn_817E04_: ipp://ZXDSL83C1II.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3050 Papersize: letter PpdFiles: HP_LaserJet_400_M401dn_817E04_: LaserJet 400 M401dn ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0W0CHX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd05/08/2017:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0W0CHX:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.sys.vendor: Dell Inc. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839586 Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in cups package in Ubuntu: New Bug description: error at the start of the pc ProblemType: Package DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 AptOrdering: cups-filters:amd64: Install NULL: ConfigurePending Architecture: amd64 CupsErrorLog: Date: Wed Aug 7 06:58:27 2019 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2019-07-30 (9 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lpstat: device for HP_LaserJet_400_M401dn_817E04_: ipp://ZXDSL83C1II.local:631/ipp/print Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:301a Dell Computer Corp. Bus 001 Device 002: ID 413c:2113 Dell Computer Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. OptiPlex 3050 Papersize: letter PpdFiles: HP_LaserJet_400_M401dn_817E04_: LaserJet 400 M401dn ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=4551de30-9a56-4e58-a09d-4b13f33a67fb ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: cups Title: package cups 2.2.7-1ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0W0CHX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd05/08/2017:svnDellInc.:pnOptiPlex3050:pvr:rvnDellInc.:rn0W0CHX:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.family: OptiPlex dmi.product.name: OptiPlex 3050 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839586/+subscriptions -- Mailing list: https://la
[Touch-packages] [Bug 1839580] Re: LucidSound LS31 only outputs mono sound
** Tags added: eoan -- 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/1839580 Title: LucidSound LS31 only outputs mono sound Status in pulseaudio package in Ubuntu: In Progress Bug description: LucidSound LS31 only outputs mono sound. The usb vendor:prod = 2f12:0109. The fix is incoming. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839580/+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 1839580] Re: LucidSound LS31 only outputs mono sound
Upstream merge request. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/143 -- 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/1839580 Title: LucidSound LS31 only outputs mono sound Status in pulseaudio package in Ubuntu: In Progress Bug description: LucidSound LS31 only outputs mono sound. The usb vendor:prod = 2f12:0109. The fix is incoming. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839580/+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 1839580] [NEW] LucidSound LS31 only outputs mono sound
Public bug reported: LucidSound LS31 only outputs mono sound. The usb vendor:prod = 2f12:0109. The fix is incoming. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Assignee: Dave Chiluk (chiluk) Status: In Progress ** Changed in: pulseaudio (Ubuntu) Status: New => In Progress -- 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/1839580 Title: LucidSound LS31 only outputs mono sound Status in pulseaudio package in Ubuntu: In Progress Bug description: LucidSound LS31 only outputs mono sound. The usb vendor:prod = 2f12:0109. The fix is incoming. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1839580/+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 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]
[Expired for bluez (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bluez (Ubuntu) Status: Incomplete => Expired -- 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/1831995 Title: Bluetooth earphone is connected but disconnected immediately. [Intel 3165] Status in bluez package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+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 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- 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/1831995 Title: Bluetooth earphone is connected but disconnected immediately. [Intel 3165] Status in bluez package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+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 1831995] Re: Bluetooth earphone is connected but disconnected immediately. [Intel 3165]
[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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1831995 Title: Bluetooth earphone is connected but disconnected immediately. [Intel 3165] Status in bluez package in Ubuntu: Expired Status in linux-firmware package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
please install headers first: sudo apt install linux-headers-5.0.0-24 sudo apt install linux-headers-5.0.0-24-generic Then install the dkms. -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
@Hui Wang Last time, I installed the file by double click it, as I see it's a .deb file. The installation process went with no issue at all. Now this time, I am trying to install the file via terminal. But it never finish the building, as shown my terminal like this... (Reading database ... 161794 files and directories currently installed.) Preparing to unpack oem-audio-hda-daily-dkms_0.1_all.deb ... Uninstall Beginning Module: oem-audio-hda-daily Version: 0.1 Kernel: 5.0.0-24-generic (x86_64) - Status: Before uninstall, this module version was ACTIVE on this kernel. snd-hda-codec-ca0132.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-realtek.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-ca0110.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-si3054.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-idt.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-analog.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-intel.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-cmedia.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-via.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-cirrus.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-hdmi.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-conexant.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. snd-hda-codec-generic.ko: - Uninstallation - Deleting from: /lib/modules/5.0.0-24-generic/ rmdir: failed to remove '': No such file or directory - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod DKMS: uninstall
[Touch-packages] [Bug 1839576] [NEW] cannot print any document
Public bug reported: Additional software needed, but when i click it and open ubuntu software center there is nothing in there i can install. and when i try to print some document it is always canceled somehow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.6 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 09:58:41 2019 InstallationDate: Installed on 2019-08-01 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for Canon-iP1800-series: usb://Canon/iP1800%20series?serial=40DDFE MachineType: Hewlett-Packard HP 14 Notebook PC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-iP1800-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-iP1800-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffe3c507-56e6-4dbf-aeee-da9a6d7c68d4 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2335 dmi.board.vendor: Hewlett-Packard dmi.board.version: 05.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr098F120600087:rvnHewlett-Packard:rn2335:rvr05.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.sku: K8U41PA#AR6 dmi.product.version: 098F120600087 dmi.sys.vendor: Hewlett-Packard ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839576 Title: cannot print any document Status in cups package in Ubuntu: New Bug description: Additional software needed, but when i click it and open ubuntu software center there is nothing in there i can install. and when i try to print some document it is always canceled somehow. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2.6 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Aug 9 09:58:41 2019 InstallationDate: Installed on 2019-08-01 (8 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lpstat: device for Canon-iP1800-series: usb://Canon/iP1800%20series?serial=40DDFE MachineType: Hewlett-Packard HP 14 Notebook PC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon-iP1800-series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon-iP1800-series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-23-generic root=UUID=ffe3c507-56e6-4dbf-aeee-da9a6d7c68d4 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2335 dmi.board.vendor: Hewlett-Packard dmi.board.version: 05.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP14NotebookPC:pvr098F120600087:rvnHewlett-Packard:rn2335:rvr05.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP 14 Notebook PC dmi.product.sku: K8U41PA#AR6 dmi.product.version: 098F120600087 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839576/+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 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
I enabled bionic-proposed and installed ibus, ibus-gtk, ibus-gtk3 versions 1.5.17-3ubuntu5. I ran the test in a bionic VM which had VMware Horizon Agent for Linux installed, version 7.9.0-13916467. Running firefox with no environment variables caused long input delays and small lockups with the affected gnome-shell library shipped by VMware Horizon. When enabling the following environment variables for ibus which are implemented as part of this SRU: $ env IBUS_DISCARD_PASSWORD=1 firefox and $ export IBUS_DISCARD_PASSWORD_APPS="firefox" $ firefox I could enter text into password fields in firefox with no problems at all, and the problem is fixed. The customer has also validated that the fix works in their VMware Horizon environment, and the problem is solved. I am happy to mark this as verified. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Bionic: Fix Committed Bug description: [Impact] The following has been seen in a VMware Horizon VDI. I cannot reproduce this issue myself. When a user interacts with any password field in Firefox, gnome-shell and Firefox both freeze and the system becomes unusable. If you ssh into the system and terminate Firefox, gnome-shell unfreezes. This only happens when the environment variable GTK_IM_MODULE is set to "ibus". If you unset the variable, or change it to GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works as intended. This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus 1.5.17-3ubuntu4 and Firefox versions starting with 68.0+build3-0ubuntu0.18.04.1 Note: Chrome[ium] and other applications do not trigger it, and it cannot be reproduced in other desktop environments. This seems to be an interaction issue between ibus and gnome-shell. [Test Case] Launch firefox from within a gnome-session, making sure the GTK_IM_MODULE is set to "ibus". Note, this is the default value. $ env GTK_IM_MODULE="ibus" firefox Navigate to any website which has a password field. Wikipedia or Reddit will do. Click a password field and attempt to enter text. Firefox and gnome- shell both lock up and stay frozen for an extended period of time. Now, try it with the fix by enabling: $ env IBUS_DISCARD_PASSWORD=1 firefox When you enter text into a password field, ibus should directly pass through the text and the problem will be solved. We can also ask it to always apply for a specific application with: $ export IBUS_DISCARD_PASSWORD_APPS="firefox" $ firefox Again, when you enter text into a password input field, the problem will be solved. Test package is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test Please test with the revised version, 1.5.17-3ubuntu4+sf235370v20190731b1. [Regression Potential] This change has a low risk of regression, because the default behaviour is unchanged. To be able to use the password input field discard functionality, a user has to explicitly set an environment variable for the specific process, or set a regex that matches a process name. This means the fix is not enabled by default on any machines, and will only be utilised by those suffering problems and go and manually set environment variables or have their system administrator enable the environment variables permanently. This commit is present in upstream ibus from version ibus-1.5.19 onward, and is currently present in cosmic, disco and eoan. If a regression occurs, users can ensure that the environment variables are unset and continue working. [Other info] * This patch is functionally the same as ibus-xx-f19-password.patch, but just hides the features behind environment variables. * When ibus is built with the patch ibus-xx-f19-password.patch which was dropped in ibus-1.5.17-2, the problem is solved. Instead of using ibus-xx-f19-password.patch, we will instead fix it with upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0: https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0 Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome Author: fujiwarat This implements the password discard functionality found in ibus-xx-f19-password.patch and places it behind two environment variables, IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS. IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS lets you set a regex of process names to filter and enable the fix for. If IBUS_DISCARD_PASSWORD is set or IBUS_DISC
[Touch-packages] [Bug 1838370] Re: slapd segfault on filter parse error
Here is a quick reproducer. sudo apt update sudo apt install slapd ldap-utils -y Reconfigure the slapd package. When asked about a domain, use "example.com". Choose a password, and accept defaults for everything else: sudo dpkg-reconfigure slapd Create a file called add-rwm.ldif with these contents: dn: cn=module{0},cn=config changetype: modify add: olcModuleLoad olcModuleLoad: rwm dn: olcOverlay=rwm,olcDatabase={1}mdb,cn=config changetype: add objectClass: olcOverlayConfig objectClass: olcRwmConfig olcOverlay: rwm olcRwmRewrite: {0} rwm-rewriteEngine "on" olcRwmRewrite: {1} rwm-rewriteContext "searchFilter" olcRwmRewrite: {2} rwm-rewriteRule "(.*)(uid=root)(.*)" "$1$2$3" "#" Then run: sudo ldapadd -Q -Y EXTERNAL -H ldapi:/// -f add-rwm.ldif And then, to trigger the crash: ldapsearch -x -h localhost -b dc=example,dc=com -LLL uid=root slapd will die, and /var/crash will have a crash file for slapd. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Disco: Confirmed Bug description: Hello! We have faced slapd crash, seems an attacker was trying to brute force one of our services and uid parsing failures caused slapd crash: Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH base="ou=test,dc=test,dc=com" scope=2 deref=0 filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadow Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host loginDisabled loginExpirationTime loginAllowedTimeMap sshPublic Key Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text=massaged filter parse error Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip 7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so [7fc8d1868000+1c] Another faulty filter example: filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0" filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ slapd -VVV @(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $ buildd@lcy01-amd64-019 :/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd Included static backends: config ldif $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1838370/+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 1839545] [NEW] Graphic environment slows down and then returns to normal
Private bug reported: After updating the mesa, the management of my graphic environment is no longer as fluid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libegl-mesa0 19.1.4-1ubuntu1 Uname: Linux 5.2.7-050207-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 16:46:39 2019 DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.10, 5.2.7-050207-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486] InstallationDate: Installed on 2018-12-02 (249 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.7-050207-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2018-12-02 (249 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.1.4-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan regression single-occurrence ubuntu wayland-session ** Information type changed from Public to Private -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1839545 Title: Graphic environment slows down and then returns to normal Status in mesa package in Ubuntu: New Bug description: After updating the mesa, the management of my graphic environment is no longer as fluid. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: libegl-mesa0 19.1.4-1ubuntu1 Uname: Linux 5.2.7-050207-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 16:46:39 2019 DistUpgraded: 2018-12-02 16:59:40,473 DEBUG inhibit gnome-session idle DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.10, 5.2.7-050207-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:8486] InstallationDate: Installed on 2018-12-02 (249 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.7-050207-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to eoan on 2018-12-02 (249 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-me
[Touch-packages] [Bug 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
I can verify that here as well uname -a Linux localhost 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux chris@localhost:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic echo $DESKTOP_SESSION gnome journalctl -b 0 | grep -i fail | grep -i colord Aug 07 17:47:57 localhost colord[1249]: failed to get session [pid 1062]: No data available Aug 07 17:47:58 localhost colord[1249]: failed to get session [pid 1062]: No data available Aug 08 00:06:43 localhost colord[1249]: failed to get session [pid 11911]: No data available Aug 08 00:06:43 localhost colord[1249]: failed to get session [pid 11911]: No data available -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1839533] [NEW] .whl/.egg support in lesspipe is undocumented
Public bug reported: Support for .whl/.egg files (used in Python packaging) was added to lesspipe in version 487-0.1 of less[1], but the lesspipe(1) manual page was apparently not updated at the time, and does not currenly list .whl/.egg as supported file types. This looks like a Debian bug, since the manual page was apparently written for Debian, but reportbug complains at me when I try to use it to submit a bug to the Debian BTS, so hopefully someone who knows what they're doing can report this upstream. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862048 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: less 487-0.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: i3 Date: Thu Aug 8 20:07:51 2019 Dependencies: debianutils 4.8.4 gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libtinfo5 6.1-1ubuntu1.18.04 InstallationDate: Installed on 2018-08-13 (360 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: less UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: less (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1839533 Title: .whl/.egg support in lesspipe is undocumented Status in less package in Ubuntu: New Bug description: Support for .whl/.egg files (used in Python packaging) was added to lesspipe in version 487-0.1 of less[1], but the lesspipe(1) manual page was apparently not updated at the time, and does not currenly list .whl/.egg as supported file types. This looks like a Debian bug, since the manual page was apparently written for Debian, but reportbug complains at me when I try to use it to submit a bug to the Debian BTS, so hopefully someone who knows what they're doing can report this upstream. [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862048 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: less 487-0.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: i3 Date: Thu Aug 8 20:07:51 2019 Dependencies: debianutils 4.8.4 gcc-8-base 8.3.0-6ubuntu1~18.04.1 libc6 2.27-3ubuntu1 libgcc1 1:8.3.0-6ubuntu1~18.04.1 libtinfo5 6.1-1ubuntu1.18.04 InstallationDate: Installed on 2018-08-13 (360 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: less UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1839533/+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 1442050] Re: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2
Still in 18.04 LTS > uname -a Linux Meerkat 5.0.0-23-generic #24~18.04.1-Ubuntu SMP Mon Jul 29 16:12:28 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux > lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.3 LTS Release:18.04 Codename: bionic > echo $DESKTOP_SESSION ubuntu > journalctl -b 0 | grep -i fail | grep -i colord Aug 07 16:25:47 Meerkat colord[981]: failed to get session [pid 847]: No data available Aug 07 16:25:47 Meerkat colord[981]: failed to get session [pid 847]: No data available Aug 08 00:08:17 Meerkat colord[981]: failed to get session [pid 9890]: No data available Aug 08 00:08:17 Meerkat colord[981]: failed to get session [pid 9890]: No data available -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to colord in Ubuntu. https://bugs.launchpad.net/bugs/1442050 Title: (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 Status in colord package in Ubuntu: Confirmed Bug description: Get that error logged into journalctl (colord:832): Cd-WARNING **: failed to get session [pid 690]: Unknown error -2 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-6ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.17-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Thu Apr 9 11:57:02 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-12-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/colord/+bug/1442050/+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 1838836] Re: network-manager needs to be restarted frequently
Here's the syslog, starting at the point where I have a connection to a local wifi, and then I have a failed switch to the other local wifi. (I am sending this after capturing the log, and restarting the network- manager service.) Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3253] device (wlp62s0): disconnecting for new activation request. Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3253] device (wlp62s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed') Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3255] manager: NetworkManager state is now DISCONNECTING Aug 8 10:01:22 serval whoopsie[2549]: [10:01:22] offline Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3316] audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" name="ATT964" pid=11238 uid=1010 result="success" Aug 8 10:01:22 serval NetworkManager[14891]: [1565283682.3317] device (wlp62s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed') Aug 8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection (0x556db1161660), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for context 0x556db1607240 == Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0 556db14b6d08 i resource:///org/gnome/shell/ui/status/network.js:1318 (7f9b93d73dc0 @ 56) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1 556db14b6c70 i resource:///org/gnome/shell/ui/status/network.js:1335 (7f9b93d73e50 @ 113) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2 556db14b6bd0 i resource:///org/gnome/shell/ui/status/network.js:2039 (7f9b93d771f0 @ 216) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #3 556db14b6b50 i resource:///org/gnome/shell/ui/status/network.js:1934 (7f9b93d75dc0 @ 80) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #4 7fff53218340 b self-hosted:979 (7f9b93f50a60 @ 440) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for context 0x556db1607240 == Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0 556db14b6d18 i resource:///org/gnome/shell/ui/status/network.js:1318 (7f9b93d73dc0 @ 56) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1 556db14b6c80 i resource:///org/gnome/shell/ui/status/network.js:1335 (7f9b93d73e50 @ 113) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2 556db14b6be0 i resource:///org/gnome/shell/ui/status/network.js:2039 (7f9b93d771f0 @ 216) Aug 8 10:01:22 serval gnome-shell[11238]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1322:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1335:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2039:52#012_syncNMState@resource:///org/gnome/shell/ui/status/network.js:1934:9 Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #3 556db14b6b50 i resource:///org/gnome/shell/ui/status/network.js:1842 (7f9b93d75790 @ 138) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #4 7fff53218340 b self-hosted:979 (7f9b93f50a60 @ 440) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: == Stack trace for context 0x556db1607240 == Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #0 556db14b6bf8 i resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f9bb45b90d0 @ 25) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #1 556db14b6b50 i resource:///org/gnome/shell/ui/status/network.js:1815 (7f9b93d75700 @ 111) Aug 8 10:01:22 serval org.gnome.Shell.desktop[11238]: #2 7fff53218340 b self-hosted:979 (7f9b93f50a60 @ 440) Aug 8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection (0x556db1161660), has been already deallocated — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Aug 8 10:01:22 serval gnome-shell[11238]: JS ERROR: TypeError: connection.get_setting_ip4_config is not a function#012_isHotSpotMaster@resource:///org/gnome/shell/ui/status/network.js:1322:25#012getIndicatorIcon@resource:///org/gnome/shell/ui/status/network.js:1335:13#012_updateIcon@resource:///org/gnome/shell/ui/status/network.js:2039:52#012_syncVpnConnections@resource:///org/gnome/shell/ui/status/network.js:1842:9 Aug 8 10:01:22 serval gnome-shell[11238]: Object NM.ActiveConnection (0x556db1161660), has been already deallocated — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Aug 8 10:01:
[Touch-packages] [Bug 1839329] Re: pgrep: Use POSIX _SC_ARG_MAX for maximum pgrep -f command line length
** Changed in: procps (Ubuntu) Status: In Progress => Fix Committed ** Summary changed: - pgrep: Use POSIX _SC_ARG_MAX for maximum pgrep -f command line length + pgrep: allows long command lines to be searched e.g. java process with long classpath -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1839329 Title: pgrep: allows long command lines to be searched e.g. java process with long classpath Status in procps package in Ubuntu: Fix Committed Status in procps source package in Xenial: In Progress Status in procps source package in Bionic: In Progress Status in procps source package in Disco: In Progress Bug description: [Impact] The pgrep -f and pkill -f commands are unable to find processes strings in processes which are beyond the 4096th character. This often happens with Java command lines with long classpaths on the command line. [Test Case] A quick test to reproduce this is to vi a file using a filename over 4k $ vi $(seq 1 1250| paste -s -d'_')_foo.txt) and leave vi running then run from another terminal $ pgrep -af 'foo.txt' to find it. Without the fix, one will only see the first 4096 chars, while the expected behaviour would be: $ pgrep -af 'foo.txt' 27667 vi 1_2_3_4_5_6_7_8_9_10_11_12_13_14_15_16_17_18_19_20_21_22_23_24_25_26_27_28_29_30_31_32_33_34_35_36_37_38_39_40_41_42_43_44_45_46_47_48_49_50_51_52_53_54_55_56_57_58_59_60_61_62_63_64_65_66_67_68_69_70_71_72_73_74_75_76_77_78_79_80_81_82_83_84_85_86_87_88_89_90_91_92_93_94_95_96_97_98_99_100_101_102_103_104_105_106_107_108_109_110_111_112_113_114_115_116_117_118_119_120_121_122_123_124_125_126_127_128_129_130_131_132_133_134_135_136_137_138_139_140_141_142_143_144_145_146_147_148_149_150_151_152_153_154_155_156_157_158_159_160_161_162_163_164_165_166_167_168_169_170_171_172_173_174_175_176_177_178_179_180_181_182_183_184_185_186_187_188_189_190_191_192_193_194_195_196_197_198_199_200_201_202_203_204_205_206_207_208_209_210_211_212_213_214_215_216_217_218_219_220_221_222_223_224_225_226_227_228_229_230_231_232_233_234_235_236_237_238_239_240_241_242_243_244_245_246_247_248_249_250_251_252_253_254_255_256_257_258_259_260_261_262_263_264_265_266_267_268_269_270_271_272_273_274_275_276_277_278_279_280_281_282_283_284_285_286_287_288_289_290_291_292_293_294_295_296_297_298_299_300_301_302_303_304_305_306_307_308_309_310_311_312_313_314_315_316_317_318_319_320_321_322_323_324_325_326_327_328_329_330_331_332_333_334_335_336_337_338_339_340_341_342_343_344_345_346_347_348_349_350_351_352_353_354_355_356_357_358_359_360_361_362_363_364_365_366_367_368_369_370_371_372_373_374_375_376_377_378_379_380_381_382_383_384_385_386_387_388_389_390_391_392_393_394_395_396_397_398_399_400_401_402_403_404_405_406_407_408_409_410_411_412_413_414_415_416_417_418_419_420_421_422_423_424_425_426_427_428_429_430_431_432_433_434_435_436_437_438_439_440_441_442_443_444_445_446_447_448_449_450_451_452_453_454_455_456_457_458_459_460_461_462_463_464_465_466_467_468_469_470_471_472_473_474_475_476_477_478_479_480_481_482_483_484_485_486_487_488_489_490_491_492_493_494_495_496_497_498_499_500_501_502_503_504_505_506_507_508_509_510_511_512_513_514_515_516_517_518_519_520_521_522_523_524_525_526_527_528_529_530_531_532_533_534_535_536_537_538_539_540_541_542_543_544_545_546_547_548_549_550_551_552_553_554_555_556_557_558_559_560_561_562_563_564_565_566_567_568_569_570_571_572_573_574_575_576_577_578_579_580_581_582_583_584_585_586_587_588_589_590_591_592_593_594_595_596_597_598_599_600_601_602_603_604_605_606_607_608_609_610_611_612_613_614_615_616_617_618_619_620_621_622_623_624_625_626_627_628_629_630_631_632_633_634_635_636_637_638_639_640_641_642_643_644_645_646_647_648_649_650_651_652_653_654_655_656_657_658_659_660_661_662_663_664_665_666_667_668_669_670_671_672_673_674_675_676_677_678_679_680_681_682_683_684_685_686_687_688_689_690_691_692_693_694_695_696_697_698_699_700_701_702_703_704_705_706_707_708_709_710_711_712_713_714_715_716_717_718_719_720_721_722_723_724_725_726_727_728_729_730_731_732_733_734_735_736_737_738_739_740_741_742_743_744_745_746_747_748_749_750_751_752_753_754_755_756_757_758_759_760_761_762_763_764_765_766_767_768_769_770_771_772_773_774_775_776_777_778_779_780_781_782_783_784_785_786_787_788_789_790_791_792_793_794_795_796_797_798_799_800_801_802_803_804_805_806_807_808_809_810_811_812_813_814_815_816_817_818_819_820_821_822_823_824_825_826_827_828_829_830_831_832_833_834_835_836_837_838_839_840_841_842_843_844_845_846_847_848_849_850_851_852_853_854_855_856_857_858_859_860_861_862_863_864_865_866_867_868_869_870_871_872_873_874_875_876_877_878_879_880_881_882_883_884_885_886_887_888_889_890_891_892_893_894_895_896_897_898_899_900_901_902_903_904_905_906_907_908_909_910_911_912_913_914_915_916_917_918_919_920_921_922_923_924_925_926_927_928_929_930_931_932_933_934_935_9
[Touch-packages] [Bug 1726129] Re: nautilus crashed with SIGSEGV in widget_needs_widget_path
** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1726129 Title: nautilus crashed with SIGSEGV in widget_needs_widget_path Status in Nautilus: Unknown Status in gtk+3.0 package in Ubuntu: New Status in nautilus package in Ubuntu: Triaged Bug description: https://gitlab.gnome.org/GNOME/nautilus/issues/1190 --- https://errors.ubuntu.com/problem/7c06cf06fd970ce31033f0d775b3adf97559e4ea ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: nautilus 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Budgie:GNOME Date: Sun Oct 22 15:30:05 2017 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2017-10-19 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) ProcCmdline: nautilus --new-window ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7fe0115bd2a4:mov0x380(%rax),%rax PC (0x7fe0115bd2a4) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1726129/+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 1839329] Re: pgrep: Use POSIX _SC_ARG_MAX for maximum pgrep -f command line length
** Changed in: procps (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: procps (Ubuntu Disco) Importance: Undecided => Low ** Changed in: procps (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1839329 Title: pgrep: Use POSIX _SC_ARG_MAX for maximum pgrep -f command line length Status in procps package in Ubuntu: In Progress Status in procps source package in Xenial: In Progress Status in procps source package in Bionic: In Progress Status in procps source package in Disco: In Progress Bug description: [Impact] The pgrep -f and pkill -f commands are unable to find processes strings in processes which are beyond the 4096th character. This often happens with Java command lines with long classpaths on the command line. [Test Case] A quick test to reproduce this is to vi a file using a filename over 4k $ vi $(seq 1 1250| paste -s -d'_')_foo.txt) and leave vi running then run from another terminal $ pgrep -af 'foo.txt' to find it. Without the fix, one will only see the first 4096 chars, while the expected behaviour would be: $ pgrep -af 'foo.txt' 27667 vi 1_2_3_4_5_6_7_8_9_10_11_12_13_14_15_16_17_18_19_20_21_22_23_24_25_26_27_28_29_30_31_32_33_34_35_36_37_38_39_40_41_42_43_44_45_46_47_48_49_50_51_52_53_54_55_56_57_58_59_60_61_62_63_64_65_66_67_68_69_70_71_72_73_74_75_76_77_78_79_80_81_82_83_84_85_86_87_88_89_90_91_92_93_94_95_96_97_98_99_100_101_102_103_104_105_106_107_108_109_110_111_112_113_114_115_116_117_118_119_120_121_122_123_124_125_126_127_128_129_130_131_132_133_134_135_136_137_138_139_140_141_142_143_144_145_146_147_148_149_150_151_152_153_154_155_156_157_158_159_160_161_162_163_164_165_166_167_168_169_170_171_172_173_174_175_176_177_178_179_180_181_182_183_184_185_186_187_188_189_190_191_192_193_194_195_196_197_198_199_200_201_202_203_204_205_206_207_208_209_210_211_212_213_214_215_216_217_218_219_220_221_222_223_224_225_226_227_228_229_230_231_232_233_234_235_236_237_238_239_240_241_242_243_244_245_246_247_248_249_250_251_252_253_254_255_256_257_258_259_260_261_262_263_264_265_266_267_268_269_270_271_272_273_274_275_276_277_278_279_280_281_282_283_284_285_286_287_288_289_290_291_292_293_294_295_296_297_298_299_300_301_302_303_304_305_306_307_308_309_310_311_312_313_314_315_316_317_318_319_320_321_322_323_324_325_326_327_328_329_330_331_332_333_334_335_336_337_338_339_340_341_342_343_344_345_346_347_348_349_350_351_352_353_354_355_356_357_358_359_360_361_362_363_364_365_366_367_368_369_370_371_372_373_374_375_376_377_378_379_380_381_382_383_384_385_386_387_388_389_390_391_392_393_394_395_396_397_398_399_400_401_402_403_404_405_406_407_408_409_410_411_412_413_414_415_416_417_418_419_420_421_422_423_424_425_426_427_428_429_430_431_432_433_434_435_436_437_438_439_440_441_442_443_444_445_446_447_448_449_450_451_452_453_454_455_456_457_458_459_460_461_462_463_464_465_466_467_468_469_470_471_472_473_474_475_476_477_478_479_480_481_482_483_484_485_486_487_488_489_490_491_492_493_494_495_496_497_498_499_500_501_502_503_504_505_506_507_508_509_510_511_512_513_514_515_516_517_518_519_520_521_522_523_524_525_526_527_528_529_530_531_532_533_534_535_536_537_538_539_540_541_542_543_544_545_546_547_548_549_550_551_552_553_554_555_556_557_558_559_560_561_562_563_564_565_566_567_568_569_570_571_572_573_574_575_576_577_578_579_580_581_582_583_584_585_586_587_588_589_590_591_592_593_594_595_596_597_598_599_600_601_602_603_604_605_606_607_608_609_610_611_612_613_614_615_616_617_618_619_620_621_622_623_624_625_626_627_628_629_630_631_632_633_634_635_636_637_638_639_640_641_642_643_644_645_646_647_648_649_650_651_652_653_654_655_656_657_658_659_660_661_662_663_664_665_666_667_668_669_670_671_672_673_674_675_676_677_678_679_680_681_682_683_684_685_686_687_688_689_690_691_692_693_694_695_696_697_698_699_700_701_702_703_704_705_706_707_708_709_710_711_712_713_714_715_716_717_718_719_720_721_722_723_724_725_726_727_728_729_730_731_732_733_734_735_736_737_738_739_740_741_742_743_744_745_746_747_748_749_750_751_752_753_754_755_756_757_758_759_760_761_762_763_764_765_766_767_768_769_770_771_772_773_774_775_776_777_778_779_780_781_782_783_784_785_786_787_788_789_790_791_792_793_794_795_796_797_798_799_800_801_802_803_804_805_806_807_808_809_810_811_812_813_814_815_816_817_818_819_820_821_822_823_824_825_826_827_828_829_830_831_832_833_834_835_836_837_838_839_840_841_842_843_844_845_846_847_848_849_850_851_852_853_854_855_856_857_858_859_860_861_862_863_864_865_866_867_868_869_870_871_872_873_874_875_876_877_878_879_880_881_882_883_884_885_886_887_888_889_890_891_892_893_894_895_896_897_898_899_900_901_902_903_904_905_906_907_908_909_910_911_912_913_914_915_916_917_918_919_920_921_922_923_924_925_926_927_928_929_930_931_932_933_934_935_936_937_938_939_940_941_942_943_944_945_946_947_948_949_950_951_9
[Touch-packages] [Bug 1839329] Re: pgrep: Use POSIX _SC_ARG_MAX for maximum pgrep -f command line length
** Description changed: [Impact] The pgrep -f and pkill -f commands are unable to find processes strings in processes which are beyond the 4096th character. This often happens with Java command lines with long classpaths on the command line. [Test Case] A quick test to reproduce this is to vi a file using a filename over 4k $ vi $(seq 1 1250| paste -s -d'_')_foo.txt) and leave vi running then run from another terminal $ pgrep -af 'foo.txt' to find it. Without the fix, one will only see the first 4096 chars, while the expected behaviour would be: $ pgrep -af 'foo.txt' 27667 vi 1_2_3_4_5_6_7_8_9_10_11_12_13_14_15_16_17_18_19_20_21_22_23_24_25_26_27_28_29_30_31_32_33_34_35_36_37_38_39_40_41_42_43_44_45_46_47_48_49_50_51_52_53_54_55_56_57_58_59_60_61_62_63_64_65_66_67_68_69_70_71_72_73_74_75_76_77_78_79_80_81_82_83_84_85_86_87_88_89_90_91_92_93_94_95_96_97_98_99_100_101_102_103_104_105_106_107_108_109_110_111_112_113_114_115_116_117_118_119_120_121_122_123_124_125_126_127_128_129_130_131_132_133_134_135_136_137_138_139_140_141_142_143_144_145_146_147_148_149_150_151_152_153_154_155_156_157_158_159_160_161_162_163_164_165_166_167_168_169_170_171_172_173_174_175_176_177_178_179_180_181_182_183_184_185_186_187_188_189_190_191_192_193_194_195_196_197_198_199_200_201_202_203_204_205_206_207_208_209_210_211_212_213_214_215_216_217_218_219_220_221_222_223_224_225_226_227_228_229_230_231_232_233_234_235_236_237_238_239_240_241_242_243_244_245_246_247_248_249_250_251_252_253_254_255_256_257_258_259_260_261_262_263_264_265_266_267_268_269_270_271_272_273_274_275_276_277_278_279_280_281_282_283_284_285_286_287_288_289_290_291_292_293_294_295_296_297_298_299_300_301_302_303_304_305_306_307_308_309_310_311_312_313_314_315_316_317_318_319_320_321_322_323_324_325_326_327_328_329_330_331_332_333_334_335_336_337_338_339_340_341_342_343_344_345_346_347_348_349_350_351_352_353_354_355_356_357_358_359_360_361_362_363_364_365_366_367_368_369_370_371_372_373_374_375_376_377_378_379_380_381_382_383_384_385_386_387_388_389_390_391_392_393_394_395_396_397_398_399_400_401_402_403_404_405_406_407_408_409_410_411_412_413_414_415_416_417_418_419_420_421_422_423_424_425_426_427_428_429_430_431_432_433_434_435_436_437_438_439_440_441_442_443_444_445_446_447_448_449_450_451_452_453_454_455_456_457_458_459_460_461_462_463_464_465_466_467_468_469_470_471_472_473_474_475_476_477_478_479_480_481_482_483_484_485_486_487_488_489_490_491_492_493_494_495_496_497_498_499_500_501_502_503_504_505_506_507_508_509_510_511_512_513_514_515_516_517_518_519_520_521_522_523_524_525_526_527_528_529_530_531_532_533_534_535_536_537_538_539_540_541_542_543_544_545_546_547_548_549_550_551_552_553_554_555_556_557_558_559_560_561_562_563_564_565_566_567_568_569_570_571_572_573_574_575_576_577_578_579_580_581_582_583_584_585_586_587_588_589_590_591_592_593_594_595_596_597_598_599_600_601_602_603_604_605_606_607_608_609_610_611_612_613_614_615_616_617_618_619_620_621_622_623_624_625_626_627_628_629_630_631_632_633_634_635_636_637_638_639_640_641_642_643_644_645_646_647_648_649_650_651_652_653_654_655_656_657_658_659_660_661_662_663_664_665_666_667_668_669_670_671_672_673_674_675_676_677_678_679_680_681_682_683_684_685_686_687_688_689_690_691_692_693_694_695_696_697_698_699_700_701_702_703_704_705_706_707_708_709_710_711_712_713_714_715_716_717_718_719_720_721_722_723_724_725_726_727_728_729_730_731_732_733_734_735_736_737_738_739_740_741_742_743_744_745_746_747_748_749_750_751_752_753_754_755_756_757_758_759_760_761_762_763_764_765_766_767_768_769_770_771_772_773_774_775_776_777_778_779_780_781_782_783_784_785_786_787_788_789_790_791_792_793_794_795_796_797_798_799_800_801_802_803_804_805_806_807_808_809_810_811_812_813_814_815_816_817_818_819_820_821_822_823_824_825_826_827_828_829_830_831_832_833_834_835_836_837_838_839_840_841_842_843_844_845_846_847_848_849_850_851_852_853_854_855_856_857_858_859_860_861_862_863_864_865_866_867_868_869_870_871_872_873_874_875_876_877_878_879_880_881_882_883_884_885_886_887_888_889_890_891_892_893_894_895_896_897_898_899_900_901_902_903_904_905_906_907_908_909_910_911_912_913_914_915_916_917_918_919_920_921_922_923_924_925_926_927_928_929_930_931_932_933_934_935_936_937_938_939_940_941_942_943_944_945_946_947_948_949_950_951_952_953_954_955_956_957_958_959_960_961_962_963_964_965_966_967_968_969_970_971_972_973_974_975_976_977_978_979_980_981_982_983_984_985_986_987_988_989_990_991_992_993_994_995_996_997_998_999_1000_1001_1002_1003_1004_1005_1006_1007_1008_1009_1010_1011_1012_1013_1014_1015_1016_1017_1018_1019_1020_1021_1022_1023_1024_1025_1026_1027_1028_1029_1030_1031_1032_1033_1034_1035_1036_1037_1038_1039_1040_1041_1042_1043_1044_1045_1046_1047_1048_1049_1050_1051_1052_1053_1054_1055_1056_1057_1058_1059_1060_1061_1062_1063_1064_1065_1066_1067_1068_1069_1070_1071_1072_1073_1074_1075_1076_1077_1078_1079_1080_1081_1082_1083_1084_1085_1086_1087_1088_1089_1090_1091_1092_1093_1094_1095_1096_1097_
[Touch-packages] [Bug 1839503] Re: apt does massive removal when install requested for specific packages
It's your job as a user to make sure the outcome is what you want. Don't blindly use -y. Yes, install can remove conflicting packages, this is by design. ** Changed in: apt (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1839503 Title: apt does massive removal when install requested for specific packages Status in apt package in Ubuntu: Invalid Bug description: I performed this command (didn't know which package provided what I needed) apt install -y lib64readline-dev libreadline-dev This REMOVED these packages: dkms oem-ethernet-realtek-r8152-lp1806322-4.15-dkms-dkms ubuntu- desktop x11-session-utils xorg To my way of thinking, apt install should never remove packages. If there is a dependency conflict with the requested packages, then that should be noted. Of course, I used '-y', and will never do so again. Further, there may be some broken dependencies in these packages I requested to install. I left the libreadline-dev installed and removed lib64readline-dev. I was able to reinstall the ones that were removed with the exception of the realtek one (apt didn't find it - not sure what repo, but I'll find it). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.11 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_1045_50_oem_53 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Aug 8 11:07:51 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-07-14 (25 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1839503/+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 1839290] Re: systemd doesn't restart a service after crashes
The attachment "debdiff for xenial systemd branch" 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1839290 Title: systemd doesn't restart a service after crashes Status in systemd package in Ubuntu: Confirmed Bug description: Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+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 1839503] [NEW] apt does massive removal when install requested for specific packages
Public bug reported: I performed this command (didn't know which package provided what I needed) apt install -y lib64readline-dev libreadline-dev This REMOVED these packages: dkms oem-ethernet-realtek-r8152-lp1806322-4.15-dkms-dkms ubuntu-desktop x11-session-utils xorg To my way of thinking, apt install should never remove packages. If there is a dependency conflict with the requested packages, then that should be noted. Of course, I used '-y', and will never do so again. Further, there may be some broken dependencies in these packages I requested to install. I left the libreadline-dev installed and removed lib64readline-dev. I was able to reinstall the ones that were removed with the exception of the realtek one (apt didn't find it - not sure what repo, but I'll find it). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.11 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_1045_50_oem_53 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Aug 8 11:07:51 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-07-14 (25 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1839503 Title: apt does massive removal when install requested for specific packages Status in apt package in Ubuntu: New Bug description: I performed this command (didn't know which package provided what I needed) apt install -y lib64readline-dev libreadline-dev This REMOVED these packages: dkms oem-ethernet-realtek-r8152-lp1806322-4.15-dkms-dkms ubuntu- desktop x11-session-utils xorg To my way of thinking, apt install should never remove packages. If there is a dependency conflict with the requested packages, then that should be noted. Of course, I used '-y', and will never do so again. Further, there may be some broken dependencies in these packages I requested to install. I left the libreadline-dev installed and removed lib64readline-dev. I was able to reinstall the ones that were removed with the exception of the realtek one (apt didn't find it - not sure what repo, but I'll find it). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: apt 1.6.11 ProcVersionSignature: Ubuntu 4.15.0-1045.50-oem 4.15.18 Uname: Linux 4.15.0-1045-oem x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_1045_50_oem_53 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Aug 8 11:07:51 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37 InstallationDate: Installed on 2019-07-14 (25 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1839503/+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 1839290] Re: systemd doesn't restart a service after crashes
Hello, everyone. Here's a debdiff patch with a backport of upstream patch to xenial branch of systemd. I've successfully built a modified source and deployed it to some xenial machines — it works as intended, failed service restart correctly, just as intended by Restart=always policy. Before: systemd[1]: vpp.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: Stopped vector packet processing engine. systemd[1]: vpp.service: Unit entered failed state. systemd[1]: vpp.service: Failed with result 'core-dump'. systemd[1]: vpp.service: Service hold-off time over, scheduling restart. systemd[1]: vpp.service: Failed to schedule restart job: Transaction is destructive. systemd[1]: vpp.service: Unit entered failed state. systemd[1]: vpp.service: Failed with result 'resources'. After: systemd[1]: vpp.service: Main process exited, code=dumped, status=6/ABRT systemd[1]: Stopped vector packet processing engine. systemd[1]: vpp.service: Unit entered failed state. systemd[1]: vpp.service: Failed with result 'core-dump'. systemd[1]: vpp.service: Service hold-off time over, scheduling restart. systemd[1]: Stopped vector packet processing engine. systemd[1]: Starting vector packet processing engine... ** Patch added: "debdiff for xenial systemd branch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+attachment/5281628/+files/lp-1839290-xenial.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1839290 Title: systemd doesn't restart a service after crashes Status in systemd package in Ubuntu: Confirmed Bug description: Affected versions of OS and systemd: $ cat /etc/issue Ubuntu 16.04.6 LTS \n \l $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN Affected packages: systemd 229-4ubuntu21.22 and previous versions. Expected behaviour you didn't see: Scheduling restart of failed service. A process crashed by sigabrt and didn't restart. Description: The bug was reported to a systemd upstream repository: https://github.com/systemd/systemd/issues/11456 The bug was fixed and accepted to the master branch: https://github.com/systemd/systemd/pull/11467/files Action: Include this patch to Ubuntu 16.04 and other version of Ubuntu which are supported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+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 1839501] [NEW] Can't Switch between Nvidia Drivers because of error in SoftwarePropertiesQt.py
Public bug reported: Hardware: Dell Latitude E6430 with GF108GLM [NVS 5200m] Lubuntu 19.04 LBS Release: Description:Ubuntu 19.04 software-properties-qt: Installed: 0.97.11 Candidate: 0.97.11 Version table: *** 0.97.11 500 500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status I ran "Additional Drivers" from the menu and switched from Nouveau to the nvidia-driver-418 to see how it ran. After testing for a couple days I tried to switch back. When I select Nouveau and click "Apply changes" nothing happens. I ran software-properties-qt from the command line and get this error when I click "Apply Changes". #lxsudo /usr/bin/software-properties-qt '--open-tab=4' (0x7ffda7818770) Warning: Icon theme "breeze" not found. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 845, in on_driver_changes_apply for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'): NameError: name 'get_dependencies' is not defined I searched through the source and I'm guessing it's the extra parameter 'nvidia' at the end that's causing the issue, since there's no 3 parameter function definition for get_dependencies. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1839501 Title: Can't Switch between Nvidia Drivers because of error in SoftwarePropertiesQt.py Status in software-properties package in Ubuntu: New Bug description: Hardware: Dell Latitude E6430 with GF108GLM [NVS 5200m] Lubuntu 19.04 LBS Release: Description:Ubuntu 19.04 software-properties-qt: Installed: 0.97.11 Candidate: 0.97.11 Version table: *** 0.97.11 500 500 http://us.archive.ubuntu.com/ubuntu disco/universe amd64 Packages 100 /var/lib/dpkg/status I ran "Additional Drivers" from the menu and switched from Nouveau to the nvidia-driver-418 to see how it ran. After testing for a couple days I tried to switch back. When I select Nouveau and click "Apply changes" nothing happens. I ran software-properties-qt from the command line and get this error when I click "Apply Changes". #lxsudo /usr/bin/software-properties-qt '--open-tab=4' (0x7ffda7818770) Warning: Icon theme "breeze" not found. QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", line 845, in on_driver_changes_apply for dep in get_dependencies(self.apt_cache, pkg.shortname, 'nvidia'): NameError: name 'get_dependencies' is not defined I searched through the source and I'm guessing it's the extra parameter 'nvidia' at the end that's causing the issue, since there's no 3 parameter function definition for get_dependencies. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1839501/+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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
Possible solution would be changing the "Cdrom with" part to something that can be used in most languages without a translation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
In my case I'm trying to get softdog to load for SBD instead of the watchdog daemon. I can see the point of marking it as opinion, but as Olivier points out, you have to eliminate the blacklist entry from all of the blacklists spammed into /lib/modprobe.d, systemd-modules-load does not discriminate for particular kernel versions and reads every .conf file. -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
I see that the version strings are hardcoded in data/templates/Ubuntu.info.in, for example for Ubuntu 19.10: _Description: Ubuntu 19.10 'Eoan Ermine' _Description: Cdrom with Ubuntu 19.10 'Eoan Ermine' Not sure if my suggested solution from #2 could be applied on the .in file, but it would be great if this issue could be finally fixed. It is really annoying for translators to update these strings manually every time a new Ubuntu release is out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+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 1535840] Re: systemd ignoring /etc/modules due to blacklist
Issue still exists in 18.04. -- 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/1535840 Title: systemd ignoring /etc/modules due to blacklist Status in systemd package in Ubuntu: Opinion Bug description: I tried the daily build of 16.04 32-bit to test out the watchdog daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in /etc/modules so it is loaded at boot-time, as watchdog timer modules are not normally auto-loaded due to the risk of an unexpected reboot. However I now find that systemd is choosing to ignore my command to load the module in /etc/modules since it appears in the watchdog blacklist. Typical syslog entries look like this: Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted This is just dumb! I have explicitly told the system to load the module, an action that works perfectly well using modprobe or by adding it to the start script for the watchdog, and yet systemd chooses to override that because of the blacklist for auto-loaded modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf). $ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 $ apt-cache policy systemd systemd: Installed: 228-4ubuntu1 Candidate: 228-4ubuntu1 Version table: *** 228-4ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages 100 /var/lib/dpkg/status What I expect to happen is modules added to /etc/modules are loaded at boot time, and not subject to the blacklist for hardware detect / automatic loading. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+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 1837821] Re: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, Left] Recording problem
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- 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/1837821 Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running Ubuntu 18.04.2 LTS. The built in microphone is not displayed and not available to select. The webcam, touchscreen, and speakers all work fine. Plugging in a headset with a microphone does allow audio to be heard through the external microphone. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carwyn 2521 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jul 24 20:57:51 2019 InstallationDate: Installed on 2019-07-22 (3 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [HP Spectre x360 Convertible 15-df0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2019 dmi.bios.vendor: AMI dmi.bios.version: F.29 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8518 dmi.board.vendor: HP dmi.board.version: 10.47 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.29:bd04/22/2019:svnHP:pnHPSpectrex360Convertible15-df0xxx:pvr:rvnHP:rn8518:rvr10.47:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-df0xxx dmi.product.sku: 6JY95UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1837821/+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 1835910] Re: Include a control to display or not the livepatch indicator
Using 0.96.24.32.11 (which includes the changes from here) the control is available and the indicator correctly responds to the status changes, marked as verified ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1835910 Title: Include a control to display or not the livepatch indicator Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact The livepatch UI design includes a control in software-properties which let you enable the indicator or not, that UI element is currently missing from bionic * Test case - start software-properties - go the livepatch tab and enable livepatch by adding an account -> the UI should include a toggle that let you activate/disactive the indicator - click on the control button -> the indicator status should reflect the control one * Regression potential The change is adding a new widget, it shouldn't impact on existing code but check that the page layout is still correct. The change also include translatable strings, they are being handled the same way as the other livepatch strings added in the previous upload (shared translations between serie included in langpack updates) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1835910/+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 1835911] Re: Handle applying status
Using 0.96.24.32.11 (which includes the changes from here) the status information is correctly displayed, marking as verified ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1835911 Title: Handle applying status Status in software-properties package in Ubuntu: Fix Released Status in software-properties source package in Bionic: Fix Committed Bug description: * Impact Sometime the livepatch status goes through an 'applying' intermediate value which can confuse the UI which then reports an non existing error * Test case Enable livepatch, go to software-properties->livepatch, check that the status matches the one reported by 'canonical-livepatch status' on a command line * Regression potential The change is simply adding an extra value to the list of handled status, check that the reporting is correct To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1835911/+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 1837098] Re: Can't print in monochrome, only in colour
The PPD you have now is completely different, it is not auto-generated based on a get-printer-attributes IPP request but it is a generic PPD which is part of the cups-filters package. How did you set up your printer under Disco? How did you set it up under Eoan? Does your printer actually print under Eoan? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: Incomplete Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1837098] Re: Can't print in monochrome, only in colour
** Attachment added: "E ipp output" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281623/+files/e_ipp.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: Incomplete Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1837098] Re: Can't print in monochrome, only in colour
** Attachment added: "E PPD" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281616/+files/C43x.ppd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: Incomplete Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
Using Ubuntu 18.04.3 LTS with 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux Output: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) Traceback (most recent call last): File "/usr/bin/apport-unpack", line 74, in pr.extract_keys(f, bin_keys, dir) File "/usr/lib/python3/dist-packages/problem_report.py", line 270, in extract_keys [item for item, element in b64_block.items() if element is False]) ValueError: ['UserGroups'] has no binary content Crash report available at /home/calin/kodi_crashlog-20190808_093922.log ** Attachment added: "dpkg-l" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281621/+files/dpkg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: Confirmed Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to-desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 6th and 16th, I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic repository), however, Kodi works again, without even requiring me to restart my machine. So, this is likely a problem with “mesa-va- drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+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 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”
kodi_crashlog-20190808_093922.log ** Attachment added: "kodi_crashlog" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+attachment/5281622/+files/kodi_crashlog-20190808_093922.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1836979 Title: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed” Status in mesa package in Ubuntu: Confirmed Bug description: Buggy as Kodi is, this seems to be a problem specifically with mesa- va-drivers. Kodi has worked just fine on my system, as recently as July 6th of this year, but yesterday (July 16) I tried Kodi again: I got a blank screen and a pause for a few moments, followed by an unceremonious crash-to-desktop. This happens every time I start Kodi, now. If I run it through the command-line, I get this: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so libva info: Found init function __vaDriverInit_1_1 libva info: va_openDriver() returns 0 kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed. Aborted (core dumped) I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”, package version 2:18.3+git20190621.1610-final-0bionic, from the Team- XBMC PPA) since its release in June, but in between July 6th and 16th, I did upgrade the Mesa packages, from 18.2.8-0ubuntu0~18.04.2 19.0.2-1ubuntu1.1~18.04.1. If I downgrade the “mesa-va-drivers” package to 18.0.0~rc5-1ubuntu1 (the version in the base, non-updates Bionic repository), however, Kodi works again, without even requiring me to restart my machine. So, this is likely a problem with “mesa-va- drivers”. I tried looking in Xorg.0.log: [ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620 [ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines: [ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0 72.33 1366 1414 1446 1526 768 770 775 790 -hsync -vsync (47.4 kHz eP) …that’s all that appears in the log when I try to load Kodi and a crash happens. I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if you need more information, I’ve attached a hardinfo report, too. I hope this bug can get fixed, soon. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1836979/+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 1837098] Re: Can't print in monochrome, only in colour
Could you also attach the ipptool output of Eoan, to see whether this is different? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: Incomplete Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1837098] Re: Can't print in monochrome, only in colour
Could you post the PPD file of Eoan then, so tat I can compare? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: Incomplete Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1176548] Re: nut-server fails if modemmanager is scanning serial ports
** Changed in: nut (Ubuntu) Status: Triaged => Incomplete ** Changed in: modemmanager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1176548 Title: nut-server fails if modemmanager is scanning serial ports Status in modemmanager package in Ubuntu: Incomplete Status in nut package in Ubuntu: Incomplete Bug description: Similar to whatPaavo Leinonen reported in 031601ce2a49$20b2efe0$6218cfa0$@leinonen.fi on the NUT mailing list. See also my mail in reply. Ubuntu runs modemmanager as a native upstart service. nut-server ends up running in parallel (on my system, probably a matter of timing). When modemmanager scans the serial ports for modems, upsd is unable to open the port configured for an UPS. (It might be possible to exclude some ports from the scan, I didn't check because I have no modem it could configure, I just kicked the package. Please convert nut-server to a native upstart service to be able to have it wait for modemmanager. (I hope upstart is clever enough to have a service wait for an optional package and let it proceed if not installed.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1176548/+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 1838370] Re: slapd segfault on filter parse error
Hm, I forgot to re-add the bug reference after a few iterating over another change, sorry. But this is a good SRU candidate. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1838370 Title: slapd segfault on filter parse error Status in openldap: Fix Released Status in openldap package in Ubuntu: Fix Released Status in openldap source package in Xenial: Confirmed Status in openldap source package in Bionic: Confirmed Status in openldap source package in Disco: Confirmed Bug description: Hello! We have faced slapd crash, seems an attacker was trying to brute force one of our services and uid parsing failures caused slapd crash: Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH base="ou=test,dc=test,dc=com" scope=2 deref=0 filter="(&(uid=aistar123<>!n)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SRCH attr=objectClass uid userPassword uidNumber gidNumber gecos homeDirectory loginShell krbPrincipalName cn memberOf modifyTimestamp modifyTimestamp shadowLastChange shadowMin shadow Max shadowWarning shadowInactive shadowExpire shadowFlag krbLastPwdChange krbPasswordExpiration pwdAttribute authorizedService accountExpires userAccountControl nsAccountLock host loginDisabled loginExpirationTime loginAllowedTimeMap sshPublic Key Jul 26 18:59:47 slapd[1252]: conn=1466 op=13 SEARCH RESULT tag=101 err=0 nentries=0 text=massaged filter parse error Jul 26 18:59:47 kernel: [ 9441.554161] slapd[2367]: segfault at 18 ip 7fc8d18ec512 sp 7fc8889e2810 error 4 in libc-2.23.so [7fc8d1868000+1c] Another faulty filter example: filter="(&(uid=sql<>?)(objectClass=posixAccount)(&(uidNumber=*)(!(uidNumber=0" filter="(&(uid=fugeone<>?123)(objectClass=posixAccount)(uid=*)(&(uidNumber=*)(!(uidNumber=0" $ lsb_release -rd Description: Ubuntu 16.04.5 LTS Release: 16.04 $ slapd -VVV @(#) $OpenLDAP: slapd (Ubuntu) (May 22 2018 13:54:12) $ buildd@lcy01-amd64-019 :/build/openldap-t_Ta0O/openldap-2.4.42+dfsg/debian/build/servers/slapd Included static backends: config ldif $ apt-cache policy slapd slapd: Installed: 2.4.42+dfsg-2ubuntu3.3 Candidate: 2.4.42+dfsg-2ubuntu3.5 Version table: 2.4.42+dfsg-2ubuntu3.5 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 2.4.42+dfsg-2ubuntu3.3 100 100 /var/lib/dpkg/status 2.4.42+dfsg-2ubuntu3.2 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 2.4.42+dfsg-2ubuntu3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages affects ubuntu/openldap To manage notifications about this bug go to: https://bugs.launchpad.net/openldap/+bug/1838370/+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 1807499] Re: 30 seconds boot delay when root fs is on lvm
According to your post, I have modified /lib/udev/rules.d/69-lvm-metad.rules the line 96, but no. # the ACTION!="remove", ENV{violently _pv_gone}=="1", RUN+="/usr/bin/systemd-run /sbin/ LVM pvscan --cache $major:$minor", GOTO=" violently _end" The ACTION!="remove", RUN+="/sbin/ LVM pvscan --cache $major:$minor --activate ay" Could you please tell me how to modify /usr/share/initramfs-tools/scripts/local-top/lvm2 ? #!/bin/sh PREREQ="mdadm mdrun multipath" prereqs() { echo "$PREREQ" } case $1 in # get pre-requisites prereqs) prereqs exit 0 ;; esac if [ ! -e /sbin/lvm ]; then exit 0 fi lvchange_activate() { lvm lvchange -aay -y --sysinit --ignoreskippedcluster "$@" } activate() { local dev="$1" # Make sure that we have a non-empty argument if [ -z "$dev" ]; then return 1 fi case "$dev" in # Take care of lilo boot arg, risky activating of all vg fe[0-9]*) lvchange_activate exit 0 ;; # FIXME: check major /dev/root) lvchange_activate exit 0 ;; /dev/mapper/*) eval $(dmsetup splitname --nameprefixes --noheadings --rows "${dev#/dev/mapper/}") if [ "$DM_VG_NAME" ] && [ "$DM_LV_NAME" ]; then lvchange_activate "$DM_VG_NAME/$DM_LV_NAME" fi ;; /dev/*/*) # Could be /dev/VG/LV; use lvs to check if lvm lvs -- "$dev" >/dev/null 2>&1; then lvchange_activate "$dev" fi ;; esac } activate "$ROOT" activate "$resume" exit 0 -- 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/1807499 Title: 30 seconds boot delay when root fs is on lvm Status in lvm2 package in Ubuntu: New Bug description: On my system the root filesystem is located on a logical volume. I have constant boot delay of 30 seconds. My current conclusion is that this problem exists due to lvm performing the initramfs-tools local- top initialization incorrectly. According to initramfs-tools(8): local-top OR nfs-top After these scripts have been executed, the root device node is expected to be present (local) or the network interface is expected to be usable (NFS). But what /usr/share/initramfs-tools/scripts/local-top/lvm2 is simply try to activate the requested root volume by means of scanning the (at that moment) available block devices. What happens on my system is that local-top/lvm2 is executed before the pv block device (SATA-SSD) shows up. Then initramfs-tools calls the wait-for-root executable which waits for the root device node notification via udev. This has a (minimum) timeout of 30 seconds configured. This timeout is exceeded since nothing will make the root volume device to be created. Then later (I guess in local-block) the root volume device is created (since the pv is available). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Dec 8 13:52:06 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_AT.UTF-8 SHELL=/bin/bash SourcePackage: lvm2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1807499/+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 1839446] Re: When trying to print a test page CUPS crashes
I wasnt able to get a backtrace because there was "no stack". This is what shows in gdb: Program received signal SIGABRT, Aborted. __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory. (gdb) Continuing. Program terminated with signal SIGABRT, Aborted. The program no longer exists. (gdb) The program is not being run. (gdb) The program is not being run. (gdb) backtrace full No stack. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839446 Title: When trying to print a test page CUPS crashes Status in cups package in Ubuntu: Incomplete Bug description: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1695611] Re: libjson-c3-0.12.1-1.1 has building bug
Please reopen if you still have this issue! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1695611 Title: libjson-c3-0.12.1-1.1 has building bug Status in json-c package in Ubuntu: Fix Released Bug description: Hi ubuntu team i am developing application based on libjson-c and libglib. The previous version is Ubuntu 16.04, everything is ok. But i found malloc corruption when my OS was upgraded to Ubuntu 17.04. I suspected the glib issue in previous, but i found the problem was caused by libjson-c after debugging. So i used the following command to rebuild libjson from souce: # apt-get source libjson-c3 # cd json-c-0.12.1 # sudo apt-get build-dep json-c # sudo debuild -i -us -uc -b i got 3 deb packages: libjson-c-dev_0.12.1-1.1_amd64.deb , libjson-c-doc_0.12.1-1.1_all.deb, libjson-c3_0.12.1-1.1_amd64.deb Then use cmd: dpkg -i <***.deb> to install the above package to overwrite(overinstall) the original libjson-c package . Last i rebuild my application and run , everything is ok. GCC verison: # gcc --version gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406 Copyright (C) 2016 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE # uname -a Linux harry-ThinkPad-Edge-E430 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux i seems the problem was caused by release build. Best regards Tony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1695611/+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 1695611] Re: libjson-c3-0.12.1-1.1 has building bug
I hope it is ok now ** Changed in: json-c (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to json-c in Ubuntu. https://bugs.launchpad.net/bugs/1695611 Title: libjson-c3-0.12.1-1.1 has building bug Status in json-c package in Ubuntu: Fix Released Bug description: Hi ubuntu team i am developing application based on libjson-c and libglib. The previous version is Ubuntu 16.04, everything is ok. But i found malloc corruption when my OS was upgraded to Ubuntu 17.04. I suspected the glib issue in previous, but i found the problem was caused by libjson-c after debugging. So i used the following command to rebuild libjson from souce: # apt-get source libjson-c3 # cd json-c-0.12.1 # sudo apt-get build-dep json-c # sudo debuild -i -us -uc -b i got 3 deb packages: libjson-c-dev_0.12.1-1.1_amd64.deb , libjson-c-doc_0.12.1-1.1_all.deb, libjson-c3_0.12.1-1.1_amd64.deb Then use cmd: dpkg -i <***.deb> to install the above package to overwrite(overinstall) the original libjson-c package . Last i rebuild my application and run , everything is ok. GCC verison: # gcc --version gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406 Copyright (C) 2016 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE # uname -a Linux harry-ThinkPad-Edge-E430 4.10.0-22-generic #24-Ubuntu SMP Mon May 22 17:43:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux i seems the problem was caused by release build. Best regards Tony To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1695611/+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 1837098] Re: Can't print in monochrome, only in colour
I tested E and that seems to work as expected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: Incomplete Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1839446] Re: When trying to print a test page CUPS crashes
** Attachment added: "error_log" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+attachment/5281584/+files/error_log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839446 Title: When trying to print a test page CUPS crashes Status in cups package in Ubuntu: Incomplete Bug description: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1839446] Re: When trying to print a test page CUPS crashes
Sorry, wrong bug, ignore that comment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839446 Title: When trying to print a test page CUPS crashes Status in cups package in Ubuntu: Incomplete Bug description: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1839446] Re: When trying to print a test page CUPS crashes
I've tested this on E, and I can now print in B&W and Colour again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839446 Title: When trying to print a test page CUPS crashes Status in cups package in Ubuntu: Incomplete Bug description: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1839446] Re: When trying to print a test page CUPS crashes
Could you follow the instructions of the section "CUPS error_log" on https://wiki.ubuntu.com/DebuggingPrintingProblems to get an error_log in debug mode from the CUPS crash? Also some form of backtrace of the crashing CUPS daemon would be great (apport record? cupsd run in a way that one can capture a core file, ...). ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839446 Title: When trying to print a test page CUPS crashes Status in cups package in Ubuntu: Incomplete Bug description: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1839446] [NEW] When trying to print a test page CUPS crashes
Public bug reported: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1839446 Title: When trying to print a test page CUPS crashes Status in cups package in Ubuntu: New Bug description: I'm trying to get my printer working correctly and when I try and print test pages it seems like cups crashes and restarts in the background. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-21.22-generic 5.0.15 Uname: Linux 5.0.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 8 10:33:49 2019 InstallationDate: Installed on 2019-07-03 (35 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lpstat: device for Samsung_C43x_Series_printer_: ipp://printer.local:631/ipp/print MachineType: LENOVO 20HN0016UK Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Samsung_C43x_Series_printer_.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Samsung_C43x_Series_printer_.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-21-generic root=UUID=91a2a717-12eb-448f-8b5b-48dd8d3dc145 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0IET57W (1.35 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HN0016UK dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0IET57W(1.35):bd03/25/2019:svnLENOVO:pn20HN0016UK:pvrThinkPadX270:rvnLENOVO:rn20HN0016UK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X270 dmi.product.name: 20HN0016UK dmi.product.sku: LENOVO_MT_20HN_BU_Think_FM_ThinkPad X270 dmi.product.version: ThinkPad X270 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+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 1740894] Re: KEY_RFKILL is not passed to userspace
** Merge proposal linked: https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/370808 -- 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/1740894 Title: KEY_RFKILL is not passed to userspace Status in OEM Priority Project: New Status in OEM Priority Project bionic series: New Status in libxkbcommon package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Status in xorgproto package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: Fix Released Status in systemd source package in Bionic: In Progress Status in xkeyboard-config source package in Bionic: Fix Committed Status in xorgproto source package in Bionic: Fix Released Status in libxkbcommon source package in Cosmic: Fix Released Status in xkeyboard-config source package in Cosmic: Fix Released Status in xorgproto source package in Cosmic: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1740894/+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 1837700] Re: Dell system takes a long time to connect network with external dock
** Merge proposal linked: https://code.launchpad.net/~fourdollars/ubuntu/+source/systemd/+git/systemd/+merge/370808 -- 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/1837700 Title: Dell system takes a long time to connect network with external dock Status in HWE Next: New Status in OEM Priority Project: In Progress Status in systemd package in Ubuntu: New Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Disco: New Bug description: update for SRU process: [Impact] 1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system occasionally install two USB ethernet with same MAC address, the system will suffer 90 seconds for network interface renaming mechanism before the last USB ethernet interface to activate. [Test Case] 1. Install ubuntu on Dell laptop. 2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users can observe the last one will take 90 seconds for renaming to rename0. 3. Users can also find that the two USB ethernet have the same MAC address. [Regression Potential] To resolve the issue, drop a debian patch from systemd package. The debian patch is to revert an upstream commit to support 75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, the regression potential should be relatively low. --- Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/s
[Touch-packages] [Bug 1837098] Re: Can't print in monochrome, only in colour
** Attachment added: "Disco PPD" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+attachment/5281554/+files/Samsung_C43x_Series_printer_.ppd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1837098 Title: Can't print in monochrome, only in colour Status in cups package in Ubuntu: Incomplete Bug description: Printer is a Samsung C430W connected over wifi and using driverless printing. Everything is discovered and I can print in colour just fine. In Bionic I was able to toggle in to monochrome, but in Disco I am not. I now have to print everything in colour. $ lpoptions -l PageSize/Media Size: 4x6 8.5x13.5 *A4 A5 A6 B5 Executive FanFoldGermanLegal ISOB5 Legal Letter Custom.WIDTHxHEIGHT MediaType/Media Type: *Stationery StationeryHeavyweight StationeryLightweight StationeryBond StationeryColored Cardstock Labels Recycled Preprinted Cotton Archive ColorModel/Print Color Mode: *RGB cupsPrintQuality/Print Quality: *4 print-scaling/Print Scaling: *auto auto-fit fill fit none I have also attached the output of ipptool. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1837098/+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 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
Hello Matthew, or anyone else affected, Accepted ibus into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ibus/1.5.17-3ubuntu5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ibus (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Bionic: Fix Committed Bug description: [Impact] The following has been seen in a VMware Horizon VDI. I cannot reproduce this issue myself. When a user interacts with any password field in Firefox, gnome-shell and Firefox both freeze and the system becomes unusable. If you ssh into the system and terminate Firefox, gnome-shell unfreezes. This only happens when the environment variable GTK_IM_MODULE is set to "ibus". If you unset the variable, or change it to GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works as intended. This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus 1.5.17-3ubuntu4 and Firefox versions starting with 68.0+build3-0ubuntu0.18.04.1 Note: Chrome[ium] and other applications do not trigger it, and it cannot be reproduced in other desktop environments. This seems to be an interaction issue between ibus and gnome-shell. [Test Case] Launch firefox from within a gnome-session, making sure the GTK_IM_MODULE is set to "ibus". Note, this is the default value. $ env GTK_IM_MODULE="ibus" firefox Navigate to any website which has a password field. Wikipedia or Reddit will do. Click a password field and attempt to enter text. Firefox and gnome- shell both lock up and stay frozen for an extended period of time. Now, try it with the fix by enabling: $ env IBUS_DISCARD_PASSWORD=1 firefox When you enter text into a password field, ibus should directly pass through the text and the problem will be solved. We can also ask it to always apply for a specific application with: $ export IBUS_DISCARD_PASSWORD_APPS="firefox" $ firefox Again, when you enter text into a password input field, the problem will be solved. Test package is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test Please test with the revised version, 1.5.17-3ubuntu4+sf235370v20190731b1. [Regression Potential] This change has a low risk of regression, because the default behaviour is unchanged. To be able to use the password input field discard functionality, a user has to explicitly set an environment variable for the specific process, or set a regex that matches a process name. This means the fix is not enabled by default on any machines, and will only be utilised by those suffering problems and go and manually set environment variables or have their system administrator enable the environment variables permanently. This commit is present in upstream ibus from version ibus-1.5.19 onward, and is currently present in cosmic, disco and eoan. If a regression occurs, users can ensure that the environment variables are unset and continue working. [Other info] * This patch is functionally the same as ibus-xx-f19-password.patch, but just hides the features behind environment variables. * When ibus is built with the patch ibus-xx-f19-password.patch which was dropped in ibus-1.5.17-2, the problem is solved. Instead of using ibus-xx-f19-password.patch, we will instead fix it with upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0: https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0 Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firef
[Touch-packages] [Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox
Excellent. If the issue is reproducible and affects multiple users, this seems like a +1 on the SRU. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1838358 Title: Ibus causes gnome-shell to freeze when password fields are selected in Firefox Status in ibus package in Ubuntu: Fix Released Status in ibus source package in Bionic: In Progress Bug description: [Impact] The following has been seen in a VMware Horizon VDI. I cannot reproduce this issue myself. When a user interacts with any password field in Firefox, gnome-shell and Firefox both freeze and the system becomes unusable. If you ssh into the system and terminate Firefox, gnome-shell unfreezes. This only happens when the environment variable GTK_IM_MODULE is set to "ibus". If you unset the variable, or change it to GTK_IM_MODULE=gtk-im-context-simple and then start Firefox, everything works as intended. This has been seen before with gnome-shell 3.28.4-0ubuntu18.04.1, ibus 1.5.17-3ubuntu4 and Firefox versions starting with 68.0+build3-0ubuntu0.18.04.1 Note: Chrome[ium] and other applications do not trigger it, and it cannot be reproduced in other desktop environments. This seems to be an interaction issue between ibus and gnome-shell. [Test Case] Launch firefox from within a gnome-session, making sure the GTK_IM_MODULE is set to "ibus". Note, this is the default value. $ env GTK_IM_MODULE="ibus" firefox Navigate to any website which has a password field. Wikipedia or Reddit will do. Click a password field and attempt to enter text. Firefox and gnome- shell both lock up and stay frozen for an extended period of time. Now, try it with the fix by enabling: $ env IBUS_DISCARD_PASSWORD=1 firefox When you enter text into a password field, ibus should directly pass through the text and the problem will be solved. We can also ask it to always apply for a specific application with: $ export IBUS_DISCARD_PASSWORD_APPS="firefox" $ firefox Again, when you enter text into a password input field, the problem will be solved. Test package is available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf235370-test Please test with the revised version, 1.5.17-3ubuntu4+sf235370v20190731b1. [Regression Potential] This change has a low risk of regression, because the default behaviour is unchanged. To be able to use the password input field discard functionality, a user has to explicitly set an environment variable for the specific process, or set a regex that matches a process name. This means the fix is not enabled by default on any machines, and will only be utilised by those suffering problems and go and manually set environment variables or have their system administrator enable the environment variables permanently. This commit is present in upstream ibus from version ibus-1.5.19 onward, and is currently present in cosmic, disco and eoan. If a regression occurs, users can ensure that the environment variables are unset and continue working. [Other info] * This patch is functionally the same as ibus-xx-f19-password.patch, but just hides the features behind environment variables. * When ibus is built with the patch ibus-xx-f19-password.patch which was dropped in ibus-1.5.17-2, the problem is solved. Instead of using ibus-xx-f19-password.patch, we will instead fix it with upstream commit f328fd67f479faa46ca87bf3c85eed7080ec5ec0: https://github.com/ibus/ibus/commit/f328fd67f479faa46ca87bf3c85eed7080ec5ec0 Subject: client/gtk2: Add IBUS_DISCARD_PASSWORD for firefox and chrome Author: fujiwarat This implements the password discard functionality found in ibus-xx-f19-password.patch and places it behind two environment variables, IBUS_DISCARD_PASSWORD and IBUS_DISCARD_PASSWORD_APPS. IBUS_DISCARD_PASSWORD is for a single process, and IBUS_DISCARD_PASSWORD_APPS lets you set a regex of process names to filter and enable the fix for. If IBUS_DISCARD_PASSWORD is set or IBUS_DISCARD_PASSWORD_APPS is set with the process name which input is being placed into password fields, ibus will pass through the input to the application without any processing. * This only affect Bionic - Upstream first introduction: $ git describe --contains f328fd67f479faa46ca87bf3c85eed7080ec5ec0 1.5.19~7 - Ubuntu ibus current version found in the archive: $ rmadison ibus ==> ibus | 1.5.17-3ubuntu4 | bionic ibus | 1.5.19-1ubuntu1 | cosmic ibus | 1.5.19-1ubuntu2 | disco ibus | 1.5.19-4ubuntu2 | eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1838358/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : http