[Touch-packages] [Bug 1754415] Re: cupsd crashed with SIGSEGV in ippCopyAttribute()
*** This bug is a duplicate of bug 1750514 *** https://bugs.launchpad.net/bugs/1750514 ** This bug is no longer a duplicate of private bug 1753766 ** This bug has been marked a duplicate of bug 1750514 cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest -- 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/1754415 Title: cupsd crashed with SIGSEGV in ippCopyAttribute() Status in cups package in Ubuntu: New Bug description: Just turn my pc on and this error apeared ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.6-5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 Date: Thu Mar 8 07:07:13 2018 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2018-02-08 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) Lpstat: device for HP-M521_GTI: socket://10.2.254.103 MachineType: Hewlett-Packard HP Compaq 6005 Pro SFF PC Papersize: a4 PpdFiles: HP_LaserJet_Pro_MFP_M521dn_68DA1F_: LaserJet Pro MFP M521dn HP_LaserJet_Pro_MFP_M521dn_DC590A_: LaserJet Pro MFP M521dn HP-M521_GTI: HP LaserJet Pro MFP M521 Postscript (recommended) HP_LaserJet_Pro_MFP_M521dn_615877_: LaserJet Pro MFP M521dn ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=550af015-9954-408f-81ad-053c28803cd4 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=550af015-9954-408f-81ad-053c28803cd4 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f160a3a8db3 : addl $0x1,0x38(%rdx) PC (0x7f160a3a8db3) ok source "$0x1" ok destination "0x38(%rdx)" (0x0038) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ippCopyAttribute () from /usr/lib/x86_64-linux-gnu/libcups.so.2 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in ippCopyAttribute() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/04/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.11 dmi.board.asset.tag: BRG112FHQ2 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: BRG112FHQ2 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:svnHewlett-Packard:pnHPCompaq6005ProSFFPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6005 Pro SFF PC dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1754415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1565940] Re: bluetoothctl systematically hangs when there is no bluetooth hardware
> My particular use case is to detect, inside a shell script, if there is any bluetooth hardware at all. I suggest a better way to detect Bluetooth hardware is to check with the kernel directly: if /sys/class/bluetooth/ exists and is non-empty then ... The directory is created when the first Bluetooth controller is added to the system, and becomes empty only after the last one is removed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1565940 Title: bluetoothctl systematically hangs when there is no bluetooth hardware Status in bluez package in Ubuntu: Fix Released Bug description: On a machine WITH bluetooth hardware, the 'bluetoothctl' command works correctly. For example, the command 'bluetoothctl < /dev/null' terminates correctly. On a machine WITHOUT bluetooth hardware, the 'bluetoothctl' command systematically hangs. Even the command 'bluetoothctl < /dev/null' systematically hangs. $ bluetoothctl & [1] 6208 $ ps -l $! F S UID PID PPID C PRI NI ADDR SZ WCHAN TTYTIME CMD 0 T 1001 6208 2525 0 80 0 - 9578 signal pts/1 0:00 bluetoothctl [1]+ Stopped bluetoothctl ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bluez 5.35-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4 Uname: Linux 4.2.0-34-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 4 20:09:39 2016 InstallationDate: Installed on 2015-07-20 (259 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: bluetooth MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-34-generic.efi.signed root=UUID=0d11df61-c758-41b1-9ec3-8310bf038b07 ro quiet splash vt.handoff=7 SourcePackage: bluez UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-22 (165 days ago) dmi.bios.date: 06/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2603 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A97 R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr2603:bd06/26/2015:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.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. hciconfig: rfkill: syslog: avril 03 15:10:45 urbah-sirius systemd[1]: Starting Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5)... avril 03 15:10:45 urbah-sirius NetworkManager[986]: Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so) avril 03 15:10:50 urbah-sirius systemd[1]: Started Automatic USB/Bluetooth printer setup (-devices-pci:00-:00:12.2-usb5-5\x2d5). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1565940/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
This bug is closed. If you have any issues at all, please log a new bug by running this command: ubuntu-bug bluez -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490349] Re: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted
first thing first: bluetooth device can be paired with command line. I have the same error on my eOS/ubuntu 16.04, "bluetoothd[17440]: Not enough free handles to register service", and have tried many many options, have desprated for a year. and today I've success connected my bluetooth headset via command line. following struction provided by "jeremy31" here at #4 : https://ubuntuforums.org/showthread.php?t=2338474 ps. at first the sound was config to use hsf/hfp be default, which will gave you horrible sound, change to A2DP Slink in pulseAudio will get much better sound. ps 2. after pair device via command line, the headset is show in system setting/bluetooth list. but new device can only be added via command line. hope this can help someone. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1490349 Title: 15:10 and 16.04: bluetoothd "Failed to start discovery: org.bluez.Error.NotReady" after bluetoothd restarted Status in bluez package in Ubuntu: Invalid Bug description: On 15:10 after the bluetooth service has been stopped and restarted it is not possible to scan or connect to devices: $ sudo systemctl restart bluetooth $ bluetoothctl [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default] [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse [bluetooth]# scan on Failed to start discovery: org.bluez.Error.NotReady To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1490349/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!
Yep, mine reverts to 1024x760 76Hz and has no options whatsoever. It's a bit of a showstopper. dmesg: nvidia: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' works: Linux betlogbrick 3.13.0-142-generic #191-Ubuntu SMP Fri Feb 2 12:13:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux fails: *3.13.0-143* -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! Status in gcc: New Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1741694] Re: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin
[Expired for coreutils (Ubuntu) because there has been no activity for 60 days.] ** Changed in: coreutils (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1741694 Title: package coreutils 8.25-2ubuntu2 [modified: bin/cat bin/chgrp bin/chmod bin/chown bin/cp bin/date bin/dd bin/df bin/dir bin/echo bin/false bin/ln bin/ls bin/mkdir bin/mknod bin/mktemp bin/mv bin/pwd bin/readlink bin/rm bin/rmdir bin/sleep bin/stty bin/sync bin/touch bin/true bin/uname bin/vdir usr/bin/basename usr/bin/dircolors usr/bin/hostid usr/bin/md5sum usr/bin/shuf usr/bin/stat usr/bin/stdbuf usr/bin/unlink usr/lib/x86_64-linux-gnu/coreutils/libstdbuf.so usr/sbin/chroot usr/share/doc/coreutils/changelog.Debian.gz usr/share/man/...] failed to install/upgrade: o pacote coreutils não está pronto para configuração não pode configurar (status actual `half-installed') Status in coreutils package in Ubuntu: Expired Bug description: Im just trying to install 0 AD game. :( ProblemType: Package DistroRelease: Ubuntu 16.04 ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98 Uname: Linux 4.4.0-104-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Sat Jan 6 21:42:52 2018 DpkgTerminalLog: dpkg: erro ao processar o pacote coreutils (--configure): o pacote coreutils não está pronto para configuração não pode configurar (status actual `half-installed') ErrorMessage: o pacote coreutils não está pronto para configuração não pode configurar (status actual `half-installed') InstallationDate: Installed on 2017-01-20 (351 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1741694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751225] Re: apt update hangs when repository url is redirect url
Hello, I verified this -proposed pkg is working. 1. upgrade apt pkg 2. insert above url in test case to sources.list 3. apt update 4. check if it hangs or not dpkg -l ii apt 1.2.26 amd64commandline package manager Thanks ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- 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/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Artful: Invalid Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] Could cause some other zero-content redirects to break again (seems unlikely...). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
Please see if this issue can be solved after remove xserver-xorg-video- intel. Also, 945GME is quite different to the one used by original bug reporter... -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754537] [NEW] Scilab 5.5.2 cannot create Java Main Class on Ubuntu 14.04.
Public bug reported: On March 5, after months of working regularly, Scilab 5.5.2 stopped working altogether if launched from GUI. Trying to launch from terminal, it still did not work but at least informed me that it could not create a Java Main Class, and some more details: Exception in thread "main" java.lang.NullPointerException at org.scilab.modules.gui.utils.ConfigManager.checkVersion(Unknown Source) at org.scilab.modules.gui.utils.ConfigManager.createUserCopy(Unknown Source) at org.scilab.modules.core.Scilab.(Unknown Source) Packages: OpenGL version string: 3.0 Mesa 10.1.3 Scilab; 5.5.0-2 libjogl2-ini; 2.1.5-1ubuntu3 libjogl1-java; 2.1.5-1ubuntu3 Ubuntu 14.04.5 LTS Release: 14.04 A related bug is: https://bugs.launchpad.net/mesa/+bug/1742894, which has been resolved for Ubuntu Xenial with a new version of libjogl2-java. No such fix seems to be available for Trusty, however. ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1754537 Title: Scilab 5.5.2 cannot create Java Main Class on Ubuntu 14.04. Status in mesa package in Ubuntu: New Bug description: On March 5, after months of working regularly, Scilab 5.5.2 stopped working altogether if launched from GUI. Trying to launch from terminal, it still did not work but at least informed me that it could not create a Java Main Class, and some more details: Exception in thread "main" java.lang.NullPointerException at org.scilab.modules.gui.utils.ConfigManager.checkVersion(Unknown Source) at org.scilab.modules.gui.utils.ConfigManager.createUserCopy(Unknown Source) at org.scilab.modules.core.Scilab.(Unknown Source) Packages: OpenGL version string: 3.0 Mesa 10.1.3 Scilab; 5.5.0-2 libjogl2-ini; 2.1.5-1ubuntu3 libjogl1-java; 2.1.5-1ubuntu3 Ubuntu 14.04.5 LTS Release: 14.04 A related bug is: https://bugs.launchpad.net/mesa/+bug/1742894, which has been resolved for Ubuntu Xenial with a new version of libjogl2-java. No such fix seems to be available for Trusty, however. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1754537/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!
I had the same problem however I don't have a Nvidia driver (Intel HD Graphics instead) I got this message before enter a loop: video: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' drm: version magic '3.13.0-143-generic SMP mod_unload modversions ' should be '3.13.0-143-generic SMP mod_unload modversions retpoline ' -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! Status in gcc: New Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1750937/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1753884] Re: session logout after suspend
Simon: 1) Regarding the crash files, it is best if one reports the crash files as documented at https://help.ubuntu.com/community/ReportingBugs (not attach them). 2) Regarding the crash files, could you please advise to their file name(s)? 3) Regarding upgrading, if you do so and the problem is fixed, then that is the best outcome, and doesn't cause anything negative to happen. ** Description changed: - When I close the lid of my laptop, my session gets logged out, where I - would expect the lock screen simply to come up. + Only when I have a second monitor plugged in, if I close the lid of my + laptop, my session gets logged out. What I'm expecting is the lock + screen comes up. + + Sometimes (but not always) the second monitor will flash the "logged + out" screen for a second or two before going dim. + + I have "Suspend even if external monitor is plugged in" enabled in Tweak + Tools. + + WORKAROUND: Suspend via the GUI with the lid open. + + WORKAROUND: Unplug the second monitor before closing the lid. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Mar 6 18:07:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2018-02-15 (19 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20AQ009HUS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic root=UUID=6f20d80f-81f4-40c1-aafd-95b2c5de55ed ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/29/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET78WW (2.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AQ009HUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET78WW(2.28):bd07/29/2014:svnLENOVO:pn20AQ009HUS:pvrThinkPadT440s:rvnLENOVO:rn20AQ009HUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20AQ009HUS dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A -- 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/1753884 Title: session logout after suspend Status in xorg package in Ubuntu: Incomplete Bug description: Only when I have a second monitor plugged in, if I close the lid of my laptop, my session gets logged out. What I'm expecting is the lock screen comes up. Sometimes (but not always) the second monitor will flash the "logged out" screen for a second or two before going dim. I have "Suspend even if external monitor is plugged in" enabled in Tweak Tools. WORKAROUND: Suspend via the GUI with the lid open. WORKAROUND: Unplug the second monitor before closing the lid. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Mar 6 18:07:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated G
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
Ubuntu 17.04 reached End of Life in January 2018. Please upgrade to Ubuntu 17.10 which is not affected by this bug. Ubuntu releases and their End of Life dates can be found at https://wiki.ubuntu.com/Releases ** Changed in: network-manager (Ubuntu Zesty) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Zesty: Won't Fix Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 715141] Re: Default NTP servers do not have AAAA records
@paelzer: There was a plan to enable IPv6 on all pools last year: https://community.ntppool.org/t/intention-to-enable-ipv6-by-default- in-2017/91 To my knowledge (and based on my brief checks just now) this didn't happen. I suspect the reasons for this are insufficient time to change the pool implementation, and (possibly) fear that the small number of IPv6 servers in the pool would be overwhelmed. IPv6 on all ntp.ubuntu.com servers is doable, but subject to Canonical IS work priorities. Best to drop us a ticket about this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/715141 Title: Default NTP servers do not have records Status in ntp package in Ubuntu: Fix Released Bug description: Binary package hint: ntp When installing ntp on an IPv6 only host, the kindly provided ntp.ubuntu.com does not work, because it does not have a record. Please provide IPv6 connectivity for this host. This affects all releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754472] Re: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754472 Title: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there Status in systemd package in Ubuntu: New Bug description: The test really seems to be triggered all of the time to resolve a flaky test. That is just not worth the test. But it provides goo coverage, so an override in britney would loose all that. Lets skip the offending test on the arch it is known to be flaky (s390x). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727753] Re: Installer crash reports failing to attach partman log
** Changed in: apport (Ubuntu) Status: New => Incomplete ** Changed in: apport (Ubuntu) Status: Incomplete => Confirmed ** Changed in: ubiquity (Ubuntu) Status: New => Fix Released ** Changed in: apport (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: apport (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: apport (Ubuntu) Assignee: (unassigned) => Tao (jupia) ** Changed in: ubiquity (Ubuntu) Assignee: (unassigned) => Tao (jupia) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1727753 Title: Installer crash reports failing to attach partman log Status in apport package in Ubuntu: Fix Released Status in ubiquity package in Ubuntu: Fix Released Bug description: Recent install crash reports have all listed a hook error and fail to attach the partman log file needed to help debug why the install failed. I think this is a grave bug that will require a respin of the 17.10 release ASAP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1727753/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur
Ok, here it is. YMMV but this should theoretically fix systemd on 18.04 WSL. ** Attachment added: "Fix wsl 18.04 bash" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+attachment/5073801/+files/fixwslsystemd.sh -- 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/1748659 Title: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: This was fresh Ubuntu 16.04 instance on Windows 10, running inside a Virtual Box on an iMac. I did an apt-get dist-upgrade before attempting to upgrade to 18.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Sat Feb 10 18:59:28 2018 Dmesg: ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.2.24 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
** No longer affects: maas ** No longer affects: nplan (Ubuntu) ** No longer affects: systemd (Ubuntu) ** Changed in: cloud-init Status: New => Confirmed ** Changed in: cloud-init Importance: Undecided => Medium ** Changed in: cloud-init Assignee: (unassigned) => Ryan Harper (raharper) -- 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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: Confirmed Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, you will see that netplan config is correctly to the 10.90.90.1 nameserver, but in resolv.conf that's a local address. Resolv.conf should really be configured to use the provided DNS server(s). That said, despite that fact, DNS resolution doesn't work with the local address. Bionic -- ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp0s25: match: macaddress: b8:ae:ed:7d:17:d2 mtu: 1500 nameservers: addresses: - 10.90.90.1 search: - maaslab - maas set-name: enp0s25 bridges: br0: addresses: - 10.90.90.3/24 gateway4: 10.90.90.1 interfaces: - enp0s25 parameters: forward-delay: 15 stp: false ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search maaslab maas ubuntu@node01:~$ ping google.com ping: google.com: Temporary failure in name resolution [...] ubuntu@node01:~$ sudo vim /etc/resolv.conf ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.90.90.1 search maaslab maas ubuntu@node01:~$ ping google.com PING google.com (172.217.0.174) 56(84) bytes of data. 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 time=4.46 ms 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 time=4.38 ms = Xenial == ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback dns-nameservers 10.90.90.1 dns-search maaslab maas auto enp0s25 iface enp0s25 inet static address 10.90.90.162/24 gateway 10.90.90.1 mtu 1500 ubuntu@node05:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.90.90.1 search maaslab maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727825] Re: networkd DHCP immediately drops lease ( on igbx cards )
Sorry to bug-report-and-run my test hardware was otherwise occupied so couldn't retest. Happily latest Bionic installer does not seem to have this issue for me any more. -- 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/1727825 Title: networkd DHCP immediately drops lease ( on igbx cards ) Status in systemd package in Ubuntu: New Bug description: On new install of 17.10 systemd-networkd loops with: Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service... Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed Oct 23 16:45:24 san-jose systemd[1]: Started Network Service. Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 10.30.3.94/24 via 12 Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The name org.freedesktop Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 10.30.3.94/24 via 12 Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The name org.freedesktop Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost that is the correct interface and address. If I manually run 'dhclient nep129s0f0' the lease sticks and 'journalctl -fu systemd-networkd' shows: Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 10.30.3.94/24 via 12 Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The name org.freedesktop Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured I have verified this is reproducible on other systems with ixgbe based add in cards. igb (1G) cards seem to behave properly as do a random assortment of onboard devices and virtio devices inside VMs. Based on a pseudo random selection of my available gear it does seem hardware specific but this is our only flavor of 10G nic (and we have kindof a lot of them). Since isc-dhcp-client can bring up the interface on the commandline I don't *think* it's a driver issue. root@host:~# lsb_release -rd;uname -r ; dpkg -l nplan systemd Description: Ubuntu 17.10 Release: 17.10 4.13.0-16-generic Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==-==-==-= ii nplan 0.30 amd64 YAML network configuration abstraction fo ii systemd 234-2ubuntu12 amd64 system and service manager my current workaround: root@host:~# cat /etc/rc.local #!/bin/sh dhclient enp129s0f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754472] Re: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there
(untested) debdiff as suggestion. I think this is trivial and will make the other tests more meaningful as a flaky test is more or less worth nothing (and consumed time on CI and of people). ** Patch added: "fix-systemd-flaky-fsck.debdiff" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+attachment/5073591/+files/fix-systemd-flaky-fsck.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/1754472 Title: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there Status in systemd package in Ubuntu: New Bug description: The test really seems to be triggered all of the time to resolve a flaky test. That is just not worth the test. But it provides goo coverage, so an override in britney would loose all that. Lets skip the offending test on the arch it is known to be flaky (s390x). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754472] [NEW] autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there
Public bug reported: The test really seems to be triggered all of the time to resolve a flaky test. That is just not worth the test. But it provides goo coverage, so an override in britney would loose all that. Lets skip the offending test on the arch it is known to be flaky (s390x). ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754472 Title: autopkgtest: systemd-fsck test is flaky on s390x, lets skip it there Status in systemd package in Ubuntu: New Bug description: The test really seems to be triggered all of the time to resolve a flaky test. That is just not worth the test. But it provides goo coverage, so an override in britney would loose all that. Lets skip the offending test on the arch it is known to be flaky (s390x). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur
Update for you all. I forced systemd down to the 16.04 version, reconfigured it and it was happy. As for upgrading it to the 18.04 version, YOU MUST PURGE THE ENTIRE /usr/lib/tempfiles.d/ DIRECTORY. One I did that, even thought the install will fail, I was able to get systemd reconfigured. It now properly responds to dpkg --configure commands and the system is no longer in a broken state. As for how to resolve this upstream, I have a felling this has to do with how WSL handles systemd (as, it doesn't, because WSL ignores systemd for the most part.) most likely related to the fact that we're not working with kernels, and systemd doesn't have anything to hook into during the upgrade. If you're having trouble with a system you forced to the 18.04 beta let me know as I'm going to write a script here in a second to resolve the issue for you. -- 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/1748659 Title: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: This was fresh Ubuntu 16.04 instance on Windows 10, running inside a Virtual Box on an iMac. I did an apt-get dist-upgrade before attempting to upgrade to 18.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Sat Feb 10 18:59:28 2018 Dmesg: ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.2.24 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices
I upgraded linux-firmware/1.157.16 to linux-firmware/1.157.17, which is what I think is neede to fix bug 1747336, but it made no difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1745828 Title: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: It is ON and VISIBLE in the control panel. My iPhone can see two other devices but it can't see the computer, and the computer can't see anything, even if left searching for tens of minutes. The previous answers listed below suggest the following diagnostics Bluetooth not working after update How can I make my bluetooth works on Ubuntu 16.04? Ubuntu 16.04 bluetooth not working (Dell XPS13) Bluetooth (Atheros AR3012) not working on Ubuntu 16.04 Bluetooth not working on Ubuntu 16.04 LTS Bluetooth cannot find any devices Stuck on a bluetooth problem The service seems to be running /home >sudo service bluetooth status ● bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago Docs: man:bluetoothd(8) Main PID: 790 (bluetoothd) Status: "Running" CGroup: /system.slice/bluetooth.service └─790 /usr/lib/bluetooth/bluetoothd Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.87 Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: sender=:1.12 Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for Headset Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: sender=:1. and not blocked /home >rfkill list 0: hci0: Bluetooth Soft blocked: no Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no I have edited /etc/bluetooth/main.conf to include AutoEnable=true but I noted that the entire file was commented out. The kernel seems reasonably up to date >uname -a Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I wonder if I need a device driver, but I have no idea how to find out. The following diagnostics may help some of you knowledgeable people find out. >hcitool dev Devices: hci0 24:0A:64:F5:EE:86 and the output of dmsg is >dmesg | grep Blue [2.030855] usb 1-1.4: Product: Bluetooth Radio [ 13.806355] Bluetooth: Core ver 2.22 [ 13.806369] Bluetooth: HCI device and connection manager initialized [ 13.806372] Bluetooth: HCI socket layer initialized [ 13.806373] Bluetooth: L2CAP socket layer initialized [ 13.806377] Bluetooth: SCO socket layer initialized [ 13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821 [ 13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin [ 13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin [ 13.877382] Bluetooth: hci0: rom_version status=0 version=1 [ 13.877387] Bluetooth: cfg_sz 0, total size 17428 [ 16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 16.550281] Bluetooth: BNEP filters: protocol multicast [ 16.550284] Bluetooth: BNEP socket layer initialized [ 27.868345] Bluetooth: RFCOMM TTY layer initialized [ 27.868350] Bluetooth: RFCOMM socket layer initialized [ 27.868354] Bluetooth: RFCOMM ver 1.11 and of lsusb is >lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 004: ID 13d3:3414 IMC Networks Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Thanking you in anticip
[Touch-packages] [Bug 1754453] Re: vim.gtk3 crashed with SIGSEGV in kill()
*** This bug is a duplicate of bug 1721280 *** https://bugs.launchpad.net/bugs/1721280 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1721280, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1754453/+attachment/5073461/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754453/+attachment/5073463/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754453/+attachment/5073467/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754453/+attachment/5073468/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754453/+attachment/5073469/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754453/+attachment/5073471/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754453/+attachment/5073472/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1721280 vim.gtk3 crashed with SIGSEGV in __new_sem_wait_fast() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1754453 Title: vim.gtk3 crashed with SIGSEGV in kill() Status in vim package in Ubuntu: New Bug description: vim.gtk3 (but on the terminal) is crashing whenever I try to save a commit message. I had to resort to using vim.tiny, which saved successfully. I tried to reproduce this in an empty git repository without success. Could be related to any number of plugins I have enabled by default. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: vim-gtk3 2:8.0.0197-4ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 8 13:50:02 2018 ExecutablePath: /usr/bin/vim.gtk3 InstallationDate: Installed on 2017-12-09 (88 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/bin/editor /home/username/.oh-my-zsh/.git/COMMIT_EDITMSG Signal: 11 SourcePackage: vim StacktraceTop: kill () at ../sysdeps/unix/syscall-template.S:84 mch_exit () getout () () at /lib/x86_64-linux-gnu/libpthread.so.0 __new_sem_wait_fast (definitive_result=0, sem=0x0) at sem_waitcommon.c:135 Title: vim.gtk3 crashed with SIGSEGV in kill() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1754453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1748659] Re: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess retur
I've gotten the release to upgrade to 18.04 on WSL, the issue I'm running into however is that systemd will not reinstall. TBH WSL does not require systemd to operate, but it defiantly makes the system angry if it can't setup a way to manage startup. Just for anyone reading this via google, if you want to push your WSL build to 18.04, DON'T. For those of you who are ignoring my warning, you can push it to 18.04 BUT YOU MUST HOLD SYSTEMD. If you try to run an upgrade and allow systemd to be upgraded the upgrade will fail and you will be left with a completely borked system. My thoughts at the moment is to try and grab a 16.04 systemd package and use that until we get a stable 18.04 one. -- 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/1748659 Title: Windows 10 Ubuntu 16.04 upgrade to 18.04: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: This was fresh Ubuntu 16.04 instance on Windows 10, running inside a Virtual Box on an iMac. I did an apt-get dist-upgrade before attempting to upgrade to 18.04. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: systemd 235-3ubuntu3 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Function not implemented Date: Sat Feb 10 18:59:28 2018 Dmesg: ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 Lsusb: Error: command ['lsusb'] failed with exit code 1: ProcInterrupts: ProcKernelCmdLine: BOOT_IMAGE=/kernel init=/init ro ProcModules: Error: command ['sort', '/proc/modules'] failed with exit code 2: sort: cannot read: /proc/modules: No such file or directory RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.2.24 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. Title: package systemd 235-3ubuntu3 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-02-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address
trusty: host~$ virsh domif-setlink lp1718568-trusty vnet4 down Device updated successfully ubuntu@lp1718568-trusty:~$ dpkg -l | grep isc-dhcp ii isc-dhcp-client 4.2.4-7ubuntu12.12 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.12 amd64common files used by all the isc-dhcp* packages ubuntu@lp1718568-trusty:~$ sudo ip l set down dev eth1 ubuntu@lp1718568-trusty:~$ sudo ip l show eth1 3: eth1: mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:1f:1a:c6 brd ff:ff:ff:ff:ff:ff ubuntu@lp1718568-trusty:~$ sudo dhclient -v -6 eth1 Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no link-local IPv6 address for eth1 with -updates pkg: ubuntu@lp1718568-trusty:~$ dpkg -l | grep isc-dhcp ii isc-dhcp-client 4.2.4-7ubuntu12.13 amd64ISC DHCP client ii isc-dhcp-common 4.2.4-7ubuntu12.13 amd64common files used by all the isc-dhcp* packages ubuntu@lp1718568-trusty:~$ sudo ip l set down dev eth1 ubuntu@lp1718568-trusty:~$ sudo ip l show eth1 3: eth1: mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:1f:1a:c6 brd ff:ff:ff:ff:ff:ff ubuntu@lp1718568-trusty:~$ sudo dhclient -v -6 eth1 Internet Systems Consortium DHCP Client 4.2.4 Copyright 2004-2012 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ (blocks) host$ virsh domif-setlink lp1718568-trusty vnet4 up Device updated successfully Listening on Socket/eth1 Sending on Socket/eth1 PRC: Soliciting for leases (INIT). XMT: Forming Solicit, 0 ms elapsed. XMT: X-- IA_NA 00:1f:1a:c6 XMT: | X-- Request renew in +3600 XMT: | X-- Request rebind in +5400 XMT: Solicit on eth1, interval 1010ms. RCV: Advertise message on eth1 from fe80::5054:ff:fec9:897c. RCV: X-- IA_NA 00:1f:1a:c6 RCV: | X-- starts 1520536242 RCV: | X-- t1 - renew +3600 RCV: | X-- t2 - rebind +7200 RCV: | X-- [Options] RCV: | | X-- IAADDR 2001:db8::93 RCV: | | | X-- Preferred lifetime 604800. RCV: | | | X-- Max lifetime 2592000. RCV: X-- Server ID: 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c RCV: Advertisement recorded. PRC: Selecting best advertised lease. PRC: Considering best lease. PRC: X-- Initial candidate 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c (s: 155, p: 0). XMT: Forming Request, 0 ms elapsed. XMT: X-- IA_NA 00:1f:1a:c6 XMT: | X-- Requested renew +3600 XMT: | X-- Requested rebind +5400 XMT: | | X-- IAADDR 2001:db8::93 XMT: | | | X-- Preferred lifetime +7200 XMT: | | | X-- Max lifetime +7500 XMT: V IA_NA appended. XMT: Request on eth1, interval 1040ms. RCV: Reply message on eth1 from fe80::5054:ff:fec9:897c. RCV: X-- IA_NA 00:1f:1a:c6 RCV: | X-- starts 1520536243 RCV: | X-- t1 - renew +3600 RCV: | X-- t2 - rebind +7200 RCV: | X-- [Options] RCV: | | X-- IAADDR 2001:db8::93 RCV: | | | X-- Preferred lifetime 604800. RCV: | | | X-- Max lifetime 2592000. RCV: X-- Server ID: 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c PRC: Bound to lease 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c. ** Tags removed: verification-needed verification-needed-artful verification-needed-trusty verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-trusty verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1718568 Title: dhclient-script fails to wait for link-local address Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Zesty: Won't Fix Status in isc-dhcp source package in Artful: Fix Committed Status in isc-dhcp source package in Bionic: Fix Released Status in isc-dhcp package in Debian: New Bug description: [impact] bug 1633479 made a change to isc-dhcp to wait for an interface's link-local ipv6 address to switch from 'tentative' to normal, because all link-local addresses briefly go through a 'tentative' state while the kernel is performing ipv6 link-local 'duplicate address detection' (DAD). While in the 'tentative' state, dhclient can't take over the interface and send out dhcpv6 requests; it must wait until DAD completes. However, the change made in that bug does not account for the case where the 'tentative' check is done before the interface has even set up a link-local address; its case statement assumes if there is no 'tentative' or 'dadfailed' string in the output, the link-local address is ready to use. When the address
[Touch-packages] [Bug 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
Hello Guilherme, or anyone else affected, Accepted systemd into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/204-5ubuntu20.27 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Trusty) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-trusty -- 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/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: Fix Committed Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address
xenial: ubuntu@lp1718568-xenial:~$ dpkg -l | grep isc-dhcp ii isc-dhcp-client 4.3.3-5ubuntu12.9 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.3.3-5ubuntu12.9 amd64common files used by all of the isc-dhcp packages host$ virsh domif-setlink lp1718568-xenial vnet6 down Device updated successfully ubuntu@lp1718568-xenial:~$ sudo dhclient -v -6 ens7 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no link-local IPv6 address for ens7 If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. with -proposed pkg: ubuntu@lp1718568-xenial:~$ dpkg -l | grep isc-dhcp ii isc-dhcp-client 4.3.3-5ubuntu12.10 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.3.3-5ubuntu12.10 amd64common files used by all of the isc-dhcp packages ubuntu@lp1718568-xenial:~$ sudo ip l set down dev ens7 ubuntu@lp1718568-xenial:~$ sudo ip l show dev ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:f3:99:a8 brd ff:ff:ff:ff:ff:ff ubuntu@lp1718568-xenial:~$ sudo dhclient -v -6 ens7 Internet Systems Consortium DHCP Client 4.3.3 Copyright 2004-2015 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ (blocks) $ virsh domif-setlink lp1718568-xenial vnet6 up Device updated successfully Listening on Socket/ens7 Sending on Socket/ens7 Created duid \000\001\000\001\"4D\337RT\000\363\231\250. PRC: Soliciting for leases (INIT). XMT: Forming Solicit, 0 ms elapsed. XMT: X-- IA_NA 00:f3:99:a8 XMT: | X-- Request renew in +3600 XMT: | X-- Request rebind in +5400 XMT: Solicit on ens7, interval 1040ms. RCV: Advertise message on ens7 from fe80::5054:ff:fec9:897c. RCV: X-- IA_NA 00:f3:99:a8 RCV: | X-- starts 1520535647 RCV: | X-- t1 - renew +3600 RCV: | X-- t2 - rebind +7200 RCV: | X-- [Options] RCV: | | X-- IAADDR 2001:db8::98 RCV: | | | X-- Preferred lifetime 604800. RCV: | | | X-- Max lifetime 2592000. RCV: X-- Server ID: 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c RCV: Advertisement recorded. PRC: Selecting best advertised lease. PRC: Considering best lease. PRC: X-- Initial candidate 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c (s: 155, p: 0). XMT: Forming Request, 0 ms elapsed. XMT: X-- IA_NA 00:f3:99:a8 XMT: | X-- Requested renew +3600 XMT: | X-- Requested rebind +5400 XMT: | | X-- IAADDR 2001:db8::98 XMT: | | | X-- Preferred lifetime +7200 XMT: | | | X-- Max lifetime +7500 XMT: V IA_NA appended. XMT: Request on ens7, interval 990ms. RCV: Reply message on ens7 from fe80::5054:ff:fec9:897c. RCV: X-- IA_NA 00:f3:99:a8 RCV: | X-- starts 1520535648 RCV: | X-- t1 - renew +3600 RCV: | X-- t2 - rebind +7200 RCV: | X-- [Options] RCV: | | X-- IAADDR 2001:db8::98 RCV: | | | X-- Preferred lifetime 604800. RCV: | | | X-- Max lifetime 2592000. RCV: X-- Server ID: 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c PRC: Bound to lease 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1718568 Title: dhclient-script fails to wait for link-local address Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Zesty: Won't Fix Status in isc-dhcp source package in Artful: Fix Committed Status in isc-dhcp source package in Bionic: Fix Released Status in isc-dhcp package in Debian: New Bug description: [impact] bug 1633479 made a change to isc-dhcp to wait for an interface's link-local ipv6 address to switch from 'tentative' to normal, because all link-local addresses briefly go through a 'tentative' state while the kernel is performing ipv6 link-local 'duplicate address detection' (DAD). While in the 'tentative' state, dhclient can't take over the interface and send out dhcpv6 requests; it must wait until DAD completes. However, the change made in that bug does not account for the case where the 'tentative' check is done before the interface has even set up a link-local address; its case statement assumes if there is no 'tentative' or 'dadfailed' string in the output, the link-local address is ready to use. When the address check f
[Touch-packages] [Bug 1718568] Re: dhclient-script fails to wait for link-local address
artful: ubuntu@lp1718568-artful:~$ dpkg -l | grep isc-dhcp ii isc-dhcp-client4.3.5-3ubuntu2.2 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common4.3.5-3ubuntu2.2 amd64common manpages relevant to all of the isc-dhcp packages ubuntu@lp1718568-artful:~$ sudo ip l set down dev ens7 ubuntu@lp1718568-artful:~$ sudo ip l show ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:bf:16:8a brd ff:ff:ff:ff:ff:ff (on host): $ virsh domif-setlink lp1718568-artful vnet8 down Device updated successfully (back on guest): ubuntu@lp1718568-artful:~$ sudo dhclient -v -6 ens7 Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no link-local IPv6 address for ens7 If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. after updating to -proposed: ubuntu@lp1718568-artful:~$ sudo ip l set down dev ens7 ubuntu@lp1718568-artful:~$ sudo ip l show ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 52:54:00:bf:16:8a brd ff:ff:ff:ff:ff:ff ubuntu@lp1718568-artful:~$ dpkg -l | grep isc-dhcp ii isc-dhcp-client4.3.5-3ubuntu2.3 amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common4.3.5-3ubuntu2.3 amd64common manpages relevant to all of the isc-dhcp packages ubuntu@lp1718568-artful:~$ sudo dhclient -v -6 ens7 Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ (blocks, waiting for ipv6 link-local addr) (on host): $ virsh domif-setlink lp1718568-artful vnet8 up Device updated successfully (back on guest): Listening on Socket/ens7 Sending on Socket/ens7 PRC: Soliciting for leases (INIT). XMT: Forming Solicit, 0 ms elapsed. XMT: X-- IA_NA 00:bf:16:8a XMT: | X-- Request renew in +3600 XMT: | X-- Request rebind in +5400 XMT: | X-- Request address 2001:db8::99. XMT: | | X-- Request preferred in +7200 XMT: | | X-- Request valid in +10800 XMT: Solicit on ens7, interval 1020ms. RCV: Advertise message on ens7 from fe80::5054:ff:fec9:897c. RCV: X-- IA_NA 00:bf:16:8a RCV: | X-- starts 1520535276 RCV: | X-- t1 - renew +3600 RCV: | X-- t2 - rebind +7200 RCV: | X-- [Options] RCV: | | X-- IAADDR 2001:db8::99 RCV: | | | X-- Preferred lifetime 604800. RCV: | | | X-- Max lifetime 2592000. RCV: X-- Server ID: 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c RCV: Advertisement recorded. PRC: Selecting best advertised lease. PRC: Considering best lease. PRC: X-- Initial candidate 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c (s: 10105, p: 0). XMT: Forming Request, 0 ms elapsed. XMT: X-- IA_NA 00:bf:16:8a XMT: | X-- Requested renew +3600 XMT: | X-- Requested rebind +5400 XMT: | | X-- IAADDR 2001:db8::99 XMT: | | | X-- Preferred lifetime +7200 XMT: | | | X-- Max lifetime +7500 XMT: V IA_NA appended. XMT: Request on ens7, interval 940ms. RCV: Reply message on ens7 from fe80::5054:ff:fec9:897c. RCV: X-- IA_NA 00:bf:16:8a RCV: | X-- starts 1520535277 RCV: | X-- t1 - renew +3600 RCV: | X-- t2 - rebind +7200 RCV: | X-- [Options] RCV: | | X-- IAADDR 2001:db8::99 RCV: | | | X-- Preferred lifetime 604800. RCV: | | | X-- Max lifetime 2592000. RCV: X-- Server ID: 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c PRC: Bound to lease 00:01:00:01:22:2c:61:12:52:54:00:c9:89:7c. -proposed package verified -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1718568 Title: dhclient-script fails to wait for link-local address Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Fix Committed Status in isc-dhcp source package in Xenial: Fix Committed Status in isc-dhcp source package in Zesty: Won't Fix Status in isc-dhcp source package in Artful: Fix Committed Status in isc-dhcp source package in Bionic: Fix Released Status in isc-dhcp package in Debian: New Bug description: [impact] bug 1633479 made a change to isc-dhcp to wait for an interface's link-local ipv6 address to switch from 'tentative' to normal, because all link-local addresses briefly go through a 'tentative' state while the kernel is performing ipv6 link-local 'duplica
[Touch-packages] [Bug 1754436] Re: evolution-addressbook-factory-subprocess crashed with SIGABRT in std::terminate()
*** This bug is a duplicate of bug 1724277 *** https://bugs.launchpad.net/bugs/1724277 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724277, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1754436/+attachment/5073332/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754436/+attachment/5073334/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754436/+attachment/5073337/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754436/+attachment/5073338/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754436/+attachment/5073339/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754436/+attachment/5073340/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754436/+attachment/5073341/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1724277 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1754436 Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in std::terminate() Status in evolution-data-server package in Ubuntu: New Bug description: ? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: evolution-data-server 3.27.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 19:33:23 2018 ExecutablePath: /usr/lib/evolution/evolution-addressbook-factory-subprocess InstallationDate: Installed on 2017-07-14 (237 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/lib/evolution/evolution-addressbook-factory-subprocess --factory google --bus-name org.gnome.evolution.dataserver.Subprocess.Backend.AddressBookx1921x3 --own-path /org/gnome/evolution/dataserver/Subprocess/Backend/AddressBook/1921/3 ProcEnviron: LANG=da_DK.UTF-8 PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= Signal: 6 SourcePackage: evolution-data-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 operator new(unsigned long) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: evolution-addressbook-factory-subprocess crashed with SIGABRT in std::terminate() UpgradeStatus: Upgraded to bionic on 2018-03-08 (0 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1754436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
Hello Alkis, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed verification-needed-xenial -- 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/696435 Title: wait-for-root fails to detect nbd root Status in linux package in Ubuntu: Fix Released Status in nbd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] Kernel does not generate any events when ndb-client connects /dev/nbd0 devices, therefore it is impossible to monitor/react to the state of /dev/nbd0. [Fix] Generate change uevent when size of /dev/nbd0 changes [Testcase] * Start udevadm monitor * modprobe nbd * use ndb-client to connect something to /dev/nbd0 * observe that there are change udev events generated on /dev/nbd0 itself [Regression Potential] There is no change to existing uevents, or their ordering. There is now an addition change event which will cause systemd to mark ndb devices as ready and trigger appropriate actions [Original Bug Report] When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: nbd-client 1:2.9.16-6ubuntu1 initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: while [ -z "${FSTYPE}" ]; do FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) # Run failure hooks, hoping one of them can fix up the system # and we can restart the wait loop. If they all fail, abort # and move on to the panic handler and shell. if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then break fi done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked and while it was still waiting. But I tried adding a "sleep 5" as the last line of local-top/nbd, so that the nbd message was displayed a lot before wait-for-root was called, and it didn't make a difference. So I don't think a race condition is involved in this problem. Temporarily I'm passing rootdelay=1 in the kernel command line to work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722481] Re: systemd should sync disks, before killing all processes on shutdown
Hello Dimitri, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1722481 Title: systemd should sync disks, before killing all processes on shutdown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] * systemd-shutdown binary is executed to complete system shutdown. In xenial, it calls sync() after killing all processes, and not before killing them. This means that processes are racing the SIGKILL/TERM timeouts to sync all IO to disk. To mitigate this race condition, and make the shutdown process more reliable the sync() should also happen before process killing spree starts. [Fix] Backport upstream commit https://github.com/systemd/systemd/commit/2e79d1828a8da9b3af1b052297e3617905ec94f3 [Test Case] * Make sure systems still shuts down, including e.g. root on raid. [Regression Potential] * Shutdowns may appear to be slower due to two sync() calls instead of one * However total shutdown time should not be impacted much, as there really should not be much additional IO caused by killing all processes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1722481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732803] Re: systemd-journald RateLimitBurst is sometimes divided by 4
Hello David, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1732803 Title: systemd-journald RateLimitBurst is sometimes divided by 4 Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] systemd-journald allows you to configure a per-service journal rate limit in /etc/systemd/journald.conf via the RateLimitBurst parameter. systemd-journald has code that effectively increases the rate limit when there is a lot of disk space available. However, all versions of systemd before v232 had a bug which would shrink the rate limit when there is between 1 and 16 MB available on disk. If you designed a service to log at a rate R and configured RateLimitBurst to a little above R, this can lead to loss of logs when free disk is between 1 and 16 MB, as your service will be surprisingly rate limited at lower than your configured rate. This bug was fixed upstream in https://github.com/systemd/systemd/pull/4218 It is a straightforward one-line change that makes the code match the comments under it. [Test Case] Run a systemd service that prints lots of logs (eg `yes`). Fill your disk to have only 1MB full. Use journalctl to see how many log lines are between "Suppressed" lines. Note that it is 1/4 of what you'd expect. (Admittedly this test case is a little hard to achieve since journald itself is writing to disk. I did run into this in production.) [Regression Potential] This does mean that journald can write slightly more to disk than it did before when free disk is between 1 and 16MB, but given that the full burst rate is available below 1MB it seems unlikely that any systems are depending on this change in order to not break. The fix has been in systemd since v232 (shipped in Zesty). I would like to see it in Xenial. [Other Info] I am seeing this on: ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 1 ~/systemd-229$ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 ubuntu@ip-10-0-2-135[i-0b196ce4b8dc3fc55] 0 ~/systemd-229$ apt-cache policy systemd systemd: Installed: 229-4ubuntu19 Candidate: 229-4ubuntu21 Version table: 229-4ubuntu21 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages *** 229-4ubuntu19 100 100 /var/lib/dpkg/status 229-4ubuntu10 500 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 229-4ubuntu4 500 500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu xenial/main amd64 Packages This bug seems to date back to the original implementation of rate limiting (https://github.com/systemd/systemd/commit/6e409ce10d). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1732803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1718444] Re: systemd-sysctl in Xenial is not obeying the order of the sysctls
Hello Philipp, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1718444 Title: systemd-sysctl in Xenial is not obeying the order of the sysctls Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] * sysctls are applied out of order [Test Case] * Monitor that sysctls are applied in-order, instead of out of order / random order. [Regression Potential] * Cherrypick of an upstream patch which is present in v232+ and in use in Ubuntu in later releases. The code changes are minimal, updating s/Hashmap/OrderedHashmap/ which is implemented and available in xenial's systemd. https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6 [Other Info] * Original bug report. systemd-sysctl in Xenial forces itself over procps by shipping a link for procps.service to systemd-sysctl.service. However, it does not obey the order both of the files and also of the sysctls within the files. Instead it uses a simple hashmap. As it turns out that's fixed upstream and systemd master uses an ordered hashmap because of this, which at least preserves order within single files. Traditionally files in sysctl.d have been prefixed with numbers to ensure an order and that's now completely non-deterministic on Xenial. Relevant upstream commit: https://github.com/systemd/systemd/commit/886cf982d3018f7451f0548dadbc05bd2d583bb6 Note that conf_files_list_nulstr in master sorts the configuration files using strcmp, so even order of configuration files should be obeyed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718444/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1721223] Re: Networkd fail to set ip address between leases if ip address changes on UbuntuCore
Hello Nicolino, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- 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/1721223 Title: Networkd fail to set ip address between leases if ip address changes on UbuntuCore Status in Snappy: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Committed Bug description: [Impact] * networkd fails to renew a lease, specifically it fails to change IPv4 address via DHCP renew/rebind. * networkd relies on a kernel feature to promote secondary IPv4 address to primary, upon primary address lease expiry. * this sysctl tunable was not enabled by default in systemd. [Test Case] Add a device, and assign two IPv4 addresses. First one, with a short lease time. Second one, with a different ip and a longer lease time. Second one should be treated as secondary ip address, and upon expiry of the first one, should be promoted and become primary ip address. The below scripted instructions simulate this: sudo ip link add name testleases type dummy sudo ip address add 192.0.2.10/27 dev testleases \ valid_lft 5 preferred_lft 5 sudo ip address add 192.0.2.11/27 dev testleases \ valid_lft 11 preferred_lft 11 ip address list dev testleases | \ grep -q 'inet 192.0.2.10/27 scope global dynamic testleases' \ && echo ok || echo not ok ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global secondary dynamic testleases' \ && echo ok || echo not ok sleep 6 ip address list dev testleases | \ grep -q 'inet 192.0.2.11/27 scope global dynamic testleases' \ && echo ok || echo not ok sudo ip link del dev testleases [Regression Potential] * This changes the default kernel behaviour, previously upon expiry of the primary address, secondary addresses were removed as well. Which is imho silly. * comparing networkd renewal with isc-dhcp renewal the semantics are quite different. Upon acquiring new ip address, isc-dhcp would instantly flush existing ip address, and add a new one. Networkd add the new address as secondary, and waits for old one to expire first before promoting / switching to using the new ip address. IMHO kernel should have an API to promote secondary ip address to a primary one. * This update also applies other safe-looking options, which are currently also already applied via sysctls shipped in other packages # Source route verification net.ipv4.conf.default.rp_filter = 1 net.ipv4.conf.all.rp_filter = 1 # Do not accept source routing net.ipv4.conf.default.accept_source_route = 0 net.ipv4.conf.all.accept_source_route = 0 # Enable hard and soft link protection fs.protected_hardlinks = 1 fs.protected_symlinks = 1 * This update also applies the following upstream/bufferbloat.net recommended setting # Fair Queue CoDel packet scheduler to fight bufferbloat net.core.default_qdisc = fq_codel * [~racb] There are complex network setups out there, such as HA with corosync/pacemaker, OpenStack Neutron, and that kind of thing. If this fix were SRU'd, will all of these things in the wild cope with this sysctl change? [Other Info] * Original bug report Hi there, we found a replicable issue that involves the Ubuntu Core networking and causes complete loss of connectivity. We run a custom board with ubuntu core: the architecure is amrhf. We replicated this issue with an official Ubuntu Core image on a Raspberry Pi: other platform was been tested. It shows that it is a snap core problem which interests networkd: we use the default network stack based on networkd
[Touch-packages] [Bug 1737570] Re: Add support for RequiredForOnline in networkd
Hello Dimitri, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed-xenial -- 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/1737570 Title: Add support for RequiredForOnline in networkd Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Zesty: Won't Fix Status in systemd source package in Artful: Fix Committed Status in systemd source package in Bionic: Fix Released Bug description: [Impact] * netplan & networkd based systems typically await networking to be up on boot, without any ability to specify that an interface should be configured, but might not be online at boot. This is a backport of the RequiredForOnline= feature to match optional=true in netplan. [Test Case] * Configure a netowkring interface using .link/.network file and specify RequiredForOnline=False * Bring the interface down / offline it * execute systemd-networkd-wait-online, which should exit immediately since no interfaces are required to be online [Regression Potential] * This adds a support for an additional stanza in the network files. This stanza is not used by default. if the stanza is used, but older networkd is in use, networkd will ignore this unknown stanza. Thus this change is backward and forward compatible. The difference is that boot is not blocked awaiting systemd-networkd-wait-online to timeout. [Other Info] * Original bug report Add support for RequiredForOnline in networkd https://github.com/systemd/systemd/commit/c1a3890410f043fe09af8b139eb6bfe2832089be RequiredForOnline= denotes a link/network that does/does not require being up for systemd-networkd-wait-online to consider the system online; this makes it possible to ignore devices without modifying parameters to wait-online. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1737570/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1734409] Re: systemd-sysctl: exit gracefully on EPERM/EACCESS
Hello Christian, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1734409 Title: systemd-sysctl: exit gracefully on EPERM/EACCESS Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Bug description: [Impact] * systemd-sysctl service fails in containers, due to read-only sysfs, which is normal. [Test Case] * Ensure systemd-sysctl is successful in containers, e.g. lxc & lxd [Regression Potential] * The application of sysctls fails anyway, but at least in this case false-errors are not reported and the container doesn't enter "degraded" state without a good reason. [Other Info] * Original bug report Hi everyone, systemd-sysctl in systemd versions prior to 232 will exit with FAILED when not being able to apply kernel variables. In containers it should simply move on and exit with SUCCESS. Upstream systemd carries appropriate patches for this already. The relevant commits are: 411e869f497c7c7bd0688f1e3500f9043bc56e48 39540de8abe24886693ca29a9caeea85c88089aa these should be backported to xenial's systemd. Christian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1734409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1717471] Re: networkd does not accept / set advertised mtu
Hello Dimitri, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed verification-needed-xenial -- 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/1717471 Title: networkd does not accept / set advertised mtu Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Released Status in systemd source package in Xenial: Fix Committed Status in nplan source package in Zesty: Fix Released Bug description: [Impact] Hosts may require a specific MTU to be set as passed by DHCP options. We should honor these settings to ensure proper communication of the host with the rest of the network. [Test case] 1) Run netplan on a system that should receive MTU settings from DHCP. 2) Validate that the MTU configuration provided by DHCP is applied to the right interface. [Regression Potential] If DHCP settings specify an invalid MTU setting which is currently being ignored and letting the systems communicate correctly with the network, then these systems would regress. --- Right, so as far as I can tell the neutron-api on lcy01 is configured to advertise an instance interface MTU of 1400, though that's lower than it has to be, and the new DHCP setup with networkd just doesn't respect that DHCP option. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1717471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754423] [NEW] This is not an official Ubuntu package (even though it is, but in a future release)
Public bug reported: Ubuntu: artful 17.10 apport: Installed: 2.20.7-0ubuntu3.7 Candidate: 2.20.7-0ubuntu3.7 Version table: *** 2.20.7-0ubuntu3.7 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful-updates/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful-updates/main i386 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful-updates/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.7-0ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main i386 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/main i386 Packages torbrowser-launcher: Installed: 0.2.9-1 Candidate: 0.2.9-1 Version table: *** 0.2.9-1 100 100 /var/lib/dpkg/status 0.2.7-3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/universe amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful/universe amd64 Packages on a ubuntu artful machine: 1) install torbrowser-launcher from bionic(even though you are running artful)* 2) ubuntu-bug torbrowser-launcher result: ubuntu-bug refuses to send a bug report, claiming that it's a non-ubuntu, third party package full error message: "The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again" This is not strictly speaking true. While it's a bionic version, not an artful version - it is a ubuntu version. expected behavior: * Failing to report the bug is more or less fine - but if it fails, it should fail with an acknowledgement that the user is trying to report a bug against a future version. or * ubuntu-bug should allow the report of bugs with a 'future' version, so that people like myself who are testing bionic packages even in an unsupported setup can feed bug reports about those packages before they hit the mainstream ubuntu user. That would make this bug probably a duplicate of other bugs like https://bugs.launchpad.net/ubuntu/+source/apport/+bug/443961 if so. *this is the suggested workaround for the complete nonfunctional version in artful. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.7 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportLog: Error: [Errno 13] Permission denied: '/var/log/apport.log' ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 8 11:37:20 2018 InstallationDate: Installed on 2017-04-18 (323 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in the 'systemd-journal' group can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to artful on 2017-10-19 (139 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1754423 Title: This is not an official Ubuntu package (even though it is, but in a future release) Status in apport package in Ubuntu: New Bug description: Ubuntu: artful 17.10 apport: Installed: 2.20.7-0ubuntu3.7 Candidate: 2.20.7-0ubuntu3.7 Version table: *** 2.20.7-0ubuntu3.7 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful-updates/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful-updates/main i386 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful-updates/main amd64 Packages 500 https://mirror.its.sfu.ca/mirror/ubuntu artful-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu artful-security/main i386 Packages 100 /var/lib/dpkg/status 2.20.7-0ubuntu3 500 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main amd64 Packages 500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu artful/main i386 Packages 500 https://mirr
[Touch-packages] [Bug 1269840] Re: ubuntu-bug ubuntu-bug doesn't work
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1269840 Title: ubuntu-bug ubuntu-bug doesn't work Status in apport package in Ubuntu: Confirmed Bug description: ubuntu-bug doesn't make program lookup when package lookup failed. This is inconvenient for users, who don't know about `which` command. Is it possible to automate lookup and continue search until something matches? ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: apport 2.12.5-0ubuntu2.2 ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Uname: Linux 3.11.0-15-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.2 Architecture: i386 CrashReports: 640:1000:122:1423125:2014-01-09 20:22:25.104739665 +0300:2014-01-09 20:22:26.104739665 +0300:/var/crash/_usr_lib_i386-linux-gnu_bamf_bamfdaemon.1000.crash 640:1000:122:157297300:2014-01-09 20:56:44.036795854 +0300:2014-01-09 20:56:45.036795854 +0300:/var/crash/_usr_bin_compiz.1000.crash 640:0:122:4884804:2014-01-10 13:10:06.891414880 +0300:2014-01-10 13:10:07.891414880 +0300:/var/crash/_usr_bin_Xorg.0.crash Date: Thu Jan 16 18:10:59 2014 InstallationDate: Installed on 2012-03-12 (675 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301) MarkForUpload: True PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to saucy on 2013-10-21 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1269840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751225] Re: apt update hangs when repository url is redirect url
Hello Seyeong, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.26 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- 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/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Artful: Invalid Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] Could cause some other zero-content redirects to break again (seems unlikely...). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754415] Re: cupsd crashed with SIGSEGV in ippCopyAttribute()
*** This bug is a duplicate of bug 1753766 *** https://bugs.launchpad.net/bugs/1753766 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1753766, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1754415/+attachment/5073254/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1754415/+attachment/5073258/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1754415/+attachment/5073269/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1754415/+attachment/5073271/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1754415/+attachment/5073272/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1754415/+attachment/5073273/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1754415/+attachment/5073274/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1753766 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1754415 Title: cupsd crashed with SIGSEGV in ippCopyAttribute() Status in cups package in Ubuntu: New Bug description: Just turn my pc on and this error apeared ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.6-5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 Date: Thu Mar 8 07:07:13 2018 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2018-02-08 (27 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) Lpstat: device for HP-M521_GTI: socket://10.2.254.103 MachineType: Hewlett-Packard HP Compaq 6005 Pro SFF PC Papersize: a4 PpdFiles: HP_LaserJet_Pro_MFP_M521dn_68DA1F_: LaserJet Pro MFP M521dn HP_LaserJet_Pro_MFP_M521dn_DC590A_: LaserJet Pro MFP M521dn HP-M521_GTI: HP LaserJet Pro MFP M521 Postscript (recommended) HP_LaserJet_Pro_MFP_M521dn_615877_: LaserJet Pro MFP M521dn ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=550af015-9954-408f-81ad-053c28803cd4 ro quiet splash vt.handoff=1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=550af015-9954-408f-81ad-053c28803cd4 ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7f160a3a8db3 : addl $0x1,0x38(%rdx) PC (0x7f160a3a8db3) ok source "$0x1" ok destination "0x38(%rdx)" (0x0038) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ippCopyAttribute () from /usr/lib/x86_64-linux-gnu/libcups.so.2 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in ippCopyAttribute() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 08/04/2010 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 786G6 v01.11 dmi.board.asset.tag: BRG112FHQ2 dmi.board.name: 3047h dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: BRG112FHQ2 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr786G6v01.11:bd08/04/2010:svnHewlett-Packard:pnHPCompaq6005ProSFFPC:pvr:rvnHewlett-Packard:rn3047h:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq 6005 Pro SFF PC dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1754415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1751225] Re: apt update hangs when repository url is redirect url
** Description changed: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) - return true; + return true; ### [2] if (Encoding == Closes) - Encoding = Stream; + Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] - TBD + Could cause some other zero-content redirects to break again (seems unlikely...). -- 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/1751225 Title: apt update hangs when repository url is redirect url Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: In Progress Status in apt source package in Artful: Invalid Bug description: [Impact] When using redirect url on /etc/apt/sources.list apt update command hangs this is affected with commit https://anonscm.debian.org/git/apt/apt.git/commit/?id=dd547ebaffd2aceb42e2908f1d5f0ab386af6cb1 In my test, moving below[1] code after[2] [1] ### if (ContentLength == 0) return true; ### [2] if (Encoding == Closes) Encoding = Stream; ### it worked fine. [Test Case] echo "deb http://packages.cloudfoundry.org/debian stable main" > /etc/apt/sources.list.d/cloudfoundry-cli.list apt update [Regression] Could cause some other zero-content redirects to break again (seems unlikely...). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1751225/+subscriptions -- Mailing list: https://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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
On Thu, Mar 08, 2018 at 04:30:30PM -, Scott Moser wrote: > I'm pretty sure that if you you rm /etc/resolv.conf > and then just write what ever you want in there, it wont get overritten. > > mv /etc/resolv.conf /etc/resolv.conf.dist > echo "nameserver 8.8.8.8" > /etc/resolv.conf Apologies, I thought I was replying to another "DNS resolution in bionic doesn't work" bug. >.< (That said, systemd-resolved does own /etc/resolv.conf, so it _could_ rewrite it. An example would be when the search domain changes, but that's unlikely in a MAAS environment.) -- 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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: New Status in MAAS: Triaged Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, you will see that netplan config is correctly to the 10.90.90.1 nameserver, but in resolv.conf that's a local address. Resolv.conf should really be configured to use the provided DNS server(s). That said, despite that fact, DNS resolution doesn't work with the local address. Bionic -- ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp0s25: match: macaddress: b8:ae:ed:7d:17:d2 mtu: 1500 nameservers: addresses: - 10.90.90.1 search: - maaslab - maas set-name: enp0s25 bridges: br0: addresses: - 10.90.90.3/24 gateway4: 10.90.90.1 interfaces: - enp0s25 parameters: forward-delay: 15 stp: false ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search maaslab maas ubuntu@node01:~$ ping google.com ping: google.com: Temporary failure in name resolution [...] ubuntu@node01:~$ sudo vim /etc/resolv.conf ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.90.90.1 search maaslab maas ubuntu@node01:~$ ping google.com PING google.com (172.217.0.174) 56(84) bytes of data. 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 time=4.46 ms 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 time=4.38 ms = Xenial == ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback dns-nameservers 10.90.90.1 dns-search maaslab maas auto enp0s25 iface enp0s25 inet static address 10.90.90.162/24 gateway 10.90.90.1 mtu 1500 ubuntu@node05:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.90.90.1 search maaslab maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754411] [NEW] package initramfs-tools 0.130ubuntu3
Public bug reported: failed to install/upgrade: Unterprozess installed initramfs-tools package post-installation script gab den Fehler-Ausgangsstatus 1 zurück ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Thu Mar 8 16:31:27 2018 ErrorMessage: Unterprozess installed initramfs-tools package post-installation script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-03-08 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: Unterprozess installed initramfs-tools package post-installation script gab den Fehler-Ausgangsstatus 1 zurück UpgradeStatus: No upgrade log present (probably fresh install) ** 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/1754411 Title: package initramfs-tools 0.130ubuntu3 Status in initramfs-tools package in Ubuntu: New Bug description: failed to install/upgrade: Unterprozess installed initramfs-tools package post-installation script gab den Fehler-Ausgangsstatus 1 zurück ProblemType: Package DistroRelease: Ubuntu 18.04 Package: initramfs-tools 0.130ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Thu Mar 8 16:31:27 2018 ErrorMessage: Unterprozess installed initramfs-tools package post-installation script gab den Fehler-Ausgangsstatus 1 zurück InstallationDate: Installed on 2018-03-08 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.130ubuntu3 failed to install/upgrade: Unterprozess installed initramfs-tools package post-installation script gab den Fehler-Ausgangsstatus 1 zurück 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/1754411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: curl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
I'm pretty sure that if you you rm /etc/resolv.conf and then just write what ever you want in there, it wont get overritten. mv /etc/resolv.conf /etc/resolv.conf.dist echo "nameserver 8.8.8.8" > /etc/resolv.conf On Thu, Mar 8, 2018 at 4:36 PM, Mike Pontillo wrote: > We discussed this today and decided that the proper place to fix this is > not in MAAS; the v1 YAML containing global DNS servers should be > converted to equivalent valid Netplan (using a heuristic). > > Alternatively, global DNS could be added to the Netplan schema (possibly > as a shortcut to apply configuration to a group of interfaces). > > -- > You received this bug notification because you are a member of Canonical > Cloudware, which is subscribed to cloud-init. > Matching subscriptions: cloud-init bugs > https://bugs.launchpad.net/bugs/1750884 > > Title: > [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, > leads to no DNS resolution > > To manage notifications about this bug go to: > https://bugs.launchpad.net/cloud-init/+bug/1750884/+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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: New Status in MAAS: Triaged Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, you will see that netplan config is correctly to the 10.90.90.1 nameserver, but in resolv.conf that's a local address. Resolv.conf should really be configured to use the provided DNS server(s). That said, despite that fact, DNS resolution doesn't work with the local address. Bionic -- ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp0s25: match: macaddress: b8:ae:ed:7d:17:d2 mtu: 1500 nameservers: addresses: - 10.90.90.1 search: - maaslab - maas set-name: enp0s25 bridges: br0: addresses: - 10.90.90.3/24 gateway4: 10.90.90.1 interfaces: - enp0s25 parameters: forward-delay: 15 stp: false ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search maaslab maas ubuntu@node01:~$ ping google.com ping: google.com: Temporary failure in name resolution [...] ubuntu@node01:~$ sudo vim /etc/resolv.conf ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.90.90.1 search maaslab maas ubuntu@node01:~$ ping google.com PING google.com (172.217.0.174) 56(84) bytes of data. 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 time=4.46 ms 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 time=4.38 ms = Xenial == ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback dns-nameservers 10.90.90.1 dns-search maaslab maas auto enp0s25 iface enp0s25 inet static address 10.90.90.162/24 gateway 10.90.90.1 mtu 1500 ubuntu@node05:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.90.90.1 search maaslab maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- Mailing list: https://launchpad.net/~touch-
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
uname -m && uname -r && cat /etc/*release x86_64 4.15.0-10-generic DISTRIB_ID=Ubuntu DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic dpkg -l|grep libcurl ii libcurl3-gnutls:amd64 7.58.0-2ubuntu2 amd64easy-to-use client-side URL transfer library (GnuTLS flavour) ii libcurl4:amd64 7.58.0-2ubuntu2 amd64easy-to-use client-side URL transfer library (OpenSSL flavour) ii libcurl4-gnutls-dev:amd64 7.58.0-2ubuntu2 amd64development files and documentation for libcurl (GnuTLS flavour) Here is attempt to install opera browser sudo dpkg -i opera-stable_51.0.2830.55_amd64.deb Selecting previously unselected package opera-stable. (Reading database ... 228694 files and directories currently installed.) Preparing to unpack opera-stable_51.0.2830.55_amd64.deb ... Unpacking opera-stable (51.0.2830.55) ... dpkg: dependency problems prevent configuration of opera-stable: opera-stable depends on libcurl3 (>= 7.16.2); however: Package libcurl3 is not installed. dpkg: error processing package opera-stable (--install): dependency problems - leaving unconfigured Processing triggers for gnome-menus (3.13.3-11ubuntu1) ... Processing triggers for desktop-file-utils (0.23-1ubuntu3) ... Processing triggers for mime-support (3.60ubuntu1) ... Processing triggers for hicolor-icon-theme (0.17-1) ... Processing triggers for shared-mime-info (1.9-2) ... Errors were encountered while processing: opera-stable here is install libcurl3 ... Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: libcurl3 : Conflicts: libcurl4 but 7.58.0-2ubuntu2 is to be installed libcurl4 : Conflicts: libcurl3 but 7.58.0-2ubuntu2 is to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). sudo apt --fix-broken install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages will be REMOVED: opera-stable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
Upstream server about using IP_FREEBIND: https://bugzilla.mindrot.org/show_bug.cgi?id=2512 ** Bug watch added: OpenSSH Portable Bugzilla #2512 https://bugzilla.mindrot.org/show_bug.cgi?id=2512 ** Also affects: openssh via https://bugzilla.mindrot.org/show_bug.cgi?id=2512 Importance: Unknown Status: Unknown -- 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/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up Status in portable OpenSSH: Unknown Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-server The sshd will not start at boot if the ListenAddress option in /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 . I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the openssh-server package. I would expect that sshd is started after boot but it will not and I found this in /var/log/auth.log: sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign requested address. sshd[4527]: fatal: Cannot bind any address. Once the System is started you can start/stop the sshd with the /etc/init.d/ssh script without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/216847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1164016] Re: restore type-ahead find
> If that is genuinely the reason (and this bug has been marked as "Fix > Released" > since Jan 2014, so it seems correct), then is it not time to raise a new bug? Maybe (though it seems a little stupid to raise a new bug for exactly the same issue). Anyway I did, like yesterday, and it got closed (can't find it right now, I don't know what's wrong with the search engine of this stupid bug tracker) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find Status in Nautilus: Expired Status in nautilus package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: GNOME removed type-ahead find in Nautilus 3.6, not without controversy: https://mail.gnome.org/archives/nautilus- list/2012-August/msg2.html Now when you type in a Nautilus window, Nautilus immediately performs a search in the current directory and all its subdirectories. I personally find this annoying. If I want to search, I'll click the search icon. Often I'm looking at a long directory listing and simply want to jump to a certain point in it, and type-ahead find works great for that. Would Ubuntu consider patching type-ahead find back in? To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1708409] Re: kdump service does not start after configure/reboot
** Changed in: makedumpfile (Ubuntu Artful) Status: Confirmed => Invalid -- 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/1708409 Title: kdump service does not start after configure/reboot Status in The Ubuntu-power-systems project: Fix Committed Status in makedumpfile package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in makedumpfile source package in Artful: Invalid Status in systemd source package in Artful: Fix Committed Status in makedumpfile source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: == Comment: #0 - Harish Sriram - 2017-08-02 01:45:01 == kdump service does not start after configure/reboot --Problem Description--- kdump service does not start after configure/reboot. It has to be started/loaded manually, everytime after reboot. # kdump-config status current state : Not ready to kdump ---uname output--- Linux ltc-test-ci2 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:02:54 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type/Model = Power 8/8247-22L Additional Info- # cat /proc/cmdline root=UUID=974df602-c0e4-4e67-8853-78ad15884c59 ro console=tty0 console=ttyS0,115200 quiet splash cgroup_enable=memory swapaccount=1 crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M ---Steps to Reproduce--- 1. installed linux-crashdump 2. edited the kdump-tools.cfg crashkernel cmdline to above 3. update-grub 4. reboot Expected: kdump-config to be loaded by default after reboot # kdump-config status current state : Not ready to kdump # service kdump-tools status * kdump-tools.service - Kernel crash dump capture service Loaded: loaded (/lib/systemd/system/kdump-tools.service; enabled; vendor pres Active: inactive (dead) ... https://github.com/systemd/systemd/issues/6334 systemd in artful is not properly picking up the unit files in /etc/systemd/system/default.target.wants To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1708409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1749086] Re: 5 minute delay on booting to login screen
Actually I think the problem was PSU related, my old PSU was inadequate it seems. After replacing it, no more errors. -- 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/1749086 Title: 5 minute delay on booting to login screen Status in xorg package in Ubuntu: Invalid Bug description: With Xubuntu or Kubuntu the screen turns off a few seconds after choosing Ubuntu in grub2 menu, and sometimes the login screen takes 5 minutes to be presented. From that point on everything seems to work as normal. Booting consistently took only a minute in Kubuntu 14.04. ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] [1002:68b8] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6] InstallationDate: Installed on 2018-02-11 (3 days ago) InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+13ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Tags: xenial ubuntu Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: 770 Extreme3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
We discussed this today and decided that the proper place to fix this is not in MAAS; the v1 YAML containing global DNS servers should be converted to equivalent valid Netplan (using a heuristic). Alternatively, global DNS could be added to the Netplan schema (possibly as a shortcut to apply configuration to a group of interfaces). -- 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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: New Status in MAAS: Triaged Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, you will see that netplan config is correctly to the 10.90.90.1 nameserver, but in resolv.conf that's a local address. Resolv.conf should really be configured to use the provided DNS server(s). That said, despite that fact, DNS resolution doesn't work with the local address. Bionic -- ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp0s25: match: macaddress: b8:ae:ed:7d:17:d2 mtu: 1500 nameservers: addresses: - 10.90.90.1 search: - maaslab - maas set-name: enp0s25 bridges: br0: addresses: - 10.90.90.3/24 gateway4: 10.90.90.1 interfaces: - enp0s25 parameters: forward-delay: 15 stp: false ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search maaslab maas ubuntu@node01:~$ ping google.com ping: google.com: Temporary failure in name resolution [...] ubuntu@node01:~$ sudo vim /etc/resolv.conf ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.90.90.1 search maaslab maas ubuntu@node01:~$ ping google.com PING google.com (172.217.0.174) 56(84) bytes of data. 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 time=4.46 ms 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 time=4.38 ms = Xenial == ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback dns-nameservers 10.90.90.1 dns-search maaslab maas auto enp0s25 iface enp0s25 inet static address 10.90.90.162/24 gateway 10.90.90.1 mtu 1500 ubuntu@node05:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.90.90.1 search maaslab maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
** Changed in: maas Importance: High => Medium ** Changed in: maas Status: Won't Fix => Triaged ** Changed in: maas Importance: Medium => Low ** Changed in: maas Milestone: None => 2.4.x -- 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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: New Status in MAAS: Triaged Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, you will see that netplan config is correctly to the 10.90.90.1 nameserver, but in resolv.conf that's a local address. Resolv.conf should really be configured to use the provided DNS server(s). That said, despite that fact, DNS resolution doesn't work with the local address. Bionic -- ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp0s25: match: macaddress: b8:ae:ed:7d:17:d2 mtu: 1500 nameservers: addresses: - 10.90.90.1 search: - maaslab - maas set-name: enp0s25 bridges: br0: addresses: - 10.90.90.3/24 gateway4: 10.90.90.1 interfaces: - enp0s25 parameters: forward-delay: 15 stp: false ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search maaslab maas ubuntu@node01:~$ ping google.com ping: google.com: Temporary failure in name resolution [...] ubuntu@node01:~$ sudo vim /etc/resolv.conf ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.90.90.1 search maaslab maas ubuntu@node01:~$ ping google.com PING google.com (172.217.0.174) 56(84) bytes of data. 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 time=4.46 ms 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 time=4.38 ms = Xenial == ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback dns-nameservers 10.90.90.1 dns-search maaslab maas auto enp0s25 iface enp0s25 inet static address 10.90.90.162/24 gateway 10.90.90.1 mtu 1500 ubuntu@node05:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.90.90.1 search maaslab maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
** Changed in: maas Status: Triaged => Won't Fix ** Changed in: maas Assignee: Mike Pontillo (mpontillo) => (unassigned) ** Changed in: maas Milestone: 2.4.0alpha2 => None -- 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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: New Status in MAAS: Triaged Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, you will see that netplan config is correctly to the 10.90.90.1 nameserver, but in resolv.conf that's a local address. Resolv.conf should really be configured to use the provided DNS server(s). That said, despite that fact, DNS resolution doesn't work with the local address. Bionic -- ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp0s25: match: macaddress: b8:ae:ed:7d:17:d2 mtu: 1500 nameservers: addresses: - 10.90.90.1 search: - maaslab - maas set-name: enp0s25 bridges: br0: addresses: - 10.90.90.3/24 gateway4: 10.90.90.1 interfaces: - enp0s25 parameters: forward-delay: 15 stp: false ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search maaslab maas ubuntu@node01:~$ ping google.com ping: google.com: Temporary failure in name resolution [...] ubuntu@node01:~$ sudo vim /etc/resolv.conf ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.90.90.1 search maaslab maas ubuntu@node01:~$ ping google.com PING google.com (172.217.0.174) 56(84) bytes of data. 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 time=4.46 ms 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 time=4.38 ms = Xenial == ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback dns-nameservers 10.90.90.1 dns-search maaslab maas auto enp0s25 iface enp0s25 inet static address 10.90.90.162/24 gateway 10.90.90.1 mtu 1500 ubuntu@node05:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.90.90.1 search maaslab maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- Mailing list: https://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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
Ok, that's not much of a workaround then :). On Thu, Mar 8, 2018 at 3:52 AM, Dan Watkins wrote: > On Wed, Mar 07, 2018 at 11:42:29PM -, Jason Hobbs wrote: >> Is there a workaround for this? I can just rm /etc/resolv.conf and >> create it with the contents I want, right? > > Yep, though you'll need to recreate it every so often as it will be > replaced. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1750884 > > Title: > [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, > leads to no DNS resolution > > Status in cloud-init: > New > Status in MAAS: > Triaged > Status in nplan package in Ubuntu: > New > Status in systemd package in Ubuntu: > New > > Bug description: > When deploying Bionic, /etc/resolv.conf is not configured correctly, > which leads to no DNS resolution. In the output below, you will see > that netplan config is correctly to the 10.90.90.1 nameserver, but in > resolv.conf that's a local address. > > Resolv.conf should really be configured to use the provided DNS > server(s). That said, despite that fact, DNS resolution doesn't work > with the local address. > > Bionic > -- > > ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml > # This file is generated from information provided by > # the datasource. Changes to it will not persist across an instance. > # To disable cloud-init's network configuration capabilities, write a file > # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: > # network: {config: disabled} > network: > version: 2 > ethernets: > enp0s25: > match: > macaddress: b8:ae:ed:7d:17:d2 > mtu: 1500 > nameservers: > addresses: > - 10.90.90.1 > search: > - maaslab > - maas > set-name: enp0s25 > bridges: > br0: > addresses: > - 10.90.90.3/24 > gateway4: 10.90.90.1 > interfaces: > - enp0s25 > parameters: > forward-delay: 15 > stp: false > ubuntu@node01:~$ cat /etc/resolv.conf > # This file is managed by man:systemd-resolved(8). Do not edit. > # > # 127.0.0.53 is the systemd-resolved stub resolver. > # run "systemd-resolve --status" to see details about the actual > nameservers. > nameserver 127.0.0.53 > > search maaslab maas > ubuntu@node01:~$ ping google.com > ping: google.com: Temporary failure in name resolution > > [...] > > ubuntu@node01:~$ sudo vim /etc/resolv.conf > ubuntu@node01:~$ cat /etc/resolv.conf > # This file is managed by man:systemd-resolved(8). Do not edit. > # > # 127.0.0.53 is the systemd-resolved stub resolver. > # run "systemd-resolve --status" to see details about the actual > nameservers. > nameserver 10.90.90.1 > > search maaslab maas > ubuntu@node01:~$ ping google.com > PING google.com (172.217.0.174) 56(84) bytes of data. > 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 > time=4.46 ms > 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 > time=4.38 ms > > = > Xenial > == > > ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg > # This file is generated from information provided by > # the datasource. Changes to it will not persist across an instance. > # To disable cloud-init's network configuration capabilities, write a file > # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: > # network: {config: disabled} > auto lo > iface lo inet loopback > dns-nameservers 10.90.90.1 > dns-search maaslab maas > > auto enp0s25 > iface enp0s25 inet static > address 10.90.90.162/24 > gateway 10.90.90.1 > mtu 1500 > ubuntu@node05:~$ cat /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN > nameserver 10.90.90.1 > search maaslab maas > > To manage notifications about this bug go to: > https://bugs.launchpad.net/cloud-init/+bug/1750884/+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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: New Status in MAAS: Triaged Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, yo
[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
THis is the result with dmesg | grep intel [1.987610] intel_idle: MWAIT substates: 0x20220 [1.987629] intel_idle: v0.4.1 model 0x1C [1.987634] intel_idle: lapic_timer_reliable_states 0x2 [2.013276] agpgart-intel :00:00.0: Intel 945GME Chipset [2.013330] agpgart-intel :00:00.0: detected gtt size: 262144K total, 262144K mappable [2.013427] agpgart-intel :00:00.0: detected 8192K stolen memory [2.013765] agpgart-intel :00:00.0: AGP aperture is 256M @ 0xd000 [3.378181] fb: switching to inteldrmfb from VESA VGA [3.808471] WARNING: CPU: 0 PID: 6 at /build/linux-0c7Pc_/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 intel_fb_initial_config+0x2d4/0x5f0 [i915]() [3.808696] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.808796] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.808904] [] intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.809006] [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915] [3.809198] [] ? intel_fbdev_init+0x530/0x530 [i915] [3.809298] [] intel_fbdev_initial_config+0x19/0x20 [i915] [3.812450] fbcon: inteldrmfb (fb0) is primary device [3.812844] i915 :00:02.0: fb0: inteldrmfb frame buffer device [3.832514] WARNING: CPU: 0 PID: 87 at /build/linux-0c7Pc_/linux-4.4.0/drivers/gpu/drm/i915/intel_fbdev.c:406 intel_fb_initial_config+0x2d4/0x5f0 [i915]() [3.832759] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.832859] [] ? intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.832967] [] intel_fb_initial_config+0x2d4/0x5f0 [i915] [3.833069] [] ? intel_crtc_fb_gamma_get+0x40/0x40 [i915] [3.84] [] intel_fbdev_output_poll_changed+0x1a/0x20 [i915] [3.834328] [] ? intel_pre_plane_update+0xd8/0x130 [i915] [3.834428] [] intel_atomic_commit+0x52f/0x6a0 [i915] [3.834988] [] intel_fbdev_output_poll_changed+0x1a/0x20 [i915] [ 16.748840] intel_rng: FWH not detected [ 19.441617] intel_powerclamp: No package C-state available at the 4th line I found that I have Intel 945GME Chipset and not I915 as referred later on in dmesg. does it effect this thread? cheers -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xse
[Touch-packages] [Bug 715141] Re: Default NTP servers do not have AAAA records
@Paul - I wondered do we converge onto providing ipv6 on all 4 ubuntu pool addresses? For bug 1754358 in chrony it would be really helpful to reach an optimal default configuration if all ubuntu pools would provide ipv6. I'm sure you know best what is planned (or could be done), so I'd be happy if you could let us know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/715141 Title: Default NTP servers do not have records Status in ntp package in Ubuntu: Fix Released Bug description: Binary package hint: ntp When installing ntp on an IPv6 only host, the kindly provided ntp.ubuntu.com does not work, because it does not have a record. Please provide IPv6 connectivity for this host. This affects all releases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card
Yes, I do. I have this problem only with some monitors / TV. -- 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/1686189 Title: External monitor connecting problem on Intel graphics card Status in linux package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1750514] Re: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest
** Changed in: cups Status: Unknown => New -- 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/1750514 Title: cupsd (11) ippCopyAttribute → copy_attrs → copy_printer_attrs → get_printer_attrs → cupsdProcessIPPRequest Status in CUPS: New Status in cups package in Ubuntu: Confirmed Status in cups source package in Bionic: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding cups. This problem was most recently seen with package version 2.2.6-5, the problem page at https://errors.ubuntu.com/problem/1b152bc770a7f1c23d7cae98db205bf7a7f45feb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1750514/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754145] Re: Pen input rotated by 90 degrees
** Package changed: ubuntu => xorg (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/1754145 Title: Pen input rotated by 90 degrees Status in xorg package in Ubuntu: New Bug description: I install and Ubuntu 18.04 on a ASUS Transformer mini T103. From the beginning the boot screen is rotated by 90 degrees ccw off like it is described in this post: https://askubuntu.com/questions/1008893/ubuntu-17-10-boots-90-degrees. The login screen has than the correct orientation, but the behaviour of the ASUS Pen is the same as it is still rotated. If I tip on the upper left corner using the pen, the pointer shows up in the upper right. If I move than down, the pointer moves left. If I touch on the screen with the finger all goes right. If I turn the tablet to portrait, the screen contents switches as expected and than the pen works correctly. It seem as if there a transformation issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754145] [NEW] Pen input rotated by 90 degrees
You have been subscribed to a public bug: I install and Ubuntu 18.04 on a ASUS Transformer mini T103. From the beginning the boot screen is rotated by 90 degrees ccw off like it is described in this post: https://askubuntu.com/questions/1008893/ubuntu-17-10-boots-90-degrees. The login screen has than the correct orientation, but the behaviour of the ASUS Pen is the same as it is still rotated. If I tip on the upper left corner using the pen, the pointer shows up in the upper right. If I move than down, the pointer moves left. If I touch on the screen with the finger all goes right. If I turn the tablet to portrait, the screen contents switches as expected and than the pen works correctly. It seem as if there a transformation issue. ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bot-comment input-device -- Pen input rotated by 90 degrees https://bugs.launchpad.net/bugs/1754145 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg 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 145289] Re: Xorg crashed with SIGSEGV in _mesa_update_state_locked() with DRI disabled
** Changed in: xorg-server Status: Confirmed => Invalid -- 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/145289 Title: Xorg crashed with SIGSEGV in _mesa_update_state_locked() with DRI disabled Status in X.Org X server: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: X crashed while I was using a custom 3D application. I was actually investigating further this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video- ati/+bug/144865 This crash was obtained using the following xorg parameters: Section "Device" Identifier "ATI Technologies Inc RV370 5B64 [FireGL V3100 (PCIE)]" Driver "ati" BusID"PCI:1:0:0" Option "GARTSize" "64" Option "DRI" "false" EndSection ProblemType: Crash Architecture: i386 CrashCounter: 1 Date: Wed Sep 26 18:44:55 2007 Disassembly: 0xaf79f0e0: DistroRelease: Ubuntu 7.10 ExecutablePath: /usr/bin/Xorg NonfreeKernelModules: cdrom Package: xserver-xorg-core 2:1.3.0.0.dfsg-12ubuntu6 PackageArchitecture: i386 ProcCmdline: /usr/bin/X :0 -br -audit 0 -auth /var/lib/gdm/:0.Xauth -nolisten tcp vt10 ProcCwd: /etc/X11 ProcEnviron: LANGUAGE= PATH=/sbin:/bin:/usr/sbin:/usr/bin LANG=fr_FR.UTF-8 Signal: 11 SourcePackage: xorg-server Stacktrace: #0 0xaf79f0e0 in ?? () StacktraceTop: ?? () ThreadStacktrace: Title: Xorg crashed with SIGSEGV Uname: Linux valette-desktop 2.6.22-12-generic #1 SMP Sun Sep 23 18:11:30 GMT 2007 i686 GNU/Linux UserGroups: #0 _mesa_update_framebuffer (ctx=0x98eb698) at framebuffer.c:674 fb = (struct gl_framebuffer *) 0x0 #1 0xaf7bff91 in _mesa_update_state_locked (ctx=0x98eb698) at state.c:1152 new_state = 4294967295 #2 0xaf7c00ea in _mesa_update_state (ctx=0x98eb698) at state.c:1218 No locals. #3 0xaf77b860 in _mesa_GetIntegerv (pname=34018, params=0xbf8b7588) at get.c:3741 ctx = (GLcontext *) 0x98eb698 #4 0xb7be90c2 in __glXDisp_GetIntegerv (cl=0x83f77d8, pc=0x843f4a0 "\217u\003") at ../../../GL/glx/indirect_dispatch.c:1905 pname = 34018 compsize = 1 answerBuffer = {-1210730033, -1209602060, 1717986918, 20, -1081378788, -1210722100, 1717986918, 11, 1, 20, 0, -1209597584, -1081379352, 135490926, 0, 0, -1081378568, 136331424, -1081378568, 0, -1081379192, 135047694, 136419728, 136406392, -1081379304, -1212712799, 135102528, 0, -1081378568, 0 , 136217184, -16, 2, -1081379144, 134820522, 0, 0, 1, 136331424, 2, 0, 134820379, 136217184, 1, 0, -1081378552, 136039487, -2147483648, 136331424, 0, 0, 0, 0, -1081378704, 8, 0 , -1081378776, -1210488832, -1209597632, 160605608, -1081378776, 1, -1081378652, -1210102424, -1081378652, 31, 160605608, 136217184, 138304976, 1, -1081378744, 136083134, 31, -1081378652, 1, -1212162056, 160605608, ---Type to continue, or q to quit--- 136217184, -1081378712, 136078111, 135624588, 136217184, -1081378680, 134821386, 136307620, 0, -1081378624, 4096, 138671264, -1210135373, 136217184, 136217184, -1081378616, 1, -1081378664, 134821040, -40, 32, -1212067132, -1212067136, 5, -1212018432} error = -1081378632 cx = #5 0xb7bddb2c in __glXDispatch (client=0x83f76a0) at ../../../GL/glx/glxext.c:551 stuff = (xGLXSingleReq *) 0x843f4a0 opcode = 117 'u' proc = (__GLXdispatchSingleProcPtr) 0xb7be9020 <__glXDisp_GetIntegerv> cl = (__GLXclientState *) 0x83f77d8 retval = 1 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/145289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754332] [NEW] /var/log/journal not created on fresh install of systemd
Public bug reported: (Such as during image builds.) ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: New ** Tags: amd64 apport-bug bionic ** Changed in: systemd (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Description changed: (Such as during image builds.) - - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: systemd 237-3ubuntu4 - ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 - Uname: Linux 4.15.0-10-generic x86_64 - ApportVersion: 2.20.8-0ubuntu10 - Architecture: amd64 - CurrentDesktop: ubuntu:GNOME - Date: Thu Mar 8 14:38:21 2018 - InstallationDate: Installed on 2017-10-23 (135 days ago) - InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) - MachineType: LENOVO 20ANCTO1WW - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 - SourcePackage: systemd - SystemdDelta: - [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf - [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf - - 2 overridden configuration files found. - UpgradeStatus: Upgraded to bionic on 2018-01-23 (44 days ago) - dmi.bios.date: 05/21/2014 - dmi.bios.vendor: LENOVO - dmi.bios.version: GLET70WW (2.24 ) - dmi.board.asset.tag: Not Available - dmi.board.name: 20ANCTO1WW - dmi.board.vendor: LENOVO - dmi.board.version: SDK0E50512 STD - dmi.chassis.asset.tag: No Asset Information - dmi.chassis.type: 10 - dmi.chassis.vendor: LENOVO - dmi.chassis.version: Not Available - dmi.modalias: dmi:bvnLENOVO:bvrGLET70WW(2.24):bd05/21/2014:svnLENOVO:pn20ANCTO1WW:pvrThinkPadT440p:rvnLENOVO:rn20ANCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNotAvailable: - dmi.product.family: ThinkPad T440p - dmi.product.name: 20ANCTO1WW - dmi.product.version: ThinkPad T440p - dmi.sys.vendor: LENOVO -- 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/1754332 Title: /var/log/journal not created on fresh install of systemd Status in systemd package in Ubuntu: New Bug description: (Such as during image builds.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1722313] Re: Enable auditing in util-linux.
** Changed in: util-linux (Debian) Status: New => Fix Released -- 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/1722313 Title: Enable auditing in util-linux. Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Released Status in util-linux source package in Zesty: Fix Committed Status in util-linux source package in Artful: Fix Released Status in util-linux package in Debian: Fix Released Bug description: [IMPACT] Enable auditing in util-linux. The config option, --with-audit enables auditing. Only the hwclock and the login commands within util-linux package have source code for auditing. But that source code is disabled by default and requires the config option, --with-audit to enable it. The login command is not built nor shipped in util-linux. Ubuntu uses the login command from shadow instead. Thus, only hwclock command would be affected by this change. The change would enable the hwclock command to generate an audit log message to /var/log/audit/audit.log whenever it changes the hardware clock. This message will only get logged to /var/log/audit/audit.log, if auditd daemon is running. Otherwise, if the auditd is not running, like most log messages, it will get logged to /var/log/kern.log and|or /var/log/syslog if these services are enabled. That the hwclock generates an audit message when hardware clock is changed is a requirement for Common Criteria EAL2 certification for Xenial. [TEST] This has been tested on both P8 and amd64 architectures. With the patch all the Common Criteria testcases pass for hwclock. Before this patch, the functional part of the testcase passed, but the check for the triggered audit records would fail. Attached the Common Criteria testcase below. Also, the util-linux package has testcases that get run during the build. All of these pass. Pointer to build log below. [REGRESSION POTENTIAL] The regression potential for this should be small. This change does not take away from any current functionality. It just adds the ability to generate an audit entry when system hardware clock is altered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754315] [NEW] just ran bug check.. sending report
Private bug reported: unknown at this time, new install.. ran check sent me here. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 8 04:12:49 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:2231] InstallationDate: Installed on 2018-03-05 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FHCTO1WW ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET33W(1.20):bd09/07/2017:svnLENOVO:pn20FHCTO1WW:pvrThinkPadT560:rvnLENOVO:rn20FHCTO1WW:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T560 dmi.product.name: 20FHCTO1WW dmi.product.version: ThinkPad T560 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Mar 8 04:05:02 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu ** Information type changed from Public to Public Security ** Information type changed from Public Security to Private -- 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/1754315 Title: just ran bug check.. sending report Status in xorg package in Ubuntu: New Bug description: unknown at this time, new install.. ran check sent me here. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Mar 8 04:12:49 2018 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu GraphicsCard: Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 520 [17aa:2231] InstallationDate: Installed on 2018-03-05 (3 days ago) InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 (20171017.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20FHCTO1WW ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic root=/dev/mapper/ubuntu--budgie--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N1KET33W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1KET33W(1.20):bd09/07/2017:svnLENOVO:pn20FHCTO1WW:p
Re: [Touch-packages] [Bug 1751129] Re: I think there is some security issue in my ubuntu .
You are not understanding the problem this way . Can u call on my number +918715091128 On Tue, 6 Mar 2018, 4:01 pm Seth Arnold, <1751...@bugs.launchpad.net> wrote: > Hello Umer, I believe this is working as intended. > > By default Ubuntu users in the admin or sudo group have full privileges > on the system via sudo. > > If you can reproduce this without being in either of these groups, > please re-open, attach your sudoers(5) file, and a terminal transcript > showing id(1) output and the problem. > > Thanks > > ** Package changed: unity (Ubuntu) => sudo (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1751129 > > Title: > I think there is some security issue in my ubuntu . > > Status in sudo package in Ubuntu: > Incomplete > > Bug description: > If I log into any other user i am able to access my main user through > terminal with my current user password. I am using ubuntu 16.04 and I > think it might be in all ubuntu 16.04 operating systems. > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: unity 7.4.5+16.04.20171201.3 > Uname: Linux 4.15.1-041501-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.1-0ubuntu2.15 > Architecture: amd64 > CompizPlugins: > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > CompositorRunning: compiz > CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' > CompositorUnredirectFSW: true > CurrentDesktop: Unity > Date: Fri Feb 23 01:06:34 2018 > DistUpgraded: Fresh install > DistroCodename: xenial > DistroVariant: ubuntu > DkmsStatus: >bbswitch, 0.8, 4.13.0-32-generic, x86_64: installed >bbswitch, 0.8, 4.15.1-041501-generic, x86_64: installed >nvidia-384, 384.111, 4.13.0-32-generic, x86_64: installed >nvidia-384, 384.111, 4.15.1-041501-generic, x86_64: installed >virtualbox, 5.0.40, 4.13.0-32-generic, x86_64: installed > ExecutablePath: /usr/bin/compiz > GconfCompiz: >/apps/compiz-1/general: > /apps/compiz-1/general/screen0: > /apps/compiz-1/general/screen0/options: >active_plugins = > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > GraphicsCard: >Intel Corporation Haswell-ULT Integrated Graphics Controller > [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) > Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics > Controller [103c:198f] > InstallationDate: Installed on 2018-01-22 (31 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > MachineType: Hewlett-Packard HP EliteBook 840 G1 > ProcEnviron: >PATH=(custom, user) >SHELL=/bin/bash >LANG=en_IN >LANGUAGE=en_IN:en >XDG_RUNTIME_DIR= > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.1-041501-generic > root=UUID=95af4278-a5ad-4183-9691-2a68fd0e627e ro > resume=UUID=a7e7e167-65b7-4b78-ad75-4400e9b38bad resume= resume= quiet > splash vt.handoff=7 > SourcePackage: unity > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 09/01/2015 > dmi.bios.vendor: Hewlett-Packard > dmi.bios.version: L71 Ver. 01.33 > dmi.board.name: 198F > dmi.board.vendor: Hewlett-Packard > dmi.board.version: KBC Version 15.57 > dmi.chassis.asset.tag: CNU4219GQQ > dmi.chassis.type: 10 > dmi.chassis.vendor: Hewlett-Packard > dmi.modalias: > dmi:bvnHewlett-Packard:bvrL71Ver.01.33:bd09/01/2015:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009FD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.57:cvnHewlett-Packard:ct10:cvr: > dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI > dmi.product.name: HP EliteBook 840 G1 > dmi.product.version: A3009FD10303 > dmi.sys.vendor: Hewlett-Packard > version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 > version.ia32-libs: ia32-libs N/A > version.libdrm2: libdrm2 2.4.83-1~16.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 > version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A > version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 > version.xserver-xorg-core: xserver-xorg-core N/A > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A > version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A > xserver.bootTime: Thu Feb 22 21:34:13 2018 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.19.5-0ubuntu2~16.04.1 > xserver.video_driver: modeset > > To manage notifications about th
[Touch-packages] [Bug 1754309] [NEW] 2 issues
Public bug reported: chack issues ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 8 17:24:03 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:39b5] InstallationDate: Installed on 2018-03-08 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210f Acer, Inc Bus 001 Device 002: ID 0bda:c024 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=3b5ebb05-0cbe-4a1a-b1f1-3e3651a75837 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN21WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55722 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN21WW:bd12/04/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55722WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: ideapad 320-15IKB dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Mar 8 17:02:43 2018 xserver.configfile: default xserver.devices: inputVideo BusKEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputEasyCamera: EasyCamera KEYBOARD, id 8 inputElan TouchpadTOUCHPAD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1754309 Title: 2 issues Status in xorg package in Ubuntu: New Bug description: chack issues ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 8 17:24:03 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:39b5] InstallationDate: Installed on 2018-03-08 (0 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:210f Acer, Inc Bus 001 Device 002: ID 0bda:c024 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81BG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=3b5ebb05-0cbe-4a1a-b1f1-3e3651a75837 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12
[Touch-packages] [Bug 1754265] Re: packagekitd crashed with SIGSEGV in utilBuildPackageId()
So, the problem is that PackageKit casts the item owner to pkgAcqArchiveSane, but I'm using the mirror method and this now fetches the mirror list every run, and that's probably not a pkgAcqArchive. ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1754265 Title: packagekitd crashed with SIGSEGV in utilBuildPackageId() Status in packagekit package in Ubuntu: Triaged Bug description: PackageKit seems to be crashing randomly on bionic, not sure why, did not investigate further yet. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: packagekit 1.1.7-1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Thu Mar 8 08:35:34 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2017-12-08 (89 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: /usr/lib/packagekit/packagekitd SegvAnalysis: Segfault happened at: 0x7fca622a9ecc <_Z18utilBuildPackageIdRKN8pkgCache11VerIteratorE+124>: cmpb $0x6,0x22(%rax) PC (0x7fca622a9ecc) ok source "$0x6" ok destination "0x22(%rax)" (0x0015f6da) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing unknown VMA Signal: 11 SourcePackage: packagekit StacktraceTop: utilBuildPackageId(pkgCache::VerIterator const&) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so AptIntf::emitPackage(pkgCache::VerIterator const&, PkInfoEnum) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so AcqPackageKitStatus::updateStatus(pkgAcquire::ItemDesc&, int) () at /usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so pkgAcquire::Worker::RunMessages() () at /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 pkgAcquire::Worker::InFdReady() () at /usr/lib/x86_64-linux-gnu/libapt-pkg.so.5.0 Title: packagekitd crashed with SIGSEGV in utilBuildPackageId() UpgradeStatus: Upgraded to bionic on 2017-12-08 (89 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1754265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf
Now I remove +s bit from /usr/bin/X, /usr/bin/xinit, /usr/bin/startx, /usr/bin/Xorg and tried to run Valgrind with it. Honestly I have no idea about debugging. I just know that valgrind and strace can be somehow use for it. Hope this helps! output of valgrind -v startx 1> valgrind_v_startx.txt 2>&1 ** Attachment added: "valgrind_v_startx.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5072779/+files/valgrind_v_startx.txt -- 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/1754296 Title: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf Status in xorg package in Ubuntu: New Bug description: [New bug filed with ubuntu-bug/apport. However there was nothing to file against in /var/crashes] For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. Disabling the Composite extension prevents tearing in (some) games and sometimes is an additional performance boost. This worked flawlessly in all previous Ubuntu versions including 17.10 (artful). This stopped working with Ubuntu 18.04 (bionic). I tested with the mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and bionic. Xserver will crash with "Option "Composite" "0/False/Disable" When I comment out the specific line in the Extensions section (that means *enabling* Composite) it works again with this xorg.conf. I can also do other stuff like disabling DRI3 or AIGLX. No crashes in these cases. My xorg.conf: Section "Device" Identifier "Intel GMA45" ##just a trivial name as Identifier Driver "intel" EndSection Section "Extensions" Option "Composite" "0" EndSection It has a backtrace and caughts signal 6. My Xorg.0.log: [ 35.779] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 35.781] X Protocol Version 11, Revision 0 [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64 [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash [ 35.787] Build Date: 22 February 2018 08:04:42PM [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see http://www.ubuntu.com/support) [ 35.789] Current version of pixman: 0.34.0 [ 35.792] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time: Wed Mar 7 22:43:35 2018 [ 35.801] (==) Using config file: "/etc/X11/xorg.conf" [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 35.803] (==) No Layout section. Using the first Screen section. [ 35.803] (==) No screen section available. Using defaults. [ 35.803] (**) |-->Screen "Default Screen Section" (0) [ 35.803] (**) | |-->Monitor "" [ 35.804] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset" [ 35.804] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 35.804] (==) Automatically adding devices [ 35.804] (==) Automatically enabling devices [ 35.804] (==) Automatically adding GPU devices [ 35.804] (==) Automatically binding GPU devices [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 35.809] Entry deleted from font path. [ 35.822] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules" [ 35.822] (**) Extension "Composite" is disabled [ 35.822] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 35.822] (II) Loader magic: 0x55cfd2964020 [ 35.822] (II) Module ABI versions: [ 35.822] X.Org ANSI C Emulation: 0.4 [ 35.822] X.Org Video Driver: 23.0 [ 35.822] X.Org XInput driver : 24.1 [ 35.822] X.Org Server Extension : 10.0 [ 35.824] (++) using VT number 1 [ 35.827] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 35.828] (II) xfree86: Adding drm device (/dev
[Touch-packages] [Bug 1754296] Re: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf
tried with "strace startx" ** Attachment added: "strace startx" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1754296/+attachment/5072778/+files/strace_startx_001.txt -- 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/1754296 Title: [bionic] startx / xinit crashes with Composite Disabled in xorg.conf Status in xorg package in Ubuntu: New Bug description: [New bug filed with ubuntu-bug/apport. However there was nothing to file against in /var/crashes] For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. Disabling the Composite extension prevents tearing in (some) games and sometimes is an additional performance boost. This worked flawlessly in all previous Ubuntu versions including 17.10 (artful). This stopped working with Ubuntu 18.04 (bionic). I tested with the mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and bionic. Xserver will crash with "Option "Composite" "0/False/Disable" When I comment out the specific line in the Extensions section (that means *enabling* Composite) it works again with this xorg.conf. I can also do other stuff like disabling DRI3 or AIGLX. No crashes in these cases. My xorg.conf: Section "Device" Identifier "Intel GMA45" ##just a trivial name as Identifier Driver "intel" EndSection Section "Extensions" Option "Composite" "0" EndSection It has a backtrace and caughts signal 6. My Xorg.0.log: [ 35.779] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 35.781] X Protocol Version 11, Revision 0 [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64 [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash [ 35.787] Build Date: 22 February 2018 08:04:42PM [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see http://www.ubuntu.com/support) [ 35.789] Current version of pixman: 0.34.0 [ 35.792] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time: Wed Mar 7 22:43:35 2018 [ 35.801] (==) Using config file: "/etc/X11/xorg.conf" [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 35.803] (==) No Layout section. Using the first Screen section. [ 35.803] (==) No screen section available. Using defaults. [ 35.803] (**) |-->Screen "Default Screen Section" (0) [ 35.803] (**) | |-->Monitor "" [ 35.804] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset" [ 35.804] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 35.804] (==) Automatically adding devices [ 35.804] (==) Automatically enabling devices [ 35.804] (==) Automatically adding GPU devices [ 35.804] (==) Automatically binding GPU devices [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 35.809] Entry deleted from font path. [ 35.822] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules" [ 35.822] (**) Extension "Composite" is disabled [ 35.822] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 35.822] (II) Loader magic: 0x55cfd2964020 [ 35.822] (II) Module ABI versions: [ 35.822] X.Org ANSI C Emulation: 0.4 [ 35.822] X.Org Video Driver: 23.0 [ 35.822] X.Org XInput driver : 24.1 [ 35.822] X.Org Server Extension : 10.0 [ 35.824] (++) using VT number 1 [ 35.827] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0) [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 0x/131072 [ 35.832] (--) PCI: (0:0:2:1) 8086
[Touch-packages] [Bug 1753928] Re: OpenCV version in Bionic
It's probably a bit too late now, as we're past feature freeze. See https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule and https://wiki.ubuntu.com/FeatureFreeze. Separately, it'd need someone to contribute the update. ** Tags added: upgrade-software-version ** Changed in: opencv (Ubuntu) Status: New => Triaged ** Changed in: opencv (Ubuntu) Importance: Undecided => Wishlist ** Summary changed: - OpenCV version in Bionic + Please update OpenCV to 3.4 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1753928 Title: Please update OpenCV to 3.4 Status in opencv package in Ubuntu: Triaged Bug description: From https://launchpad.net/ubuntu/bionic/+source/opencv I got to know the version of OpenCV that will be shipped with Bionic is 3.1. However this is way too old (from 2015). It's been more than 3 months since OpenCV 3.4.0 was released. Can you consider OpenCV version 3.4.x for Bionic release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1753928/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754296] [NEW] [bionic] startx / xinit crashes with Composite Disabled in xorg.conf
Public bug reported: [New bug filed with ubuntu-bug/apport. However there was nothing to file against in /var/crashes] For certain games I disable the Composite extension in my /etc/X11/xorg.conf when using a non-composited window manager like openbox, fluxbox or marco. Disabling the Composite extension prevents tearing in (some) games and sometimes is an additional performance boost. This worked flawlessly in all previous Ubuntu versions including 17.10 (artful). This stopped working with Ubuntu 18.04 (bionic). I tested with the mainline kernel 4.16 and the current 4.15 kernel in bionic-proposed and bionic. Xserver will crash with "Option "Composite" "0/False/Disable" When I comment out the specific line in the Extensions section (that means *enabling* Composite) it works again with this xorg.conf. I can also do other stuff like disabling DRI3 or AIGLX. No crashes in these cases. My xorg.conf: Section "Device" Identifier "Intel GMA45" ##just a trivial name as Identifier Driver "intel" EndSection Section "Extensions" Option "Composite" "0" EndSection It has a backtrace and caughts signal 6. My Xorg.0.log: [ 35.779] X.Org X Server 1.19.6 Release Date: 2017-12-20 [ 35.781] X Protocol Version 11, Revision 0 [ 35.782] Build Operating System: Linux 4.4.0-101-generic x86_64 Ubuntu [ 35.783] Current Operating System: Linux bdcomputerclub 4.16.0-994-generic #201803022100 SMP Sat Mar 3 02:03:37 UTC 2018 x86_64 [ 35.784] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.16.0-994-generic root=UUID=cb2eb60a-9760-4805-95eb-0db77947ac82 ro quiet splash [ 35.787] Build Date: 22 February 2018 08:04:42PM [ 35.788] xorg-server 2:1.19.6-1ubuntu2 (For technical support please see http://www.ubuntu.com/support) [ 35.789] Current version of pixman: 0.34.0 [ 35.792] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 35.792] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 35.799] (==) Log file: "/home/christian/.local/share/xorg/Xorg.0.log", Time: Wed Mar 7 22:43:35 2018 [ 35.801] (==) Using config file: "/etc/X11/xorg.conf" [ 35.803] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 35.803] (==) No Layout section. Using the first Screen section. [ 35.803] (==) No screen section available. Using defaults. [ 35.803] (**) |-->Screen "Default Screen Section" (0) [ 35.803] (**) | |-->Monitor "" [ 35.804] (==) No device specified for screen "Default Screen Section". Using the first device section listed. [ 35.804] (**) | |-->Device "Intel GMA45 Express Chipset" [ 35.804] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 35.804] (==) Automatically adding devices [ 35.804] (==) Automatically enabling devices [ 35.804] (==) Automatically adding GPU devices [ 35.804] (==) Automatically binding GPU devices [ 35.804] (==) Max clients allowed: 256, resource mask: 0x1f [ 35.809] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 35.809] Entry deleted from font path. [ 35.822] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 35.822] (==) ModulePath set to "/usr/lib/xorg/modules" [ 35.822] (**) Extension "Composite" is disabled [ 35.822] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 35.822] (II) Loader magic: 0x55cfd2964020 [ 35.822] (II) Module ABI versions: [ 35.822] X.Org ANSI C Emulation: 0.4 [ 35.822] X.Org Video Driver: 23.0 [ 35.822] X.Org XInput driver : 24.1 [ 35.822] X.Org Server Extension : 10.0 [ 35.824] (++) using VT number 1 [ 35.827] (II) systemd-logind: took control of session /org/freedesktop/login1/session/_32 [ 35.828] (II) xfree86: Adding drm device (/dev/dri/card0) [ 35.829] (II) systemd-logind: got fd for /dev/dri/card0 226:0 fd 11 paused 0 [ 35.832] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0459 rev 9, Mem @ 0xd000/4194304, 0xc000/268435456, I/O @ 0x50f0/8, BIOS @ 0x/131072 [ 35.832] (--) PCI: (0:0:2:1) 8086:2a43:1025:0459 rev 9, Mem @ 0xd340/1048576 [ 35.833] (II) LoadModule: "glx" [ 35.836] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 35.850] (II) Module glx: vendor="X.Org Foundation" [ 35.850] compiled for 1.19.6, module version = 1.0.0 [ 35.850] ABI class: X.Org Server Extension, version 10.0 [ 35.850] (II) LoadModule: "intel" [ 35.850] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so [ 35.856] (II) Module intel: vendor="X.Org Foundation" [ 35.856] compiled for 1.19.5, module version = 2.99.917 [ 35.856] Module class: X.Org Video Driver [ 35.856] ABI class: X.Org Video Driver, version 23.0 [ 35.856] (II) int
[Touch-packages] [Bug 1754294] [NEW] After last updated libcurl3 on libcurl4, some apps are removed.
Public bug reported: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? ** Affects: curl (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi! - After last updated libcurl3 on libcurl4, system deleted such applications as: + After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: New Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution
On Wed, Mar 07, 2018 at 11:42:29PM -, Jason Hobbs wrote: > Is there a workaround for this? I can just rm /etc/resolv.conf and > create it with the contents I want, right? Yep, though you'll need to recreate it every so often as it will be replaced. -- 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/1750884 Title: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution Status in cloud-init: New Status in MAAS: Triaged Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When deploying Bionic, /etc/resolv.conf is not configured correctly, which leads to no DNS resolution. In the output below, you will see that netplan config is correctly to the 10.90.90.1 nameserver, but in resolv.conf that's a local address. Resolv.conf should really be configured to use the provided DNS server(s). That said, despite that fact, DNS resolution doesn't work with the local address. Bionic -- ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} network: version: 2 ethernets: enp0s25: match: macaddress: b8:ae:ed:7d:17:d2 mtu: 1500 nameservers: addresses: - 10.90.90.1 search: - maaslab - maas set-name: enp0s25 bridges: br0: addresses: - 10.90.90.3/24 gateway4: 10.90.90.1 interfaces: - enp0s25 parameters: forward-delay: 15 stp: false ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search maaslab maas ubuntu@node01:~$ ping google.com ping: google.com: Temporary failure in name resolution [...] ubuntu@node01:~$ sudo vim /etc/resolv.conf ubuntu@node01:~$ cat /etc/resolv.conf # This file is managed by man:systemd-resolved(8). Do not edit. # # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 10.90.90.1 search maaslab maas ubuntu@node01:~$ ping google.com PING google.com (172.217.0.174) 56(84) bytes of data. 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 time=4.46 ms 64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 time=4.38 ms = Xenial == ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg # This file is generated from information provided by # the datasource. Changes to it will not persist across an instance. # To disable cloud-init's network configuration capabilities, write a file # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following: # network: {config: disabled} auto lo iface lo inet loopback dns-nameservers 10.90.90.1 dns-search maaslab maas auto enp0s25 iface enp0s25 inet static address 10.90.90.162/24 gateway 10.90.90.1 mtu 1500 ubuntu@node05:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 10.90.90.1 search maaslab maas To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low
This issue is still not fixed for Xorg. Not sure what package to target though... -- 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/1698270 Title: Totem pauses and stutters during video playback even when CPU usage is low Status in GTK+: Fix Released Status in totem-pl-parser: Confirmed Status in clutter-1.0 package in Ubuntu: Won't Fix Status in clutter-gtk package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Status in totem-pl-parser package in Ubuntu: Fix Released Bug description: Totem pauses and stutters during video playback even when CPU usage is low. After figuring out how to play videos with full hardware accelerated decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses and stutters during playback. Other apps like Mplayer, VLC and even gst-play-1.0 never have this problem. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.24.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 12:03:18 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754270] Re: systemd-user PAM configuration should initialize the keyring with pam_keyinit
Found a Debian bug about the same issue but with AFS instead of fscrypt: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846377 ** Bug watch added: Debian Bug tracker #846377 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846377 -- 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/1754270 Title: systemd-user PAM configuration should initialize the keyring with pam_keyinit Status in systemd package in Ubuntu: New Bug description: /etc/pam.d/systemd-user does not currently call pam_keyinit.so -- it's possible this should instead be added to common-session-noninteractive but I am not entirely sure about that - someone with more understanding of the PAM modules would probably need to weigh in on that. In any case systemd-user itself should at least have it - as it has it's own special PAMname for processes it launches. This means that the keyring does not link to the user keyring as it should, and will cause issues with programs needing a key from the keyring. In particular the use case that breaks for me is using 'fscrypt' and 'libpam-fscrypt' however anything making use of kernel keyrings would be affected. Something non-obvious about this, is that many desktop session processes are started under 'systemd-user' instead of the 'session' - this includes gnome-terminal-server which means any gnome-terminal shell runs under this context. If you start xterm instead of gnome- terminal, you get a different keyring and this can cause confusion when debugging the issue as some processes are in one state and the others are in another including your primary debug tool gnome- terminal. You can verify this by running 'systemctl status $(pidof gnome-terminal)' and 'systemctl status $(pidof xterm)' and note the different hierachy. The change to add pam_keyinit.so was made upstream in December 2016: https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f Ubuntu should make the same change so that services needing a keyring will work correctly in the desktop session, and the same keyring is used for processes launched under both methods. In my test I add the usual pam_keyinit.so line after "pam_limits.so" and before "common- session-noninteractive". I am not sure if this is the most ideal location (but it appears to work). You can test the behavior by running "keyctl show @s" in both contexts Working contexts: - xterm - SSH login Broken contexts: - gnome-terminal - systemd-run --user keyctl show @s (then check output with journalctl --user --follow) When the configuration is broken you will see this output: lathiat@ubuntu:~/src/systemd$ keyctl show @s Keyring 59654779 --alswrv 1000 1000 keyring: _ses 6806191 s-rv 0 0 \_ user: invocation_id When the configuration is working, you will see a link to the user session instead: lathiat@ubuntu:~/src/systemd$ keyctl show @s Keyring 59654779 --alswrv 1000 1000 keyring: _ses 6806191 s-rv 0 0 \_ keyring: _uid.1000 As background, what is broken on my test setup with libpam-fscrypt? gnome-terminal for example is unable to write any file in my encrypted /home which means that it cannot save preferences, so if you go into preferences and try to tick a checkbox it will immediately revert and an error is logged to the journal. You can use the guide at https://github.com/google/fscrypt to setup such a system if you wish to fully test my case. But you can simply verify the behavior as above. Verified on bionic (its the only version with fscrypt) however this issue extends back to at least xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754270/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754270] [NEW] systemd-user PAM configuration should initialize the keyring with pam_keyinit
Public bug reported: /etc/pam.d/systemd-user does not currently call pam_keyinit.so -- it's possible this should instead be added to common-session-noninteractive but I am not entirely sure about that - someone with more understanding of the PAM modules would probably need to weigh in on that. In any case systemd-user itself should at least have it - as it has it's own special PAMname for processes it launches. This means that the keyring does not link to the user keyring as it should, and will cause issues with programs needing a key from the keyring. In particular the use case that breaks for me is using 'fscrypt' and 'libpam-fscrypt' however anything making use of kernel keyrings would be affected. Something non-obvious about this, is that many desktop session processes are started under 'systemd-user' instead of the 'session' - this includes gnome-terminal-server which means any gnome-terminal shell runs under this context. If you start xterm instead of gnome-terminal, you get a different keyring and this can cause confusion when debugging the issue as some processes are in one state and the others are in another including your primary debug tool gnome-terminal. You can verify this by running 'systemctl status $(pidof gnome-terminal)' and 'systemctl status $(pidof xterm)' and note the different hierachy. The change to add pam_keyinit.so was made upstream in December 2016: https://github.com/systemd/systemd/commit/ab79099d1684457d040ee7c28b2012e8c1ea9a4f Ubuntu should make the same change so that services needing a keyring will work correctly in the desktop session, and the same keyring is used for processes launched under both methods. In my test I add the usual pam_keyinit.so line after "pam_limits.so" and before "common-session- noninteractive". I am not sure if this is the most ideal location (but it appears to work). You can test the behavior by running "keyctl show @s" in both contexts Working contexts: - xterm - SSH login Broken contexts: - gnome-terminal - systemd-run --user keyctl show @s (then check output with journalctl --user --follow) When the configuration is broken you will see this output: lathiat@ubuntu:~/src/systemd$ keyctl show @s Keyring 59654779 --alswrv 1000 1000 keyring: _ses 6806191 s-rv 0 0 \_ user: invocation_id When the configuration is working, you will see a link to the user session instead: lathiat@ubuntu:~/src/systemd$ keyctl show @s Keyring 59654779 --alswrv 1000 1000 keyring: _ses 6806191 s-rv 0 0 \_ keyring: _uid.1000 As background, what is broken on my test setup with libpam-fscrypt? gnome-terminal for example is unable to write any file in my encrypted /home which means that it cannot save preferences, so if you go into preferences and try to tick a checkbox it will immediately revert and an error is logged to the journal. You can use the guide at https://github.com/google/fscrypt to setup such a system if you wish to fully test my case. But you can simply verify the behavior as above. Verified on bionic (its the only version with fscrypt) however this issue extends back to at least xenial. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1754270 Title: systemd-user PAM configuration should initialize the keyring with pam_keyinit Status in systemd package in Ubuntu: New Bug description: /etc/pam.d/systemd-user does not currently call pam_keyinit.so -- it's possible this should instead be added to common-session-noninteractive but I am not entirely sure about that - someone with more understanding of the PAM modules would probably need to weigh in on that. In any case systemd-user itself should at least have it - as it has it's own special PAMname for processes it launches. This means that the keyring does not link to the user keyring as it should, and will cause issues with programs needing a key from the keyring. In particular the use case that breaks for me is using 'fscrypt' and 'libpam-fscrypt' however anything making use of kernel keyrings would be affected. Something non-obvious about this, is that many desktop session processes are started under 'systemd-user' instead of the 'session' - this includes gnome-terminal-server which means any gnome-terminal shell runs under this context. If you start xterm instead of gnome- terminal, you get a different keyring and this can cause confusion when debugging the issue as some processes are in one state and the others are in another including your primary debug tool gnome- terminal. You can verify this by running 'systemctl status $(pidof gnome-terminal)' and 'systemctl status $(pidof xterm)' and note the different hierachy. The change to add pam_keyinit.so was made upstream in December