[Touch-packages] [Bug 1789502] Re: Update to 0.6.50
I don't have it currently in a branch but I'm working on doing that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1077267] Re: Setting language localization doesn't set system-wide
[Expired for ubuntu-meta (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1077267 Title: Setting language localization doesn't set system-wide Status in ubuntu-meta package in Ubuntu: Expired Bug description: I am running Precise 64 bit... when I install and set localization to US English it doesn't set language system wide.. by that I mean Thunderbird uses Australian English dictionary, Firefox initially uses British English and other applications, Drivel for example will continue to use other English language dictionary (not sure which one but it likes favourite not favorite). I know that I can go from application to application changing them all but it really is wasteful to have to do so... I don't understand why at install time your language selection cannot do this. Also, in regards to Drivel, it will continue to use other English unless I delete all other language packs from /usr/share/hunspell/ and these other languages seem to come back every time Firefox upgrades. This is very frustrating. I refuse to believe that it is not possible to have the install process language settings respected system wide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1077267/+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 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Hi, Besides issues with buttons I experience transparency in dialog menus (where should not be any transparency). The updated xorg does not help (I've double check this). Downgrade mesa fixes this. I use nouveau with VGA compatible controller: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] (rev a2) ** Attachment added: "Screenshot from 2018-09-05 10-11-24.png" https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+attachment/5184681/+files/Screenshot%20from%202018-09-05%2010-11-24.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+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 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Ditto. I created a bootable DVD with 18.04 and booted it on the machine: it does NOT have this issue. But not sure if this shows anything, as 18.04 is quite different. Different desktop, gimp and emacs versions. But maybe. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+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 1790518] Re: PCI/internal sound card not detected [Inspiron 5566]
*** This bug is a duplicate of bug 1790416 *** https://bugs.launchpad.net/bugs/1790416 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1790416, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Summary changed: - PCI/internal sound card not detected + PCI/internal sound card not detected [Inspiron 5566] ** This bug has been marked a duplicate of bug 1790416 [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246) -- 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/1790518 Title: PCI/internal sound card not detected [Inspiron 5566] Status in alsa-driver package in Ubuntu: New Bug description: sem som. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Uname: Linux 4.4.0-134-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Mon Sep 3 14:16:04 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-18 (473 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 0P1MTV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/03/2017:svnDellInc.:pnInspiron5566:pvr:rvnDellInc.:rn0P1MTV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Inspiron 5566 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1790518/+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 1772578] Re: [Nvidia HDA] audio crackling
** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** 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/1772578 Title: [Nvidia HDA] audio crackling Status in gnome-shell package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Hello, on Ubuntu this bug regularly appearing: audio suddenly crackling for all softwares. If I restart pulseaudio, it changes nothing. But if I restart gnome-shell ("alt+F2", type "r"), the audio no more crackling. I had this bug for Ubuntu 17.10 and perhaps 17.04 too. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: romain 3648 F...m pulseaudio /dev/snd/controlC0: romain 3648 F pulseaudio CurrentDesktop: GNOME Date: Tue May 22 07:56:34 2018 InstallationDate: Installed on 2012-07-07 (2144 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45 (MS-7752) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7752 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772578/+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 1764779] Re: Nautilus crashed open Windows-partition
** Description changed: [ Description ] if I open a new partition from the Hard-drive (Windows in this case) Nautilus crash, report him self and after reopen it, the partition is normal available as nothing would be + + https://errors.ubuntu.com/problem/f49deb51a98d691e3e040d7f7334ad08d1e0e54c + https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938 + https://errors.ubuntu.com/problem/00db9958203affb0a98a2842bb2bd91547e6bd5a [ Test case ] * Open nautilus and select an external hd that is not mounted from the sidebar * Nautilus sould not crash (in case showing an error message) [ Regression potential ] Partitions that have been actually mounted, are not shown or an error is prompted. - Issue from the log: Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount point cleanup: Process reported exit code 5: Failed to start clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit media-username-12F6CC77F6CC5D1B.mount not found. Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: assertion 'G_IS_MOUNT (mount)' failed Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ** Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: (location != NULL) - ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 16:45:30 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-move-to-trash-shortcut-changed-dialog' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'" InstallationDate: Installed on 2018-03-16 (32 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180315) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=de_DE.UTF-8Signal: 6SourcePackage: nautilus StacktraceTop: g_assertion_message () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 Title: nautilus crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo usr_lib_nautilus: ** Description changed: [ Description ] if I open a new partition from the Hard-drive (Windows in this case) Nautilus crash, report him self and after reopen it, the partition is normal available as nothing would be https://errors.ubuntu.com/problem/f49deb51a98d691e3e040d7f7334ad08d1e0e54c https://errors.ubuntu.com/problem/868bb572668dceedfb0e3acd9b17197ca0208938 https://errors.ubuntu.com/problem/00db9958203affb0a98a2842bb2bd91547e6bd5a + https://errors.ubuntu.com/problem/818d3ad2d9fe9f9f64f32fcb5f10da4126d3827d [ Test case ] * Open nautilus and select an external hd that is not mounted from the sidebar * Nautilus sould not crash (in case showing an error message) [ Regression potential ] Partitions that have been actually mounted, are not shown or an error is prompted. - Issue from the log: Apr 17 16:45:29 hostname udisksd[1014]: Failed to setup systemd-based mount point cleanup: Process reported exit code 5: Failed to start clean-mount-point@media-username-12F6CC77F6CC5D1B.service: Unit media-username-12F6CC77F6CC5D1B.mount not found. Apr 17 16:45:29 hostname nautilus[11486]: g_mount_get_default_location: assertion 'G_IS_MOUNT (mount)' failed Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ** Apr 17 16:45:29 hostname org.gnome.Nautilus[2775]: ERROR:../src/nautilus-file.c:721:nautilus_file_get_internal: assertion failed: (location != NULL) - ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.3-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 17 16:45:30 2018 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.preferences' b'show-move-to-trash-shortcut-changed-dialog' b'false' b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' b'org.gnome.nautilus.window-state' b'geometry' b"'927x1011+926+27'" InstallationDate: Installed on
[Touch-packages] [Bug 1790553] Re: Update to 2.58.0
This bug was fixed in the package glib2.0 - 2.58.0-2 Sponsored for Iain Lane (laney) --- glib2.0 (2.58.0-2) unstable; urgency=medium * Cherry-pick upstream patch to fix test_timeval_to_iso8601_overflow on 32-bit, fixing FTBFS there. -- Iain Lane Tue, 04 Sep 2018 15:29:53 +0100 glib2.0 (2.58.0-1) unstable; urgency=medium [ Jeremy Bicha ] * New upstream release * Drop patches applied in new release: - date-test-Use-g_test_skip-not-g_test_incomplete.patch - g_binding_unbind-make-it-more-introspection-friendly-allo.patch: * Release to unstable [ Simon McVittie ] * d/p/debian/closures-test-Run-fewer-iterations-on-ARM64.patch: Update metadata * libglib2.0-dev-bin: Add Suggests for the packages containing xmllint and gdk-pixbuf-pixdata, which are sometimes invoked by glib-compile-resources (Closes: #834998) * Invoke dh_python3 twice so that we correctly rewrite the shebang line for /usr/bin scripts (Closes: #876009) * Don't install very old changelogs and NEWS files * Install README.md instead of stub README -- Jeremy Bicha Sun, 02 Sep 2018 08:57:46 -0400 ** Changed in: glib2.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1790553 Title: Update to 2.58.0 Status in glib2.0 package in Ubuntu: Fix Released Bug description: Just copy from debian please. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1790553/+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 1790747] Re: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1790747 Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post- installation script subprocess returned error exit status 127 Status in console-setup package in Ubuntu: New Bug description: When I upgrade, this happens. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 08:32:45 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-06-22 (74 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1790747/+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 1790747] [NEW] package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned erro
Public bug reported: When I upgrade, this happens. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 08:32:45 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-06-22 (74 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1790747 Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post- installation script subprocess returned error exit status 127 Status in console-setup package in Ubuntu: New Bug description: When I upgrade, this happens. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: keyboard-configuration 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Wed Sep 5 08:32:45 2018 ErrorMessage: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2018-06-22 (74 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package keyboard-configuration 1.178ubuntu2.7 failed to install/upgrade: installed keyboard-configuration package post-installation script subprocess returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1790747/+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 1134036] Re: Failure when using ssh with a locale that is not configured on the server
I'm not incredibly happy about this approach (doing it in pam_env.so would be best I think) but it does the job for now. I verified this in a minimal bionic image with and without base-files from proposed and the behaviour was as expected. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1134036 Title: Failure when using ssh with a locale that is not configured on the server Status in base-files package in Ubuntu: Fix Released Status in maas package in Ubuntu: Invalid Status in base-files source package in Bionic: Fix Committed Status in maas source package in Bionic: New Bug description: [impact] The setup: 1) The user has LC_ALL set to a locale on their machine (or some other LC_* variable but it's usually LC_ALL). 2) This locale does not exist on an Ubuntu server. 3) The user sshes into the server. ssh (at least with the settings that are default on Debian and Ubuntu and Fedora) send the value of LC_ALL to the remote server, where the default settings on Ubuntu allow this to be set in the environment of the process it launches. Because we are now in a situation where LC_ALL is set to a value that is not valid for the system, various undesirable things happen, including ugly messages from cloud-init and perl complaining every time a perl process starts and the bug that the original description below describes. [test case] Configure the setup as described above. Ssh into the server and run "perl < /dev/null" and check for warnings. [regression potential] This adds a step to the startup of every login shell, which obviously is not entirely trivial. However, the new executable being invoked is very simple and even if it fails, the startup of the shell should not be inhibited. [original description] If LC_ALL is not set (which seems to be the default on a few server installations I've done now), mid way through installing, you get this backtrace and then the installation just hangs. You can ctrl-c out of it but the package is left half configured. Traceback (most recent call last): File "/usr/bin/django-admin", line 5, in management.execute_from_command_line() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 443, in execute_from_command_line utility.execute() File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 382, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 196, in run_from_argv self.execute(*args, **options.__dict__) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/south/management/commands/syncdb.py", line 90, in handle_noargs syncdb.Command().execute(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 232, in execute output = self.handle(*args, **options) File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 371, in handle return self.handle_noargs(**options) File "/usr/lib/python2.7/dist-packages/django/core/management/commands/syncdb.py", line 57, in handle_noargs cursor = connection.cursor() File "/usr/lib/python2.7/dist-packages/django/db/backends/__init__.py", line 308, in cursor cursor = util.CursorWrapper(self._cursor(), self) File "/usr/lib/python2.7/dist-packages/django/db/backends/postgresql_psycopg2/base.py", line 177, in _cursor self.connection = Database.connect(**conn_params) File "/usr/lib/python2.7/dist-packages/psycopg2/__init__.py", line 179, in connect connection_factory=connection_factory, async=async) psycopg2.OperationalError: FATAL: password authentication failed for user "maas" FATAL: password authentication failed for user "maas" Related bugs: * bug 969462: [postgres] fails to start after install if invalid locale is set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1134036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
mssql-server is another fallen one... depends on libcurl3, and force me to uninstall KiCAD, libcurl4, libcurl4-openssl-dev, cmake and curl... How can a mess like this one make it to a LTS release... And also #3 answer is just awful, how can you just wash your hands like that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789502] Re: Update to 0.6.50
One more thought: If we would add the fallback values on initialization, can it be done without updating the keyfile? If not there is a complication, since we need to keep the keyfile and ~/.pam_environment in sync. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1789502] Re: Update to 0.6.50
Hi Robert, I see that the user_set_property() function has been dropped. Without having looked closely at the code, setting them on initialization sounds reasonable, if that can be done without confusing accountsservice. The goal is that querying the "Language" or "FormatsLocale" property should return the proper current value even if nothing has (yet) been saved in /var/lib/AccountsService/users/. Initialization - would that be the user_update_from_keyfile() function? Right now I don't have access to a working cosmic install. Possibly it's some hardware incompatibility issue, but whatever the reason is, I'm not able to do any work in a sensible way at the moment. So I'm hoping you can fix also 0010-set-language.patch .. Once I have fixed my cosmic, I'll be happy to test to make sure that it works as expected. Btw, is your work in progress available in a repository somewhere? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1789502 Title: Update to 0.6.50 Status in accountsservice package in Ubuntu: In Progress Bug description: The upstream changes are non trivial and there is work to update the patches but that would be useful to do To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1789502/+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 1558511] Re: systemd-journald crashed with SIGABRT
Got this on a new X1 Carbon with a fresh Bionic install after it failed to wake from sleep the first time (black screen) but then after closing the laptop and waiting a few minutes, it recovered and I had this error. -- 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/1558511 Title: systemd-journald crashed with SIGABRT Status in systemd package in Ubuntu: Confirmed Bug description: Crashed shortly after logging in to my laptop. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: systemd 229-2ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-11-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Thu Mar 10 21:12:39 2016 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2015-02-13 (398 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 1420 ProcCmdline: /lib/systemd/systemd-journald ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic root=UUID=71fcab68-425b-4dae-a9ec-13245f989fe1 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: systemd StacktraceTop: ?? () ?? () ?? () ?? () ?? () SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. Title: systemd-journald crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0DT492 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd12/19/2008:svnDellInc.:pnInspiron1420:pvr:rvnDellInc.:rn0DT492:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1420 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1558511/+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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
It should be possible to specify sector-size option in crypttab now, in ubuntu. And it should be supported by both initramfs-tools and systemd, depending on which one does the mount. Please test this, and let me know if everything is alright. It did work for me... but I used non-4k hardware. -- 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 Committed Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: 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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
systemd (239-7ubuntu7) cosmic; urgency=medium * boot-and-services: skip gdm test, when gdm-x-session fails. Across all architectures, gdm fails to come up reliably since cosmic. (LP: #1790478) systemd (239-7ubuntu6) cosmic; urgency=medium [ Dimitri John Ledkov ] * debian/control: strengthen dependencies. Make systemd-sysv depend on matching version of systemd. Autopkgtests at times upgrade systemd-sysv without upgrading systemd. However, upgrading systemd-sysv alone makes little sense. Make systemd conflict, rather than just break, systemd-shim. As there are upgrade failures cause by systemd-shim presence whilst upgrading to new systemd. * Correct gdm3 exclution on arm64, in boot-and-services test. [ Christian Ehrhardt ] * Improve autopkgtest success rate, by bumping up timeouts. (LP: #1789841) systemd (239-7ubuntu5) cosmic; urgency=medium [ Michael Biebl ] * Clean up dbus-org.freedesktop.timesync1.service Alias on purge (Closes: #904290) [ Martin Pitt ] * timedated: Fix wrong PropertyChanged values and refcounting [ Dimitri John Ledkov ] * autopkgtest: drop gdm3 on arm64 as well. The cloud instances are configured without a graphics card, and thus X fails to start, hence the gdm test fails. * Revert "Workaround broken meson copying symlinked data files, as dangling symlinks." This reverts commit 059bfb5349123fabc8c92324e0473193f01fc87c. * Cherrypick v239-stable patches. * cryptsetup: add support for sector-size= option (LP: #1776626) * Cherrypick upstrem patches to fix ftbfs with new glibc. [ Michael Vogt ] * Re-add support for /etc/writable for core18. (LP: #1778936) -- 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 Committed Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: 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 1790478] Re: gdm3 in cosmic fails to start fully in autopkgtest
This bug was fixed in the package systemd - 239-7ubuntu7 --- systemd (239-7ubuntu7) cosmic; urgency=medium * boot-and-services: skip gdm test, when gdm-x-session fails. Across all architectures, gdm fails to come up reliably since cosmic. (LP: #1790478) -- Dimitri John Ledkov Mon, 03 Sep 2018 16:33:00 +0100 ** Changed in: systemd (Ubuntu) Status: New => 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/1790478 Title: gdm3 in cosmic fails to start fully in autopkgtest Status in gdm3 package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Bug description: In systemd package for a while, there is a boot-and-services test case, which tries to install common/typical things and ensure they continue to operate with new systemd. One of the test cases is gdm3. The test case dependencies are: Tests: boot-and-services Depends: systemd-sysv, systemd, udev, systemd-container, systemd-coredump, libpam-systemd, xserver-xorg-video-dummy, xserver-xorg, gdm3 [!s390x], cron, network-manager, busybox-static, apparmor, pkg-config, python3 The test does following: out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) self.assertIn(b'gdm-x-session gnome-session', out) out = subprocess.check_output(['ps', 'u', '-C', 'Xorg']) self.assertIn(b'Xorg vt1', out) self.active_unit('gdm') However, this now errors out upon the first command, meaning gdm-x-session is not running anymore. On bionic, this test case continues to operate correctly in the autopkgtest cloud. test_gdm3 (__main__.ServicesTest) ... ERROR == ERROR: test_gdm3 (__main__.ServicesTest) -- Traceback (most recent call last): File "/tmp/autopkgtest.RNx2A1/build.2Wy/src/debian/tests/boot-and-services", line 66, in test_gdm3 out = subprocess.check_output(['ps', 'u', '-C', 'gdm-x-session']) File "/usr/lib/python3.6/subprocess.py", line 336, in check_output **kwargs).stdout File "/usr/lib/python3.6/subprocess.py", line 418, in run output=stdout, stderr=stderr) subprocess.CalledProcessError: Command '['ps', 'u', '-C', 'gdm-x-session']' returned non-zero exit status 1. -- Ran 24 tests in 18.974s FAILED (errors=1) From http://autopkgtest.ubuntu.com/packages/systemd/cosmic/i386 Thus it looks like there is a regression or a change of behavior of gdm3 in the cloud in cosmic; since bionic continues to work correctly. I will mark this test as an expected failure for now, and monitor it separately, as currently, this is blocking many migrations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1790478/+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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
This bug was fixed in the package systemd - 239-7ubuntu7 --- systemd (239-7ubuntu7) cosmic; urgency=medium * boot-and-services: skip gdm test, when gdm-x-session fails. Across all architectures, gdm fails to come up reliably since cosmic. (LP: #1790478) -- Dimitri John Ledkov Mon, 03 Sep 2018 16:33:00 +0100 ** Changed in: systemd (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 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 Committed Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: 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 1789841] Re: improve autopkgtest success rate
This bug was fixed in the package systemd - 239-7ubuntu7 --- systemd (239-7ubuntu7) cosmic; urgency=medium * boot-and-services: skip gdm test, when gdm-x-session fails. Across all architectures, gdm fails to come up reliably since cosmic. (LP: #1790478) -- Dimitri John Ledkov Mon, 03 Sep 2018 16:33:00 +0100 ** Changed in: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1789841 Title: improve autopkgtest success rate Status in systemd package in Ubuntu: Fix Released Bug description: Hi, being one of the many that hit retry on systemd autopkgtest rather often I was checking the logs and found more than 50% of the cases dying on timeouts which seemed to be working but slow. I wanted to suggest bumping the timeouts to hopefully improve the success rate of the tests. It is not too much of a change, and If this proves to be successful we can suggest so to include the bumps upstream. attaching a diff for your consideration ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789841/+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 1778936] Re: please re-add Support-system-image-read-only-etc.patch
This bug was fixed in the package systemd - 239-7ubuntu7 --- systemd (239-7ubuntu7) cosmic; urgency=medium * boot-and-services: skip gdm test, when gdm-x-session fails. Across all architectures, gdm fails to come up reliably since cosmic. (LP: #1790478) -- Dimitri John Ledkov Mon, 03 Sep 2018 16:33:00 +0100 ** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Bionic: New Status in systemd source package in Cosmic: Fix Released Bug description: The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1788048] Re: systemd journald failed unmounting var
Guys, I think it's a critical problem! All because I created an exclusive disk for / var -- 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/1788048 Title: systemd journald failed unmounting var Status in systemd package in Ubuntu: New Bug description: When the system is shut down or restarted the systemd-journal does not disassemble the disks correctly. On this thread https://unix.stackexchange.com/questions/378678/why- do-i-get-the-error-failed-unmounting-var-during-shutdown I checked what editing /etc/systemd/journald.conf to change the Storage = line to Storage = volatile the problem is solved, but some of the logs on the shutdown are lost. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.3 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Mon Aug 20 18:15:07 2018 ExecutablePath: /lib/systemd/systemd-journald InstallationDate: Installed on 2018-08-20 (0 days ago) InstallationMedia: Ubuntu-Server 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-32-generic root=UUID=65cb761b-4881-4031-9113-e6bb6a1437b4 ro SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH mtime.conffile..etc.systemd.journald.conf: 2018-08-20T18:00:58.586165 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788048/+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 1719579] Re: [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save
Christian, Seeing following errors on our end as well - fyi Create/delete of our XXL Guest vm. Sep 1 08:54:54 my-system libvirtd[4126]: 2018-09-01 15:54:54.426+: 4126: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error Sep 1 08:54:55 my-system libvirtd[4126]: 2018-09-01 15:54:55.009+: 4126: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error Sep 1 08:54:55 my-system libvirtd[4126]: 2018-09-01 15:54:55.177+: 4126: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error Sep 1 08:54:55 my-system libvirtd[4126]: 2018-09-01 15:54:55.325+: 4126: error : virNetSocketReadWire:1811 : End of file while reading data: Input/output error Sep 1 08:54:56 my-system libvirtd[4126]: 2018-09-01 15:54:56.936+: 4126: error : qemuMonitorIORead:610 : Unable to read from monitor: Connection reset by peer Sep 1 08:55:09 my-system libvirtd[4126]: 2018-09-01 15:55:09.503+: 4202: error : virProcessKillPainfully:401 : Failed to terminate process 48500 with SIGKILL: Device or resource busy Sep 1 08:55:16 my-system libvirtd[4126]: 2018-09-01 15:55:16.959+: 4201: error : virSecurityDACSetOwnershipInternal:619 : unable to set user and group to '0:0' on '/var/lib/libvirt/images/dgx2vm-labSat0847-16g0-15_dgx-kvm-image-4.0.0~180823-22df0e.1.qcow2': No such file or directory Sep 1 08:55:16 my-system libvirtd[4126]: 2018-09-01 15:55:16.959+: 4201: error : virSecurityDACSetOwnershipInternal:619 : unable to set user and group to '0:0' on '/raid/dgx-kvm/vol-dgx2vm-labSat0847-16g0-15': No such file or directory Sep 1 09:22:11 my-system libvirtd[4126]: 2018-09-01 16:22:11.098+: 4203: error : virProcessKillPainfully:401 : Failed to terminate process 64980 with SIGKILL: Device or resource busy Sep 1 09:22:11 my-system libvirtd[4126]: 2018-09-01 16:22:11.099+: 4126: error : qemuMonitorIO:719 : internal error: End of file from qemu monitor Sep 1 09:22:26 my-system libvirtd[4126]: 2018-09-01 16:22:26.110+: 51440: error : virProcessKillPainfully:401 : Failed to terminate process 64980 with SIGKILL: Device or resource busy thanks, Anish -- 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/1719579 Title: [Ubuntu 18.04] [libvirt] virsh restore fails from state file saved in /var/tmp folder using virsh save Status in The Ubuntu-power-systems project: Fix Released Status in apparmor package in Ubuntu: Invalid Status in libvirt package in Ubuntu: Fix Released Bug description: == Comment: #1 - SEETEENA THOUFEEK - 2017-01-17 00:09:16 == Bala, Please mail me the machine information. == Comment: #3 - SEETEENA THOUFEEK - 2017-01-17 02:14:06 == 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACRestoreFileLabelInternal:388 : Restoring DAC user and group on '/var/tmp/bala' 2017-01-16 12:09:37.707+: 7024: info : virSecurityDACSetOwnershipInternal:290 : Setting DAC user and group on '/var/tmp/bala' to '0:0' 2017-01-16 12:09:37.707+: 7024: warning : qemuDomainSaveImageStartVM:6750 : failed to restore save state label on /var/tmp/bala 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: debug : qemuDomainObjEndAsyncJob:1848 : Stopping async job: start (vm=0x3fff4ca535c0 name=virt-tests-vm1-bala) 2017-01-16 12:09:37.707+: 7024: info : virObjectRef:296 : OBJECT_REF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca62b00 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff4ca535c0 2017-01-16 12:09:37.707+: 7024: debug : virThreadJobClear:121 : Thread 7024 (virNetServerHandleJob) finished job remoteDispatchDomainRestore with ret=-1 2017-01-16 12:09:37.707+: 7024: info : virObjectUnref:259 : OBJECT_UNREF: obj=0x3fff7c002c10 2017-01-16 12:09:37.707+: 7024: debug : virNetServerProgramSendError:153 : prog=536903814 ver=1 proc=54 type=1 serial=4 msg=0x100133d2590 rerr=0x3fffa59be3c0 2017-01-16 12:09:37.707+: 7024: debug : virNetMessageEncodePayload:376 : Encode length as 172 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientSendMessageLocked:1399 : msg=0x100133d2590 proc=54 len=172 offset=0 2017-01-16 12:09:37.707+: 7024: info : virNetServerClientSendMessageLocked:1407 : RPC_SERVER_CLIENT_MSG_TX_QUEUE: client=0x100133d23c0 len=172 prog=536903814 vers=1 proc=54 type=1 status=1 serial=4 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:157 : tls=(nil) hs=-1, rx=0x100133d0670 tx=0x100133d2590 2017-01-16 12:09:37.707+: 7024: debug : virNetServerClientCalculateHandleMode:192 : mode=3 2017-01-16 12:09:37.707+: 7024: info :
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Well, I created a bootable DVD with 18.04 and booted it on the machine: it does NOT have this issue. ** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
Can someone from the ALSA team give any update on this please? It is confirmed multiple times that the 0x17 pin seems to be the one for the LFE subwoofer, but turning it on in HDAjackRetask does not work. Perhaps you can give us more information? This bug has been here since 2016.. -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
** Also affects: packagekit (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Bionic: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789422] Re: iso-codes 4.0 doesn't include XML files
The XML files were restored in 4.1-1 ** Changed in: iso-codes (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iso-codes in Ubuntu. https://bugs.launchpad.net/bugs/1789422 Title: iso-codes 4.0 doesn't include XML files Status in iso-codes package in Ubuntu: Fix Released Status in iso-codes package in Debian: New Bug description: I'm filing this bug in case iso-codes 4 gets synced to Ubuntu. We shouldn't allow it in Ubuntu until at least this issue is fixed: https://gitlab.gnome.org/GNOME/gnome-software/issues/454 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1789422/+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 1790720] [NEW] package language-pack-gnome-en-base 1:16.04+20160627 failed to install/upgrade: unable to open '/usr/share/locale-langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': O
Public bug reported: I was doing the update from 16 to 18 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-gnome-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 4 16:12:34 2018 DpkgTerminalLog: Preparing to unpack .../00-language-pack-gnome-en-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-gnome-en-base (1:18.04+20180712) over (1:16.04+20160627) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-yrd5XX/00-language-pack-gnome-en-base_1%3a18.04+20180712_all.deb (--unpack): unable to open '/usr/share/locale-langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/locale-langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-01-01 (246 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: language-pack-gnome-en-base Title: package language-pack-gnome-en-base 1:16.04+20160627 failed to install/upgrade: unable to open '/usr/share/locale-langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to bionic on 2018-09-04 (0 days ago) ** Affects: language-pack-gnome-en-base (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to language-pack-gnome-en- base in Ubuntu. https://bugs.launchpad.net/bugs/1790720 Title: package language-pack-gnome-en-base 1:16.04+20160627 failed to install/upgrade: unable to open '/usr/share/locale- langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': Operation not permitted Status in language-pack-gnome-en-base package in Ubuntu: New Bug description: I was doing the update from 16 to 18 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: language-pack-gnome-en-base 1:16.04+20160627 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-41-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 4 16:12:34 2018 DpkgTerminalLog: Preparing to unpack .../00-language-pack-gnome-en-base_1%3a18.04+20180712_all.deb ... Unpacking language-pack-gnome-en-base (1:18.04+20180712) over (1:16.04+20160627) ... [1mdpkg:[0m error processing archive /tmp/apt-dpkg-install-yrd5XX/00-language-pack-gnome-en-base_1%3a18.04+20180712_all.deb (--unpack): unable to open '/usr/share/locale-langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/share/locale-langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-01-01 (246 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: language-pack-gnome-en-base Title: package language-pack-gnome-en-base 1:16.04+20160627 failed to install/upgrade: unable to open '/usr/share/locale-langpack/en_GB/LC_MESSAGES/zenity.mo.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to bionic on 2018-09-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en-base/+bug/1790720/+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 1788486] Re: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security.
All I can say: If you treat USN reports as binaries then you are definitely missing security updates. -- 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/1788486 Title: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security. Status in apt package in Ubuntu: Won't Fix Status in landscape-client package in Ubuntu: Won't Fix Status in apt source package in Xenial: Won't Fix Status in landscape-client source package in Xenial: Won't Fix Status in apt source package in Bionic: Won't Fix Status in landscape-client source package in Bionic: Won't Fix Bug description: [Impact] We notice that situation while investigating a security update using Landscape, but it also applies to 'apt' outside the Landscape context. 'apt' should be smarter to detect/install packages with strict dependencies such as systemd[1] when a version is specified for upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1). It should automatically install the dependencies (if any) from that same version as well instead of failing trying to install the highest version available (if any) while installing the specified version for the one mentionned : $ apt-get install systemd=229-4ubuntu-21.1 "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to be installed" = To face that problem : - Package with lower version should be found in -security ( Ex: systemd/229-4ubuntu21.1 ) - Package with higher version should be found in -updates ( Ex: systemd/229-4ubuntu21.4 ) - Package should have strict dependencies ( Ex: libsystemd0 (= ${binary:Version}) ) - The upgrade should only specify version for the package, without it's dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without libsystemd0 depends) Using systemd is a good reproducer, I'm sure finding other package with the same situation is easy. It has been easily reproduced with systemd on Xenial and Bionic so far. [1] debian/control Depends: ${shlibs:Depends}, ${misc:Depends}, libsystemd0 (= ${binary:Version}), ... [Workaround] If package + dependencies are specified, the upgrade work just fine : Ex: $ apt-get install systemd=229-4ubuntu-21.1 libsystemd0=229-4ubuntu-21.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1788486/+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 1788486] Re: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security.
I mean, consider the apt one. It lists apt, but the fix is in the binary libapt-pkg5.0. I assume you can specify --only-upgrade or what it's called too to prevent removals (but also new installs). In any case, there is no solution here. -- 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/1788486 Title: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security. Status in apt package in Ubuntu: Won't Fix Status in landscape-client package in Ubuntu: Won't Fix Status in apt source package in Xenial: Won't Fix Status in landscape-client source package in Xenial: Won't Fix Status in apt source package in Bionic: Won't Fix Status in landscape-client source package in Bionic: Won't Fix Bug description: [Impact] We notice that situation while investigating a security update using Landscape, but it also applies to 'apt' outside the Landscape context. 'apt' should be smarter to detect/install packages with strict dependencies such as systemd[1] when a version is specified for upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1). It should automatically install the dependencies (if any) from that same version as well instead of failing trying to install the highest version available (if any) while installing the specified version for the one mentionned : $ apt-get install systemd=229-4ubuntu-21.1 "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to be installed" = To face that problem : - Package with lower version should be found in -security ( Ex: systemd/229-4ubuntu21.1 ) - Package with higher version should be found in -updates ( Ex: systemd/229-4ubuntu21.4 ) - Package should have strict dependencies ( Ex: libsystemd0 (= ${binary:Version}) ) - The upgrade should only specify version for the package, without it's dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without libsystemd0 depends) Using systemd is a good reproducer, I'm sure finding other package with the same situation is easy. It has been easily reproduced with systemd on Xenial and Bionic so far. [1] debian/control Depends: ${shlibs:Depends}, ${misc:Depends}, libsystemd0 (= ${binary:Version}), ... [Workaround] If package + dependencies are specified, the upgrade work just fine : Ex: $ apt-get install systemd=229-4ubuntu-21.1 libsystemd0=229-4ubuntu-21.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1788486/+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 1788486] Re: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security.
There is a similar situation where apt-get wants to remove packages when strict dependencies (equal version number) cannot be met. For example dovecot-core/dovecot-pop3d/dovecot-imapd. After installing Ubuntu 16.04.3 LTS from the ISO, install the 3 packages from the release pocket: $ sudo apt install dovecot-imapd=1:2.2.22-1ubuntu2 \ dovecot-core=1:2.2.22-1ubuntu2 \ dovecot-pop3d=1:2.2.22-1ubuntu2 USN-3587-1 [1] wants dovecot-core to be upgraded to 1:2.2.22-1ubuntu2.7 Trying to upgrade dovecot-core to 1:2.2.22-1ubuntu2.7 will want to remove dovecot-imapd and dovecot-pop3d: $ sudo apt-get install --dry-run dovecot-core=1:2.2.22-1ubuntu2.7 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: ntp dovecot-gssapi dovecot-sieve dovecot-pgsql dovecot-mysql dovecot-sqlite dovecot-ldap dovecot-imapd dovecot-pop3d dovecot-lmtpd dovecot-managesieved dovecot-solr The following packages will be REMOVED: dovecot-imapd dovecot-pop3d The following packages will be upgraded: dovecot-core 1 upgraded, 0 newly installed, 2 to remove and 171 not upgraded. Remv dovecot-imapd [1:2.2.22-1ubuntu2] Remv dovecot-pop3d [1:2.2.22-1ubuntu2] Inst dovecot-core [1:2.2.22-1ubuntu2] (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) Conf dovecot-core (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) Why? The only package that is *required* to be upgraded (because the USN specifies it, and because we currently treat USN package specs as binary packages), is dovecot-core. Apt's (simple) dependency solver figures it can upgrade that, but in doing so it breaks dovecot-imapd and dovecot-pop3d which need removing as a consequence. The workaround is to specify all 3 packages: $ sudo apt-get install --dry-run dovecot-core=1:2.2.22-1ubuntu2.7 \ dovecot-imapd=1:2.2.22-1ubuntu2.7 \ dovecot-pop3d=1:2.2.22-1ubuntu2.7 Reading package lists... Done Building dependency tree Reading state information... Done Suggested packages: ntp dovecot-gssapi dovecot-sieve dovecot-pgsql dovecot-mysql dovecot-sqlite dovecot-ldap dovecot-lmtpd dovecot-managesieved dovecot-solr The following packages will be upgraded: dovecot-core dovecot-imapd dovecot-pop3d 3 upgraded, 0 newly installed, 0 to remove and 171 not upgraded. Inst dovecot-pop3d [1:2.2.22-1ubuntu2] (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) [] Inst dovecot-imapd [1:2.2.22-1ubuntu2] (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) [] Inst dovecot-core [1:2.2.22-1ubuntu2] (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) Conf dovecot-core (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) Conf dovecot-pop3d (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) Conf dovecot-imapd (1:2.2.22-1ubuntu2.7 Ubuntu:16.04/xenial-security [amd64]) [1] https://usn.ubuntu.com/3587-1/ -- 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/1788486 Title: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security. Status in apt package in Ubuntu: Won't Fix Status in landscape-client package in Ubuntu: Won't Fix Status in apt source package in Xenial: Won't Fix Status in landscape-client source package in Xenial: Won't Fix Status in apt source package in Bionic: Won't Fix Status in landscape-client source package in Bionic: Won't Fix Bug description: [Impact] We notice that situation while investigating a security update using Landscape, but it also applies to 'apt' outside the Landscape context. 'apt' should be smarter to detect/install packages with strict dependencies such as systemd[1] when a version is specified for upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1). It should automatically install the dependencies (if any) from that same version as well instead of failing trying to install the highest version available (if any) while installing the specified version for the one mentionned : $ apt-get install systemd=229-4ubuntu-21.1 "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to be installed" = To face that problem : - Package with lower version should be found in -security ( Ex: systemd/229-4ubuntu21.1 ) - Package with higher version should be found in -updates ( Ex: systemd/229-4ubuntu21.4 ) - Package should have strict dependencies ( Ex: libsystemd0 (= ${binary:Version}) ) - The upgrade should only specify version for the package, without it's dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without libsystemd0 depends) Using systemd is a good reproducer, I'm sure finding other package with the same situation is easy. It has been easily reproduced with systemd on Xenial and Bionic so far. [1]
[Touch-packages] [Bug 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
As noted in duplicate bug report 1790693 this prevents upgrades from Cosmic to happening so the fix should be SRU'ed to Ubuntu 18.04. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
Hmm odd maybe something's in the journal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Incomplete Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1552792] Re: gnome software leaves dependencies installed
This bug was fixed in the package gnome-software - 3.29.92-0ubuntu2 --- gnome-software (3.29.92-0ubuntu2) cosmic; urgency=medium * debian/rules: - Build with PackageKit autoremove support (LP: #1552792) * debian/control: - Depend on the version of PackageKit which correctly does autoremove -- Robert Ancell Tue, 04 Sep 2018 11:04:47 +1200 ** Changed in: gnome-software (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1552792] Re: gnome software leaves dependencies installed
This bug was fixed in the package packagekit - 1.1.10-1ubuntu4 --- packagekit (1.1.10-1ubuntu4) cosmic; urgency=medium * debian/patches/aptcc-Fix-invalid-version-dereference-in-AptInf-prov.patch: Fix dereferencing of invalid version in providesCodec() (LP: #1790671) -- Julian Andres Klode Tue, 04 Sep 2018 18:18:05 +0200 ** Changed in: packagekit (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in gnome-software source package in Bionic: Triaged Status in packagekit source package in Bionic: Triaged Status in gnome-software source package in Cosmic: Fix Released Status in packagekit source package in Cosmic: Fix Released Bug description: [Impact] Installing an application them removing it leaves dependencies behind. [Test Case] 1. Ensure that GNOME Sudoku is not installed: $ sudo apt remove gnome-sudoku libqqwing2v5 2. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act 3. Open GNOME Software. 4. Search for and install GNOME Sudoku (make sure to install the .deb, not the snap). 5. Uninstall GNOME Sudoku. 6. Check if you have any packages that need autoremoval: $ sudo apt autoremove --no-act Expected result: The packages in step 6 are the same as in step 2 (which might be none). Observed result: The packages in step 6 includes libqqwing2v5, which is a dependency of gnome-sudoku and not useful without the game installed. [Regression Potential] This requires a fix to PackageKit which used to autoremove all packages (too aggressive), not just the ones related to the current transaction. A bug in the code could cause more packages to be removed than is suitable. GNOME Software previously didn't use this autoremove functionality, so by enabling it we could trigger a problem in either the existing code or the new fix. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part
This bug was fixed in the package cryptsetup - 2:2.0.4-2ubuntu2 --- cryptsetup (2:2.0.4-2ubuntu2) cosmic; urgency=medium * Implement support for --sector-size cryptsetup plain mode option in crypttab. Matching support is also proposed to systemd-cryptsetup as well. LP: #1776626 -- Dimitri John Ledkov Fri, 31 Aug 2018 17:00:07 +0100 ** Changed in: cryptsetup (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 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 Committed Status in cryptsetup package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Committed Bug description: 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 1761567] Re: Characters of selected text are vertically flipped
This bug was fixed in the package poppler - 0.68.0-0ubuntu1 --- poppler (0.68.0-0ubuntu1) cosmic; urgency=medium * New upstream version - TextPage: Add horizontal scaling to font matrix (lp: #1761567) * Updated for the soname change libpoppler73 -> 79 * debian/patches/proper-init.patch: - removed, the issue has been fixed upstream in another way since * debian/patches/01-new-gtk-doc.patch, debian/patches/cairo-good-filter.patch, debian/patches/CVE-2017-18267.patch: - removed, the fixes are in the new version * debian/patches/series: - added a comment about the remaining patches -- Sebastien Bacher Wed, 22 Aug 2018 11:30:47 +0200 ** Changed in: poppler (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-18267 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1761567 Title: Characters of selected text are vertically flipped Status in poppler package in Ubuntu: Fix Released Bug description: In the attached PDF, I expect that selected text remains readable, but here selected characters become vertically flipped. - $ lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 - $ apt-cache policy evince evince: Installed: 3.26.0-1 Candidate: 3.26.0-1 Version table: *** 3.26.0-1 500 500 http://fr.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: evince 3.26.0-1 ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 5 20:58:15 2018 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-02-19 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1761567/+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 1788457] Re: SRU of LXC 3.0.2 (upstream bugfix release)
This bug was fixed in the package lxc - 3.0.2-0ubuntu4 --- lxc (3.0.2-0ubuntu4) cosmic; urgency=medium * Cherry-pick upstream fixes: - 0024-commands-return-1-on-lxc_cmd_get_init_pid-err.patch -- Stéphane Graber Sat, 25 Aug 2018 00:49:17 -0400 ** Changed in: lxc (Ubuntu Cosmic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1788457 Title: SRU of LXC 3.0.2 (upstream bugfix release) Status in lxc package in Ubuntu: Fix Released Status in lxc source package in Xenial: Triaged Status in lxc source package in Bionic: Triaged Status in lxc source package in Cosmic: Fix Released Bug description: LXC upstream released LXC 3.0.2 as a bugfix release with following changelog: - CVE 2018-6556: verify netns fd in lxc-user-nic - fixed a range of bugs found by Coverity - lxc-usernsexec: cleanup and bugfixes - log: add CMD_SYSINFO() - log: add CMD_SYSERROR() - state: s/sleep()/nanosleep()/ - lxclock: improve file locking - lxccontainer: improve file locking - lxccontainer: fix F_OFD_GETLK checks - netlink: add __netlink_{send,recv,transaction} - netns: allocate network namespace id - MAINTAINERS: add Wolfgang Bumiller - pam_cgfs: cleanups - log: add default log priority - tree-wide: pass unsigned long to prctl() - macro: add new macro header - conf: mount devpts without “max” on EINVAL - tree-wide: handle EINTR in read() and write() - tree-wide: replace pipe() with pipe2() - confile: split mount options into flags and data - conf: improve rootfs setup - autotools: default to -Wvla -std=gnu11 - tree-wide: remove VLAs - tree-wide: replace strtok_r() with lxc_iterate_parts() - utils: add lxc_iterate_parts() - apparmor: allow start-container to change to lxc-** - apparmor: update current profiles - apparmor: Allow /usr/lib* paths for mount and pivot_root - conf: the atime flags are locked in userns - conf: handle partially functional device nodes - conf: create /dev directory - autotools: build both a shared and static liblxc - namespace: add api to convert namespaces to standard identifiers - tree-wide: set MSG_NOSIGNAL - tree-wide: use mknod() to create dummy files - cgfsng: respect lxc.cgroup.use - cgroups: remove is_crucial_cgroup_subsystem() - tree-wide: remove unneeded log prefixes - tests: cleanup all tests - terminal: set FD_CLOEXEC on pty file descriptors - conf: simplify lxc_setup_dev_console() - tools: rework tools - autodev: adapt to changes in Linux 4.18 - log: change DEBUG, INFO, TRACE, NOTICE macro using strerror to SYS* macro - log: add lxc_log_strerror_r macro - network: unpriv lxc will run lxc.net.[i].script.up now - conf: only use newuidmap and newgidmap when necessary - autotools: support tls in cross-compile Just like Ubuntu itself, upstream releases long term support releases, as is 3.0 and then periodic point releases including all the accumulated bugfixes. Only the latest upstream release gets full support from the upstream developers, everyone else is expected to first update to it before receiving any kind of support. This should qualify under the minor upstream bugfix release allowance of the SRU policy, letting us SRU this without paperwork for every single change included in this upstream release. Once the SRU hits -updates, we will be backporting this to xenial- backports as well, making sure we have the same version everywhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1788457/+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 1787324] Re: Snap policy module denies recording access to classic snaps
This bug was fixed in the package pulseaudio - 1:12.2-0ubuntu3 --- pulseaudio (1:12.2-0ubuntu3) cosmic; urgency=medium [ Ken VanDine ] * Update patch tags with more detailed descriptions and a note about not forwarding upstream: - 0700-modules-add-snappy-policy-module.patch - 0701-enable-snap-policy-module.patch [ James Henstridge ] * 0700-modules-add-snappy-policy-module.patch: grant recording access to snaps with classic confinement. (LP: #1787324) -- Ken VanDine Wed, 29 Aug 2018 09:18:41 -0400 ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- 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/1787324 Title: Snap policy module denies recording access to classic snaps Status in pulseaudio package in Ubuntu: Fix Released Bug description: With the recent updates to the snap policy module, recording access is denied to clients with a snap AppArmor label when that snap doesn't have a connected plug for "pulseaudio" or "audio-record". This is not appropriate for classic confinement snaps, which will have an AppArmor label but should still have access to recording even when there is no plug, as described by @jdstrand: https://forum.snapcraft.io/t/pulseaudio-recording/6361/14?u=jamesh This is broken with the 1:12.2-0ubuntu2 release, as can be seen with e.g.: $ aa-exec -p snap.skype.skype /usr/bin/parecord foo.wav Stream error: Access denied [note that the Skype app itself still functions because it bypasses PulseAudio all together] The above command should result in audio being recorded from the microphone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1787324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
This bug was fixed in the package packagekit - 1.1.10-1ubuntu4 --- packagekit (1.1.10-1ubuntu4) cosmic; urgency=medium * debian/patches/aptcc-Fix-invalid-version-dereference-in-AptInf-prov.patch: Fix dereferencing of invalid version in providesCodec() (LP: #1790671) -- Julian Andres Klode Tue, 04 Sep 2018 18:18:05 +0200 ** Changed in: packagekit (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 packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790370] Re: package libavahi-common3:i386 0.7-3.1ubuntu1 failed to install/upgrade: a csomag nagyon rossz, következetlen állapotban van - újra kell telepítenie a beállítási kís
** 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 avahi in Ubuntu. https://bugs.launchpad.net/bugs/1790370 Title: package libavahi-common3:i386 0.7-3.1ubuntu1 failed to install/upgrade: a csomag nagyon rossz, következetlen állapotban van - újra kell telepítenie a beállítási kísérlet előtt Status in avahi package in Ubuntu: New Bug description: h ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libavahi-common3:i386 0.7-3.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Sun Sep 2 18:29:31 2018 Dependencies: gcc-8-base 8-20180414-1ubuntu2 libavahi-common-data 0.7-3.1ubuntu1 libc6 2.27-3ubuntu1 libgcc1 1:8-20180414-1ubuntu2 ErrorMessage: a csomag nagyon rossz, következetlen állapotban van - újra kell telepítenie a beállítási kísérlet előtt InstallationDate: Installed on 2018-08-28 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: i386 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: avahi Title: package libavahi-common3:i386 0.7-3.1ubuntu1 failed to install/upgrade: a csomag nagyon rossz, következetlen állapotban van - újra kell telepítenie a beállítási kísérlet előtt UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1790370/+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 1772844] Re: snapd didn't initialize all the seeded snaps
also with proposed Setting up snapd (2.35.1+18.10) ... Installing new version of config file /etc/apparmor.d/usr.lib.snapd.snap-confine.real ... snapd.failure.service is a disabled or a static unit, not starting it. snapd.snap-repair.service is a disabled or a static unit, not starting it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Fix Released Status in snapd: New Status in livecd-rootfs package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in ubuntu-meta source package in Bionic: Fix Released Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
I was able to recreate this using 'pkcon upgrade' as mentioned in the description of the bug report. I did not find a crash report in /var/crash/ though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Incomplete Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1785498] Re: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed
** Changed in: appstream (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 glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1785498 Title: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed Status in AppStream: Fix Released Status in appstream package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Invalid Status in appstream package in Debian: Fix Released Bug description: When running sudo apt update in a terminal I sometimes see the following message printed within the output. (appstreamcli:18640): GLib-CRITICAL **: 17:47:38.047: g_atomic_ref_count_dec: assertion 'g_atomic_int_get (arc) > 0' failed This started happening today (5th August). Otherwise apt update and apt upgrade seem to correctly update the system. -- https://gitlab.gnome.org/GNOME/glib/issues/1480 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libglib2.0-0 2.57.2-1 ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9 Uname: Linux 4.17.0-6-generic x86_64 ApportVersion: 2.20.10-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Aug 5 17:52:41 2018 InstallationDate: Installed on 2018-07-12 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180711) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/appstream/+bug/1785498/+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 1790694] [NEW] Update forgets capslock gnome setting
Public bug reported: I'm not sure this package is the source of the bug. I just updated my system, including this package. Before the update, my capslock key is set in gnome-tweaks to "Caps Lock is also a Ctrl". After the update, my capslock key was back to being capslock. If I load gnome-tweaks, it shows the correct setting but behavior is wrong. I can choose another option and then choose the one I want, and the desired capslock behavior is restored. Here's the console output from the update, showing the packages involved: jlquinn@smaug:~$ sudo aptitude [sudo] password for jlquinn: Performing actions... Preconfiguring packages ... (Reading database ... 296653 files and directories currently installed.) Preparing to unpack .../00-console-setup-linux_1.178ubuntu2.7_all.deb ... Unpacking console-setup-linux (1.178ubuntu2.7) over (1.178ubuntu2.6) ... Preparing to unpack .../01-console-setup_1.178ubuntu2.7_all.deb ... Unpacking console-setup (1.178ubuntu2.7) over (1.178ubuntu2.6) ... Preparing to unpack .../02-keyboard-configuration_1.178ubuntu2.7_all.deb ... Unpacking keyboard-configuration (1.178ubuntu2.7) over (1.178ubuntu2.6) ... Preparing to unpack .../03-libpackagekit-glib2-18_1.1.9-1ubuntu2.18.04.1_amd64.deb ... Unpacking libpackagekit-glib2-18:amd64 (1.1.9-1ubuntu2.18.04.1) over (1.1.9-1ubuntu2) ... Preparing to unpack .../04-gir1.2-packagekitglib-1.0_1.1.9-1ubuntu2.18.04.1_amd64.deb ... Unpacking gir1.2-packagekitglib-1.0 (1.1.9-1ubuntu2.18.04.1) over (1.1.9-1ubuntu2) ... Preparing to unpack .../05-gnome-software-plugin-snap_3.28.1-0ubuntu4.18.04.3_amd64.deb ... Unpacking gnome-software-plugin-snap (3.28.1-0ubuntu4.18.04.3) over (3.28.1-0ubuntu4.18.04.2) ... Preparing to unpack .../06-gnome-software_3.28.1-0ubuntu4.18.04.3_amd64.deb ... Unpacking gnome-software (3.28.1-0ubuntu4.18.04.3) over (3.28.1-0ubuntu4.18.04.2) ... Preparing to unpack .../07-gnome-software-common_3.28.1-0ubuntu4.18.04.3_all.deb ... Unpacking gnome-software-common (3.28.1-0ubuntu4.18.04.3) over (3.28.1-0ubuntu4.18.04.2) ... Preparing to unpack .../08-packagekit-tools_1.1.9-1ubuntu2.18.04.1_amd64.deb ... Unpacking packagekit-tools (1.1.9-1ubuntu2.18.04.1) over (1.1.9-1ubuntu2) ... Preparing to unpack .../09-gstreamer1.0-packagekit_1.1.9-1ubuntu2.18.04.1_amd64.deb ... Unpacking gstreamer1.0-packagekit (1.1.9-1ubuntu2.18.04.1) over (1.1.9-1ubuntu2) ... Preparing to unpack .../10-packagekit_1.1.9-1ubuntu2.18.04.1_amd64.deb ... Unpacking packagekit (1.1.9-1ubuntu2.18.04.1) over (1.1.9-1ubuntu2) ... Preparing to unpack .../11-libgpgme11_1.10.0-1ubuntu2_amd64.deb ... Unpacking libgpgme11:amd64 (1.10.0-1ubuntu2) over (1.10.0-1ubuntu1) ... Preparing to unpack .../12-libgpgmepp6_1.10.0-1ubuntu2_amd64.deb ... Unpacking libgpgmepp6:amd64 (1.10.0-1ubuntu2) over (1.10.0-1ubuntu1) ... Preparing to unpack .../13-ubuntu-software_3.28.1-0ubuntu4.18.04.3_all.deb ... Unpacking ubuntu-software (3.28.1-0ubuntu4.18.04.3) over (3.28.1-0ubuntu4.18.04.2) ... Setting up keyboard-configuration (1.178ubuntu2.7) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. update-initramfs: deferring update (trigger activated) Setting up gnome-software-common (3.28.1-0ubuntu4.18.04.3) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for ureadahead (0.100.0-20) ... ureadahead will be reprofiled on next reboot Processing triggers for desktop-file-utils (0.23-1ubuntu3.18.04.1) ... Processing triggers for libglib2.0-0:amd64 (2.56.1-2ubuntu1) ... Setting up libpackagekit-glib2-18:amd64 (1.1.9-1ubuntu2.18.04.1) ... Setting up libgpgme11:amd64 (1.10.0-1ubuntu2) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for systemd (237-3ubuntu10.3) ... Processing triggers for man-db (2.8.3-2) ... Setting up gir1.2-packagekitglib-1.0 (1.1.9-1ubuntu2.18.04.1) ... Processing triggers for gnome-menus (3.13.3-11ubuntu1.1) ... Processing triggers for dbus (1.12.2-1ubuntu1) ... Setting up console-setup-linux (1.178ubuntu2.7) ... Processing triggers for hicolor-icon-theme (0.17-2) ... Setting up libgpgmepp6:amd64 (1.10.0-1ubuntu2) ... Setting up packagekit (1.1.9-1ubuntu2.18.04.1) ... Setting up console-setup (1.178ubuntu2.7) ... update-initramfs: deferring update (trigger activated) Setting up gstreamer1.0-packagekit (1.1.9-1ubuntu2.18.04.1) ... Setting up gnome-software (3.28.1-0ubuntu4.18.04.3) ... Setting up packagekit-tools (1.1.9-1ubuntu2.18.04.1) ... Setting up ubuntu-software (3.28.1-0ubuntu4.18.04.3) ... Setting up gnome-software-plugin-snap (3.28.1-0ubuntu4.18.04.3) ... Processing triggers for initramfs-tools (0.130ubuntu3.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-33-generic W: plymouth module (/usr/lib/x86_64-linux-gnu/plymouth//.so) missing, skipping that theme. Processing triggers for libc-bin (2.27-3ubuntu1) ... Press Return to continue, 'q' followed by Return to quit.
[Touch-packages] [Bug 1359439] Re: [ 7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service
I'm on ubuntu 16.04.1, doesn't work for me -- 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/1359439 Title: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service Status in NULL Project: Invalid Status in systemd package in Ubuntu: Won't Fix Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Utopic: Won't Fix Status in systemd-shim source package in Utopic: Won't Fix Status in systemd-shim package in Debian: New Bug description: [7.287663] systemd-logind[1057]: Failed to start unit user@126.service: Unknown unit: user@126.service [7.287677] systemd-logind[1057]: Failed to start user service: Unknown unit: user@126.service [7.293871] systemd-logind[1057]: New session c1 of user lightdm. [7.293902] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/126/X11-display. [7.363706] ip_tables: (C) 2000-2006 Netfilter Core Team [7.421846] nf_conntrack version 0.5.0 (16384 buckets, 65536 max) [7.484529] IPv6: ADDRCONF(NETDEV_UP): virbr0: link is not ready [9.903052] wlan0: authenticate with c8:d7:19:22:21:ec [9.912429] wlan0: send auth to c8:d7:19:22:21:ec (try 1/3) [9.920181] wlan0: authenticated [9.924352] wlan0: associate with c8:d7:19:22:21:ec (try 1/3) [9.925709] wlan0: RX AssocResp from c8:d7:19:22:21:ec (capab=0x11 status=0 aid=2) [9.927753] wlan0: associated [9.927800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 12.677104] systemd-logind[1057]: Failed to abandon scope session-c1.scope [ 12.677122] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc1_2escope [ 12.683902] systemd-logind[1057]: Failed to start unit user@1000.service: Unknown unit: user@1000.service [ 12.683912] systemd-logind[1057]: Failed to start user service: Unknown unit: user@1000.service [ 12.685157] systemd-logind[1057]: New session c2 of user caravena. [ 12.685190] systemd-logind[1057]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. [ 234.494462] systemd-logind[1057]: Failed to abandon scope session-c2.scope [ 234.494478] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc2_2escope [ 235.514349] systemd-logind[1057]: New session c3 of user lightdm. [ 244.245908] systemd-logind[1057]: Failed to abandon scope session-c3.scope [ 244.245923] systemd-logind[1057]: Failed to abandon session scope: No such interface 'org.freedesktop.systemd1.Scope' on object at path /org/freedesktop/systemd1/unit/session_2dc3_2escope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-7ubuntu4 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-9-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Aug 20 18:26:06 2014 InstallationDate: Installed on 2014-04-27 (115 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1359439/+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 1772578] Re: [Nvidia HDA] audio crackling
I can no more reproduce this bug. -- 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/1772578 Title: [Nvidia HDA] audio crackling Status in gnome-shell package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: Hello, on Ubuntu this bug regularly appearing: audio suddenly crackling for all softwares. If I restart pulseaudio, it changes nothing. But if I restart gnome-shell ("alt+F2", type "r"), the audio no more crackling. I had this bug for Ubuntu 17.10 and perhaps 17.04 too. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D7p: romain 3648 F...m pulseaudio /dev/snd/controlC0: romain 3648 F pulseaudio CurrentDesktop: GNOME Date: Tue May 22 07:56:34 2018 InstallationDate: Installed on 2012-07-07 (2144 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to bionic on 2018-04-05 (47 days ago) dmi.bios.date: 09/29/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-G45 (MS-7752) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.12:bd09/29/2013:svnMSI:pnMS-7752:pvr1.0:rvnMSI:rnZ77A-G45(MS-7752):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7752 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1772578/+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 1776622] Re: snapd on cosmic never finishes installing/updating. Can't install any other updates.
again with new snapd from proposed Setting up snapd (2.35.1+18.10) ... snapd.failure.service is a disabled or a static unit, not starting it. snapd.snap-repair.service is a disabled or a static unit, not starting it. -- 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/1776622 Title: snapd on cosmic never finishes installing/updating. Can't install any other updates. Status in snapd: Confirmed Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't install any other updates. The first time I gave up waiting and killed it. Then... $ sudo apt full-upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. $ sudo dpkg --configure -a Setting up snapd (2.33+18.10ubuntu3) ... snapd.snap-repair.service is a disabled or a static unit, not starting it. << never ends >> All the while the snap and snapd process use about 0.3% CPU (which is more than usual). WORKAROUND: sudo killall apt dpkg sudo dpkg -r snapd gnome-software-plugin-snap sudo apt update sudo apt full-upgrade --- ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: snapd 2.33+18.10ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Wed Jun 13 16:49:20 2018 InstallationDate: Installed on 2018-05-26 (17 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1776622/+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 1789924] Re: Missing Intel GPU pci-id's
already working on them -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1790664] Re: routing policy not always applied on systemd-networkd restart
** Summary changed: - routing policy not always applied on systemd-networkd restar + routing policy not always applied on systemd-networkd restart -- 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/1790664 Title: routing policy not always applied on systemd-networkd restart Status in systemd package in Ubuntu: Incomplete Bug description: We are using ubuntu 18.04 in an environment with two NIC in the same subnet. As part of network configuration we have created a routing table for each NIC. Every other time that we restart networkd we lose connectivity to eth0. After tcpdump we noticed the reason we lose connectivity to eht0 is routing problem. All connection will always go out from eht1. If we restart netowrkd one more time this will fix the routing issue instantly. Also on each reboot routing policy applies correctly. The problem only appears when we restart netwrokd every other time. We already have raised this issue with Netplan and they suggest this is a systemd bug. Please find the debugs in the attachments. Please don't hesitate to ask if you require any further logs. Regards Arash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+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 1785093] Re: RecursionError error in call_adjusted()
The bucket_id for this crash is ridiculously long and ends causing the Errors site to throw a 414 error. I was able to manually query the database using the bucket_id and discovered the following. In [10]: cassandra.get_versions_for_bucket(urllib.unquote(bucket2)) Out[10]: OrderedDict([(('Ubuntu 18.04', '1.1ubuntu1.18.04.5'), 16)]) So with that information we should be able to verify that the SRU'ed version of the package is not affected. -- 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/1785093 Title: RecursionError error in call_adjusted() Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: [Impact] * Unattended-upgrades may crash and stop installing security updates on users' system due to entering infinite loop. * The fix ensures terminating the recursive calls. [Test Case] * TODO / observe the crash not being reported for fixed releases on errors.ubuntu.com. [Regression Potential] * Unattended-upgrades now adjusts package candidates only to lower versions than the one originally offered by apt's resolver. This is a change in behavior which aligns well with the default configuration, i.e. installing packages from -security but not from -updates, since -updates almost always have higher version numbers. This change may cause using different upgrade paths when PPAs are involved and all packages can't be upgraded to the highest versions found in allowed origins, because of Conflicts: for example. * Unexpected regressions can cause candidate adjustments not taking place, but please note that autopkgtest now includes applying all outstanding security updates for the release thus the new code is covered, too. [Original Bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.5, the problem page at https://errors.ubuntu.com/problem/fa706afe2f0e04b661fe54da0a59b9fc3da50734 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 (most recent call last): File "/usr/bin/unattended-upgrade", line 1991, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1647, in main cache, options, allowed_origins, blacklisted_pkgs, whitelisted_pkgs) File "/usr/bin/unattended-upgrade", line 1349, in calculate_upgradable_pkgs whitelisted_pkgs) File "/usr/bin/unattended-upgrade", line 1288, in try_to_upgrade cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed) File "/usr/bin/unattended-upgrade", line 212, in mark_upgrade_adjusted self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 206, in call_adjusted self.call_adjusted(function, pkg, **kwargs) File "/usr/bin/unattended-upgrade", line 206, in call_adjusted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1785093/+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 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: 1st of all, i am successfully using casper netboot with this distros: menu label Ubuntu 13.10 "Saucy Salamander" - Release i386 menu label Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 menu label Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 menu label Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 but not with menu label Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 boot process gets to the point of running this services dev-hugepages.mount dev-mqueue.mount sys-fs-fuse-connections.mount sys-kernel-config.mount sys-kernel-debug.mount tmp.mount and it stops in emergency console. Too run further to gnome session i've need to do #systemctl mask dev-hugepages.mount #systemctl mask dev-mqueue.mount #systemctl mask sys-fs-fuse-connections.mount #systemctl mask sys-kernel-config.mount #systemctl mask sys-kernel-debug.mount #systemctl mask tmp.mount #ctrl-d after this i get normal live session except wrong dns setting, which is fixed by setting my router's dns as resolver #echo "nameserver 192.168.1.1" > /etc/resolv.conf Please fix boot process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+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 1790680] Re: packagekitd crashed with SIGABRT in std::terminate()
Thank you for your report! However, processing it in order to get sufficient information for the developers failed as the report has a core dump which is invalid. The corruption may have happened on the system which the crash occurred or during transit. Thank you for your understanding, and sorry for the inconvenience! ** Changed in: packagekit (Ubuntu) Status: New => Invalid ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1790680/+attachment/5184544/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790680 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: Invalid Bug description: New install from Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) just started firefox ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Sep 4 16:31:06 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-09-04 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Sent fix upstream: https://github.com/hughsie/PackageKit/pull/273 ** Changed in: packagekit (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Uploaded -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788683] Re: Totem freeze while reading a .mp4 video
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gstreamer1.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1788683 Title: Totem freeze while reading a .mp4 video Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: When I try to read a .mp4 video, Totem start without movie and quickly freeze, or doesn't open the file with an alert dialog-box "Internal data stream error" The files can be red by VLC or QuickTime on a Mac without problem Ubuntu 18.04 libgstreamer1.0-0:amd64 1.14.1-1~ubuntu18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libgstreamer1.0-0 1.14.1-1~ubuntu18.04.1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Aug 23 20:49:09 2018 InstallationDate: Installed on 2018-04-27 (118 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1788683/+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 1790644] Re: dhclient fails to apply custom config outside of the /etc/dhcp directory
*** This bug is a duplicate of bug 1704174 *** https://bugs.launchpad.net/bugs/1704174 ** This bug has been marked a duplicate of bug 1704174 update apparmor rules to include wicd's dhclient.conf file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1790644 Title: dhclient fails to apply custom config outside of the /etc/dhcp directory Status in isc-dhcp package in Ubuntu: New Bug description: 1.) Ubuntu 14.04.1 LTS 2.) Package version: isc-dhcp-client 4.2.4-7ubuntu12.13 3.) I have attempted to run dhclient using the '-cf' option to pass the path to a custom configuration file in '/etc'. My custom configuration differs from the default as it does not request a default router gateway for the interface. i.e. dhclient -v -cf /etc/my_config.conf eth0 4.) I would have expected that dhclient uses the configuration file in '/etc' as the path is valid. 5.) Instead, I observe that a default configuration is being used, i.e. the router option is still being requested. I re-attempted the test but this time placing the new configuration file in '/etc/dhcp' and rerun the client: dhclient -v -cf /etc/dhcp/my_config.conf eth0 On this occasion, I observed that my custom config is being applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1790644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
seems fairly obvious: pkgCache::VerIterator ver = m_cache->findVer(pkg); arch = string(ver.Arch()); if (ver.end() == true) { ver = m_cache->findCandidateVer(pkg); if (ver.end() == true) { continue; } } ver.Arch() is called even if ver is not valid. ** Changed in: packagekit (Ubuntu) Status: New => Triaged ** Changed in: packagekit (Ubuntu) Status: Triaged => In Progress ** Changed in: packagekit (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: packagekit (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: Fix Committed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790680] [NEW] packagekitd crashed with SIGABRT in std::terminate()
Public bug reported: New install from Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) just started firefox ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Sep 4 16:31:06 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-09-04 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash cosmic need-amd64-retrace ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790680 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: New Bug description: New install from Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) just started firefox ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu2 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 Date: Tue Sep 4 16:31:06 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-09-04 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) ProcCmdline: /usr/lib/packagekit/packagekitd Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790680/+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 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Hello, I plan to create a DVD or flash with live 18.04, boot it on the machine and test the bug. I had a vacation, so I didn't do it yet. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Incomplete Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+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 1790668] [NEW] /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin/unattended-upgrade@1485:main:do_auto_remove:cache_commit:commit:_fetch_archives
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1, the problem page at https://errors.ubuntu.com/problem/eabb483bd4584c745292dbf0b45214b2f5d75013 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: bionic xenial -- 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/1790668 Title: /usr/bin/unattended-upgrade:apt.cache.LockFailedException:/usr/bin /unattended- upgrade@1485:main:do_auto_remove:cache_commit:commit:_fetch_archives Status in unattended-upgrades package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1, the problem page at https://errors.ubuntu.com/problem/eabb483bd4584c745292dbf0b45214b2f5d75013 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1790668/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790671] [NEW] /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: artful bionic cosmic kylin-17.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790671 Title: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy Status in packagekit package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding packagekit. This problem was most recently seen with package version 1.1.10-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790677] [NEW] package console-setup 1.178ubuntu2.7 failed to install/upgrade: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (V
Public bug reported: package console-setup 1.178ubuntu2.7 failed to install/upgrade: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (Violación de segmento), volcado de «core» ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 4 17:35:15 2018 ErrorMessage: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (Violación de segmento), volcado de «core» InstallationDate: Installed on 2018-05-16 (110 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.7 failed to install/upgrade: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (Violación de segmento), volcado de «core» UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1790677 Title: package console-setup 1.178ubuntu2.7 failed to install/upgrade: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (Violación de segmento), volcado de «core» Status in console-setup package in Ubuntu: New Bug description: package console-setup 1.178ubuntu2.7 failed to install/upgrade: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (Violación de segmento), volcado de «core» ProblemType: Package DistroRelease: Ubuntu 18.04 Package: console-setup 1.178ubuntu2.7 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Tue Sep 4 17:35:15 2018 ErrorMessage: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (Violación de segmento), volcado de «core» InstallationDate: Installed on 2018-05-16 (110 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: console-setup Title: package console-setup 1.178ubuntu2.7 failed to install/upgrade: instalado console-setup paquete post-installation guión el subproceso fue asesinado por la señal (Violación de segmento), volcado de «core» UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1790677/+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 1790664] Re: routing policy not always applied on systemd-networkd restar
Hi, Please find contains of /run/systemd/netowrk in the attachments Thanks! ** Attachment added: "netplan_config" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+attachment/5184532/+files/netplan_config -- 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/1790664 Title: routing policy not always applied on systemd-networkd restar Status in systemd package in Ubuntu: Incomplete Bug description: We are using ubuntu 18.04 in an environment with two NIC in the same subnet. As part of network configuration we have created a routing table for each NIC. Every other time that we restart networkd we lose connectivity to eth0. After tcpdump we noticed the reason we lose connectivity to eht0 is routing problem. All connection will always go out from eht1. If we restart netowrkd one more time this will fix the routing issue instantly. Also on each reboot routing policy applies correctly. The problem only appears when we restart netwrokd every other time. We already have raised this issue with Netplan and they suggest this is a systemd bug. Please find the debugs in the attachments. Please don't hesitate to ask if you require any further logs. Regards Arash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+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 1762385] Re: dell_wmi: Unknown key codes
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: New Status in linux source package in Bionic: Fix Committed Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+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 1777994] Re: the header xcb/xinput.h is missing
Timo, do you want that fixed in bionic? ** Changed in: libxcb (Ubuntu Bionic) Importance: Undecided => Low ** Changed in: libxcb (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- 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: New Bug description: 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 1789924] Re: Missing Intel GPU pci-id's
Timo, do you plan to work on those fixes for bionic? Assuming you do but please talk to me if you don't (those unassigned bionic tasks against desktop-set packages show on our team report and we try to either get those assigned or untargetted because it doesn't make much sense to accept a nomination if no one is commiting to do the work) ** Changed in: xorg-server (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: mesa (Ubuntu Bionic) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: New Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+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 1790664] Re: routing policy not always applied on systemd-networkd restar
Please include the *.network, *.netdev, *.link files from /etc/systemd/network or /run/systemd/network as well for the configuration, after making sure you sanitized them if there are any information (IPs?) that you don't want public. Thanks! ** Changed in: systemd (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1790664 Title: routing policy not always applied on systemd-networkd restar Status in systemd package in Ubuntu: Incomplete Bug description: We are using ubuntu 18.04 in an environment with two NIC in the same subnet. As part of network configuration we have created a routing table for each NIC. Every other time that we restart networkd we lose connectivity to eth0. After tcpdump we noticed the reason we lose connectivity to eht0 is routing problem. All connection will always go out from eht1. If we restart netowrkd one more time this will fix the routing issue instantly. Also on each reboot routing policy applies correctly. The problem only appears when we restart netwrokd every other time. We already have raised this issue with Netplan and they suggest this is a systemd bug. Please find the debugs in the attachments. Please don't hesitate to ask if you require any further logs. Regards Arash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+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 1790664] [NEW] routing policy not always applied on systemd-networkd restar
Public bug reported: We are using ubuntu 18.04 in an environment with two NIC in the same subnet. As part of network configuration we have created a routing table for each NIC. Every other time that we restart networkd we lose connectivity to eth0. After tcpdump we noticed the reason we lose connectivity to eht0 is routing problem. All connection will always go out from eht1. If we restart netowrkd one more time this will fix the routing issue instantly. Also on each reboot routing policy applies correctly. The problem only appears when we restart netwrokd every other time. We already have raised this issue with Netplan and they suggest this is a systemd bug. Please find the debugs in the attachments. Please don't hesitate to ask if you require any further logs. Regards Arash ** Affects: systemd (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: netplan routing systemd-network ** Attachment added: "systemd_network_bug" https://bugs.launchpad.net/bugs/1790664/+attachment/5184529/+files/systemd_network_bug -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1790664 Title: routing policy not always applied on systemd-networkd restar Status in systemd package in Ubuntu: Incomplete Bug description: We are using ubuntu 18.04 in an environment with two NIC in the same subnet. As part of network configuration we have created a routing table for each NIC. Every other time that we restart networkd we lose connectivity to eth0. After tcpdump we noticed the reason we lose connectivity to eht0 is routing problem. All connection will always go out from eht1. If we restart netowrkd one more time this will fix the routing issue instantly. Also on each reboot routing policy applies correctly. The problem only appears when we restart netwrokd every other time. We already have raised this issue with Netplan and they suggest this is a systemd bug. Please find the debugs in the attachments. Please don't hesitate to ask if you require any further logs. Regards Arash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790664/+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 1786617] Re: setupterm doesn't find terminfo entry in non-standard database location
Oh and reading the original bug report posted against tmux, this problem is most likely caused because the OP is running tmux in client server mode and the server runs in an environment different from the client (at machine startup). infocmp can find the kitty terminfo because kitty sets the TERMINFO env var to point to its terminfo deifnition file. That env var is likely not present in the environment in which the tmux server is started. So the fix is to either copy the kitty terminfo files to /usr/share/terminfo or to set TERMINFO in whatever script is used to start the tmux server. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1786617 Title: setupterm doesn't find terminfo entry in non-standard database location Status in ncurses package in Ubuntu: New Bug description: My terminal emulator (Kitty) installs its terminfo entry to: /usr/local/lib/kitty/terminfo/x/xterm-kitty But it also registers /usr/local/lib/kitty/terminfo/ as a terminfo database: % infocmp -D /usr/local/lib/kitty/terminfo /etc/terminfo /lib/terminfo /usr/share/terminfo I use tmux, which uses setupterm: https://github.com/tmux/tmux/blob/b2a2c3a1e90756313b6709905f189934123f85ed /tty-term.c#L412 setupterm sets an error code unless I symlink the terminfo def to a traditional location: sudo ln -s /usr/local/lib/kitty/terminfo/x/xterm-kitty /usr/share/terminfo/x/xterm-kitty This stops the problem. setupterm is presumably not searching all database locations. I am not the developer of tmux, he directed me here to log the issue. See https://github.com/tmux/tmux/issues/1433 for the original bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1786617/+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 1790644] Re: dhclient fails to apply custom config outside of the /etc/dhcp directory
** Description changed: 1.) Ubuntu 14.04.1 LTS 2.) Package version: isc-dhcp-client 4.2.4-7ubuntu12.13 - 3.) I have attempted to run dhclient using the '-cf' option to pass the path to a custom configuration file in '/etc'. My custom configuration differs from the default as it does not request a default router gateway for the interface. i.e. dhclient -v -cf /etc/my_config.conf eth0 4.) I would have expected that dhclient uses the configuration file in '/etc' as the path is valid. 5.) - Instead, what I observer if that a default configuration is being used, - i.e. I observer that the router option is still being requested. I re- - attempted the test but this time placing the new configuration file in - '/etc/dhcp' and rerun the client: + Instead, I observe that a default configuration is being used, i.e. the + router option is still being requested. I re-attempted the test but this + time placing the new configuration file in '/etc/dhcp' and rerun the + client: - dhclient -v -cf /etc/dhcp/my_config.conf eth0 + dhclient -v -cf /etc/dhcp/my_config.conf eth0 On this occasion, I observed that my custom config is being applied. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1790644 Title: dhclient fails to apply custom config outside of the /etc/dhcp directory Status in isc-dhcp package in Ubuntu: New Bug description: 1.) Ubuntu 14.04.1 LTS 2.) Package version: isc-dhcp-client 4.2.4-7ubuntu12.13 3.) I have attempted to run dhclient using the '-cf' option to pass the path to a custom configuration file in '/etc'. My custom configuration differs from the default as it does not request a default router gateway for the interface. i.e. dhclient -v -cf /etc/my_config.conf eth0 4.) I would have expected that dhclient uses the configuration file in '/etc' as the path is valid. 5.) Instead, I observe that a default configuration is being used, i.e. the router option is still being requested. I re-attempted the test but this time placing the new configuration file in '/etc/dhcp' and rerun the client: dhclient -v -cf /etc/dhcp/my_config.conf eth0 On this occasion, I observed that my custom config is being applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1790644/+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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :
is this bug lost or not assigned to someone? It is still broken, of course there are workarounds but no one knows the exact consequences of them? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1755863 Title: netbooting the bionic live CD over NFS goes straight to maintenance mode : Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: netbooting the bionic live CD[1] over NFS goes straight to maintenance mode : [1] http://cdimage.ubuntu.com/daily-live/current/ # casper.log Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Daemon' dbus-daemon[568]: [session uid=999 pid=568] Activating service name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" label="unconfined") fuse: device not found, try 'modprobe fuse' first dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 'org.gtk.vfs.Metadata' (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed A connection to the bus can't be made done. Begin: Setting up init... ... done. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+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 1754777] Re: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp
still no fix or assignee for this? Not working as of today, possible duplicate addition to this: #1755863 still open and unassigned as well. -- 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/1754777 Title: bionic casper nfsboot not reaching desktop env, failure to mount various kernel filesystems and /tmp Status in casper package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: 1st of all, i am successfully using casper netboot with this distros: menu label Ubuntu 13.10 "Saucy Salamander" - Release i386 menu label Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 menu label Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 menu label Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 but not with menu label Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 boot process gets to the point of running this services dev-hugepages.mount dev-mqueue.mount sys-fs-fuse-connections.mount sys-kernel-config.mount sys-kernel-debug.mount tmp.mount and it stops in emergency console. Too run further to gnome session i've need to do #systemctl mask dev-hugepages.mount #systemctl mask dev-mqueue.mount #systemctl mask sys-fs-fuse-connections.mount #systemctl mask sys-kernel-config.mount #systemctl mask sys-kernel-debug.mount #systemctl mask tmp.mount #ctrl-d after this i get normal live session except wrong dns setting, which is fixed by setting my router's dns as resolver #echo "nameserver 192.168.1.1" > /etc/resolv.conf Please fix boot process. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1754777/+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 1789764] Re: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: fontconfig (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1789764 Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in fontconfig package in Ubuntu: Confirmed Bug description: Upgrade to 18.04 error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: fontconfig 2.12.6-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 Uname: Linux 4.15.0-33-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Aug 30 02:42:47 2018 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2018-04-24 (127 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: fontconfig Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to bionic on 2018-08-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1789764/+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 1164016] Re: restore type-ahead find
OK. So I was a happy user of 16.04. With a new computer in August, I thought it would make sense to go with 18.04. One of the biggest issues is this searching stuff in Nautilus. Why? 1. It is not instant (unlike the type/find ahead of Nautilus in 16.04). I cannot type and then press enter and load the folder I want. 2. It is inconsistent with file dialogs (e.g. save or open) where find/type ahead works as expected. 3. Often I just want to see the files and folders in relation to one another. I might want to see the files starting with 'th', and being able to see the files starting with 'te' and 'tg' before the ones starting with 'th' is often quite useful. 4. There is no way that I can see to make it search only within the directory and not recursively search all subdirectories. I don't like that. 5. And searching within subdirectories doesn't even work 100% of the time! E.g. A search for a dot folder consistently doesn't turn it up. Thank you Ubuntu developers for previously hiding this stupidity. Please consider getting rid of it in 18.04 as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+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 1790613] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1790613/+attachment/5184518/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Incomplete Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1790613] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1790613/+attachment/5184519/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Incomplete Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
apport information ** Tags added: apport-collected bionic ** Description changed: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.2 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2018-06-26 (69 days ago) + InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) + Package: packagekit 1.1.9-1ubuntu2.18.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 + Tags: bionic + Uname: Linux 4.15.0-33-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1790613/+attachment/5184517/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Incomplete Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library
[Touch-packages] [Bug 1790644] [NEW] dhclient fails to apply custom config outside of the /etc/dhcp directory
Public bug reported: 1.) Ubuntu 14.04.1 LTS 2.) Package version: isc-dhcp-client 4.2.4-7ubuntu12.13 3.) I have attempted to run dhclient using the '-cf' option to pass the path to a custom configuration file in '/etc'. My custom configuration differs from the default as it does not request a default router gateway for the interface. i.e. dhclient -v -cf /etc/my_config.conf eth0 4.) I would have expected that dhclient uses the configuration file in '/etc' as the path is valid. 5.) Instead, what I observer if that a default configuration is being used, i.e. I observer that the router option is still being requested. I re- attempted the test but this time placing the new configuration file in '/etc/dhcp' and rerun the client: dhclient -v -cf /etc/dhcp/my_config.conf eth0 On this occasion, I observed that my custom config is being applied. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: config dhclient -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1790644 Title: dhclient fails to apply custom config outside of the /etc/dhcp directory Status in isc-dhcp package in Ubuntu: New Bug description: 1.) Ubuntu 14.04.1 LTS 2.) Package version: isc-dhcp-client 4.2.4-7ubuntu12.13 3.) I have attempted to run dhclient using the '-cf' option to pass the path to a custom configuration file in '/etc'. My custom configuration differs from the default as it does not request a default router gateway for the interface. i.e. dhclient -v -cf /etc/my_config.conf eth0 4.) I would have expected that dhclient uses the configuration file in '/etc' as the path is valid. 5.) Instead, what I observer if that a default configuration is being used, i.e. I observer that the router option is still being requested. I re-attempted the test but this time placing the new configuration file in '/etc/dhcp' and rerun the client: dhclient -v -cf /etc/dhcp/my_config.conf eth0 On this occasion, I observed that my custom config is being applied. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1790644/+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 1638634] Re: Print Job with Authentication is postponed until queue is opened manually
OK, thanks for the update, Scott. I think there is enough information in this report now that it can be send to the programmers. For their ease, I will add a summary here. Please feel free to add any corrections. --- SUMMARY: Ubuntu version 16.04 16.04 (cups 2.1.3-4ubuntu0.5). system-config-printer-common 1.5.7+20160212-0ubuntu2. Hplip 3.16.3+repack0-1. Problem is reproducable by the bug reporter. All print jobs from many different applications Bug triager is unable to reproduce the bug. Steps to reproduce: 1. Print an any document from an any application's print dialog (e.g. evince, Okular, GIMP, ReText,...). 2. Printing does not happen. 3. Open "system-config-printer” 4. Open the printer's print queue 5. All documents in the queue are processed, i.e. printed immediately. Expected behaviour: the document prints immediately. Actual behaviour: the document is held in the queue until the print queue is opened through "system-config-printer.” Additional notes: Printer is a RICOH MP C3003 situated on a large network. CUPS interface on local computer indicates that job is stopped but “release job” button is ignored. Opening the queue in “system-config-printer” on local computer immediately starts the job. Reporter has uploaded tail of access.log which mentions authentication successful, only after the reporter opened the queue in “system-config-printer” --- Triager searched for dups - none found. -- 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/1638634 Title: Print Job with Authentication is postponed until queue is opened manually Status in cups package in Ubuntu: New Bug description: I am connected to a print host requiring authentication. The authentication data is already stored in CUPS. I can issue a new print job and the printer icon in the panel appears, but the job isn't started, until I open the queue of the respective printer. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-09-15 (1077 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for 0_prost: lpd://prost.uni-koblenz.de/ device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14 device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390 MachineType: LENOVO 20BX000XGE Package: cups 2.1.3-4ubuntu0.5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied grep: /etc/cups/ppd/0_prost.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Tags: xenial Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp vboxusers _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638634/+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 1638634] Re: Print Job with Authentication is postponed until queue is opened manually
Sorry, Brandon. I wrote your name wrong. I meant: Brandon :) G -- 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/1638634 Title: Print Job with Authentication is postponed until queue is opened manually Status in cups package in Ubuntu: New Bug description: I am connected to a print host requiring authentication. The authentication data is already stored in CUPS. I can issue a new print job and the printer icon in the panel appears, but the job isn't started, until I open the queue of the respective printer. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-09-15 (1077 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for 0_prost: lpd://prost.uni-koblenz.de/ device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14 device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390 MachineType: LENOVO 20BX000XGE Package: cups 2.1.3-4ubuntu0.5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied grep: /etc/cups/ppd/0_prost.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Tags: xenial Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp vboxusers _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638634/+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 1786617] Re: setupterm doesn't find terminfo entry in non-standard database location
Not to mention that if symlinking the compiled terminfo into /usr/share/terminfo fixes the problem, then the problem cannot be in the format of the compiled database. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1786617 Title: setupterm doesn't find terminfo entry in non-standard database location Status in ncurses package in Ubuntu: New Bug description: My terminal emulator (Kitty) installs its terminfo entry to: /usr/local/lib/kitty/terminfo/x/xterm-kitty But it also registers /usr/local/lib/kitty/terminfo/ as a terminfo database: % infocmp -D /usr/local/lib/kitty/terminfo /etc/terminfo /lib/terminfo /usr/share/terminfo I use tmux, which uses setupterm: https://github.com/tmux/tmux/blob/b2a2c3a1e90756313b6709905f189934123f85ed /tty-term.c#L412 setupterm sets an error code unless I symlink the terminfo def to a traditional location: sudo ln -s /usr/local/lib/kitty/terminfo/x/xterm-kitty /usr/share/terminfo/x/xterm-kitty This stops the problem. setupterm is presumably not searching all database locations. I am not the developer of tmux, he directed me here to log the issue. See https://github.com/tmux/tmux/issues/1433 for the original bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1786617/+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 1786617] Re: setupterm doesn't find terminfo entry in non-standard database location
No, kitty uses the tic utility to compile its terminfo file when building the kitty package. https://github.com/kovidgoyal/kitty/blob/master/setup.py#L601 ** Changed in: ncurses (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ncurses in Ubuntu. https://bugs.launchpad.net/bugs/1786617 Title: setupterm doesn't find terminfo entry in non-standard database location Status in ncurses package in Ubuntu: New Bug description: My terminal emulator (Kitty) installs its terminfo entry to: /usr/local/lib/kitty/terminfo/x/xterm-kitty But it also registers /usr/local/lib/kitty/terminfo/ as a terminfo database: % infocmp -D /usr/local/lib/kitty/terminfo /etc/terminfo /lib/terminfo /usr/share/terminfo I use tmux, which uses setupterm: https://github.com/tmux/tmux/blob/b2a2c3a1e90756313b6709905f189934123f85ed /tty-term.c#L412 setupterm sets an error code unless I symlink the terminfo def to a traditional location: sudo ln -s /usr/local/lib/kitty/terminfo/x/xterm-kitty /usr/share/terminfo/x/xterm-kitty This stops the problem. setupterm is presumably not searching all database locations. I am not the developer of tmux, he directed me here to log the issue. See https://github.com/tmux/tmux/issues/1433 for the original bug report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ncurses/+bug/1786617/+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 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
We need a crash dump to be able to investigate this. Apport can probably help you with apport-collect 1790613 or something. Without a crash dump we don't see where it crashed and thus can't do much. ** Changed in: packagekit (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: Incomplete Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1762314] Re: Sound output too low
Originally had this issue on my ThinkPad T570 running Ubuntu 16.04 and added a bug report to this issue. Yesterday, I upgraded to Ubuntu 18.04 and the problem still exists. Please advise if additional detail would be useful. -- 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/1762314 Title: Sound output too low Status in alsa-driver package in Ubuntu: Confirmed Bug description: Sound output on lenovo p51s is too low. No option to go above 100% in volume settings. Download pulse audio volume control to raise application and output volume to 153%, which helps to some extent, but then leads to distortion. Was running windows 10 on same system and audio was loud enough! Also after this morning s update, the volume keys no longer work, even after re-mapping them in shortcuts.3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jatin 2098 F pulseaudio CurrentDesktop: Budgie:GNOME Date: Sun Apr 8 22:50:04 2018 InstallationDate: Installed on 2018-03-23 (17 days ago) InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [20HCS06601, Realtek ALC298, Speaker, Internal] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1VET36W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HCS06601 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1VET36W(1.26):bd10/03/2017:svnLENOVO:pn20HCS06601:pvrThinkPadP51s:rvnLENOVO:rn20HCS06601:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P51s dmi.product.name: 20HCS06601 dmi.product.version: ThinkPad P51s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1762314/+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 1743939] Re: Canon MF8380 Wireless Network Not Printing
Thanks for the update, Scott. No need for additional testing. I will close the report now. Have a great day! :) G Closed per reporter’s feedback. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- 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/1743939 Title: Canon MF8380 Wireless Network Not Printing Status in cups package in Ubuntu: Invalid Bug description: A Canon MF8380CDW printer will not print any thing after upgrading to 17.10. I ran all the steps from this https://wiki.ubuntu.com/DebuggingPrintingProblems web site. I have attached a lot of log files. Not sure which one is needed. The printer did work back under 15.10 or 16.04 but took a lot to get it fixed to work then. I have tried to print from 18.04 and it has the same problem with this printer. myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" "MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300 C Series;CID:;CMD:LIPSLX,CPCA;" "" myuseraccount@myuseraccount-System-Product-Name:~$ sudo /usr/lib/cups/backend/dnssd [sudo] password for myuseraccount: DEBUG: sent=0, count=0 DEBUG: Querying "Canon\032MF8300C\032Series._printer._tcp.local"... DEBUG: Querying "Canon\032MF8300C\032Series._pdl-datastream._tcp.local"... DEBUG: sent=0, count=2 DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=2, protocol=0, event=0, fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, rrtype=16, rdata=0x 556cd4f97854, rdlen=338, flags=5, context=0x556cd4f95900) DEBUG2: query_callback: "txtvers=1". DEBUG2: query_callback: "note=". DEBUG2: query_callback: "qtotal=1". DEBUG2: query_callback: "priority=20". DEBUG2: query_callback: "ty=Canon MF8300C Series". DEBUG2: query_callback: "product=(CNMF8300C Series)". DEBUG2: query_callback: "pdl=application/octet-stream". DEBUG2: query_callback: "adminurl=http://Canon0f2ec4.local/m_network_tcpip.html;. DEBUG2: query_callback: "usb_MFG=Canon". DEBUG2: query_callback: "usb_MDL=MF8300C Series". DEBUG2: query_callback: "Transparent=F". DEBUG2: query_callback: "Binary=F". DEBUG2: query_callback: "TBCP=F". DEBUG2: query_callback: "Color=T". DEBUG2: query_callback: "Copies=T". DEBUG2: query_callback: "Duplex=T". DEBUG2: query_callback: "PaperCustom=T". DEBUG2: query_callback: "Bind=F". DEBUG2: query_callback: "Collate=T". DEBUG2: query_callback: "Sort=T". DEBUG2: query_callback: "Staple=F". DEBUG2: query_callback: "Punch=0". DEBUG2: query_callback: "PaperMax=legal-A4". DEBUG2: query_callback(browser=0x556cd4f96420, interfaceIndex=-1, protocol=-1, event=2, fullName="Canon\032MF8300C\032Series._printer._tcp.local", rrclass=1, rrtype=16, rdata= (nil), rdlen=0, flags=0, context=0x556cd4f95900) DEBUG2: query_callback(browser=0x556cd4f95aa0, interfaceIndex=2, protocol=0, event=0, fullName="Canon\032MF8300C\032Series._pdl-datastream._tcp.local", rrclass=1, rrtype=16, r data=0x556cd4f97a0c, rdlen=338, flags=5, context=0x556cd4f95780) DEBUG2: query_callback: "txtvers=1". DEBUG2: query_callback: "note=". DEBUG2: query_callback: "qtotal=1". DEBUG2: query_callback: "priority=10". DEBUG2: query_callback: "ty=Canon MF8300C Series". DEBUG2: query_callback: "product=(CNMF8300C Series)". DEBUG2: query_callback: "pdl=application/octet-stream". DEBUG2: query_callback: "adminurl=http://Canon0f2ec4.local/m_network_tcpip.html;. DEBUG2: query_callback: "usb_MFG=Canon". DEBUG2: query_callback: "usb_MDL=MF8300C Series". DEBUG2: query_callback: "Transparent=F". DEBUG2: query_callback: "Binary=F". DEBUG2: query_callback: "TBCP=F". DEBUG2: query_callback: "Color=T". DEBUG2: query_callback: "Copies=T". DEBUG2: query_callback: "Duplex=T". DEBUG2: query_callback: "PaperCustom=T". DEBUG2: query_callback: "Bind=F". DEBUG2: query_callback: "Collate=T". DEBUG2: query_callback: "Sort=T". DEBUG2: query_callback: "Staple=F". DEBUG2: query_callback: "Punch=0". DEBUG2: query_callback: "PaperMax=legal-A4". network dnssd://Canon%20MF8300C%20Series._pdl-datastream._tcp.local/ "Canon MF8300C Series" "Canon MF8300C Series" "MFG:Canon;MDL:MF8300C Series;" "" DEBUG: sent=2, count=2 myuseraccount@myuseraccount-System-Product-Name:~$ /usr/lib/cups/backend/snmp 192.168.1.100 network socket://192.168.1.100 "Canon MF8300C Series" "Canon MF8300C Series" "MFG:Canon;MDL:MF8300C Series;CLS:PRINTER;DES:Canon MF8300C Series;CID:;CMD:LIPSLX,CPCA;" "" myuseraccount@myuseraccount-System-Product-Name:~$ lpinfo -v network ipp network https network ipps network http file cups-brf:/ network beh direct hp serial serial:/dev/ttyS0?baud=115200 network socket network lpd direct parallel:/dev/lp0 file cups-pdf:/ network bjnp
[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps
Still broken on Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180903) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1772844 Title: snapd didn't initialize all the seeded snaps Status in OEM Priority Project: Fix Released Status in snapd: New Status in livecd-rootfs package in Ubuntu: Won't Fix Status in ubuntu-meta package in Ubuntu: Fix Released Status in livecd-rootfs source package in Bionic: Fix Released Status in ubuntu-meta source package in Bionic: Fix Released Bug description: snapd didn't initialize all the seeded snaps bionic-desktop-amd64.iso (20180522) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.32.9+18.04 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue May 22 22:59:18 2018 InstallationDate: Installed on 2018-05-23 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1772844/+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 1742901] Re: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thanks for the update, Makis. I will close the report now. Have a great day! :) G Closed per reporter’s feedback. ** Changed in: cups (Ubuntu) Status: Incomplete => Invalid -- 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/1742901 Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: Invalid Bug description: i don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.3 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CupsErrorLog: E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File \"/usr/lib/cups/filter/hpcups\" not available: No such file or directory E [12/Jan/2018:11:32:20 +0200] HP-DeskJet-4670-series: File \"/usr/lib/cups/filter/hpcups\" not available: No such file or directory Date: Fri Jan 12 11:43:52 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-01-03 (373 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for EPSON-AL-CX16NF: dnssd://EPSON%20AL-CX16NF-5FD934._pdl-datastream._tcp.local/ device for HP-DeskJet-4670-series: dnssd://HP%20DeskJet%204670%20series%20%5B22083D%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-f430b922083d device for OKI-DATA-CORP-C301: dnssd://OKI-C301-ACD8ED._pdl-datastream._tcp.local/ MachineType: LENOVO 42334AG Papersize: a4 PpdFiles: OKI-DATA-CORP-C301: Oki C301dn Foomatic/foo2hiperc (recommended) HP-DeskJet-4670-series: HP Deskjet 4670 Series, hpcups 3.16.3 EPSON-AL-CX16NF: KONICA MINOLTA magicolor 1600W Foomatic/foo2lava (recommended) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-104-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 6GET18WW(V1.09) dmi.board.name: KIWDX dmi.board.vendor: LENOVO dmi.board.version: REFERENCE dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnLENOVO:bvr6GET18WW(V1.09):bd05/22/2009:svnLENOVO:pn42334AG:pvrLenovo3000N500:rvnLENOVO:rnKIWDX:rvrREFERENCE:cvnNoEnclosure:ct10:cvrN/A: dmi.product.name: 42334AG dmi.product.version: Lenovo 3000 N500 dmi.sys.vendor: LENOVO mtime.conffile..etc.init.d.cups: 2017-12-06T20:23:04.314671 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1742901/+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 1790628] [NEW] systemd from 18.04 fails to resolve name without domain
Public bug reported: On 16.04 I had no problems. On 18.04 systemd-resolved fails to resolve host name without domain (using nslookup) even though DNS server is reported by systemd-resolve --status. If to provide DNS to nslookup explicitly, then the name is resolved. $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp0s31f6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.200.1 $ nslookup sniffer Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find sniffer: SERVFAIL $ nslookup sniffer 192.168.200.1 Server: 192.168.200.1 Address:192.168.200.1#53 Name: sniffer Address: 192.168.200.1 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1790628 Title: systemd from 18.04 fails to resolve name without domain Status in systemd package in Ubuntu: New Bug description: On 16.04 I had no problems. On 18.04 systemd-resolved fails to resolve host name without domain (using nslookup) even though DNS server is reported by systemd-resolve --status. If to provide DNS to nslookup explicitly, then the name is resolved. $ systemd-resolve --status Global DNSSEC NTA: 10.in-addr.arpa 16.172.in-addr.arpa 168.192.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa 20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa 23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa 26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa 29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa corp d.f.ip6.arpa home internal intranet lan local private test Link 3 (wlp4s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp0s31f6) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.200.1 $ nslookup sniffer Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find sniffer: SERVFAIL $ nslookup sniffer 192.168.200.1 Server: 192.168.200.1 Address:192.168.200.1#53 Name: sniffer Address: 192.168.200.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790628/+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 1789431] Re: ip rule show has unexpected space in destination prefix
This bug was fixed in the package iproute2 - 4.18.0-1ubuntu2 --- iproute2 (4.18.0-1ubuntu2) cosmic; urgency=low * d/p/1006-ubuntu-iprule-fix-output.patch Fix destination prefix output of "ip rule show" (LP: #1789431). -- Stefan Bader Tue, 28 Aug 2018 16:38:47 +0200 ** Changed in: iproute2 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1789431 Title: ip rule show has unexpected space in destination prefix Status in iproute2 package in Ubuntu: Fix Released Bug description: Introduced by upstream iproute2 v4.17.0: 0dd4ccc5 "iprule: add json support" This commit changes the output of "ip rule show" to support json output but also accidentally inserts a space character between ipv4 address and "/". This breaks for example the route_with_policy test of netplan.io. Testcase: ip rule add from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 ip rule show Expected: *: from 10.1.0.0/24 to 10.2.0.0/24 lookup 99 Actual output: *: from 0.1.0.0/24 to 10.2.0.0 /24 lookup 99 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1789431/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable
I was affected by this issue after the update of console-setup today. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1508146 Title: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I'm used to using alt+left/right arrow to navigate back and forward in web browsers and elsewhere (nautilus)... But on this fresh install of Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty consoles (the ctrl+alt+f1 ones). But it's not listed as one of the shortcuts in the "keyboard" menu, so I don't know how to disable it... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1508146/+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 1790618] [NEW] Update to 3.24.0
Public bug reported: Do it ** Affects: gtk+3.0 (Ubuntu) Importance: Wishlist Assignee: Iain Lane (laney) Status: In Progress ** Tags: upgrade-software-version ** Changed in: gtk+3.0 (Ubuntu) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1790618 Title: Update to 3.24.0 Status in gtk+3.0 package in Ubuntu: In Progress Bug description: Do it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1790618/+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 1763100] Re: FONT="x/y/z" is not applied due to setupcon script bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1763100 Title: FONT="x/y/z" is not applied due to setupcon script bug Status in console-setup package in Ubuntu: Confirmed Bug description: apt-cache policy console-setup console-setup: Installed: 1.178ubuntu1 Candidate: 1.178ubuntu1 Version table: *** 1.178ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status On 18.04 I wanted to set the TTY font to use a Powerline font. Despite being able to set the font manually it wasn't being set at boot-time. /etc/default/console-setup contains: FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz" "setupcon -v -f" reported an error: putfont: KDFONTOP: Invalid argument due to passing the font filename twice: executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline- v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz. The problem is in /bin/setupcon where the collecting variable FONTFILES has the font added twice, once at the top of the for loop FONTFILES="$FONTFILES `findfile $fontdir $f`" and again at the bottom FONTFILES="$FONTFILES $RES" Removing the first assignment fixes it. FONTFILES='' echo "DEBUG: FONT=$FONT" if [ "$FONT" ]; then for f in $FONT; do echo "DEBUG: for loop" FONTFILES="$FONTFILES `findfile $fontdir $f`" RES=`findfile $fontdir $f` if [ -z "$RES" ]; then fdec="${f%.gz}" RES=`findfile $fontdir $fdec` fi FONTFILES="$FONTFILES $RES" done fi FONTFILES=`echo $FONTFILES` # remove extra spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1763100/+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 1763100] Re: FONT="x/y/z" is not applied due to setupcon script bug
This solution seems to work. Thanks! ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1763100 Title: FONT="x/y/z" is not applied due to setupcon script bug Status in console-setup package in Ubuntu: Confirmed Bug description: apt-cache policy console-setup console-setup: Installed: 1.178ubuntu1 Candidate: 1.178ubuntu1 Version table: *** 1.178ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://gb.archive.ubuntu.com/ubuntu bionic/main i386 Packages 100 /var/lib/dpkg/status On 18.04 I wanted to set the TTY font to use a Powerline font. Despite being able to set the font manually it wasn't being set at boot-time. /etc/default/console-setup contains: FONT="/usr/local/share/fonts/ter-powerline-v22n.psf.gz" "setupcon -v -f" reported an error: putfont: KDFONTOP: Invalid argument due to passing the font filename twice: executing setfont -C /dev/tty1 /usr/local/share/fonts/ter-powerline- v22n.psf.gz /usr/local/share/fonts/ter-powerline-v22n.psf.gz. The problem is in /bin/setupcon where the collecting variable FONTFILES has the font added twice, once at the top of the for loop FONTFILES="$FONTFILES `findfile $fontdir $f`" and again at the bottom FONTFILES="$FONTFILES $RES" Removing the first assignment fixes it. FONTFILES='' echo "DEBUG: FONT=$FONT" if [ "$FONT" ]; then for f in $FONT; do echo "DEBUG: for loop" FONTFILES="$FONTFILES `findfile $fontdir $f`" RES=`findfile $fontdir $f` if [ -z "$RES" ]; then fdec="${f%.gz}" RES=`findfile $fontdir $fdec` fi FONTFILES="$FONTFILES $RES" done fi FONTFILES=`echo $FONTFILES` # remove extra spaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1763100/+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 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot
> /sbin/shutdown, post upgrade not working, imho is a severe bug I suspect no-one's bothered to report it because as soon as the machine is (somehow) rebooted, the issue goes away (and reproduction then involves the pain of going through a trusty install + xenial upgrade cycle). Still, I'm not entirely convinced this *is* a bug; I'll come back to this in a bit below... > I guess the scheduling of timeout is failing, but /sbin/shutdown now works? I thought I'd tested this and concluded it didn't, but it turns out I just didn't wait long enough. When trying "shutdown -r now" there's a fair delay, then it complains about a connection time out, exits with an error, and the system reboots anyway! ubuntu@client1:~$ sudo shutdown -r now Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. ubuntu@client1:~$ packet_write_wait: Connection to 10.123.236.170 port 22: Broken pipe So, it is mostly likely the scheduling portion that's failing, and if given an immediate request the operation does still work. I haven't got time to test the -h switch as well, but I'd assume it's probably a similar story. Now consider those two cases from the perspective of a human administrator: If you've typed "shutdown -r now" you're expecting an immediate reboot. Even if some bits of the shutdown command fail, you still expect it to do what you asked: reboot immediately. However, if you've just typed "shutdown -r +5" you're expecting a 5 minute delay before reboot. If it can't schedule that delay would you rather it exit with an error and tell you, or just immediately reboot the system? Probably the former given you're not expecting an immediate reboot. The issue in this case was that it isn't a human scheduling the reboot (directly) and the only reason landscape uses the schedule at all is to determine whether the shutdown command has (likely) worked. Which is a bit of an abuse of the shutdown command's scheduling facility, but I can't think of a better way off the top of my head (that'll reliably work in all implementations). Anyway, in landscape's case we *would* rather the system immediately reboots when shutdown fails because the delay's only there for the Landscape client's benefit, and we can't guarantee the administrator has any other means of accessing the system for the purpose of rebooting it. So in a sense we're dealing with an interface mismatch: shutdown is (understandably) written for the (direct) use of a human administrator, and landscape is (ab)using it to provide reboot/poweroff facilities on (indirect) behalf of a human administrator. So we come back to "I can't think of a better way of doing it" (that'll reliably work in all our aforementioned scenarios of upstart, systemd, and post-upgrade-almost-sort-of-systemd). > Re differences between halt & poweroff, in systemd, eventually it results in: > [snip] Yes, but have a look at the arg parsing earlier on (https://github.com/systemd/systemd/blob/master/src/systemctl/systemctl.c#L8069): case 'h': if (arg_action != ACTION_HALT) arg_action = ACTION_POWEROFF; break; In systemd, the -H and --halt options mean halt, but -h is just an alias for -P and --poweroff (unless -H or --halt also appear in the argument list ... which looks a bit weird to me, but it is what their man-page states as well, so I guess it's intentional?). I haven't dug into upstart's implementation but I assume from your comments that it's different, and that -h actually means halt. Thanks for the link on the differences between halt and power-off - I'd not seen that before! -- 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/1670291 Title: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot Status in landscape-client package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Incomplete Status in landscape-client source package in Xenial: Confirmed Status in systemd source package in Xenial: Incomplete Bug description: Used Landscape (Paid Canonical Subscription) to upgrade one of my machines. Landscape only shows "In Progress" for more than 8 hours now and asked for a reboot of the machine in a second alert. In the reboot attempt I get the message: = Failed to set wall message, ignoring: Method "SetWallMessage" with signature "sb" on interface "org.freedesktop.login1.Manager" doesn't exist Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Method "ScheduleShutdown" with signature "st" on interface "org.freedesktop.login1.Manager" doesn't exist = Steps to reproduce: * Fully updated 14.04.5 machine * Open Landscape * Choose the machine * Choose Packages * This computer can be upgraded to a newer release
[Touch-packages] [Bug 1638634] Re: Print Job with Authentication is postponed until queue is opened manually
The printer model is a RICOH MP C3003. -- 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/1638634 Title: Print Job with Authentication is postponed until queue is opened manually Status in cups package in Ubuntu: New Bug description: I am connected to a print host requiring authentication. The authentication data is already stored in CUPS. I can issue a new print job and the printer icon in the panel appears, but the job isn't started, until I open the queue of the respective printer. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-09-15 (1077 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for 0_prost: lpd://prost.uni-koblenz.de/ device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14 device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390 MachineType: LENOVO 20BX000XGE Package: cups 2.1.3-4ubuntu0.5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied grep: /etc/cups/ppd/0_prost.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-30.32~16.04.1-generic 4.15.18 Tags: xenial Uname: Linux 4.15.0-30-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-04-22 (857 days ago) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo tty uucp vboxusers _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: JBET66WW (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BX000XGE dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET66WW(1.30):bd09/13/2017:svnLENOVO:pn20BX000XGE:pvrThinkPadT450s:rvnLENOVO:rn20BX000XGE:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BX000XGE dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638634/+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 1638634] Re: Print Job with Authentication is postponed until queue is opened manually
> Did this work in a previous version of Ubuntu? I don't remember, this is >2,5 years from today, but I'm relatively sure that it didn't work back then also. > You mention a print host. Is it another computer with Ubuntu on it? If > so, what is the version of cups on the print host? Yes, this is another host (why should I have to authenticate otherwise?). I don't know the OS of this system since it is run by operators. According to its webinterface, the CUPS version is: 1.5.4. > And when you open the print queue, are you opening it on your local > computer or on the print host? I open the queue on my computer. > And just to confirm, it is a Brother MFC-9332CDW - ricoh14 printer? No, there cannot be such thing as a "Brother ricoh" printer, as these are two different companies. The Brother MFC-9332CDW is used directly via LAN (at a different location) and works just fine. ricoh14 is the shortname of the printer in question. The exact printer model is: > Can you give me the exact steps you take to produce the problem? 1. Print an arbitrary document from an arbitrary application's print dialog (e.g. evince, Okular, GIMP, ReText,...). 2. Printing does not happen. 3. Open "system-config-printer" 4. Open the printer's print queue 5. All documents in the queue are processed, i.e. printed immediately. While re-reading my original bug report, it came to my mind that it may have been ambiguous what I meant by "open print queue". I *did not* mean the queue in CUPS but what I meant is the queue view available via GNOME (see above). Today I checked what happens when I take a look at the queue via CUPS. The job is listed there with the status "stopped" (notice that I translate the notions because my system runs in German). For controlling the job CUPSs offers me three buttons: - release job ("freigeben") - delete job - move job When I choose the first one, nothing happens, i.e. the message "job was released" is shown but the state does not change. I then start system-config-printer and only when I open the queue of the exact printer that should print, the print job is started immediately. I also tail'ed /var/log/cups/access.log today when I tested it. The log is attached. You can see the excerpt begins after the print job has been issued (Print-Job successful-ok). Nothing happens and after a time I open the printer's queue (system-config-printer). Upon opening the tool, the three "Create-Printer-Subscriptions" messages appear. Only when I open the queue, the message "CUPS-Authenticate-Job successful-ok" comes up and that is the moment the printer actually starts printing. ** Attachment added: "cupsaccesslog.txt" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1638634/+attachment/5184454/+files/cupsaccesslog.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1638634 Title: Print Job with Authentication is postponed until queue is opened manually Status in cups package in Ubuntu: New Bug description: I am connected to a print host requiring authentication. The authentication data is already stored in CUPS. I can issue a new print job and the printer icon in the panel appears, but the job isn't started, until I open the queue of the respective printer. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [10/Aug/2018:07:14:50 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [10/Aug/2018:08:42:31 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [11/Aug/2018:09:58:10 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [14/Aug/2018:10:30:32 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. E [28/Aug/2018:07:21:07 +0200] Missing value on line 2137 of /var/cache/cups/job.cache. CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-09-15 (1077 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for 0_prost: lpd://prost.uni-koblenz.de/ device for 0_ricoh14: ipp://printhost.uni-koblenz.de:631/printers/ricoh14 device for MFC9332CDW: dnssd://Brother%20MFC-9332CDW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af424f390 MachineType: LENOVO 20BX000XGE Package: cups 2.1.3-4ubuntu0.5 PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/MFC9332CDW.ppd', '/etc/cups/ppd/0_prost.ppd'] failed with exit code 2: grep: /etc/cups/ppd/MFC9332CDW.ppd: Permission denied grep: /etc/cups/ppd/0_prost.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic root=UUID=93fc15f9-4090-40ff-a3ac-a642833f1da2 ro quiet splash vt.handoff=7
[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
** Summary changed: - Regression: packagekit crashes updating itslef to 1.1.9-1ubuntu2.18.04.1 + Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: New Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+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 1790613] [NEW] Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1
Public bug reported: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. ** Affects: packagekit (Ubuntu) Importance: Undecided Status: New ** Tags: regression-update ** Tags added: regression-update -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1790613 Title: Regression: packagekit crashes updating itself to 1.1.9-1ubuntu2.18.04.1 Status in packagekit package in Ubuntu: New Bug description: Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run
[Touch-packages] [Bug 1698083] Re: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions)
** Also affects: gtk Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Middle-click titlebar actions (like maximizing vertically) don't work (for all apps in Wayland sessions, and CSD apps in Xorg sessions) Status in GTK+: New Status in gnome-shell package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+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