[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)
This bug was fixed in the package git - 1:2.20.1-2ubuntu1 --- git (1:2.20.1-2ubuntu1) disco; urgency=medium * Merge with Debian; remaining change: - Build diff-highlight in the contrib dir (closes: #868871, LP: #1713690) * Dropped change: - Build against pcre3 (pcre2 is now in main) (LP: #1792544) git (1:2.20.1-2) unstable; urgency=low * package git-gui: actually Suggests: meld for mergetool support; describe what meld is used for in package description (thx Jens Reyer; closes: #707790). * package gitweb: Depends: libhttp-date-perl | libtime-parsedate-perl instead of ... | libtime-modules-perl (thx gregor herrmann; closes: #879165). * debian/control: use https in Vcs-Browser URL. * debian/rules: build and test quietly if DEB_BUILD_OPTIONS=terse. * debian/control: Standards-Version: 4.3.0.1. git (1:2.20.1-1) unstable; urgency=medium * new upstream point release (see RelNotes/2.20.1.txt). * package git-gui: Suggests: meld for mergetool support (thx Jens Reyer; closes: #707790). git (1:2.20.0-1) unstable; urgency=medium * new upstream release (see RelNotes/2.20.0.txt). * package git: Recommends: ca-certificates for https support (thx HJ; closes: #915644). git (1:2.20.0~rc2-1) unstable; urgency=low * new upstream release candidate. * rebase: specify 'rebase -i' in reflog for interactive rebase (closes: #914695). git (1:2.20.0~rc1-1) unstable; urgency=low * new upstream release candidate (see RelNotes/2.20.0.txt). * debian/rules: target clean: don't remove t/t4256/1/mailinfo.c.orig. git (1:2.19.2-1) unstable; urgency=high * new upstream point release (see RelNotes/2.19.2.txt). * run-command: do not fall back to cwd when command is not in $PATH. -- Jeremy Bicha Wed, 23 Jan 2019 11:30:48 -0500 ** Changed in: git (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 grep in Ubuntu. https://bugs.launchpad.net/bugs/1792544 Title: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x) Status in aide package in Ubuntu: Incomplete Status in anope package in Ubuntu: Incomplete Status in apache2 package in Ubuntu: Triaged Status in apr-util package in Ubuntu: Fix Released Status in clamav package in Ubuntu: Fix Released Status in exim4 package in Ubuntu: Incomplete Status in freeradius package in Ubuntu: Incomplete Status in git package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Incomplete Status in grep package in Ubuntu: Incomplete Status in haproxy package in Ubuntu: Fix Released Status in libpam-mount package in Ubuntu: Fix Released Status in libselinux package in Ubuntu: Triaged Status in nginx package in Ubuntu: Incomplete Status in nmap package in Ubuntu: Incomplete Status in pcre3 package in Ubuntu: Confirmed Status in php-defaults package in Ubuntu: Triaged Status in php7.2 package in Ubuntu: Won't Fix Status in postfix package in Ubuntu: Incomplete Status in python-pyscss package in Ubuntu: Incomplete Status in quagga package in Ubuntu: Invalid Status in rasqal package in Ubuntu: Incomplete Status in slang2 package in Ubuntu: Incomplete Status in sssd package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Triaged Status in ubuntu-core-meta package in Ubuntu: New Status in vte2.91 package in Ubuntu: Fix Released Status in wget package in Ubuntu: Fix Released Status in zsh package in Ubuntu: Incomplete Bug description: https://people.canonical.com/~ubuntu- archive/transitions/html/pcre2-main.html demotion of pcre3 in favor of pcre2. These packages need analysis what needs to be done for the demotion of pcre3: Packages which are ready to build with pcre2 should be marked as 'Triaged', packages which are not ready should be marked as 'Incomplete'. -- For clarification: pcre2 is actually newer than pcre3. pcre3 is just poorly named. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
The new mount implementation from util-linux seems to break the test, continuing triaging. ** Package changed: livecd-rootfs (Ubuntu) => util-linux (Ubuntu) ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: Invalid Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: Confirmed Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805178] Re: Apparmor should include letsencrypt directory for Slapd
[Expired for openldap (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openldap (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1805178 Title: Apparmor should include letsencrypt directory for Slapd Status in openldap package in Ubuntu: Expired Bug description: Apparmor denies access to /etc/letsencrypt for slapd, which is confusing for users trying to secure ldap with Letsencrypt in a stock configuration. The fix is inserting the following line in /etc/apparmor.d/usr.sbin.slapd: /etc/letsencrypt/** r, and then refreshing the profile: # apparmor_parser -vr usr.sbin.slapd This line should simply be included. tarek : ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1805178/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: oem-priority Status: Triaged => 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/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released 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 1813843] Re: Xorg crash
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813843 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: With the newest updates to 18 & with the HP VGA monitor attached I can enter the pswd but will NOT get to the home screen. It hangs at a black screen. If I detach the VGA cable I can power down and boot up to the internal Laptop screen then attach the VGA after logging into Ubuntu. All is fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 14:28:59 2019 DistUpgraded: 2018-09-13 08:18:43,679 DEBUG got a conffile-prompt from dpkg for file: '/etc/NetworkManager/NetworkManager.conf' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:221e] NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK106GLM [Quadro K2100M] [17aa:221e] InstallationDate: Installed on 2014-12-13 (1508 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20BG0016US ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=6f412d93-ba4b-4a3a-a067-9d615e154680 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago) dmi.bios.date: 01/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET70WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET70WW(2.18):bd01/12/2015:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jan 29 14:14:34 2019 xserver.configfile: default xserver.errors: NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1813843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813846] Re: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg
It appears you might have briefly run out of disk space. Please try running this command: sudo apt install --reinstall ubuntu-mobile-icons and send us the output from that command. ** Changed in: ubuntu-themes (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1813846 Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu- mobile/status/scalable/nm-signal-25.svg': No space left on device Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: Si è verificato un problema durante l'installazione del software. Pacchetto: gnome-icon-theme 3.12.0-1ubuntu3 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-mobile-icons (not installed) ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:54:21 2019 DuplicateSignature: package:ubuntu-mobile-icons:(not installed):error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device ErrorMessage: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: ubuntu-themes Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1813846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1806532] Re: The line-out on the Dell Dock station can't work
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1806532 Title: The line-out on the Dell Dock station can't work Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in alsa-lib package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: Fix Released Status in alsa-lib source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: New Status in alsa-lib source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: New Bug description: [Impact] On the Dell thunderbolt docs stations (WD15 and WD19), there are two playback devices, one is headphone, the other is line-out, but there is no UCM for these docks yet, so the pluseaudio only can handle the 1st playback device, need us to add the UCM for them, before adding UCM, we need to set the longname of the sound card in the linux kernel. [Fix] For Linux kernel: Cherry-picked 3 upstream patches, these patches add the longname of the sound card for the dock station. For alsa-lib: Cherry-picked 3 upstream patches from alsa-lib, these will add ucm configuration files for Dell WD15&19, and change the SPDIF conf in the USB-AUDIO.conf. [Test Case] Open the gnome-sound-setting, we can choose headphone-usb and lineout-usb from UI, and play sound via these devices [Regression Potential] Very low, these patches come from upstream, and the change is only specific to WD15 and WD19 dock station. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1806532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813759] Re: Scale display doesn't work with an external monitor attached
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Tags added: hidpi multimonitor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813759 Title: Scale display doesn't work with an external monitor attached Status in gnome-shell package in Ubuntu: Incomplete Bug description: I have a Dell XPS 13" (2018) connected to an LG 4K 32" display thru USB-C cable. both screens are supposed to have the same resolution, but the laptop one uses 200% of scale setting due to small size. When the laptop is connected to the external display, the scale setting does nothing and almost everything looks pretty small and hard to read, only gnome-terminal content seems to follow the scaling setting but windows decorators and app menus are pretty small. If I disconnect the external display everything works as expected (at least with the usual apps like GNOME apps, Firefox, Chrome, etc...). I'm using Ubuntu 18.10 with latest updates installed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:08:45 2019 DistUpgraded: 2019-01-05 13:19:27,114 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2019-01-05 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=UUID=0331a22b-f276-4072-83bb-95f04eb8ba77 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-01-05 (23 days ago) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813784] Re: tried to install skype and got this
It sounds like you might have downloaded skypeforlinux from an unsupported location. Where did you get it? ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813784 Title: tried to install skype and got this Status in Ubuntu: Incomplete Bug description: The following packages have unmet dependencies: skypeforlinux:amd64 : Depends: libasound2:amd64 (>= 1.0.16) but it is not installable Depends: libatk1.0-0:amd64 (>= 1.12.4) but it is not installable Depends: libc6:amd64 (>= 2.17) but it is not installable Depends: libcairo2:amd64 (>= 1.6.0) but it is not installable Depends: libcups2:amd64 (>= 1.4.0) but it is not installable Depends: libexpat1:amd64 (>= 2.0.1) but it is not installable Depends: libgcc1:amd64 (>= 1:4.0) but it is not installable Depends: libgconf-2-4:amd64 (>= 3.2.5) but it is not installable Depends: libgdk-pixbuf2.0-0:amd64 (>= 2.22.0) but it is not installable Depends: libglib2.0-0:amd64 (>= 2.35.8) but it is not installable Depends: libgtk-3-0:amd64 (>= 3.9.10) but it is not installable Depends: libnspr4:amd64 (>= 2:4.9-2~) but it is not installable Depends: libnss3:amd64 (>= 2:3.13.4-2~) but it is not installable Depends: libpango-1.0-0:amd64 (>= 1.14.0) but it is not installable Depends: libpangocairo-1.0-0:amd64 (>= 1.14.0) but it is not installable Depends: libsecret-1-0:amd64 (>= 0.7) but it is not installable Depends: libx11-6:amd64 (>= 2:1.4.99.1) but it is not installable Depends: libx11-xcb1:amd64 but it is not installable Depends: libxcb1:amd64 (>= 1.6) but it is not installable Depends: libxcomposite1:amd64 (>= 1:0.3-1) but it is not installable Depends: libxcursor1:amd64 (> 1.1.2) but it is not installable Depends: libxdamage1:amd64 (>= 1:1.1) but it is not installable Depends: libxext6:amd64 but it is not installable Depends: libxfixes3:amd64 but it is not installable Depends: libxi6:amd64 (>= 2:1.2.99.4) but it is not installable Depends: libxrandr2:amd64 (>= 2:1.2.99.3) but it is not installable Depends: libxrender1:amd64 but it is not installable Depends: libxss1:amd64 but it is not installable Depends: libxtst6:amd64 but it is not installable Depends: apt-transport-https:amd64 but it is not installable Depends: libfontconfig1:amd64 (>= 2.11.0) but it is not installable Depends: libdbus-1-3:amd64 (>= 1.6.18) but it is not installable Depends: libstdc++6:amd64 (>= 4.8.1) but it is not installable N: Ignoring file '50unattended-upgrades.merge-error' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 29 16:24:10 2019 DistUpgraded: 2018-09-02 09:29:06,755 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] InstallationDate: Installed on 2017-04-11 (657 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: Hewlett-Packard HP 620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=64d43abe-1712-45a1-929c-7685beb99496 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-02 (149 days ag
[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
Thanks. Please also run 'xrandr' and send us the output. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655584] Re: systemd-udevd busyloops when nvidia kernel module fails to load
In case it is not clear, I am using the same VirtualBox raw disk facility as Ross Boylan to use the raw disk partition as a virtual disk. -- 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/1655584 Title: systemd-udevd busyloops when nvidia kernel module fails to load Status in systemd package in Ubuntu: Confirmed Bug description: On a machine where nvidia-367 is installed, but the driver won't attach (due to the nvidia card being older and requiring legacy drivers), systemd-udevd repeatedly attempts to load it anyway, causing high CPU and memory usage. I observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by top(1); restarting the service reduces resource usage momentarily, but it appears to be climbing back up (I suspect the number of events is growing). Workaround is of course installing the correct driver package, but udevd really ought not behave like this if something fails to load. Some journal entries for systemd-udevd.service: Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. dmesg shows repeated failures for loading the nvidia module: [1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this system is NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 367.57 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [1675406.587936] NVRM: No NVIDIA graphics adapter found! [1675406.588078] NVRM: NVIDIA init module failed! Release information: # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt policy systemd udev systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages udev: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647467] Re: InRelease file splitter treats getline() errors as EOF
> It allows for attacking a repository via MITM attacks, circumventing the signature of the InRelease file. > ("deb http://192.168.0.2:1337/debian/ jessie-updates main" or so). [..] This simulates a MITM attack or compromised mirror. That sounds like it matters, where that InRelease file comes from, right? When I look into my /etc/apt/sources.list, I only see deb/dev-src http://.archive.ubuntu.com/... entries. I think it would be much better, if Canonical servers would require TLS 1.x encryption (STS preferred) and thusly identify themselves with a proper cert, so machines/users can make sure (nation-state actors not taken into account) who they're talking to. I think that would definitely make MITM and MOTS attacks more difficult. I'm aware of the signatures, i.e. present package security, though. Nonetheless, they do not seem to address the problem of transport security. -- 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/1647467 Title: InRelease file splitter treats getline() errors as EOF Status in apt package in Ubuntu: Fix Released Status in apt source package in Trusty: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Yakkety: Fix Released Status in apt source package in Zesty: Fix Released Bug description: We have just been made aware of a security bug upstream that affects the validation of signatures on InRelease file. This bug is to track progress for it. It allows for attacking a repository via MITM attacks, circumventing the signature of the InRelease file. It works by making a call to getline() fail with ENOMEM, which is not documented as an error for that but follows from the fact that getline() can allocate memory. In such a case, apt would treat the first part of the file as a valid release file. = Original bug report = From: Jann Horn To: secur...@debian.org Cc: Date: Mon, 5 Dec 2016 18:33:09 +0100 Subject: apt: repository signing bypass via memory allocation failure == Vulnerability == When apt-get updates a repository that uses an InRelease file (clearsigned Release files), this file is processed as follows: First, the InRelease file is downloaded to disk. In a subprocess running the gpgv helper, "apt-key verify" (with some more arguments) is executed through the following callchain: gpgv.cc:main -> pkgAcqMethod::Run -> GPGVMethod::URIAcquire -> GPGVMethod::VerifyGetSigners -> ExecGPGV ExecGPGV() splits the clearsigned file into payload and signature using SplitClearSignedFile(), calls apt-key on these two files to perform the cryptographic signature verification, then discards the split files and only retains the clearsigned original. SplitClearSignedFile() ignores leading and trailing garbage. Afterwards, in the parent process, the InRelease file has to be loaded again so that its payload can be processed. At this point, the code isn't aware anymore whether the Release file was clearsigned or split-signed, so the file is opened using OpenMaybeClearSignedFile(), which first attempts to parse the file as a clearsigned (InRelease) file and extract the payload, then falls back to treating the file as the file as a split-signed (Release) file if the file format couldn't be recognized. The weakness here is: If an attacker can create an InRelease file that is parsed as a proper split-signed file during signature validation, but then isn't recognized by OpenMaybeClearSignedFile(), the "leading garbage" that was ignored by the signature validation is interpreted as repository metadata, bypassing the signing scheme. It first looks as if it would be impossible to create a file that is recognized as split-signed by ExecGPGV(), but isn't recognized by OpenMaybeClearSignedFile(), because both use the same function, SplitClearSignedFile(), for parsing the file. However, multiple executions of SplitClearSignedFile() on the same data can actually have different non-error results because of a bug. SplitClearSignedFile() uses getline() to parse the input file. A return code of -1, which signals that either EOF or an error occured, is always treated as EOF. The Linux manpage only lists EINVAL (caused by bad arguments) as possible error code, but because the function allocates (nearly) unbounded amounts of memory, it can actually also fail with ENOMEM if it runs out of memory. Therefore, if an attacker can cause the address space in the main apt-get process to be sufficiently constrained to prevent allocation of a large line buffer while the address space of the gpgv helper process is less constrained and permits the allocation of a buffer with the same size, the attacker can use this to fake an end-of-file condition in SplitClearSignedFile() that causes the file to be parsed as a normal Rel
[Touch-packages] [Bug 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
schamane, thanks for reporting back your success. I've seen this question asked a dozen times and never seen an answer documented. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655584] Re: systemd-udevd busyloops when nvidia kernel module fails to load
I've got the same problem. nvidia-384 was installed (using Software Updater, Settings, Additional Drivers) while booting the partition native (mbr). Natively, all works fine using nvidia-384 but this problem occurs when running in VirtualBox. I had to install nvidia-384 because I could not get a high resolution when booting native using nouveau drivers. -- 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/1655584 Title: systemd-udevd busyloops when nvidia kernel module fails to load Status in systemd package in Ubuntu: Confirmed Bug description: On a machine where nvidia-367 is installed, but the driver won't attach (due to the nvidia card being older and requiring legacy drivers), systemd-udevd repeatedly attempts to load it anyway, causing high CPU and memory usage. I observed the systemd-udevd process at 98% CPU usage and 2.5G RSS reported by top(1); restarting the service reduces resource usage momentarily, but it appears to be climbing back up (I suspect the number of events is growing). Workaround is of course installing the correct driver package, but udevd really ought not behave like this if something fails to load. Some journal entries for systemd-udevd.service: Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:11 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/usr/bin/nvidia-smi' failed with exit code 9. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-drm' failed with exit code 1. Jan 11 11:22:12 systemd-udevd[11651]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1. dmesg shows repeated failures for loading the nvidia module: [1675406.587926] NVRM: The NVIDIA GeForce 9300 GE GPU installed in this system is NVRM: supported through the NVIDIA 340.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 367.57 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [1675406.587936] NVRM: No NVIDIA graphics adapter found! [1675406.588078] NVRM: NVIDIA init module failed! Release information: # lsb_release -rd Description:Ubuntu 16.04.1 LTS Release:16.04 # apt policy systemd udev systemd: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages udev: Installed: 229-4ubuntu13 Candidate: 229-4ubuntu13 Version table: *** 229-4ubuntu13 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://ftp.funet.fi/pub/Linux/mirrors/ubuntu/archive xenial/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1655584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
Steps for a workaround by disabling gnome-keyring's SSH agent component, tested in Ubuntu 18.04.1: # disable GNOME Keyring's SSH Agent, cf. # https://askubuntu.com/a/585212/43108 + https://askubuntu.com/a/607563/43108 mkdir ~/.config/autostart cp /etc/xdg/autostart/gnome-keyring-ssh.desktop ~/.config/autostart echo Hidden=true >> ~/.config/autostart/gnome-keyring-ssh.desktop # add autostart .desktop for plain SSH Agent cat > ~/.config/autostart/ssh-agent.desktop
[Touch-packages] [Bug 1813845] Re: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1813845 Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device Status in openssl package in Ubuntu: New Bug description: Segnalazione crash: si è verificato un problema durante l'installazione del software. Pacchetto: ubuntu-mobile-icons 14.04+16.04.20180326-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl-doc 1.0.1f-1ubuntu2.21 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:52:10 2019 Dependencies: DuplicateSignature: package:libssl-doc:1.0.1f-1ubuntu2.21:unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device ErrorMessage: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssl Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1813845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813846] Re: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1813846 Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu- mobile/status/scalable/nm-signal-25.svg': No space left on device Status in ubuntu-themes package in Ubuntu: New Bug description: Si è verificato un problema durante l'installazione del software. Pacchetto: gnome-icon-theme 3.12.0-1ubuntu3 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-mobile-icons (not installed) ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:54:21 2019 DuplicateSignature: package:ubuntu-mobile-icons:(not installed):error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device ErrorMessage: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: ubuntu-themes Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1813846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813846] [NEW] package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.s
Public bug reported: Si è verificato un problema durante l'installazione del software. Pacchetto: gnome-icon-theme 3.12.0-1ubuntu3 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-mobile-icons (not installed) ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:54:21 2019 DuplicateSignature: package:ubuntu-mobile-icons:(not installed):error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device ErrorMessage: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: ubuntu-themes Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) ** Affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1813846 Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu- mobile/status/scalable/nm-signal-25.svg': No space left on device Status in ubuntu-themes package in Ubuntu: New Bug description: Si è verificato un problema durante l'installazione del software. Pacchetto: gnome-icon-theme 3.12.0-1ubuntu3 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: ubuntu-mobile-icons (not installed) ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:54:21 2019 DuplicateSignature: package:ubuntu-mobile-icons:(not installed):error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device ErrorMessage: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: ubuntu-themes Title: package ubuntu-mobile-icons (not installed) failed to install/upgrade: error creating symbolic link './usr/share/icons/ubuntu-mobile/status/scalable/nm-signal-25.svg': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1813846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1813843] Re: Xorg crash
If this is not it pls provide the commands a bit of a novice -W540:~$ journalctl -- Logs begin at Thu 2018-09-13 07:43:37 PDT, end at Tue 2019-01-29 15:05:21 PST Sep 13 07:43:37 rae-W540 systemd-journald[276]: Runtime journal (/run/log/journa Sep 13 07:43:37 rae-W540 kernel: microcode: CPU0 microcode updated early to revi Sep 13 07:43:37 rae-W540 kernel: Initializing cgroup subsys cpuset Sep 13 07:43:37 rae-W540 kernel: Initializing cgroup subsys cpu Sep 13 07:43:37 rae-W540 kernel: Initializing cgroup subsys cpuacct Sep 13 07:43:37 rae-W540 kernel: Linux version 4.4.0-135-generic (buildd@lcy01-a Sep 13 07:43:37 rae-W540 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13 Sep 13 07:43:37 rae-W540 kernel: KERNEL supported cpus: Sep 13 07:43:37 rae-W540 kernel: Intel GenuineIntel Sep 13 07:43:37 rae-W540 kernel: AMD AuthenticAMD Sep 13 07:43:37 rae-W540 kernel: Centaur CentaurHauls Sep 13 07:43:37 rae-W540 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2 Sep 13 07:43:37 rae-W540 kernel: x86/fpu: Supporting XSAVE feature 0x01: 'x87 fl Sep 13 07:43:37 rae-W540 kernel: x86/fpu: Supporting XSAVE feature 0x02: 'SSE re Sep 13 07:43:37 rae-W540 kernel: x86/fpu: Supporting XSAVE feature 0x04: 'AVX re Sep 13 07:43:37 rae-W540 kernel: x86/fpu: Enabled xstate features 0x7, context s Sep 13 07:43:37 rae-W540 kernel: e820: BIOS-provided physical RAM map: Sep 13 07:43:37 rae-W540 kernel: BIOS-e820: [mem 0x-0x00 Sep 13 07:43:37 rae-W540 kernel: BIOS-e820: [mem 0x0009d000-0x00 Sep 13 07:43:37 rae-W540 kernel: BIOS-e820: [mem 0x000e-0x00 Sep 13 07:43:37 rae-W540 kernel: BIOS-e820: [mem 0x0010-0x69 Sep 13 07:43:37 rae-W540 kernel: BIOS-e820: [mem 0x697ca000-0x7c lines 1-23 On Tue, Jan 29, 2019 at 2:55 PM Sebastien Bacher wrote: > Thank you for your bug report. could you add your journal log from a > boot having the issue? > > ** Changed in: xorg (Ubuntu) >Importance: Undecided => High > > ** Changed in: xorg (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1813843 > > Title: > Xorg crash > > Status in xorg package in Ubuntu: > Incomplete > > Bug description: > With the newest updates to 18 & with the HP VGA monitor attached I can > enter the pswd but will NOT get to the home screen. It hangs at a > black screen. > > If I detach the VGA cable I can power down and boot up to the internal > Laptop screen then attach the VGA after logging into Ubuntu. All is > fine > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 > Uname: Linux 4.15.0-44-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Tue Jan 29 14:28:59 2019 > DistUpgraded: 2018-09-13 08:18:43,679 DEBUG got a conffile-prompt from > dpkg for file: '/etc/NetworkManager/NetworkManager.conf' > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation 4th Gen Core Processor Integrated Graphics Controller > [8086:0416] (rev 06) (prog-if 00 [VGA controller]) > Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics > Controller [17aa:221e] >NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) > (prog-if 00 [VGA controller]) > Subsystem: Lenovo GK106GLM [Quadro K2100M] [17aa:221e] > InstallationDate: Installed on 2014-12-13 (1508 days ago) > InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 > (20140722.2) > MachineType: LENOVO 20BG0016US > ProcEnviron: >LANGUAGE=en_US >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic > root=UUID=6f412d93-ba4b-4a3a-a067-9d615e154680 ro quiet splash vt.handoff=1 > SourcePackage: xorg > Symptom: display > Title: Xorg crash > UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago) > dmi.bios.date: 01/12/2015 > dmi.bios.vendor: LENOVO > dmi.bios.version: GNET70WW (2.18 ) > dmi.board.asset.tag: Not Available > dmi.board.name: 20BG0016US > dmi.board.vendor: LENOVO > dmi.board.version: 0B98401 Pro > dmi.chassis.asset.tag: No Asset Information > dmi.chassis.type: 10 > dmi.chassis.vendor: LENOVO > dmi.chassis.version: Not Available > dmi.modalias: > dmi:bvnLENOVO:bvrGNET70WW(2.18):bd01/12/2015:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: > dmi.product.family: ThinkPad W540 > dmi.product.name: 20BG0016US > dmi.product.vers
[Touch-packages] [Bug 1813845] [NEW] package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left o
Public bug reported: Segnalazione crash: si è verificato un problema durante l'installazione del software. Pacchetto: ubuntu-mobile-icons 14.04+16.04.20180326-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl-doc 1.0.1f-1ubuntu2.21 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:52:10 2019 Dependencies: DuplicateSignature: package:libssl-doc:1.0.1f-1ubuntu2.21:unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device ErrorMessage: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssl Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1813845 Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device Status in openssl package in Ubuntu: New Bug description: Segnalazione crash: si è verificato un problema durante l'installazione del software. Pacchetto: ubuntu-mobile-icons 14.04+16.04.20180326-0ubuntu1 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libssl-doc 1.0.1f-1ubuntu2.21 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 Date: Tue Jan 29 23:52:10 2019 Dependencies: DuplicateSignature: package:libssl-doc:1.0.1f-1ubuntu2.21:unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device ErrorMessage: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device InstallationDate: Installed on 2014-06-28 (1676 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: openssl Title: package libssl-doc 1.0.1f-1ubuntu2.21 failed to install/upgrade: unable to make backup symlink for './usr/share/man/man3/BIO_get_callback.3ssl.gz': No space left on device UpgradeStatus: Upgraded to trusty on 2019-01-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1813845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813843] Re: Xorg crash
Thank you for your bug report. could you add your journal log from a boot having the issue? ** Changed in: xorg (Ubuntu) Importance: Undecided => High ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813843 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: With the newest updates to 18 & with the HP VGA monitor attached I can enter the pswd but will NOT get to the home screen. It hangs at a black screen. If I detach the VGA cable I can power down and boot up to the internal Laptop screen then attach the VGA after logging into Ubuntu. All is fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 14:28:59 2019 DistUpgraded: 2018-09-13 08:18:43,679 DEBUG got a conffile-prompt from dpkg for file: '/etc/NetworkManager/NetworkManager.conf' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:221e] NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK106GLM [Quadro K2100M] [17aa:221e] InstallationDate: Installed on 2014-12-13 (1508 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20BG0016US ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=6f412d93-ba4b-4a3a-a067-9d615e154680 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago) dmi.bios.date: 01/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET70WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET70WW(2.18):bd01/12/2015:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jan 29 14:14:34 2019 xserver.configfile: default xserver.errors: NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813843/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813843] [NEW] Xorg crash
Public bug reported: With the newest updates to 18 & with the HP VGA monitor attached I can enter the pswd but will NOT get to the home screen. It hangs at a black screen. If I detach the VGA cable I can power down and boot up to the internal Laptop screen then attach the VGA after logging into Ubuntu. All is fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 14:28:59 2019 DistUpgraded: 2018-09-13 08:18:43,679 DEBUG got a conffile-prompt from dpkg for file: '/etc/NetworkManager/NetworkManager.conf' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:221e] NVIDIA Corporation GK106GLM [Quadro K2100M] [10de:11fc] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK106GLM [Quadro K2100M] [17aa:221e] InstallationDate: Installed on 2014-12-13 (1508 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 20BG0016US ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=UUID=6f412d93-ba4b-4a3a-a067-9d615e154680 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-09-13 (138 days ago) dmi.bios.date: 01/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: GNET70WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET70WW(2.18):bd01/12/2015:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Jan 29 14:14:34 2019 xserver.configfile: default xserver.errors: NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: High Status: Incomplete ** Tags: amd64 apport-bug bionic crash ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813843 Title: Xorg crash Status in xorg package in Ubuntu: Incomplete Bug description: With the newest updates to 18 & with the HP VGA monitor attached I can enter the pswd but will NOT get to the home screen. It hangs at a black screen. If I detach the VGA cable I can power down and boot up to the internal Laptop screen then attach the VGA after logging into Ubuntu. All is fine ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 14:28:59 2019 DistUpgraded: 2018-09-13 08:18:43,679 DEBUG got a conffile-prompt from dpkg for file: '/etc/NetworkManager/NetworkManager.conf' DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:221e] NVIDIA Corporation GK106GLM [Quadro K2100M
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Si claro, luego te dirá de pasar a la 18-04. Saludos El mar., 29 ene. 2019 22:50, juan angel Mora <1773...@bugs.launchpad.net> escribió: > La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5 > LTS. > Vale la pena actualizarla? > Graacias > > > El mar., 29 ene. 2019 a las 22:30, José Enrique (< > 1773...@bugs.launchpad.net>) > escribió: > > > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no > > quieras perder y actualizarla a 18-04. > > Funcionar funciona pero estás a punto de que no se actualice más, y > puedes > > tener problemas de seguridad, ojo se trata de una actualización > importante, > > que debes realizar, seguramente en dos pasos, dos actualizaciones > > parciales. Primero a 16 y luego a 18-04. > > Configura el gestor de actualizaciones a versiones LTS, no obstante la > > 18-04 tiene soporte para 10 años. > > Saludos > > > > El mar., 29 ene. 2019 22:15, juan angel Mora <1773...@bugs.launchpad.net > > > > escribió: > > > > > Muchas gracias por la información. > > > Si no es mucho consultarte, a veces cuando me pide actualizaciones las > > hago > > > y luego me dice que tengo el Ubuntu 14. , que si lo quiero > actualizar a > > > la ultima versión 16. y no lo hago por miedo a que se me desbarate > todo > > > de nuevo, cual es tu consejo? > > > Un saludo > > > > > > > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray () > > > escribió: > > > > > > > The upload of systemd that was purported to fix this bug report was > > > > superseded by a security update of systemd so the fix is no longer > > > > available. > > > > > > > > ** Changed in: systemd (Ubuntu Bionic) > > > >Status: Fix Committed => Triaged > > > > > > > > -- > > > > You received this bug notification because you are subscribed to a > > > > duplicate bug report (1787843). > > > > https://bugs.launchpad.net/bugs/1773859 > > > > > > > > Title: > > > > upgrades to 18.04 fail > > > > > > > > Status in systemd package in Ubuntu: > > > > Fix Released > > > > Status in systemd-shim package in Ubuntu: > > > > Won't Fix > > > > Status in systemd source package in Bionic: > > > > Triaged > > > > Status in systemd-shim source package in Bionic: > > > > Won't Fix > > > > Status in systemd source package in Cosmic: > > > > Fix Released > > > > Status in systemd-shim source package in Cosmic: > > > > Won't Fix > > > > > > > > Bug description: > > > > [Impact] > > > > > > > >* Some systems fail to upgrade due to conflicts between systemd > and > > > > the (now removed from the archive) systemd-shim / upstart. > > > > > > > >* Instead of trying to work out what's the problem in ordering / > > > > removal of diverts, ensure that systemd is never unpacked whilst > > > > systemd-shim/upstart are still on disk. Thus declare conflicts > > against > > > > systemd-shim/upstart packages in systemd package. > > > > > > > > [Test Case] > > > > > > > >* monitor drop-off of upgrades with below reported problem > > > > > > > >* Check that it is possible to upgrade to bionic's libpam-systemd > > > > from xenial with systemd-shim installed on xenial, ie. > > > > > > > > lxc launch ubuntu-daily:xenial test-shim-upgrade > > > > lxc exec test-shim-upgrade > > > > apt update > > > > apt install systemd-shim > > > > wget > > > > > > > > > > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > > > > apt install ./systemd-shim_10-3_amd64.deb > > > > sed 's/xenial/bionic/' -i /etc/apt/sources.list > > > > apt update > > > > apt install systemd > > > > > > > > this currently passes, however, systemd-shim remains installed. It > > > > should be removed instead. Apt install systemd should have lines > like > > > > this: > > > > > > > > The following packages will be REMOVED: > > > > systemd-shim > > > > ... > > > > Removing 'diversion of > > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > > > > > > > > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > > > by systemd-shim' > > > > ... > > > > > > > > > > > > [Regression Potential] > > > > > > > >* systemd-shim/upstart are both removed and not supported in > bionic, > > > > thus forcing their removal via conflicts should bring the system > into > > > > an expected state. > > > > > > > > [Other Info] > > > > > > > >* original bug report > > > > > > > > $ sudo apt upgrade > > > > Reading package lists... Done > > > > Building dependency tree > > > > Reading state information... Done > > > > Calculating upgrade... Done > > > > The following packages will be REMOVED: > > > > systemd-shim > > > > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > > > > 1 not fully installed or removed. > > > > After this operation, 71.7 kB disk space will be freed. > > > > Do you want to continue? [Y/n] y > > > > (Reading database ... 63 files and directories curr
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
** Changed in: libunistring (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: In Progress Status in libunistring package in Debian: New Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1804487] Re: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled
** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1804487 Title: systemd-resolved has issues when the answer is over 512 bytes with EDNS disabled Status in systemd: Fix Released Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Invalid Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: Fix Released Status in systemd package in Debian: Fix Released Bug description: [Impact] TCP stub is cutting down the payload to 512 bytes when EDNS is disabled. This makes non-EDNS clients (nslookup) receive a "shortened" answer even when UDP returns a truncated reply for a new TCP query. For instance, - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 In the second case, no-EDNS, TCP should provide the complete answer, but it's capped at UDP's size. [Test Case] Query systemd-resolved with a domain name that resolves to multiple (lots.. 30+) A records. A client with EDNS support (dig) will receive all of them, a client without support (nslookup or dig +noedns) will have a truncated list. Using the example above: EDNS: dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l non-EDNS: dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l [Regression potential] Minimal. This change only affects TCP requests, and the new size is already used in the code for other requests. [Other Info] Upstream bug: https://github.com/systemd/systemd/issues/10816 Fixed upstream with commit: https://github.com/systemd/systemd/commit/e6eed9445956cfa496e1db933bfd3530db23bfce [Original Description] Querying a domain name that has >512 bytes in records (e.g. 30+ A records), the number of results depends on the DNS client used: - If the client supports EDNS: $ dig +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 30 - If the client does not support EDNS: $ dig +noedns +noall +answer testing.irongiantdesign.com @127.0.0.53 | wc -l 29 Normally a client that doesn't support EDNS would receive a truncated reply from the initial UDP connection (limited by the spec to 512 bytes) and a second query would be established via TCP to receive the complete results. In this case, the number of results is the same regardless of the protocol used (29). Upstream bug: https://github.com/systemd/systemd/issues/10816 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1804487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
La que tengo es la 14.04 y la que me ofrece para actualizar es la 16.04.5 LTS. Vale la pena actualizarla? Graacias El mar., 29 ene. 2019 a las 22:30, José Enrique (<1773...@bugs.launchpad.net>) escribió: > Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no > quieras perder y actualizarla a 18-04. > Funcionar funciona pero estás a punto de que no se actualice más, y puedes > tener problemas de seguridad, ojo se trata de una actualización importante, > que debes realizar, seguramente en dos pasos, dos actualizaciones > parciales. Primero a 16 y luego a 18-04. > Configura el gestor de actualizaciones a versiones LTS, no obstante la > 18-04 tiene soporte para 10 años. > Saludos > > El mar., 29 ene. 2019 22:15, juan angel Mora <1773...@bugs.launchpad.net> > escribió: > > > Muchas gracias por la información. > > Si no es mucho consultarte, a veces cuando me pide actualizaciones las > hago > > y luego me dice que tengo el Ubuntu 14. , que si lo quiero actualizar a > > la ultima versión 16. y no lo hago por miedo a que se me desbarate todo > > de nuevo, cual es tu consejo? > > Un saludo > > > > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray () > > escribió: > > > > > The upload of systemd that was purported to fix this bug report was > > > superseded by a security update of systemd so the fix is no longer > > > available. > > > > > > ** Changed in: systemd (Ubuntu Bionic) > > >Status: Fix Committed => Triaged > > > > > > -- > > > You received this bug notification because you are subscribed to a > > > duplicate bug report (1787843). > > > https://bugs.launchpad.net/bugs/1773859 > > > > > > Title: > > > upgrades to 18.04 fail > > > > > > Status in systemd package in Ubuntu: > > > Fix Released > > > Status in systemd-shim package in Ubuntu: > > > Won't Fix > > > Status in systemd source package in Bionic: > > > Triaged > > > Status in systemd-shim source package in Bionic: > > > Won't Fix > > > Status in systemd source package in Cosmic: > > > Fix Released > > > Status in systemd-shim source package in Cosmic: > > > Won't Fix > > > > > > Bug description: > > > [Impact] > > > > > >* Some systems fail to upgrade due to conflicts between systemd and > > > the (now removed from the archive) systemd-shim / upstart. > > > > > >* Instead of trying to work out what's the problem in ordering / > > > removal of diverts, ensure that systemd is never unpacked whilst > > > systemd-shim/upstart are still on disk. Thus declare conflicts > against > > > systemd-shim/upstart packages in systemd package. > > > > > > [Test Case] > > > > > >* monitor drop-off of upgrades with below reported problem > > > > > >* Check that it is possible to upgrade to bionic's libpam-systemd > > > from xenial with systemd-shim installed on xenial, ie. > > > > > > lxc launch ubuntu-daily:xenial test-shim-upgrade > > > lxc exec test-shim-upgrade > > > apt update > > > apt install systemd-shim > > > wget > > > > > > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > > > apt install ./systemd-shim_10-3_amd64.deb > > > sed 's/xenial/bionic/' -i /etc/apt/sources.list > > > apt update > > > apt install systemd > > > > > > this currently passes, however, systemd-shim remains installed. It > > > should be removed instead. Apt install systemd should have lines like > > > this: > > > > > > The following packages will be REMOVED: > > > systemd-shim > > > ... > > > Removing 'diversion of > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > > > > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > > by systemd-shim' > > > ... > > > > > > > > > [Regression Potential] > > > > > >* systemd-shim/upstart are both removed and not supported in bionic, > > > thus forcing their removal via conflicts should bring the system into > > > an expected state. > > > > > > [Other Info] > > > > > >* original bug report > > > > > > $ sudo apt upgrade > > > Reading package lists... Done > > > Building dependency tree > > > Reading state information... Done > > > Calculating upgrade... Done > > > The following packages will be REMOVED: > > > systemd-shim > > > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > > > 1 not fully installed or removed. > > > After this operation, 71.7 kB disk space will be freed. > > > Do you want to continue? [Y/n] y > > > (Reading database ... 63 files and directories currently > > installed.) > > > Removing systemd-shim (9-1bzr4ubuntu1) ... > > > Removing 'diversion of > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > > > > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > > by systemd-shim' > > > dpkg-divert: error: rename involves overwriting > > > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' > wit
[Touch-packages] [Bug 1811447] Re: update-initramfs generates wrong RESUME if no swap + zram
*** This bug is a duplicate of bug 1781746 *** https://bugs.launchpad.net/bugs/1781746 ** Tags removed: rls-bb-incoming ** This bug has been marked a duplicate of bug 1781746 [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1811447 Title: update-initramfs generates wrong RESUME if no swap + zram Status in initramfs-tools package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: On a system with swap disabled (removed from /etc/fstab) and package zram-config installed update-initramfs -u will emit something like following: I: The initramfs will attempt to resume from /dev/zram1 I: (UUID=1d4b8573-7eee-43c9-a02a-10a65fc17b8a) I: Set the RESUME variable to override this. Obviously, resuming from zram device without actual non-volatile storage is not going to work. update-initramfs should be fixed to ignore /dev/zram* because otherwise the user must e.g. create file /etc/initramfs-tools/conf.d/resume-none with case-sensitive contents RESUME=none to workaround the issue, which may be a bit hard to guess from the above notice only. See also, somewhat related bug: 1781746 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3.6 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-lowlatency 4.18.17 Uname: Linux 4.18.0-13-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 11 19:10:41 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1811447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781746] Re: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap
While it does appear to be a simple 3 line patch and may apply cleanly the resume hook seems to have been modified heavily and the ephemeral variable does not appear in the rest of the hook, so while it would be set nothing would change with the behavior. ** Tags removed: rls-bb-incoming ** Tags added: rls-dd-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781746 Title: [SRU] Slow startup with zram-config installed (/dev/zram0) or encrypted swap Status in Default settings and artwork for Baltix OS: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in zram-config package in Ubuntu: Confirmed Status in initramfs-tools package in Debian: Fix Released Bug description: [Impact] Ubuntu 18.04 startup slowdowns for 30-120 seconds when zram swap is enabled (for example zram-config installed) or swap is encrypted. Today lots of users have SSD instead of HDD disk drives and use zram swap instead of swap partition or swap file, but if initrd is generated when zram swap is enabled then system can become "unbootable" from the user's perspective (Users with SSD storage doesn't wait 2 or more minutes...) This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d [Test Case] Install zram-config package and regenerate and initrd, for example with sudo update-initramfs -u When generating initrd I get this message in terminal: I: The initramfs will attempt to resume from /dev/zram0 I: (UUID=e380356c-767e-4265-98da-8be62ad28569) I: Set the RESUME variable to override this.###.] So the local-premount script in initramfs was waiting for a swap device that was not available, until it timed out. The relevant message was gave up waiting for suspend/resume device. [Regression Potential] None, patch simply adds case for /dev/zram*: 60case "$resume_auto" in 61/dev/zram*) 62ephemeral=true 63;; 64esac [Other Info] Manual method to disable this (as resuming from swap is not possible with an encrypted or zram swap): modify file /etc/initramfs-tools/conf.d/resume - add (or change) line RESUME=none (instead of the UUID that was here) will disable waiting for a resume device. and run sudo update-initramfs -u to apply the changes. To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1781746/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Hola no te preocupes. Yo haría un back-up de los datos y archivos, que no quieras perder y actualizarla a 18-04. Funcionar funciona pero estás a punto de que no se actualice más, y puedes tener problemas de seguridad, ojo se trata de una actualización importante, que debes realizar, seguramente en dos pasos, dos actualizaciones parciales. Primero a 16 y luego a 18-04. Configura el gestor de actualizaciones a versiones LTS, no obstante la 18-04 tiene soporte para 10 años. Saludos El mar., 29 ene. 2019 22:15, juan angel Mora <1773...@bugs.launchpad.net> escribió: > Muchas gracias por la información. > Si no es mucho consultarte, a veces cuando me pide actualizaciones las hago > y luego me dice que tengo el Ubuntu 14. , que si lo quiero actualizar a > la ultima versión 16. y no lo hago por miedo a que se me desbarate todo > de nuevo, cual es tu consejo? > Un saludo > > > El lun., 28 ene. 2019 a las 19:35, Brian Murray () > escribió: > > > The upload of systemd that was purported to fix this bug report was > > superseded by a security update of systemd so the fix is no longer > > available. > > > > ** Changed in: systemd (Ubuntu Bionic) > >Status: Fix Committed => Triaged > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1787843). > > https://bugs.launchpad.net/bugs/1773859 > > > > Title: > > upgrades to 18.04 fail > > > > Status in systemd package in Ubuntu: > > Fix Released > > Status in systemd-shim package in Ubuntu: > > Won't Fix > > Status in systemd source package in Bionic: > > Triaged > > Status in systemd-shim source package in Bionic: > > Won't Fix > > Status in systemd source package in Cosmic: > > Fix Released > > Status in systemd-shim source package in Cosmic: > > Won't Fix > > > > Bug description: > > [Impact] > > > >* Some systems fail to upgrade due to conflicts between systemd and > > the (now removed from the archive) systemd-shim / upstart. > > > >* Instead of trying to work out what's the problem in ordering / > > removal of diverts, ensure that systemd is never unpacked whilst > > systemd-shim/upstart are still on disk. Thus declare conflicts against > > systemd-shim/upstart packages in systemd package. > > > > [Test Case] > > > >* monitor drop-off of upgrades with below reported problem > > > >* Check that it is possible to upgrade to bionic's libpam-systemd > > from xenial with systemd-shim installed on xenial, ie. > > > > lxc launch ubuntu-daily:xenial test-shim-upgrade > > lxc exec test-shim-upgrade > > apt update > > apt install systemd-shim > > wget > > > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > > apt install ./systemd-shim_10-3_amd64.deb > > sed 's/xenial/bionic/' -i /etc/apt/sources.list > > apt update > > apt install systemd > > > > this currently passes, however, systemd-shim remains installed. It > > should be removed instead. Apt install systemd should have lines like > > this: > > > > The following packages will be REMOVED: > > systemd-shim > > ... > > Removing 'diversion of > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > by systemd-shim' > > ... > > > > > > [Regression Potential] > > > >* systemd-shim/upstart are both removed and not supported in bionic, > > thus forcing their removal via conflicts should bring the system into > > an expected state. > > > > [Other Info] > > > >* original bug report > > > > $ sudo apt upgrade > > Reading package lists... Done > > Building dependency tree > > Reading state information... Done > > Calculating upgrade... Done > > The following packages will be REMOVED: > > systemd-shim > > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > > 1 not fully installed or removed. > > After this operation, 71.7 kB disk space will be freed. > > Do you want to continue? [Y/n] y > > (Reading database ... 63 files and directories currently > installed.) > > Removing systemd-shim (9-1bzr4ubuntu1) ... > > Removing 'diversion of > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > > > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > > by systemd-shim' > > dpkg-divert: error: rename involves overwriting > > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > > different file > > > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > > not allowed > > dpkg: error processing package systemd-shim (--remove): > >subprocess installed post-removal script returned error exit status 2 > > Errors were encountered while processing: > >systemd-shim > > E: Sub-process /usr/bin/dpkg returned an error code (1) > > > > Commenting out the dpkg-divert in systemd-shim's postrm solved this >
[Touch-packages] [Bug 1746582] Re: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1
Thanks @Chengkinhung (chengkinhung) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1746582 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 Status in lvm2 package in Ubuntu: Confirmed Bug description: I *think* this was from trying to install python-guestfs ProblemType: Package DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.8-0ubuntu7 Architecture: amd64 Date: Wed Jan 31 09:56:36 2018 ErrorMessage: installed lvm2 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-06-28 (217 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~alpha7ubuntu1 SourcePackage: lvm2 Title: package lvm2 2.02.176-4.1ubuntu2 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-01-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1746582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Muchas gracias por la información. Si no es mucho consultarte, a veces cuando me pide actualizaciones las hago y luego me dice que tengo el Ubuntu 14. , que si lo quiero actualizar a la ultima versión 16. y no lo hago por miedo a que se me desbarate todo de nuevo, cual es tu consejo? Un saludo El lun., 28 ene. 2019 a las 19:35, Brian Murray () escribió: > The upload of systemd that was purported to fix this bug report was > superseded by a security update of systemd so the fix is no longer > available. > > ** Changed in: systemd (Ubuntu Bionic) >Status: Fix Committed => Triaged > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1787843). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > Triaged > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial, ie. > > lxc launch ubuntu-daily:xenial test-shim-upgrade > lxc exec test-shim-upgrade > apt update > apt install systemd-shim > wget > https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb > apt install ./systemd-shim_10-3_amd64.deb > sed 's/xenial/bionic/' -i /etc/apt/sources.list > apt update > apt install systemd > > this currently passes, however, systemd-shim remains installed. It > should be removed instead. Apt install systemd should have lines like > this: > > The following packages will be REMOVED: > systemd-shim > ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > ... > > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > Removing systemd-shim (9-1bzr4ubuntu1) ... > Removing 'diversion of > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to > /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd > by systemd-shim' > dpkg-divert: error: rename involves overwriting > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with > different file > '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', > not allowed > dpkg: error processing package systemd-shim (--remove): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: Triaged Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflict
[Touch-packages] [Bug 1813824] Re: package linux-image-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1813824 Title: package linux-image-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: ? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1949 F pulseaudio francky2530 F pulseaudio /dev/snd/controlC0: gdm1949 F pulseaudio francky2530 F pulseaudio Date: Tue Jan 29 20:41:01 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=669cc0b1-0e22-4644-a449-4faef54cab8f IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-43-generic root=UUID=a308ecb4-610e-4f01-b8ed-9c82127e52a5 ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: FM2A88X Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd05/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1813824/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
I originally reported this against gnome-session. @vanvugt changed it to openssh. I think it should be changed to gnome-keyring. I didn't see it at first but now it's clear that it is actually gnome-keyring that interferes: `SSH_AUTH_SOCK=/run/user/1000/keyring/ssh` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Invalid ** Changed in: systemd (Ubuntu Trusty) Status: In Progress => Invalid ** Changed in: systemd (Ubuntu Xenial) Importance: High => Undecided ** Changed in: systemd (Ubuntu Trusty) Importance: High => Undecided ** Changed in: systemd (Ubuntu Trusty) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Changed in: systemd (Ubuntu Xenial) Assignee: Dan Streetman (ddstreet) => (unassigned) ** Description changed: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have enough A records to overflow the 512 byte maximum for a UDP DNS packet. Alternately, and trivially, glibc can be forced to always use TCP DNS queries by editing the /etc/resolv.conf file and adding: options use-vc With that option, glibc will fail to lookup 100% of DNS names, s
[Touch-packages] [Bug 1813824] [NEW] package linux-image-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: ? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1949 F pulseaudio francky2530 F pulseaudio /dev/snd/controlC0: gdm1949 F pulseaudio francky2530 F pulseaudio Date: Tue Jan 29 20:41:01 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=669cc0b1-0e22-4644-a449-4faef54cab8f IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-43-generic root=UUID=a308ecb4-610e-4f01-b8ed-9c82127e52a5 ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: FM2A88X Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd05/13/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A88XExtreme4+:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1813824 Title: package linux-image-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: ? ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm1949 F pulseaudio francky2530 F pulseaudio /dev/snd/controlC0: gdm1949 F pulseaudio francky2530 F pulseaudio Date: Tue Jan 29 20:41:01 2019 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=669cc0b1-0e22-4644-a449-4faef54cab8f IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-43-generic root=UUID=a308ecb4-610e-4f01-b8ed-9c82127e52a5 ro rootflags=subvol=@ quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: grub-pc 2.02-2ubuntu8.9 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.15.0-44-generic 4.15.0-44.47 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: FM2A88X Extreme4+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr
[Touch-packages] [Bug 1804603] Re: systemd-tmpfiles-setup.service fails on btrfs
user1@teki3:~# sudo mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8173592k,nr_inodes=2043398,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1640840k,mode=755) /dev/sda3 on / type ext4 (rw,relatime,data=ordered) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=378) debugfs on /sys/kernel/debug type debugfs (rw,relatime) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) configfs on /sys/kernel/config type configfs (rw,relatime) /var/lib/snapd/snaps/core_6259.snap on /snap/core/6259 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core_6130.snap on /snap/core/6130 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core_6034.snap on /snap/core/6034 type squashfs (ro,nodev,relatime,x-gdu.hide) /dev/md0 on /aurdata type ext4 (rw,relatime,data=ordered) lxcfs on /var/lib/lxcfs type fuse.lxcfs (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other) tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=1640836k,mode=700) user1@teki3:~# sudo ls -latr / total 132 drwxr-xr-x 10 root root 4096 Apr 26 2018 usr drwxr-xr-x 2 root root 4096 Apr 26 2018 srv drwxr-xr-x 2 root root 4096 Apr 26 2018 opt drwxr-xr-x 2 root root 4096 Apr 26 2018 mnt drwxr-xr-x 2 root root 4096 Apr 26 2018 media drwxr-xr-x 2 root root 4096 Apr 26 2018 lib64 drwxr-xr-x 22 root root 4096 Apr 26 2018 lib drwxr-xr-x 13 root root 4096 Apr 26 2018 var drwx-- 2 root root 16384 Jun 30 2018 lost+found drwxr-xr-x 4 root root 4096 Jun 30 2018 snap drwxr-xr-x 2 root root 4096 Jul 1 2018 aur_sda4 drwxrwxrwx 2 user1 user1 4096 Jul 1 2018 aurCCmount drwxr-xr-x 2 root root 4096 Jul 3 2018 aurTemp1 drwxr-xr-x 2 root root 4096 Jul 4 2018 aurmd8 drwxr-xr-x 13 root root 4096 Aug 3 09:51 home drwxr-xr-x 2 root root 4096 Sep 3 17:57 aurstripe drwxrwx--- 17 user1 pub4096 Sep 12 09:17 aurdata drwxr-xr-x 2 root root 4096 Sep 28 09:43 aursdd1 drwx-- 7 root root 4096 Sep 28 10:48 root drwxr-xr-x 2 root root 4096 Nov 14 20:16 aur2Mount drwxrwx--- 9 user1 user1 4096 Jan 13 20:33 abirx drwxr-xr-x 2 root root 12288 Jan 18 17:06 sbin drwxr-xr-x 2 root root 4096 Jan 18 17:06 bin lrwxrwxrwx 1 root root 30 Jan 29 20:43 vmlinuz.old -> boot/vmlinuz-4.15.0-43-generic lrwxrwxrwx 1 root root 30 Jan 29 20:43 vmlinuz -> boot/vmlinuz-4.15.0-44-generic lrwxrwxrwx 1 root root 33 Jan 29 20:43 initrd.img.old -> boot/initrd.img-4.15.0-43-generic lrwxrwxrwx 1 root root 33 Jan 29 20:43 initrd.img -> boot/initrd.img-4.15.0-44-generic drwxrwxrwx 32 user1 user1 4096 Jan 29 20:43 .. drwxrwxrwx 32 user1 user1 4096 Jan 29 20:43 . drwxr-xr-x 3 root root 4096 Jan 29 20:43 boot drwxr-xr-x 106 root root 4096 Jan 29 21:04 etc dr-xr-xr-x 179 root root 0 Jan 29 21:06 proc dr-xr-xr-x 13 root root 0 Jan 29 21:06 sys drwxr-xr-x 19 root root 4120 Jan 29 21:07 dev drwxrwxrwt 4 root root 4096 Jan
[Touch-packages] [Bug 1574351] Re: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other in
The perl version in the cosmic release pocket was built after the changes to pkgbinarymangler so this is fixed for cosmic and later releases. ** Changed in: perl (Ubuntu) Status: Confirmed => Fix Released ** Tags removed: rls-bb-incoming verification-dome ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1574351 Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 Status in perl package in Ubuntu: Fix Released Status in pkgbinarymangler package in Ubuntu: Fix Released Status in perl source package in Bionic: Fix Released Status in pkgbinarymangler source package in Bionic: Fix Released Bug description: [Impact] * Pkgstripfiles generates different stripped documentation for arch:any packages depending on if arch:all packages are built at the same time. In practice it means that amd64 packages may end up different file contents of doc files compared to other architectures making multiarch installation of the affected packages impossible without workarounds. * To fix affected packages by a rebuild the pkgbinarymangler package needs to be backported, too. * The fix in pkgstripfiles is skipping symlinking documentation to dependent packages with identical content when the dependent packages are not built. [Test Case] * To test pkgbinarymangler rebuild perl i386 packages without arch:all packages with the fixed pkgbinarymangler package and observe the following message in the build log: ... Skipping perl-modules-5.26 because it is not to be built ... * Note that PPA builds skip the mangling steps thus the package needs to be built in sbuild/pbuilder/in the official archive with pkgbinarymangler added as an extra package in case of a local build. * The resulting libperl5.2? package can also be analyzed to see changelog.Debian.gz not symlinked to perl-modules-5.2?'s changelog, but to check if the original bug is fixed just install libperl5.26:amd64 and libperl5.26:i386 using multiarch (here we assume the current architecture is amd64): $ sudo dpkg --add-architecture i386 $ sudo apt update $ sudo apt install libperl5.26:i386 [Regression Potential] * The pkgbinarymangler fix may break the pkgstripfiles script causing FTBFS of unrelated packages or could cause building not stripped packages. The former problem would be caught early, while the latter can be avoided by checking the build logs of a few other packages rebuilt with the fixed pkgbinarymangler package. [Original Bug Text] Don't run aplication after upgrade from 14.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libperl5.22 5.22.1-9 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun Apr 24 21:08:20 2016 DpkgTerminalLog: Preparing to unpack .../libperl5.22_5.22.1-9_i386.deb ... Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 DuplicateSignature: Unpacking libperl5.22:i386 (5.22.1-9) ... dpkg: error processing archive /var/cache/apt/archives/libperl5.22_5.22.1-9_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 InstallationDate: Installed on 2016-04-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: perl Title: package libperl5.22 5.22.1-9 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.22/changelog.Debian.gz', which is different from other instances of package libperl5.22:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1574351/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
** Description changed: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have enough A records to overflow the 512 byte maximum for a UDP DNS packet. Alternately, and trivially, glibc can be forced to always use TCP DNS queries by editing the /etc/resolv.conf file and adding: options use-vc With that option, glibc will fail to lookup 100% of DNS names, since all lookups will use TCP to talk to the local systemd stub resolver, which as explained above fails to ever correctly answer glibc's pipelined TCP DNS queries. Note that in default Ubuntu installs, /etc/resolv.conf is a symlink to ../run/systemd/resolve/stub-resolv.conf, which systemd thinks it owns 100% - so any manual changes to the file may be overwritten at any time. There is no way (that I can find) to tell systemd to add any resolv.conf options (like 'use-vc')
[Touch-packages] [Bug 1772222] Re: dangling symlink in /etc/rsyslog.d breaks rsyslogd
** Tags removed: rls-bb-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/177 Title: dangling symlink in /etc/rsyslog.d breaks rsyslogd Status in rsyslog package in Ubuntu: New Status in rsyslog source package in Bionic: New Bug description: Since upgrading from artful to bionic, I noticed that /var/log/kern.log, etc., were not being updated on my machine. In comparing to another machine running a fresh install of bionic, I discovered that this seems to be the culprit: [agnew(etc)] ls -l /etc/rsyslog.d/99-conjure-up.conf lrwxrwxrwx 1 root root 45 Jun 14 2017 /etc/rsyslog.d/99-conjure-up.conf -> /usr/share/conjure-up/conjure-up-rsyslog.conf [agnew(etc)] ls -l /usr/share/conjure-up/conjure-up-rsyslog.conf ls: cannot access '/usr/share/conjure-up/conjure-up-rsyslog.conf': No such file or directory [agnew(etc)] _ Before deletion: [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. [agnew(etc)] _ After deletion: [agnew(etc)] sudo rm /etc/rsyslog.d/99-conjure-up.conf [agnew(etc)] sudo service rsyslog restart [agnew(etc)] sudo lsof -n -p $(cat /run/rsyslogd.pid) | grep /var/log lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. rsyslogd 30686 syslog8w REG 253,122782 15213384 /var/log/syslog rsyslogd 30686 syslog9w REG 253,1 2065 15219687 /var/log/auth.log [agnew(etc)] _ It didn't occur to me to check the service status until writing this bug report, but in fact it does report the problem on startup: May 20 14:39:27 agnew rsyslogd[31786]: error during parsing file /etc/rsyslog.d/postfix.conf, on or before line 1: error accessing config file or directory '/etc/rsyslog.d/99-conjure May 20 14:39:27 agnew rsyslogd[31786]: CONFIG ERROR: there are no active actions configured. Inputs will run, but no output whatsoever is created. [v8.32.0 try http://www.rsyslog.com However, it's unlikely this warning will be discovered until it's too late, if ever -- consider a remote syslogging setup on a machine that has since been decommissioned or reinstalled -- and so it would probably better for rsyslogd to cope with dangling symlinks. Indeed, given the age of the symlink, this is a regression from artful or earlier. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
The bug has been reproduced with the system's own ssh-keygen and the command `ssh-keygen -N $passphrase -f ~/.ssh/id_rsa`. Also, https://unix.stackexchange.com/a/351742 is about keys that didn't work at all. The problem here is that confirmation fails, everything seems to be working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812247] Re: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
Could this answer be related? https://unix.stackexchange.com/a/351742/254144 Are your ssh keys of the new format, having been generated with the -o option of ssh-keygen? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1812247 Title: ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation Status in openssh package in Ubuntu: New Bug description: Ubuntu uses ssh-agent from OpenSSH which supports adding keys by means of `ssh-add -c` indicating that keys "should be subject to confirmation before being used for authentication. In Ubuntu 18.10 this fails with the error sign_and_send_pubkey: signing failed: agent refused operation To reproduce I used a Ubuntu 18.10 Live "CD", apt-get update && apt- get upgrade, log out and log back in (these steps are not required but we want to use an up-to-date system). Then: $ sudo apt-get install ssh-askpass-gnome (...) $ # verify that ssh-askpass shows a popup, confirm with Enter $ ssh-askpass ; echo $? 0 $ ssh-keygen (...) $ ssh-add -D All identities removed. $ ssh-copy-id $sshuser@$sshserver (...) Number of key(s) added: 1 (...) $ ssh $sshuser@$sshserver uname -a Linux server 4.9.0-8-amd64 #1 SMP Debian 4.9.130-2 (2018-10-27) x86_64 GNU/Linux $ ssh-add -d Identity removed: /home/ubuntu/.ssh/id_rsa (ubuntu@ubuntu) $ ssh-add -c Enter passphrase for /home/ubuntu/.ssh/id_rsa (will confirm each use): Identity added: /home/ubuntu/.ssh/id_rsa (/home/ubuntu/.ssh/id_rsa) The user must confirm each use of the key $ ssh $sshuser@$sshserver uname -a sign_and_send_pubkey: signing failed: agent refused operation sshuser@server's password: [^C'ed] $ ssh-add -l 2048 SHA256:yvAFsTpkNWnlrQyCp+tWV83dIF8Je3AksM0o+Ajvyyc /home/ubuntu/.ssh/id_rsa (RSA) So, our key is loaded, ssh-askpass is working (also confirmed with `ssh-add -c LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1812247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813584] Re: libidn ftbfs in 18.04 LTS
I have a fix for it. I'll have to push it out to disco and cosmic as well as I suppose it's FTBFS there as well. ** Changed in: libidn (Ubuntu Bionic) Status: New => In Progress ** Changed in: libidn (Ubuntu) Status: New => In Progress ** Also affects: libidn (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: libidn (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: libidn (Ubuntu Cosmic) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: libidn (Ubuntu Cosmic) Importance: Undecided => High ** Changed in: libidn (Ubuntu Cosmic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: In Progress Status in libidn source package in Bionic: In Progress Status in libidn source package in Cosmic: In Progress Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798212] Re: systemd stuck in uninterruptible sleep state
I think in my case it was this issue that made systemd go into D state: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1802021 I was yet to test the fix in that bug but will do it as soon as it's available on 4.15.+ -- 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/1798212 Title: systemd stuck in uninterruptible sleep state Status in systemd package in Ubuntu: Confirmed Bug description: Ubuntu 16.04 systemd 229 may get stuck in an uninterruptible sleep state. Any subsequent systemctl command times out with "Failed to execute operation: Connection timed out" error message. gdb and strace is unable to attach to systemd process 1. $ systemd --version systemd 229 +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN $ cat /proc/1/stack [<0>] flush_work+0x129/0x1e0 [<0>] flush_delayed_work+0x3f/0x50 [<0>] fsnotify_wait_marks_destroyed+0x15/0x20 [<0>] fsnotify_destroy_group+0x48/0xd0 [<0>] inotify_release+0x1e/0x50 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x8a/0xb0 [<0>] exit_to_usermode_loop+0xc4/0xd0 [<0>] do_syscall_64+0xf4/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x $ cat /proc/1/status Name: systemd Umask: State:D (disk sleep) Tgid: 1 Ngid: 0 Pid: 1 PPid: 0 TracerPid:9724 Uid: 0 0 0 0 Gid: 0 0 0 0 FDSize: 128 Groups: NStgid: 1 NSpid:1 NSpgid: 1 NSsid:1 VmPeak: 251136 kB VmSize: 185728 kB VmLck: 0 kB VmPin: 0 kB VmHWM:6620 kB VmRSS:6264 kB RssAnon: 2380 kB RssFile: 3884 kB RssShmem:0 kB VmData: 18752 kB VmStk: 132 kB VmExe:1392 kB VmLib:3692 kB VmPTE: 128 kB VmSwap: 0 kB HugetlbPages:0 kB CoreDumping: 0 Threads: 1 SigQ: 1/257098 SigPnd: 0004 ShdPnd: 0001 SigBlk: 7be3c0fe28014a03 SigIgn: 1000 SigCgt: 000184ec CapInh: CapPrm: 003f CapEff: 003f CapBnd: 003f CapAmb: NoNewPrivs: 0 Seccomp: 0 Speculation_Store_Bypass: vulnerable Cpus_allowed: Cpus_allowed_list:0-31 Mems_allowed: ,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,0003 Mems_allowed_list:0-1 voluntary_ctxt_switches: 716968 nonvoluntary_ctxt_switches: 9565 $ dmesg [...] [1255076.993707] INFO: task systemd:1 blocked for more than 120 seconds. [1255077.000295] Not tainted 4.15.0-32-generic #35~16.04.1-Ubuntu [1255077.006804] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [1255077.014996] systemd D0 1 0 0x [1255077.015000] Call Trace: [1255077.015011] __schedule+0x3d6/0x8b0 [1255077.015019] ? enqueue_entity+0x112/0x670 [1255077.015021] schedule+0x36/0x80 [1255077.015025] schedule_timeout+0x1db/0x370 [1255077.015028] ? check_preempt_curr+0x54/0x90 [1255077.015030] ? ttwu_do_wakeup+0x1e/0x150 [1255077.015033] wait_for_completion+0xb4/0x140 [1255077.015035] ? wake_up_q+0x70/0x70 [1255077.015040] flush_work+0x129/0x1e0 [1255077.015043] ? worker_detach_from_pool+0xb0/0xb0 [1255077.015045] flush_delayed_work+0x3f/0x50 [1255077.015052] fsnotify_wait_marks_destroyed+0x15/0x20 [1255077.015055] fsnotify_destroy_group+0x48/0xd0 [1255077.015058] inotify_release+0x1e/0x50 [1255077.015063] __fput+0xea/0x220 [1255077.015065] fput+0xe/0x10 [1255077.015068] task_work_run+0x8a/0xb0 [1255077.015074] exit_to_usermode_loop+0xc4/0xd0 [1255077.015077] do_syscall_64+0xf4/0x130 [1255077.015080] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [1255077.015084] RIP: 0033:0x7f29c9c3457d [1255077.015085] RSP: 002b:7ffec956fe30 EFLAGS: 0293 ORIG_RAX: 0003 [1255077.015088] RAX: RBX: 0010 RCX: 7f29c9c3457d [1255077.015090] RDX: RSI: RDI: 0010 [1255077.015092] RBP: 7f29cb36d700 R08: 5625f0043420 R09: 0001 [1255077.015093] R10: R11: 0293 R12: 000b [1255077.015095] R13: 5625eeed6040 R14: 5625eff179b8 R15: 5625eeed746
[Touch-packages] [Bug 1805203] Re: libcurl3-gnutls in cosmic breaks git with Azure DevOps
Someone contacted me and requested the steps for the work around. Sharing here: First, you need to add the bionic security repository to your apt sources list $ sudo vim /etc/apt/sources.list Add this line: deb http://security.ubuntu.com/ubuntu/ bionic-security main restricted Update packages $ sudo apt-get update Then you need to downgrade libcurl3-gnutls: $ sudo apt-get install libcurl3-gnutls=7.58.0* As security packages are updated automatically by Ubuntu on a daily basis, you'll need to re-run this last command to downgrade libcurl3-gnutls every morning. -- 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/1805203 Title: libcurl3-gnutls in cosmic breaks git with Azure DevOps Status in curl package in Ubuntu: Confirmed Bug description: The version of libcurl3-gnutls in cosmic (7.61.0) causes authentication failures with Azure DevOps. This causes all git operations with the server to fail (eg clone, push, pull). For details see this curl bug: https://github.com/curl/curl/pull/2754 To work around this I downgraded libcurl3-gnutls to the version in bionic (7.58.0) From the curl change list https://curl.haxx.se/changes.html#7_61_1, this issue should be fixed in package version 7.61.1 or above. Request: please upgrade package in cosmic for libcurl3-gnutls to 7.61.1 or above Details: 1 - Ubuntu 18.10 2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others) 3 - Be able to git clone from an Azure DevOps repository using a Personal Access Token 4 - git operations fail to authenticate Thank you, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1805203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813432] Re: Specific PDF file fails to print to HP m551dn printer
Please run the following command: lpadmin -p duplex -o pdftops-renderer-default=gs Then print the job again on your print queue "duplex". Does the job get correctly printed now? ** Changed in: cups (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1813432 Title: Specific PDF file fails to print to HP m551dn printer Status in cups package in Ubuntu: Incomplete Bug description: One particular PDF file is failing to print. I have no idea why. When I say failing to print I mean that my computer thinks the file printed but the printer shows no sign of ever having received it. The display of the printer never changes to show that it is receiving or printing a file, and the job log of the printer doesn't show that it was received either. I also checked the printer event log and it doesn't show any events at the time I attempted to print the file. Unfortunately I can't attach the PDF file itself because it contains private information, and I can't find another PDF that exhibits this problem. I even tried generating a new PDF exactly the same way the old one was generated -- with the scan to email PDF function on my scanner -- and the new PDF prints just fine. I tried uploading the PDF directly to the printer with FTP and it prints just fine that way. I enabled CUPS debug mode before attempting to print the file. Attached is the resulting contents of /var/log/cups/error_log. I wish I knew what was going on here but honestly I have no idea. Perhaps you can learn something from the error_log. I hope so. Other files, including other PDFs, do print. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-3 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu19 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 26 17:47:49 2019 InstallationDate: Installed on 2019-01-02 (24 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for duplex: socket://m551dn.kamens.brookline.ma.us:9100 device for HP_LaserJet_500_color_M551_1637DA_: ipps://m551dn.local:443/ipp/print device for simplex: socket://m551dn.kamens.brookline.ma.us:9100 MachineType: Acer Predator G6-710 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/simplex.ppd', '/etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd', '/etc/cups/ppd/duplex.ppd'] failed with exit code 2: grep: /etc/cups/ppd/simplex.ppd: Permission denied grep: /etc/cups/ppd/HP_LaserJet_500_color_M551_1637DA_.ppd: Permission denied grep: /etc/cups/ppd/duplex.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A4 dmi.board.name: Predator G6-710 dmi.board.vendor: Acer dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A4:bd05/18/2016:svnAcer:pnPredatorG6-710:pvr:rvnAcer:rnPredatorG6-710:rvr:cvnAcer:ct3:cvr: dmi.product.family: Acer Desktop dmi.product.name: Predator G6-710 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1813432/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644996] Re: logrotate config uses syslog group
What lxd containers are affected? $ lxc launch ubuntu:bionic syslog-test Creating syslog-test Starting syslog-test $ sudo lxc exec syslog-test -- getent group syslog syslog:x:106: $ The rsyslog package is a Recommends: of the ubuntu-minimal package, which means that all images which Ubuntu produces will have this group present with the exception of the base tarball (on which the docker images are based), and the minimal image flavors (which includes a minimal lxd rootfs, but this is not currently published to streams). So how do you have "lots of lxd containers" affected y this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
** Changed in: libunistring (Ubuntu Bionic) Status: Triaged => In Progress ** Bug watch added: Debian Bug tracker #920824 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920824 ** Also affects: libunistring (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=920824 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: In Progress Status in libunistring package in Debian: Unknown Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
dmesg ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+attachment/5233781/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1812014] Re: keyboard not responding after suspend after some time
dpkg -l ** Attachment added: "dpkgl.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+attachment/5233782/+files/dpkgl.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1812014 Title: keyboard not responding after suspend after some time Status in gnome-shell package in Ubuntu: Incomplete Status in upower package in Ubuntu: Incomplete Bug description: I work on Lenovo laptop y-700. When I resume system after suspend, keyboards stop working, and sometimes there are performance problems visible when playing videos. It happens not immediately but after a few minutes or even a few hours of working. Restart or shutdown does not finish correctly and I need to hold the power button for a few seconds. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.10 GsettingsChanges: b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' redacted by apport b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2018-08-06 (165 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.30.1-2ubuntu1.18.10.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812014/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805418] Re: Update pre-populator patch with correct desktop names
** Changed in: zeitgeist (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1805418 Title: Update pre-populator patch with correct desktop names Status in zeitgeist package in Ubuntu: Fix Committed Bug description: Use correct desktop names for totem, gedit and gnome-calculator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1805418/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
I can reproduce the issue and analyze it in a qemu testbed with the following patch: --- a/live-build/functions +++ b/live-build/functions @@ -10,6 +10,7 @@ loop_raw= backing_img= clean_loops() { +sleep 1 local kpartx_ret local kpartx_stdout Oddly enough nothing seems to be using the /dev/mapper/loop3p1 device but e2fs fails: strace e2fsck -d -v -y -E discard /dev/mapper/loop3p1 ... stat("/dev/mapper/loop3p1", {st_mode=S_IFBLK|0660, st_rdev=makedev(253, 0), ...}) = 0 openat(AT_FDCWD, "/dev/mapper/loop3p1", O_RDONLY|O_EXCL) = -1 EBUSY (Device or resource busy) ... write(1, "/dev/mapper/loop3p1 is in use.\n", 31/dev/mapper/loop3p1 is in use. ) = 31 write(2, "e2fsck: Cannot continue, abortin"..., 37e2fsck: Cannot continue, aborting. ** Changed in: livecd-rootfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: Confirmed Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813792] [NEW] Window decorations flicker with OpenGL renderers
Public bug reported: When using the KDE desktop for a certain amount of time (seems random), the window decoration in the top-left corner starts for flicker for the active application. The flickering remains when the application loses focus, so more and more decorations will flicker. The flickering occurs for both OpenGL renderers, but not with XRender. I know no way of making the flickering stop, except for rebooting or switching to XRender and back. These issues started with Kubuntu 18.04, if I remember correctly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Tue Jan 29 16:51:51 2019 DistUpgraded: 2019-01-09 21:53:41,840 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694] InstallationDate: Installed on 2016-08-24 (887 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=UUID=eb8f662d-aaeb-4bdd-8750-00ed26e8a5ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-01-09 (19 days ago) dmi.bios.date: 08/29/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: Default string dmi.board.name: Z170-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd08/29/2016:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: kwin (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic kubuntu resolution ubuntu ** Package changed: xorg (Ubuntu) => kwin (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813792 Title: Window decorations flicker with OpenGL renderers Status in kwin package in Ubuntu: New Bug description: When using the KDE desktop for a certain amount of time (seems random), the window decoration in the top-left corner starts for flicker for the active application. The flickering remains when the application loses focus, so more and more decorations will flicker. The flickering occurs for both OpenGL renderers, but not with XRender. I know no way of making the flickering stop, except for rebooting or switching to XRender and back. These issues started with Kubuntu 18.04, if I remember correctly. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Tue Jan 29 16:51:51 2019 DistUpgraded: 2019-01-09 21:53:41,840 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694] InstallationDate: Installed on 2016-08-24 (887 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
[Touch-packages] [Bug 1813784] [NEW] tried to install skype and got this
Public bug reported: The following packages have unmet dependencies: skypeforlinux:amd64 : Depends: libasound2:amd64 (>= 1.0.16) but it is not installable Depends: libatk1.0-0:amd64 (>= 1.12.4) but it is not installable Depends: libc6:amd64 (>= 2.17) but it is not installable Depends: libcairo2:amd64 (>= 1.6.0) but it is not installable Depends: libcups2:amd64 (>= 1.4.0) but it is not installable Depends: libexpat1:amd64 (>= 2.0.1) but it is not installable Depends: libgcc1:amd64 (>= 1:4.0) but it is not installable Depends: libgconf-2-4:amd64 (>= 3.2.5) but it is not installable Depends: libgdk-pixbuf2.0-0:amd64 (>= 2.22.0) but it is not installable Depends: libglib2.0-0:amd64 (>= 2.35.8) but it is not installable Depends: libgtk-3-0:amd64 (>= 3.9.10) but it is not installable Depends: libnspr4:amd64 (>= 2:4.9-2~) but it is not installable Depends: libnss3:amd64 (>= 2:3.13.4-2~) but it is not installable Depends: libpango-1.0-0:amd64 (>= 1.14.0) but it is not installable Depends: libpangocairo-1.0-0:amd64 (>= 1.14.0) but it is not installable Depends: libsecret-1-0:amd64 (>= 0.7) but it is not installable Depends: libx11-6:amd64 (>= 2:1.4.99.1) but it is not installable Depends: libx11-xcb1:amd64 but it is not installable Depends: libxcb1:amd64 (>= 1.6) but it is not installable Depends: libxcomposite1:amd64 (>= 1:0.3-1) but it is not installable Depends: libxcursor1:amd64 (> 1.1.2) but it is not installable Depends: libxdamage1:amd64 (>= 1:1.1) but it is not installable Depends: libxext6:amd64 but it is not installable Depends: libxfixes3:amd64 but it is not installable Depends: libxi6:amd64 (>= 2:1.2.99.4) but it is not installable Depends: libxrandr2:amd64 (>= 2:1.2.99.3) but it is not installable Depends: libxrender1:amd64 but it is not installable Depends: libxss1:amd64 but it is not installable Depends: libxtst6:amd64 but it is not installable Depends: apt-transport-https:amd64 but it is not installable Depends: libfontconfig1:amd64 (>= 2.11.0) but it is not installable Depends: libdbus-1-3:amd64 (>= 1.6.18) but it is not installable Depends: libstdc++6:amd64 (>= 4.8.1) but it is not installable N: Ignoring file '50unattended-upgrades.merge-error' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension E: Unable to correct problems, you have held broken packages. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jan 29 16:24:10 2019 DistUpgraded: 2018-09-02 09:29:06,755 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] Subsystem: Hewlett-Packard Company Mobile 4 Series Chipset Integrated Graphics Controller [103c:1526] InstallationDate: Installed on 2017-04-11 (657 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: Hewlett-Packard HP 620 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=64d43abe-1712-45a1-929c-7685beb99496 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-02 (149 days ago) dmi.bios.date: 09/06/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PVI Ver. F.06 dmi.board.name: 1526 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 71.0D dmi.chassis.asset.tag: CNU0430H3H dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PVIVer.F.06:bd09/06/2010:svnHewlett-Packard:pnHP620:pvrF.06:rvnHewlett-Packard:rn1526:rvrKBCVersion71.0D:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP 620 dmi.product.version: F.06 dmi.sys.vendor: Hewlett-Packard version.compiz
[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
** Patch removed: "lp1811471-disco.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811471/+attachment/5233684/+files/lp1811471-disco.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have enough A records to overflo
[Touch-packages] [Bug 1811592] Re: systemd-tmpfiles-setup.service fails after update
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/1811592 Title: systemd-tmpfiles-setup.service fails after update Status in systemd package in Ubuntu: Confirmed Bug description: 1. Description: Ubuntu 16.04.5 LTS Release: 16.04 2. apt-cache policy systemd systemd: Installed: 229-4ubuntu21.15 Candidate: 229-4ubuntu21.15 Version table: *** 229-4ubuntu21.15 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 3. After VPS was rebooted I can't to connect via SSH 4. SSH Service fail because systemd-tmpfiles service fail to start after update I can connect to VPS (openVZ) only via emergency console journalctl -b 0 -u systemd-tmpfiles-setup.service -- Logs begin at Sun 2019-01-13 18:34:20 EET, end at Sun 2019-01-13 18:50:00 EET. -- Jan 13 18:34:20 wok.f.time4vps.cloud systemd[1]: Starting Create Volatile Files and Directories... Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/screen: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sshd: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sudo: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: Failed to validate path /var/run/sudo/ts: Too many levels of symbolic links Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/utmp failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/systemd/netif failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/systemd/netif/links failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd-tmpfiles[94]: fchownat() of /run/systemd/netif/leases failed: Invalid argument Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: systemd-tmpfiles-setup.service: Main process exited, code=exited, status=1/FAILURE Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: Failed to start Create Volatile Files and Directories. Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: systemd-tmpfiles-setup.service: Unit entered failed state. Jan 13 18:34:21 wok.f.time4vps.cloud systemd[1]: systemd-tmpfiles-setup.service: Failed with result 'exit-code'. workaround to start SSH is mkdir /run/sshd The situation like this https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1804847 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1783987] Re: German Neo2 Problem with Xubuntu 18.04 (try out mode)
Deactivating numlock before activting neo2 also fixed this issue for me. So it is an interference between those two. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1783987 Title: German Neo2 Problem with Xubuntu 18.04 (try out mode) Status in xkeyboard-config: Unknown Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: When trying Xubuntu 18.04 Bionic Beaver from a USB Stick, I am offered the Neo2 Keyboard Layout, but it does not work. What I get is apparently Neo2 Mod4, but not Mod 1, as it should be. I wonder if Neo2 does work if I install 18.04 properly? To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1783987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
** Patch added: "lp1811471-disco.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811471/+attachment/5233684/+files/lp1811471-disco.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have enough A records to overflow
[Touch-packages] [Bug 1811471] Re: local resolver stub fails to handle multiple TCP dns queries
-- 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/1811471 Title: local resolver stub fails to handle multiple TCP dns queries Status in systemd: New Status in systemd package in Ubuntu: In Progress Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: In Progress Status in systemd source package in Bionic: In Progress Status in systemd source package in Cosmic: In Progress Status in systemd source package in Disco: In Progress Bug description: [Impact] The systemd local 'stub' resolver handles all local DNS queries (by default configuration used in Ubuntu), and essentially proxies all requests to its configured upstream DNS resolvers. Most local DNS resolution by applications uses glibc's getaddrinfo() function. This function is configured in various ways by the /etc/resolv.conf file, which tells glibc what nameserver/resolver to contact as well as how to talk to the name server. By default, glibc performs UDP DNS queries, with a single DNS query per UDP packet. The UDP packet size is limited per DNS spec to 512 bytes. For some DNS lookups, a 512 byte UDP packet is not large enough to contain the entire response - for example, an A record lookup with a large number (e.g. 30) of A record addresses. This number of A record entries is possible in some cases of load balancing. When the DNS UDP response size is larger than 512 bytes, the server puts as much response as it can into the DNS UDP response, and marks the "trunacted" flag. This lets glibc know that the DNS UDP packet did not contain the entire response for all the A records. When glibc sees a UDP response that is "trunacted", by default it ignores the contents of that response and issues a new DNS query, using TCP instead of UDP. The TCP packet size has a higher size limit (though see bug 1804487 which is a bug in systemd's max-sizing of TCP DNS packets), and so *should* allow glibc to receive the entire DNS response. However, glibc issues DNS queries for both A and records. When it uses UDP, those DNS queries are separate (i.e. one UDP DNS packet with a single A query, and one UDP DNS packet with a single query). When glibc uses TCP, it puts both DNS queries into a single TCP DNS packet - the RFC refers to this as "pipelining" (https://tools.ietf.org/html/rfc7766#section-6.2.1.1) and states that clients SHOULD do this, and that servers MUST expect to receive pipelined queries and SHOULD respond to all of them. (Technically pipelining can be separate DNS queries, one per TCP packet, but both using the same TCP connection - but the clear intention of pipelining is to improve TCP performance, and putting both DNS queries into a single TCP packet is clearly more performant than using separate TCP packets). Unfortunately, systemd's local stub resolver has only very basic support for TCP DNS, and it handles TCP DNS queries almost identically to UDP DNS queries - it reads the DNS query 2-byte header (containing the length of the query data), reads in the single DNS query data, performs lookup and sends a response to that DNS query, and closes the TCP connection. It does not check for "pipelined" queries in the TCP connection. That would be bad enough, as glibc is (rightly) expecting a response to both its A and queries; however what glibc gets is a TCP connection-reset error. That is because the local systemd stub resolver has closed its TCP socket while input data was still pending (i.e. it never even read the second pipelined DNS query). When the kernel sees unread input bytes in a TCP connection that is closed, it sends a TCP RST to the peer (i.e. glibc) and when the kernel sees the RST, it dumps all data in its socket buffer and passes the ECONNRESET error up to the application. So glibc gets nothing besides a connection reset error. Note also that even if the systemd local stub resolver's socket flushes its input buffer before closing the TCP connection (which will avoid the TCP RST), glibc still expects responses to both its A and queries before systemd closes the TCP connection, and so a simple change to systemd to flush the input buffer is not enough to fix the bug (and would also not actually fix the bug since glibc would never get the response). [Test Case] This can be reproduced on any system using a local systemd stub resolver, when using an application that uses getaddrinfo() - such as ssh, telnet, ping, etc - or with a simple C program that uses getaddrinfo(). The dns name looked up must have enough A records to overflow the 512 byte maximum for a UDP DNS packet. Alternately, and trivially, glibc can be forced to always use TCP DNS queries by editing the /etc/resolv.conf file
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
** Description changed: + Impact + -- + libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. + + Test Case + - + Does libunistring build successfully? + + Regression Potential + + We are simply backporting the workaround we applied in Ubuntu 18.10. + + Original Bug Report + --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: Triaged Bug description: Impact -- libunistring doesn't build from source which means someone would need to fix that problem before fixing any bugs in the libunistring package for Ubuntu 18.04 LTS. Test Case - Does libunistring build successfully? Regression Potential We are simply backporting the workaround we applied in Ubuntu 18.10. Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460483] Re: File Properties "Open-With" Won't Set Default
k, let's close the bug then, thanks! ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Invalid -- 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/1460483 Title: File Properties "Open-With" Won't Set Default Status in gtk+3.0 package in Ubuntu: Invalid Bug description: It used to work, but now I'm trying to associate gedit with a .contact (xml) file and it won't switch from Google Chrome as the default. Right-mouse on .contact file Click "Open-With" Select "gedit" (related applications) Click "Set as default" The highlighted selection switches to the current Default Application that is Google-Chrome and doesn't switch to gedit. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 31 16:06:50 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified', 'mime_type']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-05-31 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1460483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1763520] Re: after upgrade to bionic, printing fails without explanation / logs / debuggability
** No longer affects: cups-filters (Ubuntu Bionic) ** No longer affects: cups-filters (Ubuntu Cosmic) ** Changed in: gtk+3.0 (Ubuntu Bionic) Importance: Undecided => High ** Changed in: gtk+3.0 (Ubuntu Cosmic) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1763520 Title: after upgrade to bionic, printing fails without explanation / logs / debuggability Status in cups-filters package in Ubuntu: Invalid Status in gtk+3.0 package in Ubuntu: In Progress Status in gtk+3.0 source package in Bionic: In Progress Status in gtk+3.0 source package in Cosmic: In Progress Bug description: [Impact] The problem occurs when the printer's driver package is updated and with this the PPD is replaced and one of the default settings of the queue is not available any more in the new PPD file. Then the setting is prefixed with "Custom." and with this the jobs fail. See comment #15 for more info. [Test Case] - Create a print queue with a PPD. - evince an arbitrary PDF file - Click the print icon - In the print dialog choose the newly created queue and choose some uncommon paper size (not custom). Click "Print". - Check /var/log/cups/error_log, the page size gets correctly received. - Close evince. - Stop CUPS, edit the PPD file removing the paper size you have selected for your job in the PageSize, PageRegion, PaperDimension, and ImageableArea lines. - Start CUPS. - Open the same PDF file again with evince, click Print and then select "Print" in the print dialog without changing anything. - The job fails, in /var/log/cups/error_log you see that the page size is prefixed with "Custom.". With the fixed package installed the job will print. [Regression Potential] The change applies only to saved settings of the print dialog not matching with any of the settings available in the PPD file. In rare cases the fix could fail by mis-understanding the setting and this way not being effective. For options which do not support setting custom values (the vast majority) the patch should always prevent a job failure though. [Other Info] Complete info about the bug and the fix in comment #15, Original bug description: I am unable to print to my network-attached printer after upgrade to bionic. ps shows: lp 26047 0.0 0.0 91668 5756 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 lp 26050 0.1 0.0 0 0 ?Z15:06 0:00 | \_ [gs] lp 26048 0.0 0.0 79908 3836 ?S15:06 0:00 \_ HP-ENVY-4500-new 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 root 26049 0.0 0.0 84388 6192 ?S15:06 0:00 \_ ipp://HP645106EA160E.local:631/ipp/print 473 vorlon USCIS Form I-9 1 print-content-optimize=auto print-rendering-intent=auto cupsPrintQuality=4 number-up=1 MediaType=Stationery noCollate print-scaling=auto PageSize=Custom.Letter.SM ColorModel=RGB Duplex=DuplexNoTumble job-uuid=urn:uuid:08c937ec-ccb6-3ff1-6ed4-212128e4257b job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1523570792 time-at-processing=1523570792 print-quality=4 Note the un-reaped gs process. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cups 2.2.7-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 12 15:07:49 2018 InstallationDate: Installed on 2010-09-24 (2757 days ago) InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1) MachineType: LENOVO 2306CTO Papersize: letter ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-13-generic.efi.signed root=/dev/mapper/hostname-root ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to bionic on 2018-03-21 (21 days ago) dmi.bios.date: 10
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
** Tags removed: rls-bb-incoming ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: Triaged Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS
** Tags removed: rls-bb-incoming ** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: In Progress Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
** Changed in: libunistring (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: Triaged Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
** Changed in: libunistring (Ubuntu Bionic) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Changed in: libunistring (Ubuntu Bionic) Status: New => Triaged ** Changed in: libunistring (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: Fix Released Status in libunistring source package in Bionic: Triaged Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
** Patch added: "console-setup_1.178ubuntu11.patch" https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5233659/+files/console-setup_1.178ubuntu11.patch -- 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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
I'd like to propose a bit different patch to keep --force with debian- installer staying consistent with console-setup.postinst. -- 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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY Status in console-setup package in Ubuntu: Confirmed Bug description: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460483] Re: File Properties "Open-With" Won't Set Default
I have LONG since moved on to Arch Linux and never looked back. -- 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/1460483 Title: File Properties "Open-With" Won't Set Default Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: It used to work, but now I'm trying to associate gedit with a .contact (xml) file and it won't switch from Google Chrome as the default. Right-mouse on .contact file Click "Open-With" Select "gedit" (related applications) Click "Set as default" The highlighted selection switches to the current Default Application that is Google-Chrome and doesn't switch to gedit. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 31 16:06:50 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified', 'mime_type']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-05-31 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1460483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460483] Re: File Properties "Open-With" Won't Set Default
Do you still see that problem in newer Ubuntu versions? ** Package changed: nautilus (Ubuntu) => gtk+3.0 (Ubuntu) ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Incomplete -- 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/1460483 Title: File Properties "Open-With" Won't Set Default Status in gtk+3.0 package in Ubuntu: Incomplete Bug description: It used to work, but now I'm trying to associate gedit with a .contact (xml) file and it won't switch from Google Chrome as the default. Right-mouse on .contact file Click "Open-With" Select "gedit" (related applications) Click "Set as default" The highlighted selection switches to the current Default Application that is Google-Chrome and doesn't switch to gedit. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 31 16:06:50 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified', 'mime_type']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-05-31 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1460483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
** Changed in: systemd Status: Unknown => Fix Released -- 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/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in lxd: New Status in systemd: Fix Released Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). === Workaround === $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1813622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1460483] [NEW] File Properties "Open-With" Won't Set Default
You have been subscribed to a public bug: It used to work, but now I'm trying to associate gedit with a .contact (xml) file and it won't switch from Google Chrome as the default. Right-mouse on .contact file Click "Open-With" Select "gedit" (related applications) Click "Set as default" The highlighted selection switches to the current Default Application that is Google-Chrome and doesn't switch to gedit. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: nautilus 1:3.14.2-0ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8 Uname: Linux 3.19.0-20-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun May 31 16:06:50 2015 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'type', 'date_modified', 'mime_type']" b'org.gnome.nautilus.list-view' b'use-tree-view' b'true' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 'permissions', 'mime_type', 'where']" InstallationDate: Installed on 2015-05-31 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Low Status: Incomplete ** Tags: amd64 apport-bug vivid -- File Properties "Open-With" Won't Set Default https://bugs.launchpad.net/bugs/1460483 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777415] Re: Local authorization bypass by using suspend mode
> Jonathan Polak (jpolak) wrote on 2018-07-09: > I confirm it affects Mate 18.04 as well. > > Moreover, a new bug on mate 18.04, plugging in an HDMI screen upon receiving > the lockscreen, > sometimes allows you to bypass it completely. I know this bug since years. When setting my Thinkpad on the Dockingstation while it was sleeping it sometimes happens that the gnome-shell just starts without asking for a password. And I don't even have to extract the harddisk. I remember some guys of the ubuntu community told me years ago that's a known issue with Xorg and gnome- shell. I did not file a bug or was looking for a known bug because it happened very seldom but the bug persisted many years and I don't know if it was fixed until now for sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777415 Title: Local authorization bypass by using suspend mode Status in Unity: New Status in pam package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Version: Ubuntu 16.04.04 LTS Desktop, all packets are updated at 15.06.2018 Affects: access to latest user opened applications, that can contain sensitive information (documents, private information, passwords, etc.) How to reproduce: 1. open some applications (LibreOffice, browsers, editors, ...) 2. go to suspend mode 3. extract hard drive 4. wake up 5. after that can be several behaviors: * Ubuntu show lock screen. Enter ANY password -> access granted. * Ubuntu show lock screen. Enter ANY password, access denied. Fast press the hardware shutdown button -> access granted. * Ubuntu does not show lock screen, only black screen. We can repeat actions like in previous paragraphs To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1777415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813759] Re: Scale display doesn't work with an external monitor attached
Thank you for your bug report, could you add your journalctl log after triggering the issue? What screen resolution do you use? ** Changed in: xorg (Ubuntu) Importance: Undecided => Low ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813759 Title: Scale display doesn't work with an external monitor attached Status in xorg package in Ubuntu: Incomplete Bug description: I have a Dell XPS 13" (2018) connected to an LG 4K 32" display thru USB-C cable. both screens are supposed to have the same resolution, but the laptop one uses 200% of scale setting due to small size. When the laptop is connected to the external display, the scale setting does nothing and almost everything looks pretty small and hard to read, only gnome-terminal content seems to follow the scaling setting but windows decorators and app menus are pretty small. If I disconnect the external display everything works as expected (at least with the usual apps like GNOME apps, Firefox, Chrome, etc...). I'm using Ubuntu 18.10 with latest updates installed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:08:45 2019 DistUpgraded: 2019-01-05 13:19:27,114 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2019-01-05 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=UUID=0331a22b-f276-4072-83bb-95f04eb8ba77 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-01-05 (23 days ago) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
** Changed in: lxd Status: Unknown => New -- 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/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in lxd: New Status in systemd: Unknown Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). === Workaround === $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1813622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
yes, it is the same, but unfortunately I don't know if the fix is sane or not. the real bug is this one https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1340250 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: New Status in libunistring source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
Actually more is needed: $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' ** Bug watch added: LXD bug tracker #5439 https://github.com/lxc/lxd/issues/5439 ** Also affects: lxd via https://github.com/lxc/lxd/issues/5439 Importance: Unknown Status: Unknown ** Changed in: lxd (Ubuntu) Importance: Undecided => High ** Description changed: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). - === Workaround === - $ lxc config set improved-kodiak raw.apparmor 'mount options=(ro,nodev,remount,bind), + $ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), + mount options=(ro,nosuid,noexec,remount,bind,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' -- 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/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in lxd: Unknown Status in systemd: Unknown Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS
** Changed in: pygobject (Ubuntu Bionic) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: In Progress Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS
** Description changed: + Impact + -- + pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. + + Test Case + - + Does pygobject build successfully? + + Regression Potential + + pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. + + The only change that is made in this upload is to the tests. There + should be no effect on anything else. + + https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 + + Original Bug Report + --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): - File "/<>/tests/test_glib.py", line 66, in test_filenames - self.assertTrue(isinstance(res, bytes)) + File "/<>/tests/test_glib.py", line 66, in test_filenames + self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) - torture test 1 (1 iterations): 0.012186 secs - torture test 2 (1 iterations): 0.068459 secs - torture test 3 (1 iterations): 0.029216 secs - torture test 4 (1 iterations): 0.065890 secs - - Total: 0.175751 sec + torture test 1 (1 iterations): 0.012186 secs + torture test 2 (1 iterations): 0.068459 secs + torture test 3 (1 iterations): 0.029216 secs + torture test 4 (1 iterations): 0.065890 secs + + Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: In Progress Bug description: Impact -- pygobject doesn't build from source which means someone would need to fix that problem before fixing any bugs in the pygobject package for Ubuntu 18.04 LTS. Test Case - Does pygobject build successfully? Regression Potential pygobject 3.28 is the intended version to match glib 2.56 but it missed the deadline for Ubuntu 18.04 LTS. So this fix is cherry-picking a small commit to fix the build tests with 18.04's glib2.0 2.56. The only change that is made in this upload is to the tests. There should be no effect on anything else. https://gitlab.gnome.org/GNOME/pygobject/commit/550bd7c7 Original Bug Report --- according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
$ lxc config set improved-kodiak raw.apparmor 'mount options=(ro,nodev,remount,bind), mount options=(ro,nosuid,nodev,remount,bind), mount options=(ro,nosuid,noexec,remount,strictatime), mount options=(ro,nosuid,nodev,noexec,remount,bind),' ** Description changed: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution -Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) -Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago - Docs: man:systemd-resolved.service(8) -https://www.freedesktop.org/wiki/Software/systemd/resolved - https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers - https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients - Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) - Main PID: 290 (code=exited, status=226/NAMESPACE) + Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) + Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago + Docs: man:systemd-resolved.service(8) + https://www.freedesktop.org/wiki/Software/systemd/resolved + https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers + https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients + Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) + Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). + + + === Workaround === + + $ lxc config set improved-kodiak raw.apparmor 'mount options=(ro,nodev,remount,bind), + mount options=(ro,nosuid,nodev,remount,bind), + mount options=(ro,nosuid,noexec,remount,strictatime), + mount options=(ro,nosuid,nodev,noexec,remount,bind),' ** Bug watch added: github.com/systemd/systemd/issues #11588 https://github.com/systemd/systemd/issues/11588 ** Also affects: systemd via https://github.com/systemd/systemd/issues/11588 Importance: Unknown Status: Unknown ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: apparmor (Ubuntu) Status: New => Invalid ** Changed in: lxd (Ubuntu) Status: New => Confirmed -- 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/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in systemd: Unknown Status in apparmor package in Ubuntu: Invalid Status in lxd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Invalid Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd
[Touch-packages] [Bug 1813622] Re: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd
This is similar to https://github.com/systemd/systemd/issues/10032 But this time around with apparmor, under lxd, on ubuntu Regression from 1beab8b0d0ff2d7d1436b52d4a0c3d56dc908962 Will be tracing this further now. ** Bug watch added: github.com/systemd/systemd/issues #10032 https://github.com/systemd/systemd/issues/10032 -- 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/1813622 Title: systemd-resolved, systemd-networkd and others fail to start in lxc container with v240 systemd Status in apparmor package in Ubuntu: New Status in lxd package in Ubuntu: New Status in systemd package in Ubuntu: Confirmed Bug description: This is a regression from 239-7ubuntu15 to 240-5ubuntu1. Steps to reproduce: lxc launch ubuntu-daily:disco rbasak-resolv lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe running echo "deb http://archive.ubuntu.com/ubuntu/ disco-proposed main universe multiverse restricted" >> /etc/apt/sources.list apt update # Update to 240-5ubuntu1 from proposed apt install systemd libsystemd0 systemd-sysv libnss-systemd libpam-systemd reboot lxc exec rbasak-resolv bash systemctl status systemd-resolved # observe failed ● systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Mon 2019-01-28 16:50:37 UTC; 2min 28s ago Docs: man:systemd-resolved.service(8) https://www.freedesktop.org/wiki/Software/systemd/resolved https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients Process: 290 ExecStart=/lib/systemd/systemd-resolved (code=exited, status=226/NAMESPACE) Main PID: 290 (code=exited, status=226/NAMESPACE) Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Service has no hold-off time (RestartSec=0), scheduling restart. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Scheduled restart job, restart counter is at 5. Jan 28 16:50:37 rbasak-resolv systemd[1]: Stopped Network Name Resolution. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Start request repeated too quickly. Jan 28 16:50:37 rbasak-resolv systemd[1]: systemd-resolved.service: Failed with result 'exit-code'. Jan 28 16:50:37 rbasak-resolv systemd[1]: Failed to start Network Name Resolution. This causes /etc/resolv.conf to point to a file that isn't created, so all name resolution fails. As far as I can determine, landing this in the release pocket would cause all default LXD containers to stop working. In my case it breaks "autopkgtest -U --apt-pocket=proposed ... -- lxd ubuntu-daily:disco" Tagging block-proposed as migration would regress the release pocket, and marking Critical as it breaks the system (presumably only in a container though, and it is only in proposed currently). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1813622/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1776499] Re: Crash in libegl-mesa0 due to out of bound array access
please test 18.2.2 from bionic-proposed ** Changed in: mesa (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1776499 Title: Crash in libegl-mesa0 due to out of bound array access Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Bionic: Fix Committed Bug description: Crash in libegl-mesa0 due to out of bound array access. Crash is fixed on Mesa master branch with change: https://cgit.freedesktop.org/mesa/mesa/commit/?id=41642bdbca007035772fbfdc311f14daa5510d5d .This bug is to request to include this change in Mesa upgrades in bionic. Please let me know if this change needs to be back ported to other branch so that libegl-mesa0 upgrade in Bionic could pick this change. lsb_release -a Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic apt-cache policy libegl-mesa0 libegl-mesa0: Installed: 18.0.0~rc5-1ubuntu1 Candidate: 18.0.0~rc5-1ubuntu1 Version table: *** 18.0.0~rc5-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1776499/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798597] Re: Backport packages for 18.04.2 HWE stack
I've tested this on two GPU configs: AMD Raven (Radeon Vega 8 Mobile) Intel Coffee Lake both upgrade and work fine. -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland package in Ubuntu: Invalid Status in xf86-input-wacom-hwe-18.04 package in Ubuntu: Invalid Status in xorg-hwe-18.04 package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-evdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-joystick-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-libinput-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-input-synaptics-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-amdgpu-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-ati-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-dummy-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-fbdev-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-nouveau-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-qxl-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vesa-hwe-18.04 package in Ubuntu: Invalid Status in xserver-xorg-video-vmware-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-7 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in wayland source package in Bionic: Fix Committed Status in xf86-input-wacom-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-hwe-18.04 source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-evdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-joystick-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-libinput-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-input-synaptics-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-amdgpu-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-ati-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-dummy-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-fbdev-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-nouveau-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-qxl-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vesa-hwe-18.04 source package in Bionic: Fix Committed Status in xserver-xorg-video-vmware-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.2 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-7: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 18.2.x series, so there shouldn't be any regressions left at that point xserver: a new major release, but since it's renamed there's no real chance of regression when it hits the archive xorg drivers: same as xserver [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813759] [NEW] Scale display doesn't work with an external monitor attached
Public bug reported: I have a Dell XPS 13" (2018) connected to an LG 4K 32" display thru USB-C cable. both screens are supposed to have the same resolution, but the laptop one uses 200% of scale setting due to small size. When the laptop is connected to the external display, the scale setting does nothing and almost everything looks pretty small and hard to read, only gnome-terminal content seems to follow the scaling setting but windows decorators and app menus are pretty small. If I disconnect the external display everything works as expected (at least with the usual apps like GNOME apps, Firefox, Chrome, etc...). I'm using Ubuntu 18.10 with latest updates installed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:08:45 2019 DistUpgraded: 2019-01-05 13:19:27,114 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on 2019-01-05 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-13-generic root=UUID=0331a22b-f276-4072-83bb-95f04eb8ba77 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2019-01-05 (23 days ago) dmi.bios.date: 11/04/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic resolution ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813759 Title: Scale display doesn't work with an external monitor attached Status in xorg package in Ubuntu: New Bug description: I have a Dell XPS 13" (2018) connected to an LG 4K 32" display thru USB-C cable. both screens are supposed to have the same resolution, but the laptop one uses 200% of scale setting due to small size. When the laptop is connected to the external display, the scale setting does nothing and almost everything looks pretty small and hard to read, only gnome-terminal content seems to follow the scaling setting but windows decorators and app menus are pretty small. If I disconnect the external display everything works as expected (at least with the usual apps like GNOME apps, Firefox, Chrome, etc...). I'm using Ubuntu 18.10 with latest updates installed. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 13:08:45 2019 DistUpgraded: 2019-01-05 13:19:27,114 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py ([Errno 2] No such file or directory: './xorg_fix_proprietary.py': './xorg_fix_proprietary.py') DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07e6] InstallationDate: Installed on
[Touch-packages] [Bug 1813584] Re: libidn ftbfs in 18.04 LTS
** Changed in: libidn (Ubuntu Bionic) Assignee: (unassigned) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libidn in Ubuntu. https://bugs.launchpad.net/bugs/1813584 Title: libidn ftbfs in 18.04 LTS Status in libidn package in Ubuntu: New Status in libidn source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libidn ftbfs. = GNU Libidn 1.33: lib/gltests/test-suite.log = # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 .. contents:: :depth: 2 FAIL: test-lock === Starting test_lock ...FAIL test-lock (exit status: 134) SKIP: test-setlocale1.sh Skipping test: no locale for testing is installed SKIP test-setlocale1.sh (exit status: 77) FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) Testsuite summary for GNU Libidn 1.33 # TOTAL: 34 # PASS: 31 # SKIP: 1 # XFAIL: 0 # FAIL: 2 # XPASS: 0 # ERROR: 0 See lib/gltests/test-suite.log Please report to bug-lib...@gnu.org Makefile:2137: recipe for target 'test-suite.log' failed make[6]: *** [test-suite.log] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libidn/+bug/1813584/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813591] Re: pygobject ftbfs in 18.04 LTS
** Changed in: pygobject (Ubuntu Bionic) Assignee: (unassigned) => Jeremy Bicha (jbicha) ** Changed in: pygobject (Ubuntu) Status: New => Fix Released ** Changed in: pygobject (Ubuntu Bionic) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1813591 Title: pygobject ftbfs in 18.04 LTS Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Bionic: Triaged Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html pygobject ftbfs. == FAIL: test_filenames (test_glib.TestGLib) -- Traceback (most recent call last): File "/<>/tests/test_glib.py", line 66, in test_filenames self.assertTrue(isinstance(res, bytes)) AssertionError: False is not true -- Ran 1211 tests in 4.072s FAILED (failures=1, skipped=4, expected failures=12) torture test 1 (1 iterations): 0.012186 secs torture test 2 (1 iterations): 0.068459 secs torture test 3 (1 iterations): 0.029216 secs torture test 4 (1 iterations): 0.065890 secs Total: 0.175751 sec Makefile:905: recipe for target 'check.real' failed make[5]: *** [check.real] Error 1 make[5]: Leaving directory '/<>/build-3.6/tests' Makefile:900: recipe for target 'check-local' failed make[4]: *** [check-local] Error 2 Makefile:738: recipe for target 'check-am' failed make[3]: *** [check-am] Error 2 Makefile:691: recipe for target 'check-recursive' failed make[2]: *** [check-recursive] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1813591/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Brian, On 1/26/19 12:47 AM, Brian Murray wrote: > Hello Marc, or anyone else affected, > > Accepted ubiquity into bionic-proposed. The package will build now and > be available at > https://launchpad.net/ubuntu/+source/ubiquity/18.04.14.11 in a few > hours, and then in the -proposed repository. If I understand well, ubiquity is the installer, so the iso image must be tested. Where can I find a 18.04-daily iso image? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Similar issue appears when zram swap is used, see bug #1781746 This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. Status in initramfs-tools package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Status in initramfs-tools source package in Bionic: Fix Committed Status in ubiquity source package in Bionic: Fix Committed Bug description: [SRU Justification] A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. 10. Reboot. 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. [Regression potential] This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644996] Re: logrotate config uses syslog group
@brian-murray , why you added "rls-bb-notfixing"? logrotate doesn't work at all in lots lxd containers because of this bug, lots of users are affected, why don't accept this one line patch into LTS releases -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813587] Re: libunistring ftbfs on 18.04 LTS
Cosmic got that workaround, it includes no details about the issue it fixes but could be the same one? http://launchpadlibrarian.net/379762076/libunistring_0.9.10-1_0.9.10-1ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libunistring in Ubuntu. https://bugs.launchpad.net/bugs/1813587 Title: libunistring ftbfs on 18.04 LTS Status in libunistring package in Ubuntu: New Status in libunistring source package in Bionic: New Bug description: according to http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html libunistring ftbfs. FAIL: test-thread_create glthread_create failed FAIL test-thread_create (exit status: 1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/1813587/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
Thankfully rbalint (who wrote the test) takes a look and knows the moving bits of this case much better than I do. Therefore I'm gladly yielding this issue to him and hope this isn't become too much of a rabbit hole to get lost in. ** Changed in: livecd-rootfs (Ubuntu) Assignee: (unassigned) => Balint Reczey (rbalint) ** No longer affects: util-linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813738] [NEW] laptop doesnt wake up
Public bug reported: after the latest update my laptop does not wake up if the external monitor was plugged in when it went to sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 10:53:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062c] InstallationDate: Installed on 2018-12-03 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0THWR2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0THWR2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813738 Title: laptop doesnt wake up Status in gnome-shell package in Ubuntu: Incomplete Bug description: after the latest update my laptop does not wake up if the external monitor was plugged in when it went to sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 10:53:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062c] InstallationDate: Installed on 2018-12-03 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0THWR2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0THWR2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813735] Re: dual taskbar ?
*** This bug is a duplicate of bug 1812407 *** https://bugs.launchpad.net/bugs/1812407 This sounds like an issue that was mentioned in bug 1769383, as well as bug 1769383 itself. 1. Please ensure no extensions are installed. Simply disabling them isn't enough. 2. Please remember to attach a screenshot. ** Package changed: xorg (Ubuntu) => gnome-shell-extension-ubuntu-dock (Ubuntu) ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813735 Title: dual taskbar ? Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: when the computer stays locked for a long time (let's say, the whole night), a taskbar appears on top of the lock screen. when unlocked, it seems that there is 2 taskbars (with little margin differences, see attached screencast). config : ubuntu 18.10 standart ubuntu desktop dock configured at bottom no gnome extension activated many applications running (haven't done the test without apps running) apps are still launchable, only the margin difference is annoying. haven't tried to launch app from the lock screen, it may be a security issue. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 09:28:53 2019 DistUpgraded: 2018-10-22 03:09:20,483 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1215] InstallationDate: Installed on 2018-04-03 (300 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ea369caf-e759-4349-904a-b584e8d71d5b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-10-22 (99 days ago) dmi.bios.date: 12/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd12/25/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.1-0~c~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.1-0~c~padoka0 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1813735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813738] Re: laptop doesnt wake up
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813738 Title: laptop doesnt wake up Status in gnome-shell package in Ubuntu: Incomplete Bug description: after the latest update my laptop does not wake up if the external monitor was plugged in when it went to sleep. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 10:53:33 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 [1028:062c] InstallationDate: Installed on 2018-12-03 (56 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E5550 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0THWR2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/18/2015:svnDellInc.:pnLatitudeE5550:pvr:rvnDellInc.:rn0THWR2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5550 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813735] Re: dual taskbar ?
*** This bug is a duplicate of bug 1812407 *** https://bugs.launchpad.net/bugs/1812407 ** Attachment added: "taskbar-2019-01-29_09.36.08.mkv" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1813735/+attachment/5233505/+files/taskbar-2019-01-29_09.36.08.mkv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813735 Title: dual taskbar ? Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: when the computer stays locked for a long time (let's say, the whole night), a taskbar appears on top of the lock screen. when unlocked, it seems that there is 2 taskbars (with little margin differences, see attached screencast). config : ubuntu 18.10 standart ubuntu desktop dock configured at bottom no gnome extension activated many applications running (haven't done the test without apps running) apps are still launchable, only the margin difference is annoying. haven't tried to launch app from the lock screen, it may be a security issue. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 09:28:53 2019 DistUpgraded: 2018-10-22 03:09:20,483 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1215] InstallationDate: Installed on 2018-04-03 (300 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ea369caf-e759-4349-904a-b584e8d71d5b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-10-22 (99 days ago) dmi.bios.date: 12/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd12/25/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.1-0~c~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.1-0~c~padoka0 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1813735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
It seems it builds rootfs three times. 1. Building rootfs for project: 'ubuntu-base' subproject: '' template: '' in /tmp/tmp.xDZut7D9xl/ubuntu-base:: 2. Building rootfs for project: 'ubuntu-cpc' subproject: '' template: 'ubuntu-cpc' in /tmp/tmp.xDZut7D9xl/ubuntu-cpc::ubuntu-cpc 3. Building rootfs for project: 'ubuntu-cpc' subproject: 'minimized' template: 'ubuntu-cpc' in /tmp/tmp.HhlWE1BxmO/ubuntu-cpc:minimized :ubuntu-cpc Of these #1 works and #2/#3 fail, so is it related to the "ubuntu-cpc" template? I don't know enough about it, but try to find something worth to debug ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813735] [NEW] dual taskbar ?
Public bug reported: when the computer stays locked for a long time (let's say, the whole night), a taskbar appears on top of the lock screen. when unlocked, it seems that there is 2 taskbars (with little margin differences, see attached screencast). config : ubuntu 18.10 standart ubuntu desktop dock configured at bottom no gnome extension activated many applications running (haven't done the test without apps running) apps are still launchable, only the margin difference is annoying. haven't tried to launch app from the lock screen, it may be a security issue. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:07:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 415.27 Thu Dec 20 17:25:03 CST 2018 GCC version: gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1) ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jan 29 09:28:53 2019 DistUpgraded: 2018-10-22 03:09:20,483 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 415.27, 4.18.0-13-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070 Ti] [10de:1b82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Device [196e:1215] InstallationDate: Installed on 2018-04-03 (300 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) MachineType: Gigabyte Technology Co., Ltd. AB350M-Gaming 3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=ea369caf-e759-4349-904a-b584e8d71d5b ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-10-22 (99 days ago) dmi.bios.date: 12/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F24 dmi.board.asset.tag: Default string dmi.board.name: AB350M-Gaming 3-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF24:bd12/25/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350M-Gaming 3 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.3.1-0~c~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.3.1-0~c~padoka0 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1813735 Title: dual taskbar ? Status in xorg package in Ubuntu: New Bug description: when the computer stays locked for a long time (let's say, the whole night), a taskbar appears on top of the lock screen. when unlocked, it seems that there is 2 taskbars (with little margin differences, see attached screencast). config : ubuntu 18.10 standart ubuntu desktop dock configured at bottom no gnome extension activated many applications running (haven't done the test without apps running) apps are still launchable, only the margin difference is annoying. haven't tried to launch app from the lock screen, it may be a security issue. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..07.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpu
[Touch-packages] [Bug 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
FYI: For the sake of giving it a try I restarted one of the fails with all-proposed=1 in the background. As of now this is still running ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813730] Re: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux
I happened to realize that the failure changed since yesterday. The last two logs: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/l/livecd-rootfs/20190128_084254_b5919@/log.gz https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/l/livecd-rootfs/20190128_090339_25cc4@/log.gz Point to a different issue being triggered now. The tail of the fails is now: + udevadm settle + '[' -n /dev/mapper/loop0p1 -a -b /dev/mapper/loop0p1 ']' + '[' -e /etc/mtab ']' + e2fsck -y -E discard /dev/mapper/loop0p1 e2fsck 1.44.5 (15-Dec-2018) /dev/mapper/loop0p1 is in use. e2fsck: Cannot continue, aborting. + clean_loops + local kpartx_ret + local kpartx_stdout + '[' -n binary/boot/disk.ext4 ']' + sync + kpartx_ret= ++ kpartx -v -d binary/boot/disk.ext4 + kpartx_stdout='loop0p1 is in use. Not removingloop deleted : /dev/loop0' + kpartx_ret=1 + echo 'loop0p1 is in use. Not removingloop deleted : /dev/loop0' loop0p1 is in use. Not removingloop deleted : /dev/loop0 + '[' -n 1 ']' + grep -q 'loop deleted' + echo 'loop0p1 is in use. Not removingloop deleted : /dev/loop0' + echo 'Suppressing kpartx returning error (#860894)' Suppressing kpartx returning error (#860894) + unset backing_img + '[' -z /dev/mapper/loop0p1 ']' + unset loop_device + unset loop_raw + unset rootfs_dev_mapper E: config/hooks/014-disk-image.binary failed (exit non-zero). You should check for errors. P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... That matches what I see when running it in autopkgtest locally which means it might be debuggable after all. Unfortunately the test runs some cleanup stages that make the situation that made it fail disappear. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1813730] Re: autopkgtest fails configuring required packages in bootstrap calling out util-linux
Adding all currently known packages that are affected being non migratable due to this issue (so that package maintainers are aware and join forces here). ** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Also affects: qemu (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Invalid ** Also affects: rsync (Ubuntu) Importance: Undecided Status: New ** Changed in: rsync (Ubuntu) Status: New => Invalid ** Summary changed: - autopkgtest fails configuring required packages in bootstrap calling out util-linux + livecd-rootfs autopkgtest fails configuring required packages calling out util-linux ** Also affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Changed in: python-apt (Ubuntu) Status: New => Invalid ** Also affects: xz-utils (Ubuntu) Importance: Undecided Status: New ** Changed in: xz-utils (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1813730 Title: livecd-rootfs autopkgtest fails configuring required packages calling out util-linux Status in livecd-rootfs package in Ubuntu: New Status in python-apt package in Ubuntu: Invalid Status in qemu package in Ubuntu: Invalid Status in rsync package in Ubuntu: Invalid Status in util-linux package in Ubuntu: New Status in xz-utils package in Ubuntu: Invalid Bug description: As of recently autopkgtests of livecd-rootfs fail. It seems unrelated to which package is tested, the failure is always the same. => http://autopkgtest.ubuntu.com/packages/l/livecd-rootfs/disco/amd64 It is failing for qemu, xz-utils, rsync, python-apt and qemu. From the log we see all sub-cases fail with a tail like: W: Failure while configuring required packages. W: See /tmp/tmp.qy1mya9uZ0/ubuntu-base::/chroot/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) P: Begin unmounting filesystems... P: Saving caches... P: Begin unmounting filesystems... P: Saving caches... autopkgtest [13:39:10]: test default-bootstraps: ---] default-bootstraps FAIL non-zero exit status 1 Full log of one such cases: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-disco/disco/amd64/l/livecd- rootfs/20190125_133950_dc236@/log.gz I found no related open bugs in https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bugs?orderby=-date_last_updated&start=0 nor in https://bugs.launchpad.net/ubuntu/+source/util-linux/+bugs?orderby=-date_last_updated&start=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1813730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp