[Touch-packages] [Bug 1817077] Re: package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128
Hi John, the report has a lot of red herrings (all the error device is in use), but IMHO in the log the error that you hit was. Use of uninitialized value $reply in scalar chomp at /usr/share/perl5/Debconf/FrontEnd/Passthrough.pm line 66 That is a known and unfortunate issue, as it occurs every now and then and sometimes is fixed but seems to come back - often with hard to analyze (and thereby hard to identify and fix) root causes. It all seems like bug 1646739 to me, but since that was fixed in bug 1679435 it must be a new trigger for the same symptom. In any case it is in debconf, so I add a bug task - but I also set it to incomplete as we'd need more information why/how it was triggered for you. The only good side for now, usually it is a one off error that does work fine when retrying. ** Changed in: grub-legacy-ec2 (Ubuntu) Status: New => Incomplete ** Also affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1817077 Title: package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128 Status in debconf package in Ubuntu: New Status in grub-legacy-ec2 package in Ubuntu: Incomplete Bug description: I applied an system update and was presented with this error after the next login. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Feb 14 00:00:24 2019 ErrorMessage: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128 IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=36f6b4c3-1f42-11e9-99c9-00155d195067 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.8 RfKill: SourcePackage: grub-legacy-ec2 Title: package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2012 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v1.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v1.0 dmi.chassis.asset.tag: 0298-0271-9062-6147-4258-1509-89 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v1.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.version: Hyper-V UEFI Release v1.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1817077/+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 1817041] Re: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Hi Hrovje, Thank you for taking the time to report this bug and helping to make Ubuntu better. The directory would usually be created for you on system start. There were cases where users set /var to tmpfs or similar things eventually breaking this. You might take a look at [1] as that pretty much sounds like your issue already Since it seems likely to me that this is a local configuration problem, rather than a bug in Ubuntu, I'm marking this bug as Incomplete. If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community Or if you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New. [1]: https://serverfault.com/questions/941855/why-am-i-missing-var-run-sshd-after-every-boot ** Changed in: openssh (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1817041 Title: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Incomplete Bug description: During an automated update process ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Feb 21 10:50:04 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (868 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-04 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1817041/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** No longer affects: dd-plist (Ubuntu) ** No longer affects: clojure1.8 (Ubuntu) ** No longer affects: gradle-debian-helper (Ubuntu) ** No longer affects: jtreg (Ubuntu) ** No longer affects: libcommons-lang3-java (Ubuntu) ** No longer affects: maven-compiler-plugin (Ubuntu) ** No longer affects: maven-debian-helper (Ubuntu) ** No longer affects: plexus-languages (Ubuntu) ** No longer affects: surefire (Ubuntu) ** No longer affects: testng (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Packages from stage 3 and later are not yet reviewed and should not be uploaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1814133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1817243] Re: I have dual boot ubuntu. in Ubunt, there is no output sound devices and always keep muted. In windows sound working perfectly
The reason why you are not getting sound is because: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - No To find out why this is so, please: 1. Follow these instructions to check for crashes: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment 2. If no evidence of 'pulseaudio' crashing could be found then please try this: 2.1. Edit your /etc/pulse/daemon.conf and add a new line that is: realtime-scheduling = no 2.2. Reboot and tell us if the problem persists. ** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- 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/1817243 Title: I have dual boot ubuntu. in Ubunt, there is no output sound devices and always keep muted. In windows sound working perfectly Status in pulseaudio package in Ubuntu: Incomplete Bug description: No output sound device available. Sound icon shows it is muted and the sound button on the keyboard as well. It does not let to unmute as well. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Feb 22 09:20:20 2019 InstallationDate: Installed on 2019-02-06 (15 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG6097143 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook650G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 650 G2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1817243/+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 1817243] [NEW] I have dual boot ubuntu. in Ubunt, there is no output sound devices and always keep muted. In windows sound working perfectly
Public bug reported: No output sound device available. Sound icon shows it is muted and the sound button on the keyboard as well. It does not let to unmute as well. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Feb 22 09:20:20 2019 InstallationDate: Installed on 2019-02-06 (15 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG6097143 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook650G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 650 G2 dmi.sys.vendor: HP ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1817243 Title: I have dual boot ubuntu. in Ubunt, there is no output sound devices and always keep muted. In windows sound working perfectly Status in pulseaudio package in Ubuntu: New Bug description: No output sound device available. Sound icon shows it is muted and the sound button on the keyboard as well. It does not let to unmute as well. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.10 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Fri Feb 22 09:20:20 2019 InstallationDate: Installed on 2019-02-06 (15 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2015 dmi.bios.vendor: HP dmi.bios.version: N76 Ver. 01.00 dmi.board.name: 80FD dmi.board.vendor: HP dmi.board.version: KBC Version 22.36 dmi.chassis.asset.tag: 5CG6097143 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN76Ver.01.00:bd12/07/2015:svnHP:pnHPProBook650G2:pvr:rvnHP:rn80FD:rvrKBCVersion22.36:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 650 G2 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1817243/+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 1574266] Re: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning
** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1574266 Title: Xorg freeze [drm] stuck on render ring - gpu hanging too fast, banning Status in linux package in Ubuntu: Incomplete Bug description: dmesg output : [ 8815.416923] [drm] stuck on render ring [ 8815.417367] [drm] GPU HANG: ecode 6:0:0x05b2c6c5, in Compositor [21164], reason: Ring hung, action: reset [ 8815.419462] drm/i915: Resetting chip after gpu hang [ 8821.417592] [drm] stuck on render ring [ 8821.418007] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8821.420108] drm/i915: Resetting chip after gpu hang [ 8827.430254] [drm] stuck on render ring [ 8827.430672] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], reason: Ring hung, action: reset [ 8827.432786] drm/i915: Resetting chip after gpu hang [ 8833.418862] [drm] stuck on render ring [ 8833.419454] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [3107], reason: Ring hung, action: reset [ 8833.421551] drm/i915: Resetting chip after gpu hang [ 8839.419503] [drm] stuck on render ring [ 8839.419971] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8839.422060] drm/i915: Resetting chip after gpu hang [ 8845.432118] [drm] stuck on render ring [ 8845.432647] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8845.434799] drm/i915: Resetting chip after gpu hang [ 8851.432751] [drm] stuck on render ring [ 8851.433142] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], reason: Ring hung, action: reset [ 8851.435224] drm/i915: Resetting chip after gpu hang [ 8857.457381] [drm] stuck on render ring [ 8857.457797] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6783], reason: Ring hung, action: reset [ 8857.459883] drm/i915: Resetting chip after gpu hang [ 8863.458003] [drm] stuck on render ring [ 8863.458555] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8863.460640] drm/i915: Resetting chip after gpu hang [ 8869.458654] [drm] stuck on render ring [ 8869.459001] [drm] GPU HANG: ecode 6:0:0xfeff, in Xorg [1058], reason: Ring hung, action: reset [ 8869.459095] [drm:i915_set_reset_status [i915]] *ERROR* gpu hanging too fast, banning! [ 8869.461116] drm/i915: Resetting chip after gpu hang [ 8875.435238] [drm] stuck on render ring [ 8875.435606] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8875.437697] drm/i915: Resetting chip after gpu hang [ 8881.447863] [drm] stuck on render ring [ 8881.448251] [drm] GPU HANG: ecode 6:0:0xfeff, in Compositor [21164], reason: Ring hung, action: reset [ 8881.450331] drm/i915: Resetting chip after gpu hang [ 8887.436497] [drm] stuck on render ring [ 8887.436876] [drm] GPU HANG: ecode 6:0:0xbb88, in compiz [6817], reason: Ring hung, action: reset [ 8887.438961] drm/i915: Resetting chip after gpu hang [ 8893.437078] [drm] stuck on render ring [ 8893.437471] [drm] GPU HANG: ecode 6:0:0xfeff, in compiz [6817], reason: Ring hung, action: reset [ 8893.439562] drm/i915: Resetting chip after gpu hang ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 24 15:57:17 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2002] InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=45576678-3e92-4769-b6d3-3e3cafa54c2e ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156
[Touch-packages] [Bug 1817222] Re: [nvidia] Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Summary changed: - Xorg freeze + [nvidia] Xorg freeze ** Tags added: nvidia ** Tags removed: nvidia ** Tags added: nouveau ** Summary changed: - [nvidia] Xorg freeze + [nouveau] Xorg freeze ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817222 Title: [nouveau] Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: I have selected the NVIDIA driver instead and can report the same problem - screen frozen one internet page open no other programs. Using Firefox as per original install, each time this freeze has occurred only when connected to wireless network and using the internet. So this is an update to the original logged error report. Have been using Ubuntu online/offline for occasional browsing or offline use since installation and no issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 21:49:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2019-02-20 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1817222/+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 1398681] Re: [Satellite C655D, Conexant CX20585, Black Headphone Out, Left] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1398681 Title: [Satellite C655D, Conexant CX20585, Black Headphone Out, Left] No sound at all Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm having several problems. Some of my vidios lose audio after I start playing, this maybe caused by a paticular vidio down loader I was using I've switch to ANT and so far it seems to be working. Recently I've tryed to empty my trash basket and I cant get it to work I've tried different ways and all that happens is the computer freezes up and the only way out is to turn the computer off with the power switch I have also noticed that working with Firefox it seems that it is taking a long time to open websites meny I have to do a retry, I am also noticeing that when shutdown the computer normaly the wifi dosen't allwas shutdown I have to restart and shutdown manualy and then shutdown. I am using Ubuntu 2014-04 LTS and ATT wireless DSL U-verse. I think my system maybe getting infected. Are there any Anti virus and Malware progams for Ubuntu available from Ubuntu or Conical?l ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clark 1643 F pulseaudio /dev/snd/pcmC0D0p: clark 1643 F...m pulseaudio CurrentDesktop: Unity Date: Tue Dec 2 20:09:13 2014 InstallationDate: Installed on 2014-04-24 (223 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clark 1643 F pulseaudio /dev/snd/pcmC0D0p: clark 1643 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite C655D, Conexant CX20585, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.60 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.60:bd06/23/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-018001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-018001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1398681/+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 1398681] Re: [Satellite C655D, Conexant CX20585, Black Headphone Out, Left] No sound at all
** Tags added: bionic -- 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/1398681 Title: [Satellite C655D, Conexant CX20585, Black Headphone Out, Left] No sound at all Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm having several problems. Some of my vidios lose audio after I start playing, this maybe caused by a paticular vidio down loader I was using I've switch to ANT and so far it seems to be working. Recently I've tryed to empty my trash basket and I cant get it to work I've tried different ways and all that happens is the computer freezes up and the only way out is to turn the computer off with the power switch I have also noticed that working with Firefox it seems that it is taking a long time to open websites meny I have to do a retry, I am also noticeing that when shutdown the computer normaly the wifi dosen't allwas shutdown I have to restart and shutdown manualy and then shutdown. I am using Ubuntu 2014-04 LTS and ATT wireless DSL U-verse. I think my system maybe getting infected. Are there any Anti virus and Malware progams for Ubuntu available from Ubuntu or Conical?l ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clark 1643 F pulseaudio /dev/snd/pcmC0D0p: clark 1643 F...m pulseaudio CurrentDesktop: Unity Date: Tue Dec 2 20:09:13 2014 InstallationDate: Installed on 2014-04-24 (223 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB successful Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: clark 1643 F pulseaudio /dev/snd/pcmC0D0p: clark 1643 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [Satellite C655D, Conexant CX20585, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.60 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.60:bd06/23/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-018001:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-018001 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1398681/+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 1817202] Re: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all
*** This bug is a duplicate of bug 1398681 *** https://bugs.launchpad.net/bugs/1398681 Actually, let's use bug 1398681 since it's the same machine type. ** This bug has been marked a duplicate of bug 1398681 [Satellite C655D, Conexant CX20585, Black Headphone Out, Left] No sound at all -- 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/1817202 Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all running "intel HDA" Azalia SBX00 kernel module reported as snd_hda_intel, unless my speakers are just dead!! Thanks I'm running ubuntu 18.04 and love it!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user2 1650 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 14:34:25 2019 InstallationDate: Installed on 2015-12-24 (1155 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1281 F pulseaudio user2 1650 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd12/20/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-04V03X:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.family: Type1Family dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-04V03X dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1817202/+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 1817202] Re: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all
*** This bug is a duplicate of bug 1398681 *** https://bugs.launchpad.net/bugs/1398681 Please try different speakers/headphones. Please also try booting with NONE connected and tell us if it works by connecting them after you have logged in. -- 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/1817202 Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all running "intel HDA" Azalia SBX00 kernel module reported as snd_hda_intel, unless my speakers are just dead!! Thanks I'm running ubuntu 18.04 and love it!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user2 1650 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 14:34:25 2019 InstallationDate: Installed on 2015-12-24 (1155 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1281 F pulseaudio user2 1650 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd12/20/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-04V03X:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.family: Type1Family dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-04V03X dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1817202/+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 1817216] Re: Xorg freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817216 Title: Xorg freeze Status in xorg-server package in Ubuntu: Incomplete Bug description: Hi just wanted to report in addition I had two webpages open no other programs running. The webpages were youtube and msn when the page froze - the cursor/mouse did not respond and the keyboard was locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 20:58:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2019-02-20 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1817216/+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 1817062] Re: computer reported that thete is a systemproblem
Please attach a photo of the problem you are seeing. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817062 Title: computer reported that thete is a systemproblem Status in Ubuntu: Incomplete Bug description: Systemproblem, how to solve that? Thanks in advance, J.Minekus ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 21 14:24:13 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2000] InstallationDate: Installed on 2019-02-02 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1d6da071-0c5e-4565-abc3-a06444c93cd7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-201:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1817062/+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 1817222] [NEW] Xorg freeze
Public bug reported: I have selected the NVIDIA driver instead and can report the same problem - screen frozen one internet page open no other programs. Using Firefox as per original install, each time this freeze has occurred only when connected to wireless network and using the internet. So this is an update to the original logged error report. Have been using Ubuntu online/offline for occasional browsing or offline use since installation and no issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 21:49:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2019-02-20 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817222 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: I have selected the NVIDIA driver instead and can report the same problem - screen frozen one internet page open no other programs. Using Firefox as per original install, each time this freeze has occurred only when connected to wireless network and using the internet. So this is an update to the original logged error report. Have been using Ubuntu online/offline for occasional browsing or offline use since installation and no issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 21:49:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2019-02-20 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: G31M-ES2L
[Touch-packages] [Bug 1817216] Re: Xorg freeze
** Information type changed from Public to Public Security -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817216 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hi just wanted to report in addition I had two webpages open no other programs running. The webpages were youtube and msn when the page froze - the cursor/mouse did not respond and the keyboard was locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 20:58:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2019-02-20 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1817216/+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 1817216] [NEW] Xorg freeze
*** This bug is a security vulnerability *** Public security bug reported: Hi just wanted to report in addition I had two webpages open no other programs running. The webpages were youtube and msn when the page froze - the cursor/mouse did not respond and the keyboard was locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 20:58:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2019-02-20 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817216 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: Hi just wanted to report in addition I had two webpages open no other programs running. The webpages were youtube and msn when the page froze - the cursor/mouse did not respond and the keyboard was locked. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 20:58:48 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: This is the first time GraphicsCard: NVIDIA Corporation GT218 [NVS 300] [10de:10d8] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company GT218 [NVS 300] [103c:0862] InstallationDate: Installed on 2019-02-20 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. G31M-ES2L ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FG dmi.board.name: G31M-ES2L dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd02/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnG31M-ES2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG31M-ES2L:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G31M-ES2L dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A
[Touch-packages] [Bug 1814562] Re: Update to new upstream 1.0.2
This bug was fixed in the package zeitgeist - 1.0.2-0ubuntu1 --- zeitgeist (1.0.2-0ubuntu1) disco; urgency=medium * New upstream release (LP: #1814562) -- Rico Tzschichholz Thu, 14 Feb 2019 07:54:18 +0100 ** Changed in: zeitgeist (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1814562 Title: Update to new upstream 1.0.2 Status in zeitgeist package in Ubuntu: Fix Released Bug description: There is a new upstream release which fixes issues with valac 0.43/44 https://launchpad.net/zeitgeist/+milestone/1.0.2 2018-01-31: Zeitgeist 1.0.2 "Phoenix" --- Overall: - Fix compile errors and warnings with new vala - fts: Correctly implement the org.gnome.zeitgeist.Index DBus interface - test-log: Use correct free function for ZeitgeistResultSet - Do not require rapper as it is not used anymore - Make ontology2code work with python3 - Properly fallback with the Zeitgeist version - rdflib directly to parse the trig files - Update Ontology2code to ba able to specify the output path Libzeitgeist: - Asynchronous out-parameters are only allowed at the end of argument lists *** THIS IS AN UNAVOIDABLE VALA API BREAK *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1814562/+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 1817202] [NEW] [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all
Public bug reported: No sound at all running "intel HDA" Azalia SBX00 kernel module reported as snd_hda_intel, unless my speakers are just dead!! Thanks I'm running ubuntu 18.04 and love it!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user2 1650 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 14:34:25 2019 InstallationDate: Installed on 2015-12-24 (1155 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1281 F pulseaudio user2 1650 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd12/20/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-04V03X:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.family: Type1Family dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-04V03X dmi.sys.vendor: TOSHIBA ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1817202 Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: No sound at all running "intel HDA" Azalia SBX00 kernel module reported as snd_hda_intel, unless my speakers are just dead!! Thanks I'm running ubuntu 18.04 and love it!! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user2 1650 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 14:34:25 2019 InstallationDate: Installed on 2015-12-24 (1155 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:SB failed Symptom_Card: Built-in Audio - HDA ATI SB Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1281 F pulseaudio user2 1650 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [Satellite C655D, Conexant CX20585, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.80 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.80:bd12/20/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-04V03X:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.family: Type1Family dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-04V03X dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1817202/+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 1817097] Comment bridged from LTC Bugzilla
--- Comment From christian.r...@de.ibm.com 2019-02-21 12:51 EDT--- There is a minor correction needed to the setup outlined above, as the enc-loop mapper device is backed by the second loopback device, and the volume group consists of the two devices listed in [ ] : LV | VG: LOOP_VG [ /dev/loop0, /dev/mapper/enc-loop ] | PV: /dev/loop0 --> /dev/mapper/enc-loop ( backed by /dev/loop1 ) Mind there are SCSI devices providing 4k block sizes, thus check with 'blockdev --getbsz' to actually run a scenario from 512 --> 4096 bytes block sizes. -- 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/1817097 Title: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices Status in Ubuntu on IBM z Systems: New Status in lvm2 package in Ubuntu: New Bug description: Problem Description--- Summary === Environment: IBM Z13 LPAR and z/VM Guest IBM Type: 2964 Model: 701 NC9 OS: Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x) Package: lvm2 version 2.02.176-4.1ubuntu3 LVM: pvmove operation corrupts file system when using 4096 (4k) logical block size and default block size being 512 bytes in the underlying devices The problem is immediately reproducible. We see a real usability issue with data destruction as consequence - which is not acceptable. We expect 'pvmove' to fail with error in such situations to prevent fs destruction, which might possibly be overridden by a force flag. Details === After a 'pvmove' operation is run to move a physical volume onto an ecrypted device with 4096 bytes logical block size we experience a file system corruption. There is no need for the file system to be mounted, but the problem surfaces differently if so. Either, the 'pvs' command after the pvmove shows /dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument or a subsequent mount shows (after umount if the fs had previously been mounted as in our setup) mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error. A minimal setup of LVM using one volume group with one logical volume defined, based on one physical volume is sufficient to raise the problem. One more physical volume of the same size is needed to run the pvmove operation to. LV | VG: LOOP_VG [ ] | PV: /dev/loop0 --> /dev/mapper/enc-loop ( backed by /dev/mapper/enc-loop ) The physical volumes are backed by loopback devices (losetup) to base the problem report on, but we have seen the error on real SCSI multipath volumes also, with and without cryptsetup mapper devices in use. Further discussion == https://www.saout.de/pipermail/dm-crypt/2019-February/006078.html The problem does not occur on block devices with native size of 4k. E.g. DASDs, or file systems with mkfs -b 4096 option. Terminal output === See attached file pvmove-error.txt Debug data == pvmove was run with -dd (maximum debug level) See attached journal file. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:00:35 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM Type: 2964 Model: 701 NC9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Create two image files of 500MB in size and set up two loopback devices with 'losetup -fP FILE' 2.) Create one physical volume and one volume group 'LOOP_VG', and one logical volume 'VG' Run: pvcreate /dev/loop0 vgcreate LOOP_VG /dev/loop0 lvcreate -L 300MB LOOP_VG -n LV /dev/loop0 3.) Create a file system on the logical volume device: mkfs.ext4 /dev/mapper/LOOP_VG-LV 4.) mount the file system created in the previous step to some empty available directory: mount /dev/mapper/LOOP_VG-LV /mnt 5.) Set up a second physical volume, this time encrypted with LUKS2, and open the volume to make it available: cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1 cryptsetup luksOpen /dev/loop1 enc-loop 6.) Create the second physical volume, and add it to the LOOP_VG pvcreate /dev/mapper/enc-loop vgextend LOOP_VG /dev/mapper/enc-loop 7.) Ensure the new physical volume is part of the volume group: pvs 8.) Move the /dev/loop0 volume onto the encrypted volume with maximum debug
[Touch-packages] [Bug 1571531] Re: cupsd cause apparmor denials for /etc/ld.so.preload
Hi guys Waiting for new instructions Thank you -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1571531 Title: cupsd cause apparmor denials for /etc/ld.so.preload Status in apparmor package in Ubuntu: New Bug description: There is a constant flood of messages in dmesg: [ 4431.638163] audit: type=1400 audit(1460962510.272:60): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10559 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 4431.661208] audit: type=1400 audit(1460962510.296:61): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 4431.661390] audit: type=1400 audit(1460962510.296:62): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 4431.661759] audit: type=1400 audit(1460962510.296:63): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10564 comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0 [ 4431.661936] audit: type=1400 audit(1460962510.296:64): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 4431.661937] audit: type=1400 audit(1460962510.296:65): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10565 comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0 [ 4431.662534] audit: type=1400 audit(1460962510.296:66): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10566 comm="dbus" requested_mask="r" denied_mask="r" fsuid=7 ouid=0 [ 5081.410342] audit: type=1400 audit(1460963160.033:67): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10810 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 5081.446507] audit: type=1400 audit(1460963160.069:68): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/etc/ld.so.preload" pid=10815 comm="cups-exec" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CupsErrorLog: CurrentDesktop: X-Cinnamon Date: Mon Apr 18 10:56:37 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2013-07-19 (1003 days ago) InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1) Lpstat: device for Generic-PCL-5e: socket://192.168.1.100:9100 MachineType: LENOVO 4298R86 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Generic-PCL-5e.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Generic-PCL-5e.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic root=UUID=3d4ce850-6e8a-4cf5-9b82-fb135c22fe1e ro SourcePackage: cups UpgradeStatus: Upgraded to xenial on 2015-10-29 (171 days ago) dmi.bios.date: 12/01/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 8DET56WW (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 4298R86 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr8DET56WW(1.26):bd12/01/2011:svnLENOVO:pn4298R86:pvrThinkPadX220Tablet:rvnLENOVO:rn4298R86:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4298R86 dmi.product.version: ThinkPad X220 Tablet dmi.sys.vendor: LENOVO modified.conffile..etc.default.cups: # Cups configure options # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf # LOAD_LP_MODULE=yes mtime.conffile..etc.default.cups: 2014-03-12T15:11:15.740184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1571531/+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 1814562] Re: Update to new upstream 1.0.2
** Changed in: zeitgeist (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1814562 Title: Update to new upstream 1.0.2 Status in zeitgeist package in Ubuntu: Fix Committed Bug description: There is a new upstream release which fixes issues with valac 0.43/44 https://launchpad.net/zeitgeist/+milestone/1.0.2 2018-01-31: Zeitgeist 1.0.2 "Phoenix" --- Overall: - Fix compile errors and warnings with new vala - fts: Correctly implement the org.gnome.zeitgeist.Index DBus interface - test-log: Use correct free function for ZeitgeistResultSet - Do not require rapper as it is not used anymore - Make ontology2code work with python3 - Properly fallback with the Zeitgeist version - rdflib directly to parse the trig files - Update Ontology2code to ba able to specify the output path Libzeitgeist: - Asynchronous out-parameters are only allowed at the end of argument lists *** THIS IS AN UNAVOIDABLE VALA API BREAK *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1814562/+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 1163406] Re: Device-mapper initialized before hardware-raid during system boot
If you are finding this bug and having an issue after upgrading to 16.04 and keeping upstart, see Bug #1573982 for a fix. -- 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/1163406 Title: Device-mapper initialized before hardware-raid during system boot Status in lvm2 package in Ubuntu: Expired Bug description: I set up a LVM on a freshly installed Ubuntu Server 12.04.2 LTS 64 Bit. If I locate the LVM's physical volume on a partition residing on a hardware RAID-1 (dev/sdb), the logical volumes are in NOT available state after system start and have to be activated by the command vgchange -ay. As soon I locate the LVM's physical volume on the non- raid boot-drive (/dev/sda), the logical volumes are activated on system start and can even be mounted by an entry in /etc/fstab. Due to this behaviour I assume, that the hardware-raid is initialized AFTER the device-mapper is loaded. This way the LVM's logical volumes on the raid can not be initialized during system start. This is also indicated by the following logfile entry: /var/log/syslog ... Mar 29 15:02:01 ikarus kernel: [0.470265] device-mapper: uevent: version 1.0.3 Mar 29 15:02:01 ikarus kernel: [0.470297] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: dm-de...@redhat.com ... Mar 29 15:02:01 ikarus kernel: [0.782506] 3ware 9000 Storage Controller device driver for Linux v2.26.02.014. Mar 29 15:02:01 ikarus kernel: [0.782937] 3w-9xxx: scsi6: ERROR: (0x06:0x000D): PCI Abort: clearing. Mar 29 15:02:01 ikarus kernel: [0.812967] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null) ... System Configuration: -Ubuntu Server 12.04.2 64 Bit -Intel Core i5-3450, 16G RAM -128 GB SSD as System disk (/dev/sda) -3ware 9650SE-4LPML Raid-Controller, RAID1 with 2 TB capacity (/dev/sdb) -Bootloader and root-partition located on /dev/sda -For /var and /tmp two primary partitions on /dev/sdb are used -The third (extended) partition of /dev/sdb is used as physical volume for the LVM -The LVM only stores user-data, no system related information Steps leading to issue: -Installed Ubuntu Server 12.04.2 64 Bit on /dev/sda without setting up LVM -Partitioned /dev/sdb using fdisk and set partition type to '8e' -Installed lvm: apt-get install lvm2 -Set up lvm with four logical volumes (physical volume residing on /dev/sdb5) -Formatted logical volumes with ext4 using mkfs -Command lvdisplay shows all logical volumes as available -Created mount points for logical volumes -Manual mount of logical volumes works -Edited /etc/fstab to automatically mount logical volumes - example for one logical volume: UUID=[uuid-like-displayed-by-lvdisplay] /mnt/images ext4 default 0 1 - Rebooted system Problem: - System displays the following message when booting up and waits for user action to skip mount commands: -The disk drive for /mnt/images is not ready yet or present. -Continue to wait, or press S to skip mounting or M for manual recovery -When skipped the same message is shown for the next logical volume mount point -After skipping the last mount point boot up proceeds until login screen -When login in the logical volumes are not mounted and in status "NOT available" according to lvdisplay This bug is related to the following tread in the Ubuntu-Forum: http://ubuntuforums.org/showthread.php?t=2130232 If I have a solution for this issue I will update the tread to make the information public to other Ubuntu-users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1163406/+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 1815494] Re: May remove autoremovable non-kernel packages matching pattern from APT::VersionedKernelPackages
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.9 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: unattended-upgrades (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1815494
Title:
May remove autoremovable non-kernel packages matching pattern from
APT::VersionedKernelPackages
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
New
Status in unattended-upgrades source package in Bionic:
Fix Committed
Status in unattended-upgrades source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* Non-kernel related autoremovable packages may be removed by
unattended-upgrades due to their name matching generic patterns like
'.*-modules' which should be applied to versioned kernel packages only.
* The fix corrects the way those patterns are handled.
[Test Case]
* test/test_remove_unused.py checks for correct pattern usage now.
[Regression Potential]
* Unattended-upgrades may stop removing autoremovable kernels, but the
tests also contain cases covering this and u-u's kernel autoremoval
still works.
[Original Bug Text]
Unattended-upgrades and Update Manager use the patterns from the
APT::VersionedKernelPackages list directly for finding kernel packages
to remove while APT uses patterns by attaching version and flavor to
them.
As a result in APT's script ".*-modules" becomes
"^.*-modules-4\.15\.0-45-generic$":
...
for package in $(apt-config dump --no-empty --format '%v%n'
'APT::VersionedKernelPackages'); do
for kernel in $kernels; do
echo " \"^${package}-${kernel}$\";"
done
...
In unattended-upgrades and update-manager ".*-modules" is used
directly for matching and may false identify autoremovable packages
as kernel-related ones and remove them (of just offer the removal in
case of update-manager):
...
Removing unused kernel packages: extra-cmake-modules
marking extra-cmake-modules for removal
(Reading database ... 31149 files and directories currently installed.)
Removing extra-cmake-modules (5.44.0-0ubuntu1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Packages that were successfully auto-removed: extra-cmake-modules
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1815494/+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 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.1ubuntu1.18.04.9 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: unattended-upgrades (Ubuntu Bionic)
Status: Confirmed => Fix Committed
** Tags removed: verification-failed verification-failed-bionic
** 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1781176
Title:
Blacklisted packages are included in the "upgradable origin", while
they should not
Status in unattended-upgrades:
Fix Released
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in unattended-upgrades source package in Xenial:
In Progress
Status in unattended-upgrades source package in Bionic:
Fix Committed
Bug description:
[Impact]
* Reports from u-u incorrectly list packages from non-upgradable
origins as "Packages with upgradable origin but kept back"
* Listing the packages incorrectly is a result of
is_pkgname_in_blacklist() having a side effect and removing the side
effect is part of fixing LP: #1396787 which fix is also being SRU-d.
* The fix is removing the side effect of is_pkgname_in_blacklist()
[Test Case]
* There is a build-time test in test/test_blacklisted_wrong_origin.py
* To reproduce the original problem set up a system where all security
updates are installed but ebtables (from bionic-updates) is not updated:
$ sudo unattended-upgrade --verbose
Initial blacklisted packages:
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
No packages found that can be upgraded unattended and no pending auto-removals
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
apt apt-utils ebtables initramfs-tools initramfs-tools-bin
initramfs-tools-core libapt-inst2.0 libapt-pkg5.0
liblxc-common liblxc1 libpython3-stdlib lxcfs lxd lxd-client netplan.io
networkd-dispatcher nplan
python-apt-common python3 python3-apt python3-minimal
python3-update-manager snapd squashfs-tools
unattended-upgrades update-manager-core update-notifier-common
27 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 24.1 MB of archives.
After this operation, 1454 kB of additional disk space will be used.
Do you want to continue? [Y/n] n
Abort.
* blacklist ebtables, set up emails from u-u, then run u-u again:
$ sudo echo 'Unattended-Upgrade::Package-Blacklist {"ebtables";};' >
/etc/apt/apt.conf.d/51unattended-upgrades-blacklist-ebtables
$ sudo echo 'Unattended-Upgrade::Mail "root";' >
/etc/apt/apt.conf.d/51unattended-upgrades-mail
$ sudo unattended-upgrade --verbose
Initial blacklisted packages: ebtables
Initial whitelisted packages:
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
Packages that will be upgraded:
* Observe ebtables listed as being kept back and having upgradable origin
with buggy u-u:
$ sudo cat /var/mail/mail
...
Packages with upgradable origin but kept back:
ebtables=20
...
* Upgrade u-u to a fixed version and run it, observing ebtables to be
not listed as having upgradable origin
[Regression Potential]
* Regressions may make packages incorrectly missing from u-u's
report, but the autopkgtests also cover that to some extent.
[Other Info]
* Original report: https://github.com/mvo5/unattended-
upgrades/issues/116
To manage notifications about this bug go to:
[Touch-packages] [Bug 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.1ubuntu1.18.04.9 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: unattended-upgrades (Ubuntu Bionic) Status: Fix Released => Fix Committed ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Unattended-upgrades can be crashing when packages are marked for removal after collecting upgradable packages. * The fix clear the cache when it may be in an invalid state to lose markings. [Test Case] * Observe https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2 not occurring in fixed versions. [Regression Potential] * The extra cache.clear() can take extra CPU time when invoked needlessly or can cause skipping updates when invoked at the wrong time. However the fix received extensive testing in newer releases making unnoticed regressions unlikely to surface. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic Also seen as: https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1817123] [NEW] tmpfiles.d files pointing to legacy directory /var/run
Public bug reported: Just updated cosmic and got: Setting up systemd (239-7ubuntu10.8) ... [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly. andre@thinkpad:~$ lsb_release -rd Description:Ubuntu 18.10 Release:18.10 andre@thinkpad:~$ apt-cache policy systemd systemd: Installed: 239-7ubuntu10.8 Candidate: 239-7ubuntu10.8 Version table: *** 239-7ubuntu10.8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 100 /var/lib/dpkg/status 239-7ubuntu10 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - tmpfiles.d files poiting to legacy directory /var/run + tmpfiles.d files pointing to legacy directory /var/run -- 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/1817123 Title: tmpfiles.d files pointing to legacy directory /var/run Status in systemd package in Ubuntu: New Bug description: Just updated cosmic and got: Setting up systemd (239-7ubuntu10.8) ... [/usr/lib/tmpfiles.d/speech-dispatcher.conf:1] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher → /run/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:2] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache → /run/speech-dispatcher/.cache; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:3] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.speech-dispatcher → /run/speech-dispatcher/.speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:4] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/.cache/speech-dispatcher → /run/speech-dispatcher/.cache/speech-dispatcher; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/speech-dispatcher.conf:5] Line references path below legacy directory /var/run/, updating /var/run/speech-dispatcher/log → /run/speech-dispatcher/log; please update the tmpfiles.d/ drop-in file accordingly. [/usr/lib/tmpfiles.d/spice-vdagentd.conf:2] Line references path below legacy directory /var/run/, updating /var/run/spice-vdagentd → /run/spice-vdagentd; please update the tmpfiles.d/ drop-in file accordingly. andre@thinkpad:~$ lsb_release -rd Description:Ubuntu 18.10 Release:18.10 andre@thinkpad:~$ apt-cache policy systemd systemd: Installed: 239-7ubuntu10.8 Candidate: 239-7ubuntu10.8 Version table: *** 239-7ubuntu10.8 500 500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu cosmic-security/main amd64 Packages 100 /var/lib/dpkg/status 239-7ubuntu10 500 500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1817123/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1777994] Re: the header xcb/xinput.h is missing
Reuploaded with 1.13-2~ubuntu18.04 version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1777994 Title: the header xcb/xinput.h is missing Status in libxcb package in Ubuntu: Fix Released Status in libxcb source package in Bionic: Fix Committed Bug description: [Impact] Allow Qt 5.12 to be compiled with full input support. This allows applications to be built using complex input devices such as drawing pads. This is used in e.g Krita which KDE builds into a Snap package for distribution. Currently Krita does not work with pen input devices with pressure sensitivity. [Test Case] Install Krita with Qt 5.12 from current Snap and note how pressure sensitivity does not work. [Regression Potential] None that I can see, it's just packaging a few new header files. I suspect this means there should be another package, libxcb-xinput-dev perhaps? I already did sudo apt install "libxcb*dev" to get all related dev packages, but none of them provide xcb/xinput.h. The result is that when building Qt from source, it's necessary to use a copy of this file which Qt provides (qtbase/src/3rdparty/xcb/include/xcb/xinput.h), because it's missing from the system. So if you don't give the option -qt-xcb to configure, then Qt will be built without multi-touch support. https://bugreports.qt.io/browse/QTBUG-69045 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libxcb1-dev 1.13-1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jun 21 08:32:12 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 04f2:b5da Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80Y7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro SourcePackage: libxcb UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5NCN38WW:bd02/22/2018:svnLENOVO:pn80Y7:pvrLenovoYOGA920-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKB: dmi.product.family: YOGA 920-13IKB dmi.product.name: 80Y7 dmi.product.version: Lenovo YOGA 920-13IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxcb/+bug/1777994/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
Just a question, is this update going to affect these packages: jabref scilab octave pdfsam ? Also, I hope this update brings 18.04 LTS closer to Debian 10 regarding OpenJdk-11 and its dependant packages to facilitate the maintenance burden. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Packages from stage 3 and later are not yet reviewed and should not be uploaded. To manage notifications about this bug go to:
[Touch-packages] [Bug 1815494] Re: May remove autoremovable non-kernel packages matching pattern from APT::VersionedKernelPackages
** Description changed:
+ [Impact]
+
+ * Non-kernel related autoremovable packages may be removed by
unattended-upgrades due to their name matching generic patterns like
'.*-modules' which should be applied to versioned kernel packages only.
+ * The fix corrects the way those patterns are handled.
+
+ [Test Case]
+
+ * test/test_remove_unused.py checks for correct pattern usage now.
+
+ [Regression Potential]
+
+ * Unattended-upgrades may stop removing autoremovable kernels, but the
+ tests also contain cases covering this and u-u's kernel autoremoval
+ still works.
+
+ [Original Bug Text]
+
Unattended-upgrades and Update Manager use the patterns from the
APT::VersionedKernelPackages list directly for finding kernel packages
to remove while APT uses patterns by attaching version and flavor to
them.
As a result in APT's script ".*-modules" becomes
"^.*-modules-4\.15\.0-45-generic$":
...
- for package in $(apt-config dump --no-empty --format '%v%n'
'APT::VersionedKernelPackages'); do
- for kernel in $kernels; do
- echo " \"^${package}-${kernel}$\";"
- done
+ for package in $(apt-config dump --no-empty --format '%v%n'
'APT::VersionedKernelPackages'); do
+ for kernel in $kernels; do
+ echo " \"^${package}-${kernel}$\";"
+ done
...
In unattended-upgrades and update-manager ".*-modules" is used directly
for matching and may false identify autoremovable packages as kernel-
related ones and remove them (of just offer the removal in case of
update-manager):
...
Removing unused kernel packages: extra-cmake-modules
marking extra-cmake-modules for removal
(Reading database ... 31149 files and directories currently installed.)
Removing extra-cmake-modules (5.44.0-0ubuntu1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Packages that were successfully auto-removed: extra-cmake-modules
...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1815494
Title:
May remove autoremovable non-kernel packages matching pattern from
APT::VersionedKernelPackages
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
New
Status in unattended-upgrades source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* Non-kernel related autoremovable packages may be removed by
unattended-upgrades due to their name matching generic patterns like
'.*-modules' which should be applied to versioned kernel packages only.
* The fix corrects the way those patterns are handled.
[Test Case]
* test/test_remove_unused.py checks for correct pattern usage now.
[Regression Potential]
* Unattended-upgrades may stop removing autoremovable kernels, but the
tests also contain cases covering this and u-u's kernel autoremoval
still works.
[Original Bug Text]
Unattended-upgrades and Update Manager use the patterns from the
APT::VersionedKernelPackages list directly for finding kernel packages
to remove while APT uses patterns by attaching version and flavor to
them.
As a result in APT's script ".*-modules" becomes
"^.*-modules-4\.15\.0-45-generic$":
...
for package in $(apt-config dump --no-empty --format '%v%n'
'APT::VersionedKernelPackages'); do
for kernel in $kernels; do
echo " \"^${package}-${kernel}$\";"
done
...
In unattended-upgrades and update-manager ".*-modules" is used
directly for matching and may false identify autoremovable packages
as kernel-related ones and remove them (of just offer the removal in
case of update-manager):
...
Removing unused kernel packages: extra-cmake-modules
marking extra-cmake-modules for removal
(Reading database ... 31149 files and directories currently installed.)
Removing extra-cmake-modules (5.44.0-0ubuntu1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Packages that were successfully auto-removed: extra-cmake-modules
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1815494/+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 1817097] Re: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices
** Package changed: linux (Ubuntu) => lvm2 (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) ** Changed in: ubuntu-z-systems Importance: Undecided => Critical -- 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/1817097 Title: pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices Status in Ubuntu on IBM z Systems: New Status in lvm2 package in Ubuntu: New Bug description: Problem Description--- Summary === Environment: IBM Z13 LPAR and z/VM Guest IBM Type: 2964 Model: 701 NC9 OS: Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x) Package: lvm2 version 2.02.176-4.1ubuntu3 LVM: pvmove operation corrupts file system when using 4096 (4k) logical block size and default block size being 512 bytes in the underlying devices The problem is immediately reproducible. We see a real usability issue with data destruction as consequence - which is not acceptable. We expect 'pvmove' to fail with error in such situations to prevent fs destruction, which might possibly be overridden by a force flag. Details === After a 'pvmove' operation is run to move a physical volume onto an ecrypted device with 4096 bytes logical block size we experience a file system corruption. There is no need for the file system to be mounted, but the problem surfaces differently if so. Either, the 'pvs' command after the pvmove shows /dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument or a subsequent mount shows (after umount if the fs had previously been mounted as in our setup) mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error. A minimal setup of LVM using one volume group with one logical volume defined, based on one physical volume is sufficient to raise the problem. One more physical volume of the same size is needed to run the pvmove operation to. LV | VG: LOOP_VG [ ] | PV: /dev/loop0 --> /dev/mapper/enc-loop ( backed by /dev/mapper/enc-loop ) The physical volumes are backed by loopback devices (losetup) to base the problem report on, but we have seen the error on real SCSI multipath volumes also, with and without cryptsetup mapper devices in use. Further discussion == https://www.saout.de/pipermail/dm-crypt/2019-February/006078.html The problem does not occur on block devices with native size of 4k. E.g. DASDs, or file systems with mkfs -b 4096 option. Terminal output === See attached file pvmove-error.txt Debug data == pvmove was run with -dd (maximum debug level) See attached journal file. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:00:35 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM Type: 2964 Model: 701 NC9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Create two image files of 500MB in size and set up two loopback devices with 'losetup -fP FILE' 2.) Create one physical volume and one volume group 'LOOP_VG', and one logical volume 'VG' Run: pvcreate /dev/loop0 vgcreate LOOP_VG /dev/loop0 lvcreate -L 300MB LOOP_VG -n LV /dev/loop0 3.) Create a file system on the logical volume device: mkfs.ext4 /dev/mapper/LOOP_VG-LV 4.) mount the file system created in the previous step to some empty available directory: mount /dev/mapper/LOOP_VG-LV /mnt 5.) Set up a second physical volume, this time encrypted with LUKS2, and open the volume to make it available: cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1 cryptsetup luksOpen /dev/loop1 enc-loop 6.) Create the second physical volume, and add it to the LOOP_VG pvcreate /dev/mapper/enc-loop vgextend LOOP_VG /dev/mapper/enc-loop 7.) Ensure the new physical volume is part of the volume group: pvs 8.) Move the /dev/loop0 volume onto the encrypted volume with maximum debug option: pvmove -dd /dev/loop0 /dev/mapper/enc-loop 9.) The previous step succeeds, but corrupts the file system on the logical volume We expect an error here. There might be a command line flag to override used
[Touch-packages] [Bug 1599646] Re: E-mail report contains repeated "Reading database ... NN%" lines
Hello Daniel, or anyone else affected, Accepted unattended-upgrades into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.5ubuntu3.18.10.2 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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: unattended-upgrades (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1599646 Title: E-mail report contains repeated "Reading database ... NN%" lines Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Bionic: Fix Committed Status in unattended-upgrades source package in Cosmic: Fix Committed Status in apt package in Debian: New Bug description: [Impact] * Unattended-upgrades sends the following repeating dpkg progress lines with almost no informational value in the email report: ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 60486 files and directories currently installed.) ... * This makes the report email too verbose and makes harder to spot real problems. [Test Case] * Run package autopkgtest and observe no such lines in the echoed email in upgrade-all-security and upgrade-between-snapshots tests. [Regression Potential] * The fix filters dpkg's output only and in the worst case other lines could be missing or u-u could crash. Since the applied hard- coded regex pattern is fairly simple and we observed no crashes in the tests those regressions are unlikey to occur. [Originial Bug Text] This concerns unattended-upgrades 0.90 in Xenial. Here is an excerpt from an e-mail report sent out by u-u after the upgrade process is completed: Package installation log: Log started: 2016-07-06 17:24:21 Preconfiguring packages ... (Reading database ... (Reading database ... 5% (Reading database ... 10% (Reading database ... 15% (Reading database ... 20% (Reading database ... 25% (Reading database ... 30% (Reading database ... 35% (Reading database ... 40% (Reading database ... 45% (Reading database ... 50% (Reading database ... 55% (Reading database ... 60% (Reading database ... 65% (Reading database ... 70% (Reading database ... 75% (Reading database ... 80% (Reading database ... 85% (Reading database ... 90% (Reading database ... 95% (Reading database ... 100% (Reading database ... 314949 files and directories currently installed.) Preparing to unpack .../tzdata_2016f-0ubuntu0.16.04_all.deb ... Unpacking tzdata (2016f-0ubuntu0.16.04) over (2016d-0ubuntu0.16.04) ... Preparing to unpack .../libgimp2.0_2.8.16-1ubuntu1.1_i386.deb ... All but the last "Reading database ..." line should be elided from the message. As a matter of fact, those lines do not appear in messages mailed out from current Trusty systems (u-u version 0.82.1ubuntu2.4), so this appears to be a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1599646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1817097] [NEW] pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices
You have been subscribed to a public bug: Problem Description--- Summary === Environment: IBM Z13 LPAR and z/VM Guest IBM Type: 2964 Model: 701 NC9 OS: Ubuntu 18.10 (GNU/Linux 4.18.0-13-generic s390x) Package: lvm2 version 2.02.176-4.1ubuntu3 LVM: pvmove operation corrupts file system when using 4096 (4k) logical block size and default block size being 512 bytes in the underlying devices The problem is immediately reproducible. We see a real usability issue with data destruction as consequence - which is not acceptable. We expect 'pvmove' to fail with error in such situations to prevent fs destruction, which might possibly be overridden by a force flag. Details === After a 'pvmove' operation is run to move a physical volume onto an ecrypted device with 4096 bytes logical block size we experience a file system corruption. There is no need for the file system to be mounted, but the problem surfaces differently if so. Either, the 'pvs' command after the pvmove shows /dev/LOOP_VG/LV: read failed after 0 of 1024 at 0: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314507264: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 314564608: Invalid argument /dev/LOOP_VG/LV: read failed after 0 of 1024 at 4096: Invalid argument or a subsequent mount shows (after umount if the fs had previously been mounted as in our setup) mount: /mnt: wrong fs type, bad option, bad superblock on /dev/mapper/LOOP_VG-LV, missing codepage or helper program, or other error. A minimal setup of LVM using one volume group with one logical volume defined, based on one physical volume is sufficient to raise the problem. One more physical volume of the same size is needed to run the pvmove operation to. LV | VG: LOOP_VG [ ] | PV: /dev/loop0 --> /dev/mapper/enc-loop ( backed by /dev/mapper/enc-loop ) The physical volumes are backed by loopback devices (losetup) to base the problem report on, but we have seen the error on real SCSI multipath volumes also, with and without cryptsetup mapper devices in use. Further discussion == https://www.saout.de/pipermail/dm-crypt/2019-February/006078.html The problem does not occur on block devices with native size of 4k. E.g. DASDs, or file systems with mkfs -b 4096 option. Terminal output === See attached file pvmove-error.txt Debug data == pvmove was run with -dd (maximum debug level) See attached journal file. Contact Information = christian.r...@de.ibm.com ---uname output--- Linux system 4.18.0-13-generic #14-Ubuntu SMP Wed Dec 5 09:00:35 UTC 2018 s390x s390x s390x GNU/Linux Machine Type = IBM Type: 2964 Model: 701 NC9 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1.) Create two image files of 500MB in size and set up two loopback devices with 'losetup -fP FILE' 2.) Create one physical volume and one volume group 'LOOP_VG', and one logical volume 'VG' Run: pvcreate /dev/loop0 vgcreate LOOP_VG /dev/loop0 lvcreate -L 300MB LOOP_VG -n LV /dev/loop0 3.) Create a file system on the logical volume device: mkfs.ext4 /dev/mapper/LOOP_VG-LV 4.) mount the file system created in the previous step to some empty available directory: mount /dev/mapper/LOOP_VG-LV /mnt 5.) Set up a second physical volume, this time encrypted with LUKS2, and open the volume to make it available: cryptsetup luksFormat --type luks2 --sector-size 4096 /dev/loop1 cryptsetup luksOpen /dev/loop1 enc-loop 6.) Create the second physical volume, and add it to the LOOP_VG pvcreate /dev/mapper/enc-loop vgextend LOOP_VG /dev/mapper/enc-loop 7.) Ensure the new physical volume is part of the volume group: pvs 8.) Move the /dev/loop0 volume onto the encrypted volume with maximum debug option: pvmove -dd /dev/loop0 /dev/mapper/enc-loop 9.) The previous step succeeds, but corrupts the file system on the logical volume We expect an error here. There might be a command line flag to override used because corruption does not cause a data loss. Userspace tool common name: pvmove The userspace tool has the following bit modes: 64bit Userspace rpm: lvm2 in versoin 2.02.176-4.1ubuntu3 Userspace tool obtained from project website: na *Additional Instructions for christian.r...@de.ibm.com: -Attach ltrace and strace of userspace application. ** Affects: lvm2 (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-175696 severity-critical targetmilestone-inin1810 -- pvmove causes file system corruption without notice upon move from 512 -> 4096 logical block size devices https://bugs.launchpad.net/bugs/1817097 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to
[Touch-packages] [Bug 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install
Hello errors.ubuntu.com, or anyone else affected, Accepted unattended-upgrades into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /unattended-upgrades/1.5ubuntu3.18.10.2 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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: unattended-upgrades (Ubuntu Cosmic) Status: New => Fix Committed ** Tags removed: verification-failed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: In Progress Status in unattended-upgrades source package in Bionic: Fix Released Status in unattended-upgrades source package in Cosmic: Fix Committed Bug description: [Impact] * Unattended-upgrades can be crashing when packages are marked for removal after collecting upgradable packages. * The fix clear the cache when it may be in an invalid state to lose markings. [Test Case] * Observe https://errors.ubuntu.com/problem/66b5fef8d6dd83a7db6c494c807cfc067626c0c2 not occurring in fixed versions. [Regression Potential] * The extra cache.clear() can take extra CPU time when invoked needlessly or can cause skipping updates when invoked at the wrong time. However the fix received extensive testing in newer releases making unnoticed regressions unlikely to surface. [Original Bug Text] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic Also seen as: https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+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 1815494] Re: May remove autoremovable non-kernel packages matching pattern from APT::VersionedKernelPackages
Hello Balint, or anyone else affected,
Accepted unattended-upgrades into cosmic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/unattended-upgrades/1.5ubuntu3.18.10.2 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-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. 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: unattended-upgrades (Ubuntu Cosmic)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1815494
Title:
May remove autoremovable non-kernel packages matching pattern from
APT::VersionedKernelPackages
Status in unattended-upgrades package in Ubuntu:
Fix Released
Status in update-manager package in Ubuntu:
New
Status in unattended-upgrades source package in Cosmic:
Fix Committed
Bug description:
[Impact]
* Non-kernel related autoremovable packages may be removed by
unattended-upgrades due to their name matching generic patterns like
'.*-modules' which should be applied to versioned kernel packages only.
* The fix corrects the way those patterns are handled.
[Test Case]
* test/test_remove_unused.py checks for correct pattern usage now.
[Regression Potential]
* Unattended-upgrades may stop removing autoremovable kernels, but the
tests also contain cases covering this and u-u's kernel autoremoval
still works.
[Original Bug Text]
Unattended-upgrades and Update Manager use the patterns from the
APT::VersionedKernelPackages list directly for finding kernel packages
to remove while APT uses patterns by attaching version and flavor to
them.
As a result in APT's script ".*-modules" becomes
"^.*-modules-4\.15\.0-45-generic$":
...
for package in $(apt-config dump --no-empty --format '%v%n'
'APT::VersionedKernelPackages'); do
for kernel in $kernels; do
echo " \"^${package}-${kernel}$\";"
done
...
In unattended-upgrades and update-manager ".*-modules" is used
directly for matching and may false identify autoremovable packages
as kernel-related ones and remove them (of just offer the removal in
case of update-manager):
...
Removing unused kernel packages: extra-cmake-modules
marking extra-cmake-modules for removal
(Reading database ... 31149 files and directories currently installed.)
Removing extra-cmake-modules (5.44.0-0ubuntu1) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Packages that were successfully auto-removed: extra-cmake-modules
...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1815494/+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 1774443] Re: wireless hardblocked and wireless enable button not functional
Please attach output of `rfkill list`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1774443 Title: wireless hardblocked and wireless enable button not functional Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and ubuntu. In Windows, system boots with wireless disabled and then pressing the wireless enable button twice enables WiFi. In ubuntu, system boots with wireless disabled and wireless enable button has no functionality either directly or in combination with the fn-key. Module hp_wmi may be the culprit? But disabling this has no effect on hardblock. reference forum post for more detailed info: https://ubuntuforums.org/showthread.php?t=2392934=13772159#post13772159 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.2 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 31 10:32:38 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-19 (11 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 172.16.96.1 dev eno1 proto static metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 172.16.96.0/19 dev eno1 proto kernel scope link src 172.16.119.109 metric 100 192.17.90.180 via 172.16.96.1 dev eno1 proto dhcp metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: yes SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 0357c159-f43c-38f9-8b6f-91bb641d1712 802-3-ethernet 1527780471 Thu 31 May 2018 10:27:51 AM CDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected/org/freedesktop/NetworkManager/Devices/2 Wired connection 1 0357c159-f43c-38f9-8b6f-91bb641d1712 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp8s0 wifi unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled disabled enabled enabled --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: naww 1928 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=96f5e2e6-1a22-453e-84c5-21cb7094a381 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-05-19 (32 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) IpRoute: default via 192.168.42.129 dev enp0s20u3 proto static metric 100 169.254.0.0/16 dev enp0s20u3 scope link metric 1000 192.168.42.0/24 dev enp0s20u3 proto kernel scope link src 192.168.42.168 metric 100 MachineType: Hewlett-Packard HP Pavilion dm4 Notebook PC NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.2.6-0ubuntu0.16.04.2 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=753230c7-6c88-415a-93f2-c133b9a161b1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu
[Touch-packages] [Bug 1817088] [NEW] (silent) testsuite failure in test-apt-progress-fd-errror
Public bug reported: [Impact] test-apt-progress-fd-error is failing on trusty due to a space difference, but the failure is not causing the tests to fail. [Test case] The fix fixes the test case and rewrites it to also detect failure. We can however, only detect success in the testsuite, as we do not have a testsuite testsuite :) [Regression potential] If something is wrong with the change, it could cause the tests to fail even though they are good. ** Affects: apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: apt (Ubuntu Trusty) Importance: Undecided Status: In Progress ** Changed in: apt (Ubuntu) Status: New => Incomplete ** Changed in: apt (Ubuntu) Status: Incomplete => Fix Released ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Trusty) Status: New => In Progress -- 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/1817088 Title: (silent) testsuite failure in test-apt-progress-fd-errror Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Bug description: [Impact] test-apt-progress-fd-error is failing on trusty due to a space difference, but the failure is not causing the tests to fail. [Test case] The fix fixes the test case and rewrites it to also detect failure. We can however, only detect success in the testsuite, as we do not have a testsuite testsuite :) [Regression potential] If something is wrong with the change, it could cause the tests to fail even though they are good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1817088/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1814551] Re: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA)
I can into this when using the following: $ apt list --installed gnome-shell xorg ibus gnome-shell/cosmic-updates,now 3.30.1-2ubuntu1.18.10.2 amd64 [installed] ibus/cosmic,now 1.5.19-1ubuntu1 amd64 [installed] xorg/cosmic,now 1:7.7+19ubuntu8 amd64 [installed] On Thu, 21 Feb 2019, 14:30 Olivier Tilloy, wrote: > Also tested firefox 65.0+build2-0ubuntu0.18.10.1 from the Ubuntu > repositories, and I cannot observe the problem there either. > > To everyone affected: what's your desktop session? Are you running X11 > or Wayland? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1814551 > > Title: > Ubuntu 18.10's ibus package breaks password fields in Firefox Beta > (65, 66 via PPA) > > Status in ibus package in Ubuntu: > Confirmed > > Bug description: > Essentially > https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but > reproducible in Cosmic even with the patched gnome-shell installed via > APT. > > SYSTEM INFO > = > > * Ubuntu 18.10 Cosmic with latest updates > * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20 > * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 > 09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux > * gnome-shell 3.30.1-2ubuntu1.18.10.2 > * ibus 1.5.19-1ubuntu1 > * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official > PPA) > > > STEPS TO REPRODUCE > = > > 1. Ensure keyboard input method system is > 1. Download Firefox Beta channel via their official PPA: > https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next > 2. Download and install the 1Password X firefox extentsion: > https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/ > 3. Open the extension window by either pressing the shortcut Ctrl+. or > clicking the 1Password icon in the Firefox UI > 4. Enter in the password in the input and press enter. > > Expected: The vault unlocks or displays a "this is a wrong password" > > Actual: The UI appears to "refresh" and nothing occurs. > > WORKAROUND/VALIDATION > = > > Like the original bug, switching the keyboard input method to XIM from > iBus resolves the issue suggesting to me that the symptoms I am > experiencing are caused by the root issue previously filed, fixed, and > deployed. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1814551/+subscriptions > -- 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/1814551 Title: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA) Status in ibus package in Ubuntu: Confirmed Bug description: Essentially https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but reproducible in Cosmic even with the patched gnome-shell installed via APT. SYSTEM INFO = * Ubuntu 18.10 Cosmic with latest updates * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20 * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux * gnome-shell 3.30.1-2ubuntu1.18.10.2 * ibus 1.5.19-1ubuntu1 * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA) STEPS TO REPRODUCE = 1. Ensure keyboard input method system is 1. Download Firefox Beta channel via their official PPA: https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next 2. Download and install the 1Password X firefox extentsion: https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/ 3. Open the extension window by either pressing the shortcut Ctrl+. or clicking the 1Password icon in the Firefox UI 4. Enter in the password in the input and press enter. Expected: The vault unlocks or displays a "this is a wrong password" Actual: The UI appears to "refresh" and nothing occurs. WORKAROUND/VALIDATION = Like the original bug, switching the keyboard input method to XIM from iBus resolves the issue suggesting to me that the symptoms I am experiencing are caused by the root issue previously filed, fixed, and deployed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1814551/+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 1816767] Re: purge does not remove whoopsie-id
This bug was fixed in the package whoopsie - 0.2.64 --- whoopsie (0.2.64) disco; urgency=medium * When the package is being purged remove /var/lib/whoopsie/whoopsie-id. (LP: #1816767) -- Brian Murray Thu, 21 Feb 2019 01:33:34 -0800 ** Changed in: whoopsie (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1816767 Title: purge does not remove whoopsie-id Status in whoopsie package in Ubuntu: Fix Released Bug description: whoopsie 0.2.63 $ sudo apt remove --purge whoopsie Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: whoopsie* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 109 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 220908 files and directories currently installed.) Removing whoopsie (0.2.63) ... (Reading database ... 220902 files and directories currently installed.) Purging configuration files for whoopsie (0.2.63) ... dpkg: warning: while removing whoopsie, directory '/var/lib/whoopsie' not empty so not removed Processing triggers for systemd (240-5ubuntu4) ... $ ls /var/lib/whoopsie/ whoopsie-id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1816767/+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 1815882] Re: Update evolution-data-server to 3.30.5
Hello Sebastien, or anyone else affected, Accepted evolution-data-server into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /evolution-data-server/3.30.5-0ubuntu0.18.10.1 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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: evolution-data-server (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1815882 Title: Update evolution-data-server to 3.30.5 Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Committed Bug description: * Impact That's a new bug-fix only update from GNOME There is a micro-release exception for GNOME: https://wiki.ubuntu.com/StableReleaseUpdates#GNOME https://gitlab.gnome.org/GNOME/evolution-data-server/blob/gnome-3-30/NEWS https://gitlab.gnome.org/GNOME/evolution-data-server/commits/gnome-3-30 * Test Case After installing the update, restart your computer. Run several eds-using apps like Evolution, GNOME Calendar and verify that they continue to run at least as well as before this update. * Regression Potential It's a new version with a bug of changes and fixes including in imap, calendar and gpg signing code so those features need to be well tested. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1815882/+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 1813268] Re: connection issues with Kopano IMAP servers
Hello bjo, or anyone else affected, Accepted evolution-data-server into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /evolution-data-server/3.30.5-0ubuntu0.18.10.1 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-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. 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: evolution-data-server (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1813268 Title: connection issues with Kopano IMAP servers Status in evolution-data-server package in Ubuntu: Fix Released Status in evolution-data-server source package in Cosmic: Fix Committed Bug description: * Impact Evolution doesn't work with Kopano IMAP servers: * Test case Configure an account on a Kopano IMAP server and try to use it from evolution * Regression potential The change is in the imap handling code so it would be good to test on a few different type of server that things still work correctly - 3.30.1-1 has the following issue with Kopano IMAP servers: Disable request of BODYSTRUCTURE when its response is broken https://gitlab.gnome.org/GNOME/evolution-data-server/issues/37 In 3.30.4-1 it's fixed, so a backport to cosmic would be great. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1813268/+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 1814551] Re: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA)
I cannot reproduce the issue. I'm on cosmic fully up-to-date with the same versions of gnome-shell and ibus as in the descriptino, tested firefox 66 beta 9 from the firefox-next PPA. I cannot reproduce the issue described here, nor the original issue in bug #1765304. -- 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/1814551 Title: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA) Status in ibus package in Ubuntu: Confirmed Bug description: Essentially https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but reproducible in Cosmic even with the patched gnome-shell installed via APT. SYSTEM INFO = * Ubuntu 18.10 Cosmic with latest updates * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20 * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux * gnome-shell 3.30.1-2ubuntu1.18.10.2 * ibus 1.5.19-1ubuntu1 * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA) STEPS TO REPRODUCE = 1. Ensure keyboard input method system is 1. Download Firefox Beta channel via their official PPA: https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next 2. Download and install the 1Password X firefox extentsion: https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/ 3. Open the extension window by either pressing the shortcut Ctrl+. or clicking the 1Password icon in the Firefox UI 4. Enter in the password in the input and press enter. Expected: The vault unlocks or displays a "this is a wrong password" Actual: The UI appears to "refresh" and nothing occurs. WORKAROUND/VALIDATION = Like the original bug, switching the keyboard input method to XIM from iBus resolves the issue suggesting to me that the symptoms I am experiencing are caused by the root issue previously filed, fixed, and deployed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1814551/+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 1814551] Re: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA)
Also tested firefox 65.0+build2-0ubuntu0.18.10.1 from the Ubuntu repositories, and I cannot observe the problem there either. To everyone affected: what's your desktop session? Are you running X11 or Wayland? -- 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/1814551 Title: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA) Status in ibus package in Ubuntu: Confirmed Bug description: Essentially https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but reproducible in Cosmic even with the patched gnome-shell installed via APT. SYSTEM INFO = * Ubuntu 18.10 Cosmic with latest updates * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20 * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux * gnome-shell 3.30.1-2ubuntu1.18.10.2 * ibus 1.5.19-1ubuntu1 * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA) STEPS TO REPRODUCE = 1. Ensure keyboard input method system is 1. Download Firefox Beta channel via their official PPA: https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next 2. Download and install the 1Password X firefox extentsion: https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/ 3. Open the extension window by either pressing the shortcut Ctrl+. or clicking the 1Password icon in the Firefox UI 4. Enter in the password in the input and press enter. Expected: The vault unlocks or displays a "this is a wrong password" Actual: The UI appears to "refresh" and nothing occurs. WORKAROUND/VALIDATION = Like the original bug, switching the keyboard input method to XIM from iBus resolves the issue suggesting to me that the symptoms I am experiencing are caused by the root issue previously filed, fixed, and deployed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1814551/+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 1814551] Re: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA)
** Changed in: ibus (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) -- 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/1814551 Title: Ubuntu 18.10's ibus package breaks password fields in Firefox Beta (65, 66 via PPA) Status in ibus package in Ubuntu: Confirmed Bug description: Essentially https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1765304 but reproducible in Cosmic even with the patched gnome-shell installed via APT. SYSTEM INFO = * Ubuntu 18.10 Cosmic with latest updates * proc/version_signature: Ubuntu 4.18.0-14.15-generic 4.18.20 * uname: Linux justin-ubuntu 4.18.0-14-generic #15-Ubuntu SMP Mon Jan 14 09:01:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux * gnome-shell 3.30.1-2ubuntu1.18.10.2 * ibus 1.5.19-1ubuntu1 * Both Firefox 65 and 66 (66.0~b4+build1-0ubuntu0.18.04.1 per official PPA) STEPS TO REPRODUCE = 1. Ensure keyboard input method system is 1. Download Firefox Beta channel via their official PPA: https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next 2. Download and install the 1Password X firefox extentsion: https://addons.mozilla.org/en-US/firefox/addon/1password-x-password-manager/ 3. Open the extension window by either pressing the shortcut Ctrl+. or clicking the 1Password icon in the Firefox UI 4. Enter in the password in the input and press enter. Expected: The vault unlocks or displays a "this is a wrong password" Actual: The UI appears to "refresh" and nothing occurs. WORKAROUND/VALIDATION = Like the original bug, switching the keyboard input method to XIM from iBus resolves the issue suggesting to me that the symptoms I am experiencing are caused by the root issue previously filed, fixed, and deployed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1814551/+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 1817065] [NEW] apt/trusty: Unset proxy variables in tests
Public bug reported: [Impact] apt autopkgtest on armhf fails in trusty, as it applies the no_proxy setting to the apt.conf defined proxy, which fails a test that requires using the proxy. Cherry pick a fix to unset all proxy related variables that we've been using in apt since 2015. [Test case] Make sure we don't fail with W: Failed to fetch http://localhost:8080/dists/unstable/main/source/Sources 400 Bad Request [IP: ::1 8080] in test-bug-717891-abolute-uris-for-proxies on armhf [Regression potential] testsuite-only change, so regressions are restricted to more failing autopkgtests. ** Affects: apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: apt (Ubuntu Trusty) Importance: Undecided Status: In Progress ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Trusty) Status: New => In Progress ** Changed in: apt (Ubuntu) Status: New => Fix Released -- 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/1817065 Title: apt/trusty: Unset proxy variables in tests Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: In Progress Bug description: [Impact] apt autopkgtest on armhf fails in trusty, as it applies the no_proxy setting to the apt.conf defined proxy, which fails a test that requires using the proxy. Cherry pick a fix to unset all proxy related variables that we've been using in apt since 2015. [Test case] Make sure we don't fail with W: Failed to fetch http://localhost:8080/dists/unstable/main/source/Sources 400 Bad Request [IP: ::1 8080] in test-bug-717891-abolute-uris-for-proxies on armhf [Regression potential] testsuite-only change, so regressions are restricted to more failing autopkgtests. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1817065/+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 1817062] Re: computer reported that thete is a systemproblem
non -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817062 Title: computer reported that thete is a systemproblem Status in xorg package in Ubuntu: New Bug description: Systemproblem, how to solve that? Thanks in advance, J.Minekus ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 21 14:24:13 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2000] InstallationDate: Installed on 2019-02-02 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1d6da071-0c5e-4565-abc3-a06444c93cd7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-201:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1817062/+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 1817062] [NEW] computer reported that thete is a systemproblem
Public bug reported: Systemproblem, how to solve that? Thanks in advance, J.Minekus ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 21 14:24:13 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2000] InstallationDate: Installed on 2019-02-02 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1d6da071-0c5e-4565-abc3-a06444c93cd7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-201:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1817062 Title: computer reported that thete is a systemproblem Status in xorg package in Ubuntu: New Bug description: Systemproblem, how to solve that? Thanks in advance, J.Minekus ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Feb 21 14:24:13 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2000] InstallationDate: Installed on 2019-02-02 (19 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, no user) LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=1d6da071-0c5e-4565-abc3-a06444c93cd7 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: BLH6710H.86A.0160.2012.1204.1156 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH67CF dmi.board.vendor: Intel Corporation dmi.board.version: AAG10215-201 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrBLH6710H.86A.0160.2012.1204.1156:bd12/04/2012:svn:pn:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-201:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted groovy into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/groovy/2.4.16-1ubuntu1~18.04.1 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: groovy (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in groovy source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted gradle-debian-helper into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /gradle-debian-helper/2.0.2~18.04.1 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: gradle-debian-helper (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in gradle-debian-helper source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05)
[Touch-packages] [Bug 1814133] Please test proposed package
Hello Matthias, or anyone else affected, Accepted gradle into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gradle/4.4.1-3~18.04.1 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: jtreg (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2
[Touch-packages] [Bug 1814133] Please test proposed package
Hello Matthias, or anyone else affected, Accepted surefire into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/surefire/2.22.0-1~18.04.1 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1
[Touch-packages] [Bug 1814133] Please test proposed package
Hello Matthias, or anyone else affected, Accepted maven-compiler-plugin into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /maven-compiler-plugin/3.8.0-1ubuntu1~18.04.1 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: surefire (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05)
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted clojure1.8 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/clojure1.8/1.8.0-7ubuntu1~18.04.1 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: clojure1.8 (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: gradle (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: *
[Touch-packages] [Bug 1814133] Please test proposed package
Hello Matthias, or anyone else affected, Accepted jtreg into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/jtreg/4.2-b13-1ubuntu0.1~18.04.1 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: maven-compiler-plugin (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in clojure1.8 source package in Bionic: Fix Committed Status in dd-plist source package in Bionic: Fix Committed Status in gradle source package in Bionic: Fix Committed Status in jtreg source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-compiler-plugin source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in surefire source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) *
[Touch-packages] [Bug 1783499] Re: systemd: Failed to send signal
This get stuck in max 5 hours. We'll try to install a non systemd Ubuntu, like v14 to test it. ** Attachment added: "centos7.PNG" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783499/+attachment/5240612/+files/centos7.PNG -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted dd-plist into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dd- plist/1.20-1~18.04.1 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: dd-plist (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in dd-plist source package in Bionic: Fix Committed Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago
[Touch-packages] [Bug 1814133] Please test proposed package
Hello Matthias, or anyone else affected, Accepted libcommons-lang3-java into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /libcommons-lang3-java/3.8-1~18.04.2 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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg
[Touch-packages] [Bug 1814133] Please test proposed package
Hello Matthias, or anyone else affected, Accepted plexus-languages into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/plexus- languages/0.9.10-1~18.04.1 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: libcommons-lang3-java (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) *
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted testng into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/testng/6.9.12-2ubuntu1 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: testng (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: plexus-languages (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in libcommons-lang3-java source package in Bionic: Fix Committed Status in maven-debian-helper source package in Bionic: Fix Committed Status in plexus-languages source package in Bionic: Fix Committed Status in testng source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8
[Touch-packages] [Bug 1817052] [NEW] bug with ls command, doesn't list only a single directory.
Public bug reported: If is the only one which starts with an specified letter, won't show it with grep. Example: if there is only a directory starting with 'w', ls -l | grep ^[w] won't show it. With ls -l w* happens the same problem. I think you should check. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 12:37:04 2019 ExecutablePath: /bin/bash InstallationDate: Installed on 2019-01-13 (38 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANG=es_ES.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bash (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 bash in Ubuntu. https://bugs.launchpad.net/bugs/1817052 Title: bug with ls command, doesn't list only a single directory. Status in bash package in Ubuntu: New Bug description: If is the only one which starts with an specified letter, won't show it with grep. Example: if there is only a directory starting with 'w', ls -l | grep ^[w] won't show it. With ls -l w* happens the same problem. I think you should check. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash 4.4.18-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 12:37:04 2019 ExecutablePath: /bin/bash InstallationDate: Installed on 2019-01-13 (38 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: LANG=es_ES.UTF-8 SHELL=/bin/bash TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1817052/+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 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest
Ok. so in xenial, on top of upstream release we cherrypick a few lscpu "fixes" for various arches, including powerpc from, what at the time was development. Clearly we didn't cherrypick enough of things, hence the lscpu regression. By 2.31 as used in bionic, things are all fine again. So there must be patches in upstream util-linux between 2.27 and 2.31 which we do not have, but need to fix this. ** Changed in: util-linux (Ubuntu) Assignee: Canonical Foundations Team (canonical-foundations) => Manoj Iyer (manjo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1764628 Title: incorrect hypervisor and virtualization type reported in compat mode guest Status in The Ubuntu-power-systems project: Triaged Status in util-linux package in Ubuntu: New Bug description: ---uname output--- Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 2018 ppc64le ppc64le ppc64le GNU/Linux Machine Type = boston-LC ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 guest running in P8compat mode on P9 boston-LC: root@guest:/tmp# lscpu Architecture: ppc64le Byte Order:Little Endian CPU(s):2 On-line CPU(s) list: 0,1 Thread(s) per core:2 Core(s) per socket:1 Socket(s): 1 NUMA node(s): 1 Model: 2.2 (pvr 004e 1202) Model name:POWER8 (architected), altivec supported >> Hypervisor vendor: horizontal >> Virtualization type: full L1d cache: 32K L1i cache: 32K NUMA node0 CPU(s): 0,1 Stack trace output: no Oops output: no We test what is coming along with distro. If you are not able to see issue with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can we get this included in 16.04.x train ? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
Hello Matthias, or anyone else affected, Accepted maven-debian-helper into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /maven-debian-helper/2.3.2~18.04.1 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: maven-debian-helper (Ubuntu Bionic) Status: New => 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 gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Status in maven-debian-helper source package in Bionic: Fix Committed Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) *
[Touch-packages] [Bug 1817048] [NEW] apt/trusty: Stack overflow in apt-ftparchive; on arm64, breaking about a third of the tests
Public bug reported: [Impact] autopkgtest suite on arm64 is basically useless, as about a third of the tests do not work, because they rely on apt-ftparchive generating an archive [Test case] Substantially less tests should fail, there should be no segfaults. [Regression potential] I am cherry-picking a fix that changes statically length arrays (that are too small) to vector. A possible regression could be fields missing I guess, it should definitely be easily noticeable. Low risk. ** Affects: apt (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: apt (Ubuntu Trusty) Importance: Undecided Status: Triaged ** Also affects: apt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Trusty) Status: New => Triaged ** Changed in: apt (Ubuntu) Status: New => Fix Released -- 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/1817048 Title: apt/trusty: Stack overflow in apt-ftparchive; on arm64, breaking about a third of the tests Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Bug description: [Impact] autopkgtest suite on arm64 is basically useless, as about a third of the tests do not work, because they rely on apt-ftparchive generating an archive [Test case] Substantially less tests should fail, there should be no segfaults. [Regression potential] I am cherry-picking a fix that changes statically length arrays (that are too small) to vector. A possible regression could be fields missing I guess, it should definitely be easily noticeable. Low risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1817048/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic- security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- - security ONLY. + security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - jtreg and testng are new versions required as build dependencies of openjdk-11 - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Packages from stage 3 and later are not yet reviewed and should not be uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. This will be done/decided by the security team. A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. [2018-02-21] Packages in stage 1 and stage 2 have been verified by
[Touch-packages] [Bug 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic- security. + NOTE TO SRU MEMBERS: The packages are to be released into bionic- + security ONLY. + A few packages might also need to be updated in Cosmic, but as an exception that will be done after the Bionic transition is worked out. - [2018-02-21] Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. Notes: - - jtreg and testng are new versions required as build dependencies of openjdk-11 - - all other packages are backports that must be build/bootstrapped with openjdk-10 + - jtreg and testng are new versions required as build dependencies of openjdk-11 + - all other packages are backports that must be build/bootstrapped with openjdk-10 PPAs: https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 - Please copy them in the following order/grouping. Group 1: * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 2: * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) Please upload libcommons-lang3-java from stage 2 (ignore the version in stage 1). Group 3: * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 4: * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) Group 5: * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) - - Packages from stage 3 and later are not yet reviewed and should not be uploaded. + Packages from stage 3 and later are not yet reviewed and should not be + uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. A few packages might also need to be updated in Cosmic,
[Touch-packages] [Bug 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
** Changed in: cryptsetup (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: ubuntu-z-systems Status: In Progress => Fix Released -- 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/1776626 Title: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part Status in Ubuntu on IBM z Systems: Fix Released Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in cryptsetup source package in Bionic: Won't Fix Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * cryptsetup in bionic supports creating luks volumes with a non- standard sector-size option, and thus this option also needs to be used when activating the LUKS volumes. Add sector-size= option support to /etc/crypttab. [Test Case] * Create a plain LUKS volume with sector-size 4096 * Specify sector-size=4096 option in /etc/crypttab * reload systemd, start systemd-cryptsetup@.service for that volume * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup) [Regression Potential] * This is an optional argument, not used by default. Currently custom sector-size crypttab does not work correctly, and thus cannot regress. [Other Info] * Original bug report Support fast clear key dm-crypt with 4k support Extend /etc/crypttab to enable 4k sector support in plain mode The proposed enhancements are posted on github, see https://github.com/systemd/systemd/issues/8881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+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 1814133] Re: update to openjdk 11 in 18.04 LTS
** Description changed: Transition OpenJDK 11 to 18.04 LTS. - This transition is a security update of openjdk-lts and requires new dependencies as well as package backports and SRU fixes to go into the security pocket for a couple reasons: - - openjdk-lts 11 needs newer build dependencies - - various packages have runtime failures when run with openjdk-11 + This transition is a security update of openjdk-lts from openjdk-10 to + openjdk-11. This introduces runtime and FTBFS issues which requires + backports of multiple packages into the security pocket as well. - A few packages *must* be updated/patched before openjdk-11 itself is uploaded: - TBD + The packages are being build on PPAs under the + https://launchpad.net/~openjdk-11-transition team. The PPAs depend + solely on the security pocket and are separated in stages. + + The agreed process among foundations and the security team is that + packages in the PPAs will be binary copied into bionic-proposed, checked + for migration issues, and - no issues pending - copied into bionic- + security. + + A few packages might also need to be updated in Cosmic, but as an + exception that will be done after the Bionic transition is worked out. + + + [2018-02-21] + Packages in stage 1 and stage 2 have been verified by the security team and are ready to be copied into bionic-proposed. + + Notes: + - jtreg and testng are new versions required as build dependencies of openjdk-11 + - all other packages are backports that must be build/bootstrapped with openjdk-10 + + PPAs: + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage1 + https://launchpad.net/~openjdk-11-transition/+archive/ubuntu/stage2 + + + Please copy them in the following order/grouping. + + Group 1: + * maven-debian-helper 2.3.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 2: + * dd-plist 1.20-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * libcommons-lang3-java 3.8-1~18.04.2 Tiago Stürmer Daitx (2019-02-05) + * plexus-languages 0.9.10-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * testng 6.9.12-2ubuntu1 Tiago Stürmer Daitx (2019-02-05) + + Please upload libcommons-lang3-java from stage 2 (ignore the version in + stage 1). + + Group 3: + * clojure1.8 1.8.0-7ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-06) + * gradle 4.4.1-3~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * jtreg 4.2-b13-1ubuntu0.1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * maven-compiler-plugin 3.8.0-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + * surefire 2.22.0-1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 4: + * gradle-debian-helper 2.0.2~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + Group 5: + * groovy 2.4.16-1ubuntu1~18.04.1 Tiago Stürmer Daitx (2019-02-05) + + + Packages from stage 3 and later are not yet reviewed and should not be uploaded. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1814133 Title: update to openjdk 11 in 18.04 LTS Status in ca-certificates-java package in Ubuntu: New Status in clojure1.8 package in Ubuntu: New Status in dd-plist package in Ubuntu: New Status in gettext package in Ubuntu: New Status in gradle package in Ubuntu: New Status in gradle-debian-helper package in Ubuntu: New Status in groovy package in Ubuntu: New Status in jaxws-api package in Ubuntu: New Status in jtreg package in Ubuntu: New Status in junit4 package in Ubuntu: New Status in jws-api package in Ubuntu: New Status in jython package in Ubuntu: New Status in libcommons-lang3-java package in Ubuntu: New Status in maven-compiler-plugin package in Ubuntu: New Status in maven-debian-helper package in Ubuntu: New Status in metro-policy package in Ubuntu: New Status in openjdk-11-jre-dcevm package in Ubuntu: New Status in openjdk-lts package in Ubuntu: New Status in openjfx package in Ubuntu: New Status in plexus-languages package in Ubuntu: New Status in saaj package in Ubuntu: New Status in saaj-ri package in Ubuntu: New Status in scala package in Ubuntu: New Status in surefire package in Ubuntu: New Status in testng package in Ubuntu: New Bug description: Transition OpenJDK 11 to 18.04 LTS. This transition is a security update of openjdk-lts from openjdk-10 to openjdk-11. This introduces runtime and FTBFS issues which requires backports of multiple packages into the security pocket as well. The packages are being build on PPAs under the https://launchpad.net/~openjdk-11-transition team. The PPAs depend solely on the security pocket and are separated in stages. The agreed process among foundations and the security team is that packages in the PPAs will be binary copied into bionic-proposed, checked for migration issues, and - no issues pending - copied into bionic-security. NOTE TO SRU MEMBERS: The packages are to be released into bionic- security ONLY. A few packages
[Touch-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)
--
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/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
Status in cups-filters package in Ubuntu:
New
Bug description:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.
The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.
Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.
```
Error: Ignoring spurious ET operator. Output may be inco
```
For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.
```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```
On the Epson printer _WorkForce WF-2660_, no error page is printed,
but on the first page everything after _Email_ _is missing_ too.
Trying to use different pdftops renderers did not make any difference.
For example,
```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```
gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.
Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured
the data sent to the printer with the commands below.
$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf
I get the attached Postscript file, which indeed contains the error
messages.
```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```
Please find that file attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lpstat:
device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
device for DCP375CW: socket://141.14.220.198
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp.
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Papersize: a4
PpdFiles:
Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
DCP375CW: Brother DCP-375CW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M
vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (113 days ago)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0839Y6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
[Touch-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
This should be reassigned to the package cups-filters, which I actually
had selected in the Web page dialog.
--
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/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
Status in cups package in Ubuntu:
New
Bug description:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.
The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.
Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.
```
Error: Ignoring spurious ET operator. Output may be inco
```
For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.
```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```
On the Epson printer _WorkForce WF-2660_, no error page is printed,
but on the first page everything after _Email_ _is missing_ too.
Trying to use different pdftops renderers did not make any difference.
For example,
```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```
gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.
Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured
the data sent to the printer with the commands below.
$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf
I get the attached Postscript file, which indeed contains the error
messages.
```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```
Please find that file attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lpstat:
device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
device for DCP375CW: socket://141.14.220.198
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp.
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Papersize: a4
PpdFiles:
Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
DCP375CW: Brother DCP-375CW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M
vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (113 days ago)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0839Y6
dmi.board.vendor: Dell
[Touch-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
I forgot to mention, that the document prints fine with Microsoft
Windows.
--
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/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
Status in cups package in Ubuntu:
New
Bug description:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.
The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.
Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.
```
Error: Ignoring spurious ET operator. Output may be inco
```
For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.
```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```
On the Epson printer _WorkForce WF-2660_, no error page is printed,
but on the first page everything after _Email_ _is missing_ too.
Trying to use different pdftops renderers did not make any difference.
For example,
```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```
gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.
Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured
the data sent to the printer with the commands below.
$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf
I get the attached Postscript file, which indeed contains the error
messages.
```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```
Please find that file attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lpstat:
device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
device for DCP375CW: socket://141.14.220.198
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp.
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Papersize: a4
PpdFiles:
Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
DCP375CW: Brother DCP-375CW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M
vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (113 days ago)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0839Y6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
[Touch-packages] [Bug 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
I can also reproduce this with the generic Postscript printer [1].
```
[…]
%%EndSetup
%%Page: 1 1
%%BeginPageSetup
%%EndPageSetup
%%BeginDocument: nondsc
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
%!PS-Adobe-3.0
%%BoundingBox: 0 0 596 842
%%HiResBoundingBox: 0 0 596.00 842.00
%%Creator: GPL Ghostscript 926 (ps2write)
%%LanguageLevel: 2
%%CreationDate: D:2019022055+01'00'
%%Pages: 2
%%EndComments
[…]
```
So maybe it is a Ghostscript issue.
[1]: https://www.openprinting.org/printer/Generic/Generic-
PostScript_Printer
--
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/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
Status in cups package in Ubuntu:
New
Bug description:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.
The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.
Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.
```
Error: Ignoring spurious ET operator. Output may be inco
```
For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.
```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```
On the Epson printer _WorkForce WF-2660_, no error page is printed,
but on the first page everything after _Email_ _is missing_ too.
Trying to use different pdftops renderers did not make any difference.
For example,
```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```
gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.
Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured
the data sent to the printer with the commands below.
$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf
I get the attached Postscript file, which indeed contains the error
messages.
```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```
Please find that file attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic
[Touch-packages] [Bug 1817041] Re: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1817041 Title: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: During an automated update process ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Feb 21 10:50:04 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (868 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-04 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1817041/+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 1817041] [NEW] package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: During an automated update process ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Feb 21 10:50:04 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (868 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-04 (170 days ago) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1817041 Title: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: During an automated update process ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.7 ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167 Uname: Linux 4.4.0-142-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Feb 21 10:50:04 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-10-06 (868 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: Missing privilege separation directory: /var/run/sshd SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-09-04 (170 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1817041/+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 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
The Wiki page *DebuggingPrintingProblems* [1] says:
> If the file is PostScript or PDF, subscribe "cliddell" (Chris Liddell,
> Ghostscript upstream
> developer) to the bug report and also try to display the file on the screen
> with "evince" and "gs".
But, I am unable to find him in the Launchpad database, so cannot
subscribe him.
[1]: https://wiki.ubuntu.com/DebuggingPrintingProblems
--
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/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
Status in cups package in Ubuntu:
New
Bug description:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.
The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.
Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.
```
Error: Ignoring spurious ET operator. Output may be inco
```
For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.
```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```
On the Epson printer _WorkForce WF-2660_, no error page is printed,
but on the first page everything after _Email_ _is missing_ too.
Trying to use different pdftops renderers did not make any difference.
For example,
```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```
gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.
Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured
the data sent to the printer with the commands below.
$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf
I get the attached Postscript file, which indeed contains the error
messages.
```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```
Please find that file attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lpstat:
device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
device for DCP375CW: socket://141.14.220.198
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp.
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Papersize: a4
PpdFiles:
Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
DCP375CW: Brother DCP-375CW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic
[Touch-packages] [Bug 1775018] Re: Fix for openssl 1.0.2 backport
This will be uploaded into the unapproved queue for SRU review on 27th of February. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1775018 Title: Fix for openssl 1.0.2 backport Status in Ubuntu on IBM z Systems: Triaged Status in openssl package in Ubuntu: New Bug description: This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and upstream code are not affected ). Original LP ticket : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+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 1817033] Re: Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
Here is the problematic PDF file.
** Attachment added: "Problematic PDF file"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1817033/+attachment/5240571/+files/antrag_exmatrikulation.pdf
--
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/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
Status in cups package in Ubuntu:
New
Bug description:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.
The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.
Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.
```
Error: Ignoring spurious ET operator. Output may be inco
```
For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.
```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```
On the Epson printer _WorkForce WF-2660_, no error page is printed,
but on the first page everything after _Email_ _is missing_ too.
Trying to use different pdftops renderers did not make any difference.
For example,
```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```
gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.
Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured
the data sent to the printer with the commands below.
$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf
I get the attached Postscript file, which indeed contains the error
messages.
```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```
Please find that file attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lpstat:
device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
device for DCP375CW: socket://141.14.220.198
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp.
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Papersize: a4
PpdFiles:
Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
DCP375CW: Brother DCP-375CW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M
vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (113 days ago)
dmi.bios.date: 09/27/2018
[Touch-packages] [Bug 1817033] [NEW] Unable to correctly print PDF file: Error: Ignoring spurious ET operator.
Public bug reported:
Upstream bug report https://github.com/OpenPrinting/cups-
filters/issues/93.
The university document
[antrag_exmatrikulation.pdf](https://github.com/OpenPrinting/cups-
filters/files/2881078/antrag_exmatrikulation.pdf) causes problems on
different printers.
Printing on the Canon iR-ADV C2225i using the Canon PCL, an error page
is first printed, and on the first page after _Email_ everything is
missing. The second page is fine.
```
Error: Ignoring spurious ET operator. Output may be inco
```
For that printer a special filter `sicgsfilter` has to be used, and is
distributed by Canon. This also happens with their CQue 4.0-1 release
from September 2018.
```
*FoomaticRIPCommandLine: "gs -q -dBATCH %F -dPARANOIDSAFER -dNOPAUSE %B%A%C
-dPDFFitPage -sOutputFile=- - %D%E | sicgsfilter -MPCL -NP %G%H%I -u
-V -n "
```
On the Epson printer _WorkForce WF-2660_, no error page is printed, but
on the first page everything after _Email_ _is missing_ too.
Trying to use different pdftops renderers did not make any difference.
For example,
```
lpr -o pdftops-renderer=pdftops -P chipprinterpcl antrag_exmatrikulation.pdf
```
gave the same result, the same with `pdftocairo`, `acroread`, `mupdf`.
Following `/usr/share/doc/cups-filters/README.gz` and
https://wiki.ubuntu.com/DebuggingPrintingProblems, I verified that the
exact same PDF is put into the CUPS spool directory, and I captured the
data sent to the printer with the commands below.
$ lpadmin -p chipprinterpclfile -E -v file:/tmp/printout -P
~/chipprinterpcl.ppd
$ lpr -P chipprinterpclfile -o psdebug ~/antrag_exmatrikulation.pdf
I get the attached Postscript file, which indeed contains the error
messages.
```
ESC%-12345X@PJL CQue4.0-1 x86_64
@PJL COMMENT CANPJL SET USERNAME="pmenzel@localhost"
@PJL COMMENT CANPJL SET DOCNAME="antrag_exmatrikulation.pdf!pmenz"
@PJL SET RENDERMODE=COLOR
@PJL COMMENT CANPJL SET FORCEMONOCHROME=FALSE
@PJL COMMENT CANPJL SET SORTERMODE=GENERICON
@PJL COMMENT CANPJL SET STAPLE=GENERICOFF
@PJL COMMENT CANPJL SET BOOKLET=GENERICOFF
@PJL SET DENSITY=0
@PJL ENTER LANGUAGE=PCL
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
Error: Ignoring spurious ET operator.
Output may be incorrect.
Error: Executing Do inside a text block, attempting to recover
Output may be incorrect.
Error: illegal nested BT operator detected.
Output may be incorrect.
[…]
```
Please find that file attached.
ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: cups 2.2.8-5ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-15.16-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
Date: Thu Feb 21 10:23:08 2019
InstallationDate: Installed on 2017-03-20 (702 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lpstat:
device for Canon-iR-ADV-C2225: lpd://winprima.molgen.mpg.de/test
device for DCP375CW: socket://141.14.220.198
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 04f3:2234 Elan Microelectronics Corp.
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
Papersize: a4
PpdFiles:
Canon-iR-ADV-C2225: Canon iR-ADV C2225 PCL
DCP375CW: Brother DCP-375CW CUPS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-15-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash initcall_debug log_buf_len=16M
vt.handoff=1
SourcePackage: cups
UpgradeStatus: Upgraded to cosmic on 2018-10-30 (113 days ago)
dmi.bios.date: 09/27/2018
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0839Y6
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.10.0:bd09/27/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.product.sku: 075B
dmi.sys.vendor: Dell Inc.
** Affects: cups (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug cosmic
** Attachment added: "Data sent to the Canon printer"
https://bugs.launchpad.net/bugs/1817033/+attachment/5240554/+files/printout
--
You received this bug notification because
[Touch-packages] [Bug 1817034] [NEW] Text console login does not allow login - it behaves as if "entered" is continuously keyed after "login". N
Public bug reported: The following happens with any user, WITHOUT typing any password !! Only one "ENTER" keyed. Login: myuser Password: Login incorrect Login: Login incorrect ... To happens to all Alt+Ctrl+Fx , while no problem appears in graphical terminals or Gnome. That appeared only after the last updates, with kernel 4.15.0-45 . If I boot back to 4.15.0-43 the issue does not appear. The /var/log/auth.log shows: login[6180]: pam_unix(login:auth): conversation failed login[6180]: pam_unix(login:auth): auth could not identify password for [myuser] login[6180]: FAILED LOGIN (1) on '/dev/tty3' FOR 'myuser', Authentication failure login[6180]: pam_securetty(login:auth): cannot determine username login[6180]: FAILED LOGIN (2) on '/dev/tty3' FOR 'UNKNOWN', Error in service module login[6180]: pam_securetty(login:auth): cannot determine username login[6180]: FAILED LOGIN (3) on '/dev/tty3' FOR 'UNKNOWN', Error in service module login[6180]: pam_securetty(login:auth): cannot determine username login[6180]: FAILED LOGIN (4) on '/dev/tty3' FOR 'UNKNOWN', Error in service module The /var/log/audit.log shows: type=USER_LOGIN msg=audit(1550742677.578:221): pid=7230 uid=0 auid=4294967295 ses=4294967295 msg='op=login acct="UNKNOWN" exe="/bin/login" hostname=P50 addr=? terminal=/dev/tty3 res=failed' type=USER_AUTH msg=audit(1550742680.902:222): pid=7230 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication acct="?" exe="/bin/login" hostname=P50 addr=? terminal=/dev/tty3 res=failed' type=USER_LOGIN msg=audit(1550742680.902:223): pid=7230 uid=0 auid=4294967295 ses=4294967295 msg='op=login acct="UNKNOWN" exe="/bin/login" hostname=P50 addr=? terminal=/dev/tty3 res=failed' type=SERVICE_STOP msg=audit(1550742730.226:224): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' type=SERVICE_START msg=audit(1550742730.226:225): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' type=SERVICE_STOP msg=audit(1550742730.226:226): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' type=SERVICE_START msg=audit(1550742730.230:227): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=getty@tty3 comm="systemd" exe="/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: login 1:4.5-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 21 10:17:48 2019 InstallationDate: Installed on 2018-11-05 (107 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: shadow UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: shadow (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 shadow in Ubuntu. https://bugs.launchpad.net/bugs/1817034 Title: Text console login does not allow login - it behaves as if "entered" is continuously keyed after "login". N Status in shadow package in Ubuntu: New Bug description: The following happens with any user, WITHOUT typing any password !! Only one "ENTER" keyed. Login: myuser Password: Login incorrect Login: Login incorrect ... To happens to all Alt+Ctrl+Fx , while no problem appears in graphical terminals or Gnome. That appeared only after the last updates, with kernel 4.15.0-45 . If I boot back to 4.15.0-43 the issue does not appear. The /var/log/auth.log shows: login[6180]: pam_unix(login:auth): conversation failed login[6180]: pam_unix(login:auth): auth could not identify password for [myuser] login[6180]: FAILED LOGIN (1) on '/dev/tty3' FOR 'myuser', Authentication failure login[6180]: pam_securetty(login:auth): cannot determine username login[6180]: FAILED LOGIN (2) on '/dev/tty3' FOR 'UNKNOWN', Error in service module login[6180]: pam_securetty(login:auth): cannot determine username login[6180]: FAILED LOGIN (3) on '/dev/tty3' FOR 'UNKNOWN', Error in service module login[6180]: pam_securetty(login:auth): cannot determine username login[6180]: FAILED LOGIN (4) on '/dev/tty3' FOR 'UNKNOWN', Error in service module The /var/log/audit.log shows: type=USER_LOGIN msg=audit(1550742677.578:221): pid=7230 uid=0 auid=4294967295 ses=4294967295 msg='op=login acct="UNKNOWN" exe="/bin/login" hostname=P50 addr=? terminal=/dev/tty3 res=failed' type=USER_AUTH msg=audit(1550742680.902:222): pid=7230 uid=0 auid=4294967295 ses=4294967295
[Touch-packages] [Bug 1816767] Re: purge does not remove whoopsie-id
** Branch linked: lp:whoopsie -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1816767 Title: purge does not remove whoopsie-id Status in whoopsie package in Ubuntu: In Progress Bug description: whoopsie 0.2.63 $ sudo apt remove --purge whoopsie Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: whoopsie* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 109 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 220908 files and directories currently installed.) Removing whoopsie (0.2.63) ... (Reading database ... 220902 files and directories currently installed.) Purging configuration files for whoopsie (0.2.63) ... dpkg: warning: while removing whoopsie, directory '/var/lib/whoopsie' not empty so not removed Processing triggers for systemd (240-5ubuntu4) ... $ ls /var/lib/whoopsie/ whoopsie-id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1816767/+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 1816704] Re: help
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1816704 Title: help Status in xorg package in Ubuntu: New Bug description: help ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompositorRunning: None Date: Wed Feb 20 01:05:13 2019 DistUpgraded: 2018-11-03 00:06:35,514 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:221e] NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K1100M] [17aa:221e] InstallationDate: Installed on 2017-06-08 (621 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 20EGS2Y100 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=634836b3-fbce-46ef-a204-02830b05eb59 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-11-03 (109 days ago) dmi.bios.date: 09/01/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET75WW (2.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EGS2Y100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET75WW(2.23):bd09/01/2015:svnLENOVO:pn20EGS2Y100:pvrThinkPadW541:rvnLENOVO:rn20EGS2Y100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W541 dmi.product.name: 20EGS2Y100 dmi.product.version: ThinkPad W541 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Fri Nov 2 22:48:29 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5571 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1816704/+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 1816767] Re: purge does not remove whoopsie-id
** Changed in: whoopsie (Ubuntu) Status: New => In Progress ** Changed in: whoopsie (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1816767 Title: purge does not remove whoopsie-id Status in whoopsie package in Ubuntu: In Progress Bug description: whoopsie 0.2.63 $ sudo apt remove --purge whoopsie Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: whoopsie* 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. After this operation, 109 kB disk space will be freed. Do you want to continue? [Y/n] (Reading database ... 220908 files and directories currently installed.) Removing whoopsie (0.2.63) ... (Reading database ... 220902 files and directories currently installed.) Purging configuration files for whoopsie (0.2.63) ... dpkg: warning: while removing whoopsie, directory '/var/lib/whoopsie' not empty so not removed Processing triggers for systemd (240-5ubuntu4) ... $ ls /var/lib/whoopsie/ whoopsie-id To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1816767/+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 1816630] Re: systemd-timedated fails to start with /tmp as a symlink
Thank for the debugging, I'm updating the title to reflect better the issue and it's up to the systemd team then to see how important they believe the issue to be ** Summary changed: - Gnome Control Center does not start due to GDBus.Error:org.freedesktop.DBus.Error.TimedOut + systemd-timedated fails to start with /tmp as a symlink -- 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/1816630 Title: systemd-timedated fails to start with /tmp as a symlink Status in systemd package in Ubuntu: New Bug description: When I try to start the `gnome-control-center`, then it hangs after a few seconds. I recently changed the timezone due to travelling. I can login normally. Another source of the error could be, that I symlinked the `/tmp` and `/opt` directory to another partition. ``` $ gnome-control-center (gnome-control-center:29386): datetime-cc-panel-WARNING **: 10:13:23.508: could not get proxy for DateTimeMechanism: Fehler beim Aufruf von StartServiceByName für org.freedesktop.timedate1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ** ERROR:../shell/cc-panel.c:202:cc_panel_size_allocate: assertion failed: (child) Abgebrochen (Speicherabzug geschrieben) ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path /org/freedesktop/timedate1 Fehler: Zeitüberschreitung wurde erreicht ``` ``` $ gdbus introspect --system --dest org.freedesktop.timedate1 --object-path / Fehler: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl Failed to query server: Failed to activate service 'org.freedesktop.timedate1': timed out (service_start_timeout=25000ms) ``` ``` $ timedatectl --version systemd 237 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid ``` systemd-timedated service is not starting: ``` $ sudo systemctl status systemd-timedated.service ● systemd-timedated.service - Time & Date Service Loaded: loaded (/lib/systemd/system/systemd-timedated.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2019-02-19 10:47:33 CST; 2min 53s ago Docs: man:systemd-timedated.service(8) man:localtime(5) https://www.freedesktop.org/wiki/Software/systemd/timedated Process: 3618 ExecStart=/lib/systemd/systemd-timedated (code=exited, status=226/NAMESPACE) Main PID: 3618 (code=exited, status=226/NAMESPACE) Feb 19 10:47:33 home systemd[1]: Starting Time & Date Service... Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed to set up mount namespacing: No such file or directory Feb 19 10:47:33 home systemd[3618]: systemd-timedated.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE Feb 19 10:47:33 home systemd[1]: systemd-timedated.service: Failed with result 'exit-code'. Feb 19 10:47:33 home systemd[1]: Failed to start Time & Date Service. ``` ``` $ journalctl -xe Feb 19 18:03:59 home ntpd[21785]: 176.221.42.125 local addr 192.168.0.102 -> Feb 19 18:04:05 home sudo[17719]: sebastian : TTY=pts/0 ; PWD=/home/sebastian ; USER=root ; COMMAND=/bin/systemctl start systemd-timedated Feb 19 18:04:05 home sudo[17719]: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 19 18:04:05 home systemd[1]: Starting Time & Date Service... -- Subject: Unit systemd-timedated.service has begun start-up -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- Unit systemd-timedated.service has begun starting up. Feb 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed to set up mount namespacing: No such file or directory Feb 19 18:04:05 home systemd[17724]: systemd-timedated.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-timedated: No such file or directory -- Subject: Process /lib/systemd/systemd-timedated could not be executed -- Defined-By: systemd -- Support: http://www.ubuntu.com/support -- -- The process /lib/systemd/systemd-timedated could not be executed and failed. -- -- The error number returned by this process is 2. Feb 19 18:04:05 home systemd[1]: systemd-timedated.service: Main process exited, code=exited, status=226/NAMESPACE Feb 19 18:04:05 home systemd[1]: systemd-timedated.service: Failed with result 'exit-code'. Feb 19 18:04:05 home systemd[1]: Failed to start Time &
[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot
I have the same problem in Debian 9 Stretch, net.netfilter.nf_conntrack_max and net.nf_conntrack_max does not apply after reboot. The pure solution is load module nf_conntrack before sysctl. You can do this with the command: echo "nf_conntrack" >> /etc/modules -- 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/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
https://github.com/lxc/lxd/issues/4656 ** Bug watch added: LXD bug tracker #4656 https://github.com/lxc/lxd/issues/4656 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' Status in linux package in Ubuntu: Triaged Status in lxc package in Ubuntu: Confirmed Status in linux source package in Cosmic: Triaged Status in lxc source package in Cosmic: Confirmed Bug description: I'm not sure exactly what got me into this state, but I have several lxc containers that cannot be deleted. $ lxc info api_status: stable api_version: "1.0" auth: trusted public: false auth_methods: - tls environment: addresses: [] architectures: - x86_64 - i686 certificate: | -BEGIN CERTIFICATE- -END CERTIFICATE- certificate_fingerprint: 3af6f8b8233c5d9e898590a9486ded5c0bec045488384f30ea921afce51f75cb driver: lxc driver_version: 3.0.1 kernel: Linux kernel_architecture: x86_64 kernel_version: 4.15.0-23-generic server: lxd server_pid: 15123 server_version: "3.2" storage: zfs storage_version: 0.7.5-1ubuntu15 server_clustered: false server_name: milhouse $ lxc delete --force b1 Error: Failed to destroy ZFS filesystem: cannot destroy 'default/containers/b1': dataset is busy Talking in #lxc-dev, stgraber and sforeshee provided diagnosis: | short version is that something unshared a mount namespace causing | them to get a copy of the mount table at the time that dataset was | mounted, which then prevents zfs from being able to destroy it) The work around provided was | you can unstick this particular issue by doing: | grep default/containers/b1 /proc/*/mountinfo | then for any of the hits, do: | nsenter -t PID -m -- umount /var/snap/lxd/common/lxd/storage-pools/default/containers/b1 | then try the delete again ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.15.0-23-generic 4.15.0-23.25 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: smoser31412 F pulseaudio /dev/snd/controlC2: smoser31412 F pulseaudio /dev/snd/controlC0: smoser31412 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jun 28 10:42:45 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (1071 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) MachineType: b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' b'\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff' ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.174 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/09/2015 dmi.bios.vendor: Intel Corporation dmi.bios.version: RYBDWi35.86A.0246.2015.0309.1355 dmi.board.asset.tag: � dmi.board.name: NUC5i5RYB dmi.board.vendor: Intel Corporation dmi.board.version: H40999-503 dmi.chassis.asset.tag: � dmi.chassis.type: 3 dmi.chassis.vendor: � dmi.chassis.version: � dmi.modalias: dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0246.2015.0309.1355:bd03/09/2015:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-503:cvn:ct3:cvr: dmi.product.family: � dmi.product.name: � dmi.product.version: � dmi.sys.vendor: � To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779156/+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 1783499] Re: systemd: Failed to send signal
Or a kernel regression, Centos 7 uses an older kernel. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1783499 Title: systemd: Failed to send signal Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: systemd: Failed to send signal. [3.137257] systemd[1]: Failed to send job remove signal for 109: Connection reset by peer [3.138119] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.138185] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.138512] systemd[1]: run-rpc_pipefs.mount: Failed to send unit change signal for run-rpc_pipefs.mount: Transport endpoint is not connected [3.142719] systemd[1]: Failed to send job remove signal for 134: Transport endpoint is not connected [3.142958] systemd[1]: auth-rpcgss-module.service: Failed to send unit change signal for auth-rpcgss-module.service: Transport endpoint is not connected [3.165359] systemd[1]: Failed to send job remove signal for 133: Transport endpoint is not connected [3.165505] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.165541] systemd[1]: dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Failed to send unit change signal for dev-mapper-ubuntu\x2d\x2dvg\x2droot.device: Transport endpoint is not connected [3.166854] systemd[1]: Failed to send job remove signal for 66: Transport endpoint is not connected [3.167072] systemd[1]: proc-fs-nfsd.mount: Failed to send unit change signal for proc-fs-nfsd.mount: Transport endpoint is not connected [3.167130] systemd[1]: systemd-modules-load.service: Failed to send unit change signal for systemd-modules-load.service: Transport endpoint is not connected [2.929018] systemd[1]: Failed to send job remove signal for 53: Transport endpoint is not connected [2.929220] systemd[1]: systemd-random-seed.service: Failed to send unit change signal for systemd-random-seed.service: Transport endpoint is not connected [3.024320] systemd[1]: sys-devices-platform-serial8250-tty-ttyS12.device: Failed to send unit change signal for sys-devices-platform-serial8250-tty-ttyS12.device: Transport endpoint is not connected [3.024421] systemd[1]: dev-ttyS12.device: Failed to send unit change signal for dev-ttyS12.device: Transport endpoint is not connected [3.547019] systemd[1]: proc-sys-fs-binfmt_misc.automount: Failed to send unit change signal for proc-sys-fs-binfmt_misc.automount: Connection reset by peer [3.547144] systemd[1]: Failed to send job change signal for 207: Transport endpoint is not connected How to reproduce: 1. enable debug level journal LogLevel=debug in /etc/systemd/system.conf 2. reboot the system 3. journalctl | grep "Failed to send" sliu@vmlxhi-094:~$ lsb_release -rd Description: Ubuntu 16.04.4 LTS Release: 16.04 sliu@vmlxhi-094:~$ systemctl --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN sliu@vmlxhi-094:~$ dbus-daemon --version D-Bus Message Bus Daemon 1.10.6 Copyright (C) 2002, 2003 Red Hat, Inc., CodeFactory AB, and others This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1783499/+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
