[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
I was in discussion with Kurt Roeckx on NTPsec before and the NTPsec folks as well but never had the time to continue - thanks you a lot for packaging it up Richard. I subscribed myself to 819806. Nice to hear that this will fix it for you as well! -- 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/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Triaged Status in ntp source package in Artful: New Status in ntp source package in Bionic: Triaged Bug description: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable
windows 10 lost ! Ubuntu begun with problems to install ! Ubuntu hav e problems to boot at the beginning! CIAO hans ** Changed in: debconf (Ubuntu) Assignee: (unassigned) => tritonus (prestosfz) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/349469 Title: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable Status in Aptdaemon: Fix Released Status in Debconf: New Status in aptdaemon package in Ubuntu: Invalid Status in debconf package in Ubuntu: Triaged Bug description: Upgrading packages that use debconf sometimes fail with the following error: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/349469/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1720684] Re: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile
Here's the same fix, for bionic. Unfortunately even with this fix it's too hard for me to tell if it's any improvement. My system seems to reliably default to the last used audio profile for the device. Even if I have removed and re-paired the device. So it seems like the fix at most is only necessary for brand new devices you've never had on your system before. ** Patch added: "pulseaudio_11.1-1ubuntu2.debdiff" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1720684/+attachment/5022464/+files/pulseaudio_11.1-1ubuntu2.debdiff ** Changed in: pulseaudio (Ubuntu) Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1720684 Title: Bluetooth speaker used the HSP/HFP profile by default rather than the higher-quality A2DP profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: In Progress Bug description: Kubuntu 17.04 Bluetooth device: https://smile.amazon.com/VicTsing-Wireless-Waterproof-Hands-Free-Speakerphone/dp/B074DX13T1 (itentifies itself as "C6") The above Bluetooth speaker paired and started streaming audio perfectly in Kubuntu 17.04. But the audio quality was poor, because the default audio profile was the low-quality HSP/HFP one. When I switched it to the A2DP profile, it sounded perfect again. Can we make A2DP the default playback profile for Bluetooth audio devices? To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
I'm seeing the same errors with NTPsec (a fork of this ntpd, which I have packaged for Debian) on 16.04. The apparmor policy is copied from this ntp package. I'm not able to reproduce the problem at will, but it seems to happen regularly. The proposed change seems to have resolved it. -- 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/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Triaged Status in ntp source package in Artful: New Status in ntp source package in Bionic: Triaged Bug description: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Yes I understand you and most people are asking for a resolution to "Not enough free handles to register service". However it is better for a bug's resolution if we focus on the problem that the original reporter was trying to describe. And that's a very different, unrelated problem. We certainly could rename this bug and commandeer it to be about "Not enough free handles to register service". But there's probably no need for that. If anyone would like a resolution to "Not enough free handles to register service" then please start by opening a bug for it here: https://bugs.launchpad.net/ubuntu/+source/bluez/+filebug Very simple and very clean. -- 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 1733557] Re: Login screen showing Authentication Failed Switch to greeter...
Anyone know either the cause, or a solution? If it helps, the two computers where I'm seeing this also happen to be the two host computers where I run Virtualbox. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failed Switch to greeter... Status in lightdm package in Ubuntu: Confirmed Bug description: When I lock my machine, the login screen shows my current user with the message: "Authentication Failed" ..and in the position when the password normally exists, the option "Switch to greeter..." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 21 10:28:47 2017 InstallationDate: Installed on 2017-04-17 (217 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1733557/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Complement to #56, Ubuntu 16.04.3, Kernel 4.14.4, journalctl -b: Dec 13 20:44:33 alien bluetoothd[928]: Failed to obtain handles for "Service Changed" characteristic Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Error adding Link Loss service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Current Time Service could not be registered Dec 13 20:44:33 alien bluetoothd[928]: gatt-time-server: Input/output error (5) Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service Dec 13 20:44:33 alien bluetoothd[928]: Not enough free handles to register service -- 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
This bug effects 128 people and closing it because you don't like the title feels wrong. Two Ask Ubuntu questions point to this Lanuchpad bug report in the hopes it will be solved: https://askubuntu.com/questions/757396/bluetooth-how-to-solve-not- enough-free-handles-to-register-service-error and https://askubuntu.com/questions/773629/16-04-bluetooth-error-not-enough- free-handles-to-register-service A Debian bug report suggests a solution by using -E (experimental) parameter on the systemd service exec doesn't work for Ubuntu 16.04, Kernel 4.14.4: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949 When a hundred reported people are effected by "Not enough free handles to register service" and you don't want to look at it because the bug title isn't right, why not simply change the title? Something else to consider are the thousands of people effected by bluetooth connection problems, re-pairing, etc. What if the root of their problems was this bug that you don't want to look at? ** Bug watch added: Debian Bug tracker #813949 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813949 -- 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 1717471] Re: networkd does not accept / set advertised mtu
Verification-done for xenial 0.32~16.04.3, and zesty 0.32~17.04.1: UseMTU=yes is set on the interfaces for which a MTU is set, and the MTU coming from DHCP is applied correctly when running 'netplan apply'. ** Tags removed: verification-needed-xenial verification-needed-zesty ** Tags added: verification-done-xenial verification-done-zesty ** Tags removed: verification-needed -- 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 Committed Status in systemd source package in Xenial: New Status in nplan source package in Zesty: Fix Committed 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 1709135] Re: add bond primary parameter
Verification-done xenial with 0.32~16.04.3: Testing bonding in active-backup and balance-tlb mode; in both cases when primary: is set, that device it correctly set to be used as the primary slave, as shown in both /proc/net/bonding/bond0 and /sys/class/net/bond0/bonding/primary. ** Tags removed: verification-needed 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Released Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737046] Re: Razer Naga Chroma wheel tilt being remapped to vertical scroll
I tested with evdev with the same daily image and it doesn't work there either. -- 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/1737046 Title: Razer Naga Chroma wheel tilt being remapped to vertical scroll Status in xorg package in Ubuntu: Incomplete Bug description: My Razer Naga Chroma's wheel tilt right and left (buttons 6, and 7) are being remapped to scroll up and down (buttons 4, and 5) as per xev. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-17.20~16.04.1-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 BootLog: Scanning for Btrfs filesystems Ubuntu: clean, 394556/11829248 files, 20977988/47286784 blocks 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 Dec 7 14:25:33 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer Device [1558:1303] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 5986: Acer, Inc Bus 001 Device 004: ID 1532:0053 Razer USA, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System76 Galago Pro ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic root=UUID=4bf03301-9454-4893-8590-722b1fa2efa7 ro quiet splash crashkernel=384M-2G:128M,2G-:256M vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.04nRSA dmi.board.asset.tag: Tag 12345 dmi.board.name: Galago Pro dmi.board.vendor: System76 dmi.board.version: galp2 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.04nRSA:bd04/26/2017:svnSystem76:pnGalagoPro:pvrgalp2:rvnSystem76:rnGalagoPro:rvrgalp2:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Galago Pro dmi.product.version: galp2 dmi.sys.vendor: System76 version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.80-1~xenial version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Thu Dec 7 14:21:19 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1~16.04.4 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1737046/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1644995] Re: specific SVG file breaks Ubuntu 16.04 desktop + nautilus
** Changed in: librsvg Status: Confirmed => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1644995 Title: specific SVG file breaks Ubuntu 16.04 desktop + nautilus Status in librsvg: Expired Status in librsvg package in Ubuntu: Triaged Bug description: Saving following file on Desktop (Ubuntu 16.04.1) results in: 1. Wallpaper and all icons on the desktop disappear 2. Nautilus starts for ~1sec then breaks with "Floating point exception" I suspect it's related to librsvg. In syslog I have many records similar to this one: kernel: [ 20.076864] traps: nautilus[2270] trap divide error ip:7f63fbddf716 sp:7f63fad3f5b0 error:0 in librsvg-2.so.2.40.13[7f63fbdc9000+35000] Here is the file (I can't even attach it here with Firefox, because it makes it crash): http://www.w3.org/2000/svg"; xmlns:xlink="http://www.w3.org/1999/xlink"; xmlns:ev="http://www.w3.org/2001/xml-events";> https://encrypted-tbn2.gstatic.com/images?q=tbn:ANd9GcRiXhgkC523CD5DIdvfwFl3G_S1Hc3oHzh8NUTXPeRSfYv1i8rA"; result="pattern" width="4" height="4"/> To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1644995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738085] Re: Bridge gets created while the network interfaces are still being renamed
I previously said that the "rename7" bridge name seemed constant, but after playing around a bit today I noticed that it's not exactly so. For example, I just saw following bridge setup after restarting my server: bridge name bridge id STP enabled interfaces lan 8000.7085c2026d54 no lan1 lan3 veth0P2CUY veth0QOJAX veth2MHFCX vethS3BS5A rename108000.90e2baaee820 no wlan rename7 8000.90e2baaee822 no lan2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1738085 Title: Bridge gets created while the network interfaces are still being renamed Status in bridge-utils package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed from eth1 Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed from eth2 Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed from eth3 Dec 13 16:03:38 trout kernel: [ 20.572747] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts t o load br_netfilter if you need this. Dec 13 16:03:38 trout kernel: [ 20.575364] device lan1 entered promiscuous mode Dec 13 16:03:38 trout kernel: [ 20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: link is not ready Dec 13 16:03:38 trout kernel: [ 21.097073] rename7: renamed from lan Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' is taking a long time Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/lan Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/rename7 Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC address for lan: No such file or directory Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan. Dec 13 16:04:59 trout kernel: [ 111.797526] device wlan entered promiscuous mode Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on /run/network/ifstate.lan Dec 13 16:04:59 trout kernel: [ 111.943158] device lan3 entered promiscuous mode Dec 13 16:05:00 trout kernel: [ 112.240052] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.240081] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: link is not ready Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 seconds). Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Dec 13 16:05:01 trout kernel: [ 113.610184] igb :01:00.2 lan2: igb: lan2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX Dec 13 16:05:01 trout kernel: [ 113.610324] lan: port 2(lan2) ente
[Touch-packages] [Bug 1568560] Re: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed
Not sure I agree with #13 because message comes AFTER network is up: Dec 13 05:52:20 alien NetworkManager[902]: [1513169540.4985] platform-linux: kernel support for IFLA_INET6_ADDR_GEN_MODE failed to detect; assume no support Dec 13 05:52:20 alien NetworkManager[902]: [1513169540.4991] manager: (enp59s0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/0) Dec 13 05:52:20 alien NetworkManager[902]: [1513169540.4998] keyfile: add connection in-memory (f1d049d0-ad20-3201-ac70-5cb8cc06a6e5,"Wired connection 1") Dec 13 05:52:20 alien NetworkManager[902]: [1513169540.5001] settings: (enp59s0): created default wired connection 'Wired connection 1' Dec 13 05:52:20 alien NetworkManager[902]: [1513169540.5007] device (enp59s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Dec 13 05:52:20 alien NetworkManager[902]: [1513169540.5025] device (enp59s0): link connected Dec 13 05:52:20 alien kernel: alx :3b:00.0 enp59s0: NIC Up: 1 Gbps Full Dec 13 05:52:20 alien NetworkManager[902]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed D Ubuntu 16.04.3, Kernel 4.14.4, Skylake laptop. IPv6 disabled with kernel command line in grub just because it life seems simpler that way. Only a couple of minor network interruptions requiring reboot over the last month. -- 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/1568560 Title: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed Status in NetworkManager: New Status in network-manager package in Ubuntu: Confirmed Bug description: Hello, On Ubuntu 15.10 4.2.0-35, with network-manager 1.0.4-0ubuntu5.3 My WiFi connection is very unstable and I have to often restart NetworkManager service (~ a dozen times every day...): sudo systemctl -l status NetworkManager ● NetworkManager.service - Network Manager Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled) Active: active (running) since dim. 2016-04-10 18:17:07 CEST; 2min 58s ago Main PID: 27832 (NetworkManager) Memory: 13.8M CPU: 1.729s CGroup: /system.slice/NetworkManager.service ├─ 2703 /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/run/sendsigs.omit.d/network-manager.dnsmasq.pid --listen-address=127.0.1.1 --conf-file=/var/run/NetworkManager/dnsmasq.conf --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d ├─27832 /usr/sbin/NetworkManager --no-daemon └─30448 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/sendsigs.omit.d/network-manager.dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-7ec429cb-9dde-4ea4-8eda-f259b66e38a7-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: keyfile: add connection in-memory (068de9b1-513a-46f0-b4be-93462d19f68b,"lxcbr0") avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unmanaged -> unavailable (reason 'connection-assumed') [10 20 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): device state change: unavailable -> disconnected (reason 'connection-assumed') [20 30 41] avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (lxcbr0): Activation: starting connection 'lxcbr0' (068de9b1-513a-46f0-b4be-93462d19f68b) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): new Tun device (carrier: OFF, driver: 'tun', ifindex: 34) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1): bridge port virbr1-nic was attached avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr1-nic): enslaved to virbr1 avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: (virbr0): new Bridge device (carrier: OFF, driver: 'bridge', ifindex: 29) avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: nm_device_get_device_type: assertion 'NM_IS_DEVICE (self)' failed avril 10 18:17:08 samsung-ubuntu NetworkManager[27832]: failed to enumerate oFono devices: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files Also, each time I restart my desktop, NetworkManager generates a crash report: cf. attached screenshots. I have tried an Ubuntu VM with the same packages related to networking and the exact same releases (same repositories), the crash never happens; the difference appears to be only the type of network connection: WiFi for the desktop vs Ethernet for the VM. Any suggestion? To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1568560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1611945] Re: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks
Just to confirm this year old bug is still around. Ubuntu 16.04.3, Kernel 4.14.4, NVMe Gen 3.0 x 4 M.2 SSD + Legacy 1 TB spinner, 3 NTFS-3G mounts: /mnt/c/, /mnt/d, /mnt/e defined in /etc/fstab. 3 Errors, with 2 info lines in between, reported by `journalctl -b`: Dec 13 05:52:20 alien systemd[1]: dev-disk-by\x2dpartlabel- Microsoft\x5cx20reserved\x5cx20partition.device: Dev dev-disk-by \x2dpartlabel-Microsoft\x5cx20reserved\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:1d.0/:3e:00.0/nvme/nvme0/nvme0n1/nvme0n1p3 and /sys/devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda2 Dec 13 05:52:20 alien systemd[1]: dev-disk-by\x2dpartlabel- Basic\x5cx20data\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel- Basic\x5cx20data\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:1d.0/:3e:00.0/nvme/nvme0/nvme0n1/nvme0n1p4 and /sys/devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda3 Dec 13 05:52:20 alien systemd[1]: Found device HGST_HTS721010A9E630 HGST_Win10. Dec 13 05:52:20 alien systemd[1]: Mounting /mnt/d... Dec 13 05:52:20 alien systemd[1]: dev-disk-by\x2dpartlabel- EFI\x5cx20system\x5cx20partition.device: Dev dev-disk-by\x2dpartlabel- EFI\x5cx20system\x5cx20partition.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:1d.0/:3e:00.0/nvme/nvme0/nvme0n1/nvme0n1p2 and /sys/devices/pci:00/:00:17.0/ata2/host1/target1:0:0/1:0:0:0/block/sda/sda1 Parition Information from `lsblk` = NAMEFSTYPE LABELMOUNTPOINT SIZE MODEL sda931.5G HGST HTS721010A9 ├─sda4 ntfs WINRETOOLS450M ├─sda2 128M ├─sda5 ntfs Image11.4G ├─sda3 ntfs HGST_Win10 /mnt/d 919G └─sda1 vfat ESP 500M nvme0n1 477G Samsung SSD 960 PRO 512GB ├─nvme0n1p5 ext4 NVMe_Ubuntu_16.0 / 44.6G ├─nvme0n1p3 16M ├─nvme0n1p1 ntfs 450M ├─nvme0n1p6 swap Linux Swap [SWAP] 7.9G ├─nvme0n1p4 ntfs NVMe_Win10 /mnt/c 414.9G ├─nvme0n1p2 vfat/boot/efi 99M └─nvme0n1p7 ntfs Shared_WSL+Linux /mnt/e 9G -- 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/1611945 Title: /dev/disk/by-path not properly populated for (e)SATA port multiplier disks Status in systemd package in Ubuntu: Confirmed Bug description: We have a just-installed Ubuntu 16.04 LTS machine with a number of disks behind port-multiplier eSATA ports, all of them driven by a SiI 3124 controller (sata_sil24 kernel driver). Our machine sees all disks on all channels, however under 16.04 only one disk from each channel shows up in /dev/disk/by-path/ (all disks show up in /dev/disk/by-id and /dev/disk/by-uuid). For our usage this is a severe defect because we rotate disks in and out of the external enclosure and rely on mounting specific slots in the external enclosure through /dev/disk /by-path. This did not happen in Ubuntu 12.04 LTS, the release that this machine was previously running. According to 'udevadm info --export-db' and 'udevadm test-builtin path_id' and so on, systemd's udev stuff is assigning all drives behind the same port the same disk/by-path data (ID_PATH et al). In 'udevadm info /sys/block/sdX', the 'P:' and 'E: DEVPATH=' values show a difference in the target portion of PCI path, eg: P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:0:0/0:0:0:0/block/sda P: /devices/pci:00/:00:01.0/:01:00.0/:02:00.0/ata1/host0/target0:1:0/0:1:0:0/block/sdb However the 'S: disk/by-path', 'E: DEVLINKS=', and 'E: ID_PATH' portions do not. For both devices above, we see: S: disk/by-path/pci-:02:00.0-ata-1 E: ID_PATH=pci-:02:00.0-ata-1 Naturally only one device can have a /dev/disk/by- path/pci-:02:00.0-ata-1 symlink, so instead of four disks per channel in /dev/disk/by-path we see one. Ubuntu release: 16.04 Package versions from 'apt-cache policy udev systemd': udev: Installed: 229-4ubuntu7 systemd: Installed: 229-4ubuntu7 'journalctl -b' reports that during boot systemd does report some 'appeared twice with different sysfs paths' notes, eg: Aug 10 13:34:21 verdandi systemd[1]: dev-disk-by\x2dpath- pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device: Dev dev-disk-by \x2dpath-pci\x2d:02:00.0\x2data\x2d1\x2dpart1.device appeared twice with different sysf
[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
Hi @Łukasz, per #26, zesty version did fix LP: #1693756. If the difference between SRU zesty version and the backport in LP: #1693756 is something within two weeks, I think we should proceed to SRU zesty version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: In Progress Status in libmbim source package in Xenial: New Status in libqmi source package in Xenial: New Status in modemmanager source package in Xenial: New Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054 libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1723956] Re: busybox-static: several network applets segfaulting
Thanks. Loading busybox-static-dbgsym and retracing this with gdb, I see the following backtrace: (gdb) thread apply all bt full Thread 1 (Thread 0x11bb880 (LWP 31592)): #0 0x in ?? () No symbol table info available. #1 0x7f601bb0af90 in __pthread_initialize_minimal_internal () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #2 0x7f601bb0a571 in _init () from /lib/x86_64-linux-gnu/libpthread.so.0 No symbol table info available. #3 0x7f601c358f70 in ?? () No symbol table info available. #4 0x004f147a in call_init.part () No symbol table info available. #5 0x004f1635 in _dl_init () No symbol table info available. #6 0x004e3a46 in dl_open_worker () No symbol table info available. #7 0x004e11f4 in _dl_catch_error () No symbol table info available. #8 0x004e33b9 in _dl_open () No symbol table info available. #9 0x0049ff22 in do_dlopen () No symbol table info available. ---Type to continue, or q to quit--- #10 0x004e11f4 in _dl_catch_error () No symbol table info available. #11 0x004a010e in __libc_dlopen_mode () No symbol table info available. #12 0x00493aa8 in __nss_next2 () No symbol table info available. #13 0x0048b310 in gethostbyaddr_r () No symbol table info available. #14 0x0048d158 in gni_host_inet_name.isra () No symbol table info available. #15 0x0048d752 in getnameinfo () No symbol table info available. #16 0x0058c312 in sockaddr2str (sa=0x11bdc50, flags=flags@entry=10) at libbb/xconnect.c:439 host = "8.8.8.8\000\000\334\033\001", '\000' , "\350\003\000\000\000\000\000\000\261tB\000\000\000\000\000\002\000\000\000\000\000\000\000\b\000\000\000\000\000\000\000\240\064\203\230\377\177\000\000\372\316B\000\000\000\000\000\003\000\000\000\000\000\000\000\240\064\203\230\377\177\000\000\220\064\203\230\377\177\000\000\372\235O\000\000\000\000\000\003\000\000\000\000\000\000\000K\303X\000\000\000\000" serv = "0\000\000\000\000\000\000\000\000K~\000\000\000\000" rc = salen = ---Type to continue, or q to quit--- #17 0x0058caf0 in xmalloc_sockaddr2hostonly_noport (sa=) at libbb/xconnect.c:476 No locals. #18 0x0050eb64 in print_host (hostname=, header=header@entry=0x5c187f "Server:") at networking/nslookup.c:92 dotted = 0x11be080 "8.8.8.8" revhost = cur = 0x11bdc20 cnt = 0 result = 0x11bdc20 rc = 0 hint = {ai_flags = 0, ai_family = 0, ai_socktype = 1, ai_protocol = 0, ai_addrlen = 0, ai_addr = 0x0, ai_canonname = 0x0, ai_next = 0x0} #19 0x0050ec15 in server_print () at networking/nslookup.c:129 server = sa = #20 nslookup_main (argc=, argv=0x7fff988337a0) at networking/nslookup.c:189 No locals. #21 0x004f890e in run_applet_no_and_exit (applet_no=, argv=argv@entry=0x7fff988337a0) at libbb/appletlib.c:759 argc = #22 0x004f8aa8 in run_applet_and_exit (name=0x7fff988344df "nslookup", ---Type to continue, or q to quit--- argv=argv@entry=0x7fff988337a0) at libbb/appletlib.c:766 applet = #23 0x004f8d19 in busybox_main (argv=0x7fff988337a0) at libbb/appletlib.c:728 No locals. #24 run_applet_and_exit (name=, argv=argv@entry=0x7fff98833798) at libbb/appletlib.c:768 applet = #25 0x004f8ede in main (argc=, argv=0x7fff98833798) at libbb/appletlib.c:823 No locals. (gdb) I think this may map to https://errors.ubuntu.com/problem/c7906cb4fb8d9ab7fa9b995d00b3565b2eddccd4 on the error tracker, which interestingly enough is reported only on 17.04 (zesty). The stack trace points into the NSS modules used behind gethostbyaddr_r(). I'm unclear why the nslookup tool would be using NSS, but maybe we can understand the bug better by looking at this. Can you attach the /etc/nsswitch.conf file from the affected system? Can you also confirm the version of the libc6 package you have installed when this happens? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1723956 Title: busybox-static: several network applets segfaulting Status in busybox package in Ubuntu: Incomplete Bug description: On a fully up-to-date Ubuntu 17.04, running most applets from busybox- static that are network-related lead to a segfault. Example: $ busybox nslookup google.com 8.8.8.8 Server:8.8.8.8 Segmentation fault $ busybox BusyBox v1.22.1 (Ubuntu 1:1.22.0-19ubuntu2) multi-call binary. [...] $ apt-cache policy busybox busybox: Installed: (none) Candidate: 1:1.22.0-19ubuntu2 Version table: 1:1.22.0-19ubuntu2 500 500 http://ftp.fau.de/ubuntu zesty/universe amd64 Packages $ dpkg -S /bin/busybox busybox-static: /bin/busybox $ apt-cache policy busybox
[Touch-packages] [Bug 1309535] Re: Running without pam-kwallet installed issues a warning in auth.log
#19 works for me except there are two extra lines and another identical file to change: #authoptionalpam_kwallet.so #authoptionalpam_kwallet5.so #session optionalpam_kwallet.so auto_start #session optionalpam_kwallet5.so auto_start ...are the four lines to comment out. /etc/pam.d/lightdm /etc/pam.d/lightdm-greeter ...are the two files to modify. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1309535 Title: Running without pam-kwallet installed issues a warning in auth.log Status in lightdm package in Ubuntu: Won't Fix Status in pam package in Ubuntu: Won't Fix Bug description: After upgrading to lightdm 1.10.0-0ubuntu2 I started to see this error in auth.log: Apr 10 14:34:54 simon-laptop lightdm: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory Apr 10 14:34:54 simon-laptop lightdm: PAM adding faulty module: pam_kwallet.so This seems like a regression because with lightdm 1.10.0-0ubuntu1 or before I didn't have this error showing. FYI, I don't have the pam- kwallet package installed. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy lightdm pam-kwallet lightdm: Installed: 1.10.0-0ubuntu3 Candidate: 1.10.0-0ubuntu3 Version table: *** 1.10.0-0ubuntu3 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 18 09:12:37 2014 InstallationDate: Installed on 2014-01-26 (81 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140124) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1309535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738110] [NEW] RSS feed in Rhythmbox pulling images instead of mp3 files
Public bug reported: I reported this bug here: https://bugzilla.gnome.org/show_bug.cgi?id=791154 I was asked to report this bug report on launchpad.net and to state: "I am requesting the commit to be backported." I am not sure how this reporting all works. Thank you for looking into it. Nathaniel --- 1) Running fully updated Ubuntu 17.10 - Rhythmbox 3.4.1-2ubuntu5 2) apt-cache policy pkgname N: Unable to locate package pkgname 3) downloading mp3 file form rss feed 4) it is downloading the png file instead ** Affects: totem-pl-parser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to totem-pl-parser in Ubuntu. https://bugs.launchpad.net/bugs/1738110 Title: RSS feed in Rhythmbox pulling images instead of mp3 files Status in totem-pl-parser package in Ubuntu: New Bug description: I reported this bug here: https://bugzilla.gnome.org/show_bug.cgi?id=791154 I was asked to report this bug report on launchpad.net and to state: "I am requesting the commit to be backported." I am not sure how this reporting all works. Thank you for looking into it. Nathaniel --- 1) Running fully updated Ubuntu 17.10 - Rhythmbox 3.4.1-2ubuntu5 2) apt-cache policy pkgname N: Unable to locate package pkgname 3) downloading mp3 file form rss feed 4) it is downloading the png file instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem-pl-parser/+bug/1738110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409166] Re: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration
Have a three screen setup now: 1) Laptop screen primary gets User ID password on boot. After boot chrome windows which were on screen 2 are restored here along with this screens chrome windows. 2) HDMI nVvidia hardwired TV, steals focus on resume to password. 3) Thunderbolt 3 USB-C HDMI TV which occasionally doesn't get signal when rebooted and has to be powered off and on. Other notes when booting all three monitors turn on and off a few times. There is one patch applied during boot to enable nVidia HDMI sound: setpci -vD -s 01:00.0 0x488.l=0x:0x sh -c 'echo 1 > /sys/bus/pci/devices/:01:00.0/remove' sh -c 'echo 1 > /sys/bus/pci/devices/:00:01.0/rescan' systemctl restart lightdm.service Ubuntu 16.04.3, Kernel 4.14.4, Skylake 6700HQ, nVidia GTX 970M, Samsung Pro 960 NVMe SSD. -- 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/1409166 Title: Popup dialog "could not set the configuration for CRTC 65" steals keyboard, hinders login in 3-monitor configuration Status in xorg package in Ubuntu: Triaged Bug description: Every time I boot, while I'm trying to enter my password in the initial login screen (from Unity?), a dialog box pops up saying "Could not switch the monitor configuration could not set the configuration for CRTC 65". The dialog box also steals the keyboard focus, which is very confusing if for some reason you're entering the password on an external display while the normally unused laptop display is not visible. For example, three times in a row this morning I rebooted and tried unsuccessfully to log in. Since the dialog box is only displayed on the laptop display, which I never use when external monitors are available, I had no idea why my keyboard seemed broken. Background: My Lenovo Thinkpad X230 Tablet laptop has a VGA and a DVI connector. I have the VGA hooked up to a Viewsonic 1920x1080 monitor, positioned above the laptop display. I have a Samsung monitor to the right of the Viewsonic. Since my laptop seems to only support two displays (which also seems true in Windows), I normally disable and totally ignore my laptop display, and may have papers propped up in front of it etc. Note that when I initially configured the third display I saw the following highly confusing behavior. From Settings I tried to add a Samsung monitor to the right of the Viewsonic, via a DVI-to-HDMI passive connector, and got this dialog box when I hit "Apply": The selected configuration for displays could not be applied could not set the configuration for CRTC 65 I clicked "OK" and got another dialog box: Failed to apply configuration: %s Can't add monitor: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._gnome_2drr_2derror_2dquark.Code2: could not set the configuration for CRTC 65 It works if I disable my laptop monitor, so it looks like the problem is with adding a third display. I would think it would be a pretty common use case to use two nice external displays and disable the laptop display. Even when the hardware can't handle a third display, the error messages should not be so confusing, and the login process shouldn't result in the keyboard being mysteriously stolen by a dialog box on a display which may never be visible. This is on Trusty 64-bit, up-to-date with upgrades. This bug seems similar to bug 1304627, but it seemed cleanest to get all the right information reported via ubuntu-bug. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 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: Fri Jan 9 15:35:57 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:2203] InstallationDate: Installed on 2015-01-01 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 343522U ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-43-generic root=UUID=6dce26c4-3d5b-4980-880e-06f249f77c57 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2013 dmi.bios.vendor: LENOVO d
[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
If I add "root" as member of the "lpadmin" group in /etc/group, all is working perfecty: Kill button of the job list entry, "Clear all" at the top of job list, and "Restart" in the print queue entry. OdyX, WDYT? Should we add root as member of the lpadmin group? shemgp, your latest patch is still not working for me, see comment #42. Unsubscribing ubuntu-sponsors, as cups-pk-helper patch does not solve the problem. ** Changed in: cups-pk-helper (Ubuntu) Status: Triaged => Incomplete ** Changed in: cups (Ubuntu) Status: Invalid => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Incomplete Status in cups-pk-helper package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
"Restart" button for the queue returns to work when I re-install the original cups-pk-helper without the patch. -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Incomplete Status in cups-pk-helper package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
I have applied the patch of comment #36 to cups-pk-helper now (nothing uploaded, only local testing) and for me it does not work. On the command line I have disabled a print queue and send a job to it, by disabling the job stays in the queue so that one has time to do the actual test. Now I have started gnome-control-center and opened the section "Devices"/"Printers". The queue I have stopped is shown as such and it is also shown that it has one job. I clicked the "1 job" button to open the job viewer. There are pause and kill buttons in the job line and a "Clear all" button at the top. Neither with the kill button nor with the "Clear all" button I can remove the jobe. I also cannot re-enable the queue via the "Restart" in the print queue list. -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Incomplete Status in cups-pk-helper package in Ubuntu: Incomplete Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- Mailing list: https://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 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
On Wed, Dec 13, 2017 at 6:00 PM Robie Basak <1732...@bugs.launchpad.net> wrote: > On Wed, Dec 13, 2017 at 10:34:25PM -, Andres Rodriguez wrote: > > FWIW, this is currently affecting customers who are running MAAS and > > require livepatch. > > It's been affecting users since January, no? This hasn’t been affecting users since January. This bug has been reported in November and only affects users running MAAS who someway or another installed systemd. In this particular case, on November a customer installed live patch on a system, hence the issue. Why the sudden urgency? > What difference will a week or two make? > > > Comments #11 and #12 above confirm that the patch is enough for the MAAS > > needs. Whichever way MAAS decides to check for systemd is up to MAAS and > > that is not a reason to block an SRU provided that it does not impact > > any other piece of software. That said, this patch does not does not > > introduce a regression to MAAS nor any other software. > > I think that's quite a brave claim to make. I'm sure "does not > introduce a regression" was a claim that might have been made in the > systemd SRU that regressed this too, and yet here we are. There is no supported way on Ubuntu Trusty (nor package in the archive) that will create a symlink of /sbin/init to systemd. This only happens By the systemd-sysv package which is only available in Xenial. So, since systemd is not supported as a init system in trusty and this would only happen if a user manually does this, then this doesn’t introduce any regressions in MAAS. So it is not a brave claim to make, it is a claim based on facts. > > > > Lastly, this patch is *only* for 1.9 as this code path is only available > > in Trusty, so upgrades to later Ubuntu releases will yield on using a > > newer version of MAAS that doesn't rely on this code path. > > If we did decide to SRU an emergency fix as a stopgap for MAAS' use > case, and it's for Trusty only, then why have a test at all? Can we just > return 'upstart' without a test? > > To be clear, I'm not demanding or even requesting anything specific > right now. I don't feel that a case for urgency has yet been made, given > the currently known regression timeline. In the meantime I think it's > worth understanding how we want to fix this properly, because requiring > multiple SRUs while we swing back and forth is bad for everyone, and > equally I don't want to see us locked into a suboptimal solution. > > If a case is accepted on the basis of urgency, or another SRU team > member disagrees with my assessment, I wouldn't want to block that. Feel > free to land what you think is appropriate. > > -- > You received this bug notification because you are a bug assignee. > https://bugs.launchpad.net/bugs/1732703 > > Title: > MAAS does not detect properly if Ubuntu is using upstart/systemd > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions > > Launchpad-Notification-Type: bug > Launchpad-Bug: product=maas; status=Won't Fix; importance=Undecided; > assignee=None; > Launchpad-Bug: product=maas; productseries=1.9; milestone=1.9.6; status=In > Progress; importance=Critical; assignee=andres...@ubuntu-pe.org; > Launchpad-Bug: distribution=ubuntu; sourcepackage=maas; component=main; > status=New; importance=Critical; assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=snapd; component=main; > status=Won't Fix; importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; sourcepackage=systemd; component=main; > status=New; importance=Undecided; assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=trusty; > sourcepackage=maas; component=main; status=New; importance=Undecided; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=trusty; > sourcepackage=snapd; component=universe; status=New; importance=Undecided; > assignee=None; > Launchpad-Bug: distribution=ubuntu; distroseries=trusty; > sourcepackage=systemd; component=main; status=New; importance=Critical; > assignee=None; > Launchpad-Bug-Tags: regression-update sts > Launchpad-Bug-Information-Type: Public > Launchpad-Bug-Private: no > Launchpad-Bug-Security-Vulnerability: no > Launchpad-Bug-Commenters: afreiberger andreserl racb vorlon vtapia xnox > Launchpad-Bug-Reporter: Victor Tapia (vtapia) > Launchpad-Bug-Modifier: Robie Basak (racb) > Launchpad-Message-Rationale: Assignee > Launchpad-Message-For: andreserl > -- Andres Rodriguez (RoAkSoAx) Ubuntu Server Developer MSc. Telecom & Networking Systems Engineer -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: Won't Fix Status in snapd package in Ubuntu: Won't Fix Status i
[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
Added cups-pk-helper task and re-subscribed ubuntu-sponsors. ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Invalid Status in cups-pk-helper package in Ubuntu: Triaged Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
So then why does no one apply the patch of comment #36? OdyX (printing maintainer for Debian) and me, we are OK with this solution. ** Changed in: cups (Ubuntu) Status: Confirmed => Invalid ** Also affects: cups-pk-helper (Ubuntu) Importance: Undecided Status: New ** Changed in: cups-pk-helper (Ubuntu) Status: New => Triaged ** Changed in: cups-pk-helper (Ubuntu) Importance: Undecided => High -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Invalid Status in cups-pk-helper package in Ubuntu: Triaged Status in gnome-control-center package in Ubuntu: Invalid Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
Had same problems on my Dell XPS 15 9560. The last solution of Paul did it for me, running ``hdajackretask``. But in my case, I had to uncheck the override boxes. I remember I had to check them in the past, so I presume a recent update (kernel? I have 17.04 with 4.10.0-42-generic) changed things Is it back to normal now? Dont know... Anyway, all seems perfect now :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
** Changed in: maas (Ubuntu) Status: New => Won't Fix ** Changed in: maas (Ubuntu Trusty) Status: New => Triaged ** Changed in: maas (Ubuntu Trusty) Importance: Undecided => Critical -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: Won't Fix Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: Triaged Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
This bug was fixed in the package apport - 2.20.8-0ubuntu4 --- apport (2.20.8-0ubuntu4) bionic; urgency=medium * data/apport: add a second os.path.exists check to ensure we do not receive a Traceback in is_container_id(). (LP: #1733366) -- Brian Murray Wed, 13 Dec 2017 10:30:23 -0800 ** Changed in: apport (Ubuntu Bionic) Status: In Progress => Fix Released -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: Fix Released Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: Fix Released Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
Welcome 2 Linux. Enduser is worthless! -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
I would accept a version of this SRU that hard-codes the choice of upstart as the init system on 14.04, because that is the only init system supported in that version of Ubuntu. We can discuss further whether the deput-init systemd package in trusty needs further changes to not fall afoul of common init system detection techniques, but I don't think that should block fixing MAAS in this scenario. Currently, all the proposed methods of detecting the init system have corner cases where they break. Most of these corner cases are negligible for maas, however. The one option I know that doesn't have corner cases is to invoke '/sbin/initctl version' and check its return code. But I leave it up to the MAAS team whether to implement this vs. a lighter-weight check. -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
Ok, this actually looks better. It seems that the overlay was at fault here indeed. Should we proceed instantly with SRUing the zesty version (it can take time for it to get processed in the SRU queue), or do we want to release LP: #1693756 first? Anyway, looking into if we can just proceed with the backporting tomorrow in the morning. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: In Progress Status in libmbim source package in Xenial: New Status in libqmi source package in Xenial: New Status in modemmanager source package in Xenial: New Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054 libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698593] Re: [Blade, Realtek ALC298, Black Mic, Left] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1698593 Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm trying to get the mic from the combo jack on my Razer Blade working. Headphones are functioning perfectly, but the mic seems to be picking up on random data, unrelated to sound output or my surroundings. I know the jack is working as I dual-boot Windows, and it works great there. I've added the `options snd-hda-intel model=laptop-dmic` line as recommended in some other threads, and tried setting pin 0x18 to mic using hdajackretask, but it hasn't fixed it or made any difference. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: octy 1971 F...m pulseaudio /dev/snd/pcmC0D0p: octy 1971 F...m pulseaudio /dev/snd/controlC0: octy 1971 F pulseaudio CurrentDesktop: X-Cinnamon Date: Sat Jun 17 15:21:41 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-04-06 (72 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: octy 1971 F...m pulseaudio /dev/snd/pcmC0D0p: octy 1971 F...m pulseaudio /dev/snd/controlC0: octy 1971 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [Blade, Realtek ALC298, Black Mic, Left] No sound at all UpgradeStatus: Upgraded to zesty on 2017-04-15 (63 days ago) dmi.bios.date: 01/10/2017 dmi.bios.vendor: Razer dmi.bios.version: 1.00 dmi.board.name: Razer dmi.board.vendor: Razer dmi.chassis.type: 9 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr1.00:bd01/10/2017:svnRazer:pnBlade:pvr6.06:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr: dmi.product.name: Blade dmi.product.version: 6.06 dmi.sys.vendor: Razer mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-06-17T15:06:35.753276 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1698593/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
To clarify, I think these patches may reduce the number of reports in the error tracker; but to eliminate the reports, the exception needs to be handled. Thanks -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: In Progress Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://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 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
On Wed, Dec 13, 2017 at 10:34:25PM -, Andres Rodriguez wrote: > FWIW, this is currently affecting customers who are running MAAS and > require livepatch. It's been affecting users since January, no? Why the sudden urgency? What difference will a week or two make? > Comments #11 and #12 above confirm that the patch is enough for the MAAS > needs. Whichever way MAAS decides to check for systemd is up to MAAS and > that is not a reason to block an SRU provided that it does not impact > any other piece of software. That said, this patch does not does not > introduce a regression to MAAS nor any other software. I think that's quite a brave claim to make. I'm sure "does not introduce a regression" was a claim that might have been made in the systemd SRU that regressed this too, and yet here we are. > Lastly, this patch is *only* for 1.9 as this code path is only available > in Trusty, so upgrades to later Ubuntu releases will yield on using a > newer version of MAAS that doesn't rely on this code path. If we did decide to SRU an emergency fix as a stopgap for MAAS' use case, and it's for Trusty only, then why have a test at all? Can we just return 'upstart' without a test? To be clear, I'm not demanding or even requesting anything specific right now. I don't feel that a case for urgency has yet been made, given the currently known regression timeline. In the meantime I think it's worth understanding how we want to fix this properly, because requiring multiple SRUs while we swing back and forth is bad for everyone, and equally I don't want to see us locked into a suboptimal solution. If a case is accepted on the basis of urgency, or another SRU team member disagrees with my assessment, I wouldn't want to block that. Feel free to land what you think is appropriate. -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1045790] Re: Rendering error on OCAL website
** Changed in: librsvg Status: Confirmed => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1045790 Title: Rendering error on OCAL website Status in librsvg: Expired Status in openclipart: Invalid Status in librsvg package in Ubuntu: New Bug description: I uploaded an SVG that is a map of the UK and Ireland http://openclipart.org/detail/171939/uk-and-ireland-by- hellocatfood-171939 It was generated in Inkscape and then cleaned up using SVG Cleaner In Inkscape, GIMP and the Firefox SVG preview it displays correctly, but on OCAL it looks very weird! Steps to reproduce: Download the original SVG https://bugs.launchpad.net/librsvg/+bug/1045790/+attachment/3302221/+files/uk-ireland-vector_original.svg Download and install SVG Cleaner https://github.com/RazrFalcon/SVGCleaner/ Run SVG Cleaner on the folder containing the SVG Look at the thumbnail preview on programs that use librsvg (Open Clip Art Library, Nautilus) To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1045790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
FWIW, this is currently affecting customers who are running MAAS and require livepatch. Comments #11 and #12 above confirm that the patch is enough for the MAAS needs. Whichever way MAAS decides to check for systemd is up to MAAS and that is not a reason to block an SRU provided that it does not impact any other piece of software. That said, this patch does not does not introduce a regression to MAAS nor any other software. Lastly, this patch is *only* for 1.9 as this code path is only available in Trusty, so upgrades to later Ubuntu releases will yield on using a newer version of MAAS that doesn't rely on this code path. That said, there's no supported way in Ubuntu that will symlink /sbin/init -> /lib/systemd/systemd , provided that systemd-sysv is *only* available in Xenial, and again, upgrades to Xenial will result in MAAS not using this codepath at all. -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709135] Re: add bond primary parameter
Verification-done-artful with 0.32~17.10.1: Bonding in active-backup mode with primary: set to a suitable device shows the bond with that device set as primary slave. -- 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/1709135 Title: add bond primary parameter Status in nplan package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Fix Released Status in nplan source package in Xenial: Fix Committed Status in systemd source package in Xenial: Fix Released Status in nplan source package in Zesty: Fix Committed Status in systemd source package in Zesty: Fix Released Status in nplan source package in Artful: Fix Released Status in systemd source package in Artful: Fix Released Bug description: [Impact] Some complex bond configurations require setting a "primary" interface for the bond, or setting this greatly improves performance on the network bond. [Test case] See below for a configuration example. 1) Apply configuration on a system with netplan. 2) Run 'netplan apply' 3) Validate that netplan apply does not return with an error 4) Validate that netplan properly sets the "primary_slave" value on the bond. This can be verified by looking at /sys/class/net//bonding/primary_slave. 5) Validate that there are no parsing errors from systemd-networkd in the journalctl [Regression potential] If existing configuration fails to be parsed, or lack of primary interface breaks configuration for existing bonds, this would be a regression caused by this update. --- ifenslave/eni support a bond parameter: bond-primary which accepts an interface name that can be used to tell the kernel bonding driver which interface it should preferred in active-backup (and other modes). This config option is missing in netplan. % cat bond-primary.yaml network: version: 2 ethernets: eth0: match: driver: virtio ens4: match: driver: e1000 bonds: bond0: parameters: mode: active-backup mii-monitor-interval: 100 primary: e1000 dhcp4: true % ./generate -r `pwd`/target Error in network definition /home/rharper/work/git/netplan/target//etc/netplan/bond-primary.yaml line 12 column 8: unknown key primary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1709135/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738085] Re: Bridge gets created while the network interfaces are still being renamed
** Also affects: bridge-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bridge-utils in Ubuntu. https://bugs.launchpad.net/bugs/1738085 Title: Bridge gets created while the network interfaces are still being renamed Status in bridge-utils package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed from eth1 Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed from eth2 Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed from eth3 Dec 13 16:03:38 trout kernel: [ 20.572747] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts t o load br_netfilter if you need this. Dec 13 16:03:38 trout kernel: [ 20.575364] device lan1 entered promiscuous mode Dec 13 16:03:38 trout kernel: [ 20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: link is not ready Dec 13 16:03:38 trout kernel: [ 21.097073] rename7: renamed from lan Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' is taking a long time Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/lan Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/rename7 Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC address for lan: No such file or directory Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan. Dec 13 16:04:59 trout kernel: [ 111.797526] device wlan entered promiscuous mode Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on /run/network/ifstate.lan Dec 13 16:04:59 trout kernel: [ 111.943158] device lan3 entered promiscuous mode Dec 13 16:05:00 trout kernel: [ 112.240052] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.240081] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: link is not ready Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 seconds). Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Dec 13 16:05:01 trout kernel: [ 113.610184] igb :01:00.2 lan2: igb: lan2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX Dec 13 16:05:01 trout kernel: [ 113.610324] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610365] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610486] IPv6: ADDRCONF(NETDEV_CHANGE): lan: link becomes ready And after the boot process completes, the bridge is not configured as requested: # brctl show bridge name bridge id STP enabled interfaces lan 8000.7085c2026d54 no lan2 lan3 wlan rename7 8000.90e2baaee821 no lan1 Note that while the "rename7" name of the bridge seems to be constant, the inter
[Touch-packages] [Bug 1738085] [NEW] Bridge gets created while the network interfaces are still being renamed
Public bug reported: I have a problem with bridge configuration for the interfaces on my system that I also happen to rename explicitly. Specifically, I have following network configuration: # WAN interface auto wan iface wan inet dhcp # LAN interfaces iface wlan inet manual iface lan1 inet manual iface lan2 inet manual iface lan3 inet manual # LAN bridge auto lan iface lan inet static address 10.0.0.1 netmask 255.255.255.0 bridge_ports wlan lan1 lan2 lan3 I use systemd .link files for renaming each of the 5 bridged interfaces, e.g. cat /etc/systemd/network/10-lan1.link [Match] MACAddress=90:e2:ba:ae:e8:21 [Link] Name=lan1 (BTW, I previously used udev rules to handle the renaming, before I migrated to systemd .link files hoping for improvement) Upon system boot, I see following messages: Dec 13 16:03:38 trout kernel: [2.61] r8169 :03:00.0 lan3: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.729493] igb :01:00.0 wlan: renamed from eth1 Dec 13 16:03:38 trout kernel: [2.867121] igb :01:00.2 lan2: renamed from eth2 Dec 13 16:03:38 trout kernel: [2.879221] igb :01:00.1 lan1: renamed from eth0 Dec 13 16:03:38 trout kernel: [2.899203] igb :01:00.3 wan: renamed from eth3 Dec 13 16:03:38 trout kernel: [ 20.572747] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts t o load br_netfilter if you need this. Dec 13 16:03:38 trout kernel: [ 20.575364] device lan1 entered promiscuous mode Dec 13 16:03:38 trout kernel: [ 20.705483] IPv6: ADDRCONF(NETDEV_UP): lan1: link is not ready Dec 13 16:03:38 trout kernel: [ 21.097073] rename7: renamed from lan Dec 13 16:04:29 trout systemd-udevd[466]: seq 2799 '/devices/virtual/net/lan' is taking a long time Dec 13 16:04:59 trout systemd-udevd[540]: error changing net interface name 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd-udevd[540]: could not rename interface '7' from 'lan' to 'lan1': File exists Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/lan Dec 13 16:04:59 trout systemd[1]: sys-subsystem-net-devices-lan1.device: Dev sys-subsystem-net-devices-lan1.device appeared twice with different sysfs paths /sys/devices/pci:00/:00:02.1/:01:00.1/net/lan1 and /sys/devices/virtual/net/rename7 Dec 13 16:04:59 trout systemd-udevd[543]: Could not generate persistent MAC address for lan: No such file or directory Dec 13 16:04:59 trout systemd[1]: Started ifup for lan. Dec 13 16:04:59 trout systemd[1]: Found device /sys/subsystem/net/devices/lan. Dec 13 16:04:59 trout kernel: [ 111.797526] device wlan entered promiscuous mode Dec 13 16:04:59 trout ifup[1753]: /sbin/ifup: waiting for lock on /run/network/ifstate.lan Dec 13 16:04:59 trout kernel: [ 111.943158] device lan3 entered promiscuous mode Dec 13 16:05:00 trout kernel: [ 112.240052] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.240081] r8169 :03:00.0 lan3: link down Dec 13 16:05:00 trout kernel: [ 112.242397] IPv6: ADDRCONF(NETDEV_UP): lan: link is not ready Dec 13 16:05:00 trout sh[1689]: Waiting for lan to get ready (MAXWAIT is 32 seconds). Dec 13 16:05:00 trout CRON[1841]: (root) CMD ([ -x /usr/sbin/dma ] && /usr/sbin/dma -q1) Dec 13 16:05:01 trout kernel: [ 113.610184] igb :01:00.2 lan2: igb: lan2 NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX Dec 13 16:05:01 trout kernel: [ 113.610324] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610365] lan: port 2(lan2) entered forwarding state Dec 13 16:05:01 trout kernel: [ 113.610486] IPv6: ADDRCONF(NETDEV_CHANGE): lan: link becomes ready And after the boot process completes, the bridge is not configured as requested: # brctl show bridge name bridge id STP enabled interfaces lan 8000.7085c2026d54 no lan2 lan3 wlan rename7 8000.90e2baaee821 no lan1 Note that while the "rename7" name of the bridge seems to be constant, the interface bridged is not. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu21 ProcVersionSignature: Ubuntu 4.4.0-103.126-generic 4.4.98 Uname: Linux 4.4.0-103-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 Date: Wed Dec 13 16:11:11 2017 InstallationDate: Installed on 2016-07-28 (503 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 ProcKernelC
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
Note that these fixes are susceptible to a race condition; better would handle the exception from Python. Probably returning 'false' is the right option in that case. (Assuming that's the case that then does less processing.) Thanks -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: In Progress Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
** Tags added: patch -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: In Progress Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738077] [NEW] login screen doesn't appear on primary monitor
Public bug reported: I have 4 monitors connect. Three are turned of physically and under settings/devices/display. One monitor is turned on physically and under settings/devices/display. That one monitor is my primary. When Ubuntu boots, the login screen appears on one of the other monitors and not on the primary. Once I log in, everything works fine and everything displays fine on the single primary monitor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 14:25:24 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:366a] InstallationDate: Installed on 2017-12-11 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 8300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=3e947631-03e9-4e93-ac6e-d68ee7a1efe3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.name: 0Y2MRG dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA06:bd10/17/2011:svnDellInc.:pnXPS8300:pvr:rvnDellInc.:rn0Y2MRG:rvrA00:cvnDellInc.:ct3:cvr: dmi.product.name: XPS 8300 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1738077 Title: login screen doesn't appear on primary monitor Status in xorg package in Ubuntu: New Bug description: I have 4 monitors connect. Three are turned of physically and under settings/devices/display. One monitor is turned on physically and under settings/devices/display. That one monitor is my primary. When Ubuntu boots, the login screen appears on one of the other monitors and not on the primary. Once I log in, everything works fine and everything displays fine on the single primary monitor. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 14:25:24 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-16-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM204 [GeForce GTX 970] [10de:13c2] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd GM204 [GeForce GTX 970] [1458:366a] InstallationDate: Installed on 2017-12-11 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Dell Inc. XPS 8300 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=3e947631-03e9-4e93-ac6e-d68ee7a1efe3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version:
[Touch-packages] [Bug 575984] Re: SVG's render incomplete/incorrectly
** Changed in: librsvg Status: Confirmed => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/575984 Title: SVG's render incomplete/incorrectly Status in librsvg: Expired Status in librsvg package in Ubuntu: Triaged Bug description: Some SVGs don't render entirely. Here is one that was created in Inkscape that does not render properly. See the difference in Inkscape and pitivi/eye of gnome To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/575984/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
xenial fix ** Patch added: "bug-1733366-xenial.debdiff" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5022278/+files/bug-1733366-xenial.debdiff -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: In Progress Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
zesty fix ** Patch added: "bug-1733366-zesty.debdiff" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5022277/+files/bug-1733366-zesty.debdiff -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: In Progress Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
artful fix ** Changed in: apport (Ubuntu Bionic) Status: Triaged => In Progress ** Changed in: apport (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: apport (Ubuntu Artful) Assignee: (unassigned) => Canonical Security Team (canonical-security) ** Patch added: "bug-1733366-artful.debdiff" https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1733366/+attachment/5022276/+files/bug-1733366-artful.debdiff -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: In Progress Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
The updates for this fix will need to go through security since many people are getting the package from there. ** Also affects: apport (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apport (Ubuntu Zesty) Importance: Undecided Status: New -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: In Progress Status in apport source package in Xenial: New Status in apport source package in Zesty: New Status in apport source package in Artful: New Status in apport source package in Bionic: In Progress Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 236527] Re: Waved text in svg not shown in nautilus, gThumb and F-Spot
** Changed in: librsvg Status: Confirmed => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/236527 Title: Waved text in svg not shown in nautilus, gThumb and F-Spot Status in librsvg: Expired Status in librsvg package in Ubuntu: Confirmed Bug description: When you create a waved (a text put along a path) the text is only in Inkscape and Firefox 3 b5 (other versions unknown) showed. In gThumb, Nautilus & F-Spot you can see only the path (if it's visible). (@ Ubuntu 8.04) To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/236527/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738058] [NEW] vlan usage requires an intermediate step
Public bug reported: If I try to apply vlans directly: network: version: 2 renderer: networkd ethernets: eth0: {} vlans: vlan1: id: 1 link: eth0 addresses: [ 192.168.0.10/23 ] vlan10: id: 10 link: eth0 addresses: [ 10.0.0.5/24 ] The vlan devices never come up, they are left in degraded state by networkd. If I define an address for eth0, then eth0 and all of the vlans will have the same address. Needless to say, this doesn't work. If I use an intermediary device instead, such as a bond: network: version: 2 renderer: networkd ethernets: eth0: {} bonds: vmaster: interfaces: [ eth0 ] vlans: vlan1: id: 1 link: vmaster addresses: [ 192.168.0.10/23 ] vlan10: id: 10 link: vmaster addresses: [ 10.0.0.5/24 ] Then the vlans are correctly applied and brought up by systemd. I think this is either a systemd bug or a netplan bug; it's possible we don't generate the config quite in the way that systemd expects it (even though it looks straightforward enough). ** Affects: nplan (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also 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/1738058 Title: vlan usage requires an intermediate step Status in nplan package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: If I try to apply vlans directly: network: version: 2 renderer: networkd ethernets: eth0: {} vlans: vlan1: id: 1 link: eth0 addresses: [ 192.168.0.10/23 ] vlan10: id: 10 link: eth0 addresses: [ 10.0.0.5/24 ] The vlan devices never come up, they are left in degraded state by networkd. If I define an address for eth0, then eth0 and all of the vlans will have the same address. Needless to say, this doesn't work. If I use an intermediary device instead, such as a bond: network: version: 2 renderer: networkd ethernets: eth0: {} bonds: vmaster: interfaces: [ eth0 ] vlans: vlan1: id: 1 link: vmaster addresses: [ 192.168.0.10/23 ] vlan10: id: 10 link: vmaster addresses: [ 10.0.0.5/24 ] Then the vlans are correctly applied and brought up by systemd. I think this is either a systemd bug or a netplan bug; it's possible we don't generate the config quite in the way that systemd expects it (even though it looks straightforward enough). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1738058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736770] Re: debian-installer/main-menu changes priority
I take this back, it is still an issue with the amd64 ISO: https://paste.ubuntu.com/26178135/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1736770 Title: debian-installer/main-menu changes priority Status in debconf package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: During a test install of Bionic it appears that the debian-installer /main-menu option changes priority from medium to critical part way through the test: Dec 6 04:18:55 debconf: --> INPUT medium debian-installer/main-menu Dec 6 04:18:55 debconf: <-- 30 question skipped Dec 6 04:18:55 debconf: --> GO ... Dec 6 04:19:54 debconf: --> METAGET debian-installer/live-installer/title Description Dec 6 04:19:54 debconf: <-- 0 Install the system Dec 6 04:19:54 debconf: --> SET debian-installer/main-menu Install the system Dec 6 04:19:54 debconf: <-- 0 value set Dec 6 04:19:54 debconf: --> INPUT critical debian-installer/main-menu Dec 6 04:19:54 debconf: <-- 0 question will be asked Dec 6 04:19:54 debconf: --> GO Working test on Dec 1: https://paste.ubuntu.com/26126878/ Failing test on Dec 6: https://paste.ubuntu.com/26126090/ Steps to reproduce: 1. Get latest ISO from: http://cdimage.ubuntu.com/ubuntu-server/daily/pending/ 2. Pull out the kernel and initrd $ mkdir iso $ bsdtar xfp bionic-server-amd64.iso -C iso $ cp iso/install/vmlinuz . $ cp iso/install/initrd.gz . 3. Create QEMU disk $ qemu-img create -f qcow2 vdisk.img 4G 4. Launch ISO via QEMU $ qemu-system-x86_64 -enable-kvm -cpu host -m 1024 -boot d \ -initrd initrd.gz -kernel vmlinuz -display none -nographic \ -hda vdisk.img -cdrom bionic-server-amd64.iso \ -append 'console=ttyS0 locale=en_US.UTF-8 priority=critical' 5. Proceed with the install by 1) enter user info and 2) select disk 6. Eventually the "Ubuntu installer main menu" will appear. Even if you click on "Install the system" the installation step will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1736770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
** Branch linked: lp:~ubuntu-core-dev/ubuntu/bionic/apport/ubuntu -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: Triaged Status in apport source package in Bionic: Triaged Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701222] Re: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services
** Changed in: linux (Ubuntu Xenial) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Zesty) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu Artful) Status: In Progress => Incomplete ** Changed in: linux (Ubuntu) Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701222 Title: [Hyper-V] LIS daemons fail to start after disable/re-enable VM integration services Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux source package in Zesty: Incomplete Status in linux source package in Artful: Incomplete Bug description: Issue description: Hyper-V daemons fail to start after disable/re- enable VM integration services. Platform: host independent Affected daemons - KVP, FCOPY and VSS. Distribution name and release: Ubuntu 16.04, Ubuntu 17.04 Kernel version: 4.11.0-rc7-next-20170421 (for Ubuntu 16.04), 4.10.0-19-generic (for Ubuntu 17.04) Repro rate: 100% Steps to reproduce: 1.Start VM with Guest Services enabled (FCopy daemon starts automatically) 2.Go to File > Settings > Integration Services, uncheck Guest Services and apply (FCopy daemon will stop at this point) 3.Re-enable Guest Services from VM Settings (Fcopy daemon is not running). This is the issue. systemd monitors for the service and if we have the hook for the Guest Service, it tries to start the daemon again. systemd attempt to start any of the LIS daemons will fail, but manually executing the daemon binary, it will start the daemon. Additional Info: - the steps above can be repro'd with KVP / Data Exchange integration service as well. - Manually starting hv_fcopy_daemon works fine. - other distros (RHEL) does not have this behavior, the LIS daemons are started automatically by systemd once we re-enable the integration service. On the upstream kernel and the upstream hv daemons, these messages are recorded in syslog, once we re-enable the Guest service: HV_FCOPY: pread failed: Bad file descriptor systemd[1]: hv-fcopy-daemon.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: hv-fcopy-daemon.service: Unit entered failed state. systemd[1]: hv-fcopy-daemon.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1729634] Re: Linker warnings for apparmor.o
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1729634 Title: Linker warnings for apparmor.o Status in apparmor package in Ubuntu: Confirmed Bug description: Building the Ubuntu kernel at version 4.4.0-97.120 or 4.4.0-98.121 gives warnings when linking apparmor.o such as: LD security/apparmor/apparmor.o WARNING: security/apparmor/apparmor.o(.text+0x1087b): Section mismatch in reference from the function param_get_mode() to the variable .init.data:apparmor_initialized (next build fault) The function param_get_mode() references the variable __initdata apparmor_initialized. This is often because param_get_mode lacks a __initdata annotation or the annotation of apparmor_initialized is wrong. I believe this is because the __initdata annotation was removed from security/apparmor/lsm.c but not from security/apparmor/include/lib.h The following patch cleans the compilation warnings, but may not be the correct fix: --- security/apparmor/include/lib.h.orig2017-11-02 14:43:59.903230945 + +++ security/apparmor/include/lib.h 2017-11-02 14:44:57.992635353 + @@ -56,7 +56,7 @@ } while (0) /* Flag indicating whether initialization completed */ -extern int apparmor_initialized __initdata; +extern int apparmor_initialized; /* fn's in lib */ char *aa_split_fqname(char *args, char **ns_name); To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1729634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738051] Re: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
** Tags removed: need-duplicate-check -- 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/1738051 Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: New Bug description: error installing updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 640:0:117:360050:2017-12-13 12:08:24.439189427 -0300:2017-12-13 12:08:24.443189481 -0300:/var/crash/_usr_lib_xorg_Xorg.0.crash 600:0:117:200154:2017-12-13 14:18:13.689794540 -0300:2017-12-13 14:18:14.689794540 -0300:/var/crash/apport.0.crash Date: Wed Dec 13 14:18:14 2017 DuplicateSignature: package:apport:2.20.1-0ubuntu2.14 Installing new version of config file /etc/init/apport.conf ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-11-03 (40 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
I've deferred my decision as to whether to accept what's currently in the queue on this thread: https://lists.ubuntu.com/archives/ubuntu- devel/2017-December/040093.html -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738051] [NEW] package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
Public bug reported: error installing updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 640:0:117:360050:2017-12-13 12:08:24.439189427 -0300:2017-12-13 12:08:24.443189481 -0300:/var/crash/_usr_lib_xorg_Xorg.0.crash 600:0:117:200154:2017-12-13 14:18:13.689794540 -0300:2017-12-13 14:18:14.689794540 -0300:/var/crash/apport.0.crash Date: Wed Dec 13 14:18:14 2017 DuplicateSignature: package:apport:2.20.1-0ubuntu2.14 Installing new version of config file /etc/init/apport.conf ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-11-03 (40 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1738051 Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: New Bug description: error installing updates ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 640:0:117:360050:2017-12-13 12:08:24.439189427 -0300:2017-12-13 12:08:24.443189481 -0300:/var/crash/_usr_lib_xorg_Xorg.0.crash 600:0:117:200154:2017-12-13 14:18:13.689794540 -0300:2017-12-13 14:18:14.689794540 -0300:/var/crash/apport.0.crash Date: Wed Dec 13 14:18:14 2017 DuplicateSignature: package:apport:2.20.1-0ubuntu2.14 Installing new version of config file /etc/init/apport.conf ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2017-11-03 (40 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1733366] Re: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid'
There is an errors bucket for this: https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2 -- 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/1733366 Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' Status in Apport: New Status in apport package in Ubuntu: Triaged Status in apport source package in Bionic: Triaged Bug description: It appears that after login this was the first action performed by the system which resulted in the generation of the crash report. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: apport 2.20.8-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu1 Architecture: amd64 CrashReports: 640:0:119:17503:2017-11-20 01:59:45.143901348 +0530:2017-11-20 01:59:46.143901348 +0530:/var/crash/_usr_share_apport_apport.0.crash Date: Mon Nov 20 01:59:46 2017 ExecutablePath: /usr/share/apport/apport InstallationDate: Installed on 2017-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.0 2017.11.11 amd64 "Unity 7 Desktop Experience Bionic Beaver" InterpreterPath: /usr/bin/python3.6 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/share/apport/apport 11102 11 0 1 11102 ProcEnviron: Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonArgs: ['/usr/share/apport/apport', '11102', '11', '0', '1', '11102'] PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged SourcePackage: apport Title: apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1733366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737867] Re: apport crashes with FileNotFoundError in is_same_ns
*** This bug is a duplicate of bug 1733366 *** https://bugs.launchpad.net/bugs/1733366 Here's the full traceback: Traceback (most recent call last): File "/usr/share/apport/apport", line 380, in if not is_same_ns(host_pid, "pid") and not is_same_ns(host_pid, "mnt"): File "/usr/share/apport/apport", line 305, in is_same_ns if os.readlink('/proc/%s/ns/%s' % (pid, ns)) == os.readlink('/proc/self/ns/%s' % ns): FileNotFoundError: [Errno 2] No such file or directory: '/proc/3558/ns/pid' I've already committed this fix upstream and I linked the fix to another bug so will mark this as a duplicate of that one. ** This bug has been marked a duplicate of bug 1733366 apport crashed with FileNotFoundError in is_container_pid(): [Errno 2] No such file or directory: '/proc/11102/ns/pid' -- 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/1737867 Title: apport crashes with FileNotFoundError in is_same_ns Status in Apport: New Status in apport package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding apport. This problem was most recently seen with package version 2.20.8-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/b6b178fe6ed572189dbfe2627876ed9e9d59ace2 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/apport/+bug/1737867/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624320] Re: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries
Today I discovered some additional information in regard to this issue. I am using Virt-Manager and KVM, I have a Br0 bridge configured to start onboot. When this is the case name resolution as above fails. If I delete the bridge using VMM name resolution starts working ( after a reboot ). Put the bridge back in and it fails. I do have 3 network interfaces, 1 wlan, 1 ethernet, and and additional usb ethernet configured as eth1. I've configured the 3 interfaces using a persistent-rules file in /etc/udev/rules.d/ so that they bind to eth0, wlan0 and eth1. By configuring my VMM Br0 interface to Hotplug, so that it does not start onboot, this has resolved the issue. However, on Ubuntu 16.04 everything worked as expected including having the Br0 bridge start onboot. Can't say I understand what magic SystemD witchcraft is going up here, but I hope the above info provides some useful clues. -- 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/1624320 Title: systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing entries Status in systemd package in Ubuntu: Confirmed Bug description: systemd-resolved, or more precisely the hook script /lib/systemd/system/systemd-resolved.service.d/resolvconf.conf, causes resolvconf to add 127.0.0.53 to the set of nameservers in /etc/resolv.conf alongside the other nameservers. That makes no sense because systemd-resolved sets up 127.0.0.53 as a proxy for those other nameservers. The effect is similar to bug 1624071 but for applications doing their own DNS lookups. It breaks any DNSSEC validation that systemd-resolved tries to do; applications will failover to the other nameservers, bypassing validation failures. And it makes failing queries take twice as long. /etc/resolv.conf should have only 127.0.0.53 when systemd-resolved is active. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
Verified the test case - on xenial with version 3.18.2-0ubuntu0.2 from xenial-proposed - on zesty with version 3.24.1-0ubuntu0.2 from zesty-proposed - on artful with version 3.26.0-1ubuntu0.1 from artful-proposed ** Tags removed: verification-needed verification-needed-artful verification-needed-xenial verification-needed-zesty ** Tags added: verification-done verification-done-artful verification-done-xenial verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Committed Status in libgweather source package in Zesty: Fix Committed Status in libgweather source package in Artful: Fix Committed Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1725190] Re: Please update modemmanager in xenial to the 1.6 series
Thanks Robert for testing this! I'm actually re-running the test now with the overlay disabled. It looks like Bileto's britney by default uses the stable-phone-overlay which seems to have a slightly modified Qt5 stack - maybe that's related. Let's see if the run without it will also fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1725190 Title: Please update modemmanager in xenial to the 1.6 series Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: In Progress Status in libmbim source package in Xenial: New Status in libqmi source package in Xenial: New Status in modemmanager source package in Xenial: New Bug description: [Impact] * the new modemmanager packages bring in DW5816 supporting. * These modemmanager packages is needed to support new devices. [Test Case] * install modemmanager and it's dependencies from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3054 libmbim-glib4:amd64 1.14.0-1ubuntu0.16.04.1 libmbim-proxy 1.14.0-1ubuntu0.16.04.1 libmm-glib0:amd64 1.6.4-1ubuntu0.16.04.1 libqmi-glib5:amd64 1.16.2-1ubuntu0.16.04.1 libqmi-proxy 1.16.2-1ubuntu0.16.04.1 modemmanager 1.6.4-1ubuntu0.16.04.1 * reboot and try WWAN function to see if any regression there. * perform general dogfooding of its reverse dependencies (network-manager, gnome-control-center etc.) [Regression Potential] * The package comes from Zesty and should not have regression there. * Every new upstream release can potentially break existing dependencies if any of the required features have been changed/removed, so besides regular testing a general dogfooding session with the new modemmanager is advised. [Original Description] We would like to upgrade xenial to 1.6 series so it supports the same modems as the modem-manager snap, specifically some new Sierra modems (HL8548 and others from HL series, popular in IoT devices). These are the packages that would need to be updated: libmbim: 1.12.2-2ubuntu1 in xenial, 1.14.0 in snap libqmi: 1.12.6-1 in xenial, 1.16.2 in snap modemmanager: 1.4.12-1ubuntu1 in xenial, 1.6.2 in snap This is also related to bug #1693756 which includes a subset of patches of what would be updated. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1725190/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735134] Re: ModemManager uses a wrong plugin for Dell DW5818/5819
I would say this is much more fitting for an SRU than the big backport. I would propose trying to release this anyway as the backport can take longer to get prepared and then reviewed - big upstream releases as SRUs are never easy to handle. Looking at the debdiff, it's mostly ok although we would need a DEP-3 header on the patch [1] to give more background on the change that's being made. Also, the 'Non-maintainer upload' changelog entry is not required in Ubuntu. Could you fix those and re-attach the patch? Thanks! [1] http://dep.debian.net/deps/dep3/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1735134 Title: ModemManager uses a wrong plugin for Dell DW5818/5819 Status in modemmanager package in Ubuntu: New Bug description: [Impact] * Dell Wireless DW5818/5819 modems showed an incorrect signal strength and were using a ttyUSB* port for data connections instead of the MBIM device (which provides better performance). Since linux-4.4.0-98, the kernel additionally loads gcserial driver for Dell Wireless DW5818/5819. The reason behind it is to support firmware switching and upgrading. However, the change makes ModemManager use Gobi plugin for this two modules. With Gobi plugin, the modules could establish data links, but it failed to retrieve the signal state. And it caused the mmcli and nm-applet giving wrong signal strength. The modules support the MBIM protocol, so ModemManager should use Dell plugin for these two modules. I have worked out a patch to forbid these two modules in Gobi plugin, and it does work well. [Test Case] Current MM: * Create connection with $ nmcli c add type gsm ifname ttyUSB2 con-name gsmconn apn * Without the patched package, mmcli shows, with an active connection (see comment #2): primary port: 'ttyUSB2' signal quality: '0' (recent) Patched MM: * Create connection with $ nmcli c add type gsm ifname cdc-wdm0 con-name gsmconn apn * With the patched package, mmcli shows, with an active connection (see comment #7): primary port: 'cdc-wdm0' signal quality: '38' (cached) [Regression Potential] The patch simply adds the Sierra modems VID/PIDs to the list of forbidden ids in the Gobi plugin, so the possibility of a regression is very small: only products with said VID/PID will be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1735134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs
** Branch linked: lp:~smoser/maas-images/trunk.add-zfs -- 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/1737592 Title: no zfs module in initramfs Status in maas-images: Confirmed Status in initramfs-tools package in Ubuntu: Invalid Bug description: zfs support exists in Ubuntu kernels for 16.04 and later, but the default initramfs build does not include this module. Other common filesystems are included. As a small piece of information: $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/ 3.2M /lib/modules/4.13.0-17-generic/kernel/zfs/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools-core 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 13:05:15 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (872 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1737592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
This is quite unique to maas; as no other software is getting backports with explicit features that enables systemd support on trusty. E.g. cloud-init backports are done in such a way, that when compiled on trusty, no systemd support is installed nor available. You may want to choose to make init-system selection code innert, as a compile time / dependency option, such that on trusty there is no dynamic selection of things at all. -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
It is correct, in general, to check for /run/systemd/system to detect if systemd manages pid 1. Imho deputy systemd (used by snapd, on trusty, with xenial-lts kernel) should not have been creating that, however I fear that without that directory snapd and snaps therein may get confused (in classic confinment). It is true that trusty only uses upstart as pid1 with no other options; and any system systemd jobs are inert (deputy systemd only looks for deputy things). Note that although xenial ships both upstart & systemd; only systemd is supported as pid1 on all form-factors. (upstart as pid1 is only supported on xenial ubuntu touch product, which is now end-of-life). Possibly we could create one more directory e.g. /run/dsystemd/system or some such, which maas can check for to destinguish "systemd or deputy- systemd". However, checking /sbin/init like done in the proposed merge proposal is very adequate for maas needs, and should yield correct results. As far as I can tell, since on xenial either upstart-sysv or systemd-sysv may provide /sbin/init, with systemd-sysv being the default everywhere. (upstart-sysv on xenial is for ubuntu touch only). Ideally, I do not want to touch deputy systemd uploads. -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 934291] Re: Deleting or stopping print jobs does not work
Can't believe that this bug is still present after 5 years -- 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/934291 Title: Deleting or stopping print jobs does not work Status in gnome-control-center: Incomplete Status in cups package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Deleting or stopping print jobs through the "gnome-control-center -> printers" menu is not possible. (Black rectangle for stopping can be pressed, nothing happens.) Deleting with cups via webinterface does work. ( http://localhost:631/ ) Please let me know which information to provide. Cheers ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.2.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17 Uname: Linux 3.0.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu4 Architecture: amd64 Date: Fri Feb 17 16:47:32 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago) usr_lib_gnome-control-center: deja-dup 22.0~bzr1290.37~oneiric1 gnome-bluetooth3.2.0-0ubuntu2 indicator-datetime 0.3.1-0ubuntu1.1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/934291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
snapd will not function without systemd as a deputy init. nothing to fix in snapd. ** Changed in: snapd (Ubuntu) Status: New => Won't Fix -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs
** Changed in: maas-images Status: New => Confirmed ** Changed in: maas-images Importance: Undecided => Medium ** Changed in: initramfs-tools (Ubuntu) Status: New => Invalid -- 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/1737592 Title: no zfs module in initramfs Status in maas-images: Confirmed Status in initramfs-tools package in Ubuntu: Invalid Bug description: zfs support exists in Ubuntu kernels for 16.04 and later, but the default initramfs build does not include this module. Other common filesystems are included. As a small piece of information: $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/ 3.2M /lib/modules/4.13.0-17-generic/kernel/zfs/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools-core 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 13:05:15 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (872 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1737592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
Further extensive discussion at https://irclogs.ubuntu.com/2017/12/13 /%23ubuntu-devel.html#t15:15 Our current belief is that the bug is in the systemd package, introduced by the SRU tracked in bug 1656280. That update broke our standard test for determining if we're on a systemd system by creating /run/systemd/system when the systemd package is installed even if pid 1 is upstart. It looks like this regressed eleven months ago but was only reported last month, so I don't think the MAAS fix is critical. I would prefer to get this fixed properly in systemd because it may have a wider impact than just MAAS. -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1732703] Re: MAAS does not detect properly if Ubuntu is using upstart/systemd
** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: maas (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided => Critical -- 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/1732703 Title: MAAS does not detect properly if Ubuntu is using upstart/systemd Status in MAAS: Won't Fix Status in MAAS 1.9 series: In Progress Status in maas package in Ubuntu: New Status in snapd package in Ubuntu: Won't Fix Status in systemd package in Ubuntu: New Status in maas source package in Trusty: New Status in snapd source package in Trusty: New Status in systemd source package in Trusty: New Bug description: [impact] Since Trusty uses upstart by default, MAAS manages its services with upstart. However, when a user installs systemd (even if it is not used as the init system), MAAS detects systemd installed and tries to manage its services via systemd. This obviously creates issues and prevents MAAS from working. [Test Case] 1. Install & configure MAAS 2. Add machines 3. install systemd 4. MAAS will fail to manage machines [Regression potential] Minimal. This just ensures that upstart is detected correctly even if systemd is installed (but not used). [Original bug report] Trusty uses upstart by default, and installing snapd (e.g. for livepatch purposes), pulls systemd too. In this setup, upstart is _not_ replaced by systemd, but MAAS "detects" systemd as init because of the existence of /run/systemd/system: @src/provisioningserver/utils/__init__.py:505 SYSTEMD_RUN_PATH = '/run/systemd/system' def get_init_system(): """Returns 'upstart' or 'systemd'.""" if os.path.exists(SYSTEMD_RUN_PATH): return 'systemd' else: return 'upstart' One possible solution would be to check if /sbin/init is a symlink pointing to /lib/systemd/systemd: def get_init_system(): """Returns 'upstart' or 'systemd'.""" initpath = os.readlink("/sbin/init") if (initpath == "/lib/systemd/systemd"): return 'systemd' else: return 'upstart' Other affected parts of the code are the postinst files for maas-proxy and maas-dhcp (debian/maas-proxy.postinst debian/maas-dhcp.postinst), throwing an error if maas is installed after systemd in Trusty To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1732703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738039] Re: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
** Tags removed: need-duplicate-check -- 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/1738039 Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: New Bug description: The normal update failed to finish properly. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 640:0:116:100989:2017-12-10 09:09:24.099369764 +0200:2017-12-10 09:09:25.099369764 +0200:/var/crash/_usr_bin_atop.0.crash 640:1000:116:5469774:2017-12-07 18:53:05.238692741 +0200:2017-12-09 09:04:37.246543187 +0200:/var/crash/_usr_bin_compiz.1000.crash 644:0:116:0:2017-12-10 09:09:25.703367143 +0200:2017-12-10 09:09:25.703367143 +0200:/var/crash/_usr_bin_atop.0.upload 600:0:116:84324:2017-12-10 09:10:03.171132802 +0200:2017-12-10 09:10:04.171132802 +0200:/var/crash/apport.0.crash 600:109:116:0:2017-12-10 09:09:26.815362361 +0200:2017-12-10 09:09:26.815362361 +0200:/var/crash/_usr_bin_atop.0.uploaded Date: Sun Dec 10 09:10:04 2017 DuplicateSignature: package:apport:2.20.1-0ubuntu2.14 Setting up apport (2.20.1-0ubuntu2.14) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2016-04-23 (599 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737592] Re: no zfs module in initramfs
** Also affects: maas-images Importance: Undecided Status: New -- 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/1737592 Title: no zfs module in initramfs Status in maas-images: New Status in initramfs-tools package in Ubuntu: New Bug description: zfs support exists in Ubuntu kernels for 16.04 and later, but the default initramfs build does not include this module. Other common filesystems are included. As a small piece of information: $ du -hs /lib/modules/4.13.0-17-generic/kernel/zfs/ 3.2M /lib/modules/4.13.0-17-generic/kernel/zfs/ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: initramfs-tools-core 0.125ubuntu12 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 11 13:05:15 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (872 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: initramfs-tools UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/maas-images/+bug/1737592/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737998] Re: trying to bind on all interfaces is a good default, but fails on ipv6 link local
Thanks a lot Simon for your thoughts - this is exactly what I was looking for. "On a hypervisor, binding on link local IPs is undesirable IMHO" Thats what I thought as well But - if there is valid use of link locals in general - as I was unsure of and you as well suggest there might be folks doing that; then we do not want to ignore them by default. TL;DR we better have it working for all and have those "undesired" disabling it instead of not working by default in some environments. If more people chime in we can make an overall summary and either reopen or keep as is. For now this stays incomplete. -- 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/1737998 Title: trying to bind on all interfaces is a good default, but fails on ipv6 link local Status in ntp package in Ubuntu: Incomplete Bug description: The default is "grab all" which is great for convenience and can be configured to be differently by argument -I (interface) or interface commands in the config. Currently it is "too" open on that. I see it trying to bing link local addresses for each of the KVM guests I spawn. They get virtual network devices and due to that ntp sees it tries to bind and fails. Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested address Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) for fe80::fc54:ff:fec3:3eb0%47#123 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address fe80::fc54:ff:fec3:3eb0%47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738039] [NEW] package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239
Public bug reported: The normal update failed to finish properly. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 640:0:116:100989:2017-12-10 09:09:24.099369764 +0200:2017-12-10 09:09:25.099369764 +0200:/var/crash/_usr_bin_atop.0.crash 640:1000:116:5469774:2017-12-07 18:53:05.238692741 +0200:2017-12-09 09:04:37.246543187 +0200:/var/crash/_usr_bin_compiz.1000.crash 644:0:116:0:2017-12-10 09:09:25.703367143 +0200:2017-12-10 09:09:25.703367143 +0200:/var/crash/_usr_bin_atop.0.upload 600:0:116:84324:2017-12-10 09:10:03.171132802 +0200:2017-12-10 09:10:04.171132802 +0200:/var/crash/apport.0.crash 600:109:116:0:2017-12-10 09:09:26.815362361 +0200:2017-12-10 09:09:26.815362361 +0200:/var/crash/_usr_bin_atop.0.uploaded Date: Sun Dec 10 09:10:04 2017 DuplicateSignature: package:apport:2.20.1-0ubuntu2.14 Setting up apport (2.20.1-0ubuntu2.14) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2016-04-23 (599 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1738039 Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 Status in apport package in Ubuntu: New Bug description: The normal update failed to finish properly. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.14 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Uname: Linux 4.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.14 Architecture: amd64 CrashReports: 640:0:116:100989:2017-12-10 09:09:24.099369764 +0200:2017-12-10 09:09:25.099369764 +0200:/var/crash/_usr_bin_atop.0.crash 640:1000:116:5469774:2017-12-07 18:53:05.238692741 +0200:2017-12-09 09:04:37.246543187 +0200:/var/crash/_usr_bin_compiz.1000.crash 644:0:116:0:2017-12-10 09:09:25.703367143 +0200:2017-12-10 09:09:25.703367143 +0200:/var/crash/_usr_bin_atop.0.upload 600:0:116:84324:2017-12-10 09:10:03.171132802 +0200:2017-12-10 09:10:04.171132802 +0200:/var/crash/apport.0.crash 600:109:116:0:2017-12-10 09:09:26.815362361 +0200:2017-12-10 09:09:26.815362361 +0200:/var/crash/_usr_bin_atop.0.uploaded Date: Sun Dec 10 09:10:04 2017 DuplicateSignature: package:apport:2.20.1-0ubuntu2.14 Setting up apport (2.20.1-0ubuntu2.14) ... Segmentation fault dpkg: error processing package apport (--configure): subprocess installed post-installation script returned error exit status 239 ErrorMessage: subprocess installed post-installation script returned error exit status 239 InstallationDate: Installed on 2016-04-23 (599 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 239 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1738039/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737998] Re: trying to bind on all interfaces is a good default, but fails on ipv6 link local
On a hypervisor, binding on link local IPs is undesirable IMHO and that's why I always added a similar ignore to the one you proposed. That said, NTP works well over link local addresses so some folks are probably using it. -- 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/1737998 Title: trying to bind on all interfaces is a good default, but fails on ipv6 link local Status in ntp package in Ubuntu: Incomplete Bug description: The default is "grab all" which is great for convenience and can be configured to be differently by argument -I (interface) or interface commands in the config. Currently it is "too" open on that. I see it trying to bing link local addresses for each of the KVM guests I spawn. They get virtual network devices and due to that ntp sees it tries to bind and fails. Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested address Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) for fe80::fc54:ff:fec3:3eb0%47#123 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address fe80::fc54:ff:fec3:3eb0%47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
As expected I could solve the issue in a test via flags=(attach_disconnected). Although I had cases where the issue appeared and others where it never showed up - didn't find the difference for that yet. Never the less the fix will help the affected cases and should not break others. The worst is that I found this to be hiding the actual error message. In my case where I was seeing it ntp was "actually" complaining about bug 1737998. But I think atm most ntp errors might look like the apparmor deny which makes this a bit more severe than I thought at first. Opened an MP for it at [1]. @Martin - do you test Debian as well and if you have apparmor enabled there does it hit there as well? Just to know if you have a bug I could post the fix on @Martin - since I failed to see when it hits and when not - if you can test from a ppa [2] (or modify the case to have the one line change) it would be nice if you could confirm the fix. If you happen to see why it only happens "sometimes" let me know. [1]: https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/335147 [2]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3080 ** Changed in: ntp (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Triaged Status in ntp source package in Artful: New Status in ntp source package in Bionic: Triaged Bug description: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser
Requesting a sponsor to upload the fix's backport :) ** Patch added: "Debdiff patch to backport the fix from GNOME's git." https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1714518/+attachment/5022155/+files/gtk+3.0_3.22.26-2ubuntu1.1.debdiff -- 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/1714518 Title: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser Status in GTK+: Fix Released Status in chromium-browser package in Ubuntu: New Status in deja-dup package in Ubuntu: New Status in firefox package in Ubuntu: New Status in gdebi package in Ubuntu: New Status in gtk+3.0 package in Ubuntu: In Progress Status in meld package in Ubuntu: New Status in remmina package in Ubuntu: New Status in thunderbird package in Ubuntu: New Status in transmission package in Ubuntu: New Status in usb-creator package in Ubuntu: New Status in vinagre package in Ubuntu: New Bug description: Steps to reproduce: 1. Install any Gtk3 application such as Firefox or Chromium which use modern file-chooser dialog. 2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, "sftp://"; = SFTP/SSH and so on) 3. Try to save/open file to/from the remote location from Gtk3 application. Expected results: * user is able to find network folder and save/open file to/from it with GtkFileChooser dialog Actual results: * user is unable to find network folder and save/open file to/from it with GtkFileChooser dialog and many user applications are affected - Original bug description is below: GTK+3 doesn't show FUSE network shares in file chooser - it used to do so in GTK+2, and the GTK+3 documentation still mentions it should do it. In the mean time, every user of every application switching to GTK+3 -- including Chromium, at some point between 58 and 60 -- (a change which happened in 16.04 LTS!!), loses the functionality to open or save directly to a network share. I had chosen 16.04 LTS for deploying our workstations at work, and my 50 users have been suddenly unable to do a simple operation they have to do dozens of times a day. They now have to "buffer" these files to their local filesystem when saving them and before uploading them, and then copy them to the company's network shares. They were already a little bit grumpy when it stopped working with Firefox, and are now really side-eyeing me when they apply updates and find Chromium broken. I have reported the bug upstream and provided a patch to fix this. I hope you'll be able and willing to include it to Ubuntu's GTK+3 package. Thanks in advance. Colin To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1714518/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/335147 -- 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/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Triaged Status in ntp source package in Artful: New Status in ntp source package in Bionic: Triaged Bug description: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737998] Re: trying to bind on all interfaces is a good default, but fails on ipv6 link local
Ok I debugged more and it seems that the situation where i was unable to bind is the special one. I usually got this now: Dec 13 15:24:31 bionic-test-kvm ntpd[6142]: Listen normally on 8 vnet0 [fe80::fc54:ff:fe46:80ed%10]:123 Dec 13 15:24:31 bionic-test-kvm ntpd[6142]: new interface(s) found: waking up resolver If that is the usual case I'm fine and close this bug for now. Please note that 1727202 needs to be fixed to actually see the message. ** Changed in: ntp (Ubuntu) Status: New => Incomplete -- 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/1737998 Title: trying to bind on all interfaces is a good default, but fails on ipv6 link local Status in ntp package in Ubuntu: Incomplete Bug description: The default is "grab all" which is great for convenience and can be configured to be differently by argument -I (interface) or interface commands in the config. Currently it is "too" open on that. I see it trying to bing link local addresses for each of the KVM guests I spawn. They get virtual network devices and due to that ntp sees it tries to bind and fails. Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested address Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) for fe80::fc54:ff:fec3:3eb0%47#123 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address fe80::fc54:ff:fec3:3eb0%47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1727202] Re: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path
** Also affects: ntp (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: ntp (Ubuntu Bionic) Importance: Undecided Status: Triaged -- 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/1727202 Title: [17.10 regression] AppArmor denial: Failed name lookup - disconnected path Status in ntp package in Ubuntu: Triaged Status in ntp source package in Artful: New Status in ntp source package in Bionic: Triaged Bug description: Merely installing and starting ntp.service in Ubuntu 17.10 now causes this AppArmor violation: audit: type=1400 audit(1508915894.215:25): apparmor="DENIED" operation="sendmsg" info="Failed name lookup - disconnected path" error=-13 profile="/usr/sbin/ntpd" name="run/systemd/journal/dev-log" pid=5600 comm="ntpd" requested_mask="w" denied_mask="w" fsuid=0 ouid=0 (many times). This hasn't happened in earlier Ubuntu releases yet. This was spotted by Cockpit's integration tests, as our "ubuntu- stable" image now moved to 17.10 after its release. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ntp 1:4.2.8p10+dfsg-5ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 Date: Wed Oct 25 03:19:34 2017 SourcePackage: ntp UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1727202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737998] Re: trying to bind on all interfaces is a good default, but fails on ipv6 link local
Reading more into [1] and [2] I'm not 100% if ntp just has an issue or if in general we should mask this interface type like: interface ignore fe80::/64 [1]: https://www.eecis.udel.edu/~mills/ntp/html/miscopt.html#interface [2]: https://www.cisco.com/c/en/us/support/docs/ip/ip-version-6-ipv6/113328-ipv6-lla.html -- 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/1737998 Title: trying to bind on all interfaces is a good default, but fails on ipv6 link local Status in ntp package in Ubuntu: Incomplete Bug description: The default is "grab all" which is great for convenience and can be configured to be differently by argument -I (interface) or interface commands in the config. Currently it is "too" open on that. I see it trying to bing link local addresses for each of the KVM guests I spawn. They get virtual network devices and due to that ntp sees it tries to bind and fails. Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested address Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) for fe80::fc54:ff:fec3:3eb0%47#123 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address fe80::fc54:ff:fec3:3eb0%47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704533] Please test proposed package
Hello NoOne, or anyone else affected, Accepted libgweather into artful-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libgweather/3.26.0-1ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-artful to verification-done-artful. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-artful. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Committed Status in libgweather source package in Zesty: Fix Committed Status in libgweather source package in Artful: Fix Committed Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704533] Please test proposed package
Hello NoOne, or anyone else affected, Accepted libgweather into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libgweather/3.24.1-0ubuntu0.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-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Committed Status in libgweather source package in Zesty: Fix Committed Status in libgweather source package in Artful: Fix Committed Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704533] Re: French language locale missing : Gnome-Weather
Hello NoOne, or anyone else affected, Accepted libgweather into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libgweather/3.18.2-0ubuntu0.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, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: libgweather (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: libgweather (Ubuntu Zesty) Status: In Progress => Fix Committed ** Tags added: verification-needed-zesty ** Changed in: libgweather (Ubuntu Artful) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgweather in Ubuntu. https://bugs.launchpad.net/bugs/1704533 Title: French language locale missing : Gnome-Weather Status in GNOME Weather: Unknown Status in Ubuntu Translations: In Progress Status in gnome-weather package in Ubuntu: Invalid Status in libgweather package in Ubuntu: Fix Released Status in libgweather source package in Xenial: Fix Committed Status in libgweather source package in Zesty: Fix Committed Status in libgweather source package in Artful: Fix Committed Bug description: [Impact] The variable GETTEXT_PACKAGE is set to "libgweather-3.0" when building libgweather, which makes the libgweather-common binary look for translations in files named "libgweather-3.0.mo". The template name in Rosetta (LP) is "libgweather", so the files provided by the language packs are named "libgweather.mo". This mismatch results in the messages describing the weather type always be displayed in English. The uploaded package works around the issue by setting GETTEXT_PACKAGE to "libgweather". In bionic the template name in Rosetta has been changed to "libgweather-3.0", and thus the workaround will be reversed. [Test Case] * Install French language support * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is displayed in English. * Install these packages from -proposed: - gir1.2-gweather-3.0 - libgweather-3-6 - libgweather-common * Start gnome-weather with: LANGUAGE=fr gnome-weather and find that the description of the weather type is now displayed in French. [Regression Potential] None. [Original description] In Gnome Weather, part of it is not translated in french : cloudy, rain showers, etc. Should be : nuageux, pluie fine, etc. I guess it's a missing french localization. Fedora does not have that problem. In Gnome-Software, they have a section for languages, under the extensions section. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-weather/+bug/1704533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736556] Re: mount can exit 0 (success) when it fails
** Summary changed: - mount can exit (success) when it fails + mount can exit 0 (success) when it fails -- 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/1736556 Title: mount can exit 0 (success) when it fails Status in util-linux package in Ubuntu: Confirmed Bug description: I'm on softlayer in an official Ubuntu image and 'mount' exits success even when it fails. $ cat /etc/cloud/build.info build_name: server serial: 20171116 $ cat /etc/fstab LABEL=cloudimg-rootfs /ext4 defaults,relatime 0 0 # Added by Cloud Image build process LABEL=cloudimg-bootfs /boot ext3defaults,relatime0 0 # CLOUD_IMG: This file was created/modified by the Cloud Image build process # Mount the metadata disk for cloud-init, if present LABEL=METADATA /var/lib/cloud/seed/config_drive vfat defaults,nofail 0 0 LABEL=SWAP-xvdb1noneswapsw,comment=cloudconfig 0 2 $ blkid /dev/xvda1: LABEL="cloudimg-bootfs" UUID="63ea63a7-f64c-493c-90d4-384adc196be9" TYPE="ext3" PARTUUID="3276fc6f-01" /dev/xvda2: LABEL="cloudimg-rootfs" UUID="82ca1e17-8bc2-4895-96bb-3c39e5863238" TYPE="ext4" PARTUUID="3276fc6f-02" /dev/xvdh: SEC_TYPE="msdos" LABEL="config-2" UUID="9796-932E" TYPE="vfat" /dev/xvdb1: LABEL="SWAP-xvdb1" UUID="d51fcca0-6b10-4934-a572-f3898dfd8840" TYPE="swap" PARTUUID="00025cdb-01" $ whoami root $ grep /var/lib/cloud/seed/config_drive /proc/mounts $ mount /var/lib/cloud/seed/config_drive $ echo $? 0 ## it exited 0 so it should be mounted, but it is not. $ ls /var/lib/cloud/seed/config_drive $ grep /var/lib/cloud/seed/config_drive /proc/mounts ## try somewhere else and with /dev/ path. it works. $ mount /dev/xvdh /mnt $ echo $? 0 $ grep /mnt /proc/mounts /dev/xvdh /mnt vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0 $ find /mnt/ /mnt/ /mnt/openstack /mnt/openstack/latest /mnt/openstack/latest/meta_data.json /mnt/openstack/latest/network_data.json /mnt/openstack/latest/user_data /mnt/openstack/latest/vendor_data.json $ journalctl -o short-monotonic --boot --no-pager | pastebinit http://paste.ubuntu.com/26119983/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: mount 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90 Uname: Linux 4.4.0-98-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.12 Architecture: amd64 Date: Tue Dec 5 17:52:14 2017 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1736556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737998] Re: trying to bind on all interfaces is a good default, but fails on ipv6 link local
This looks promising https://www.eecis.udel.edu/~mills/ntp/html/miscopt.html#interface -- 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/1737998 Title: trying to bind on all interfaces is a good default, but fails on ipv6 link local Status in ntp package in Ubuntu: New Bug description: The default is "grab all" which is great for convenience and can be configured to be differently by argument -I (interface) or interface commands in the config. Currently it is "too" open on that. I see it trying to bing link local addresses for each of the KVM guests I spawn. They get virtual network devices and due to that ntp sees it tries to bind and fails. Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested address Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) for fe80::fc54:ff:fec3:3eb0%47#123 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address fe80::fc54:ff:fec3:3eb0%47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737998] [NEW] trying to bind on all interfaces is a good default, but fails on ipv6 link local
Public bug reported: The default is "grab all" which is great for convenience and can be configured to be differently by argument -I (interface) or interface commands in the config. Currently it is "too" open on that. I see it trying to bing link local addresses for each of the KVM guests I spawn. They get virtual network devices and due to that ntp sees it tries to bind and fails. Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested address Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) for fe80::fc54:ff:fec3:3eb0%47#123 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address fe80::fc54:ff:fec3:3eb0%47 ** Affects: ntp (Ubuntu) Importance: Undecided Status: New -- 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/1737998 Title: trying to bind on all interfaces is a good default, but fails on ipv6 link local Status in ntp package in Ubuntu: New Bug description: The default is "grab all" which is great for convenience and can be configured to be differently by argument -I (interface) or interface commands in the config. Currently it is "too" open on that. I see it trying to bing link local addresses for each of the KVM guests I spawn. They get virtual network devices and due to that ntp sees it tries to bind and fails. Dez 13 11:35:41 seidel ntpd[35826]: bind(31) AF_INET6 fe80::fc54:ff:fec3:3eb0%47#123 flags 0x11 failed: Cannot assign requested address Dez 13 11:35:41 seidel ntpd[35826]: unable to create socket on vnet0 (27) for fe80::fc54:ff:fec3:3eb0%47#123 Dez 13 11:35:41 seidel ntpd[35826]: failed to init interface for address fe80::fc54:ff:fec3:3eb0%47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1737998/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic
py-macaroon-bakery cannot be imported as it is (otherwise we'll need to update the version of protobuf and python3-nacl in xenial, breaking all applications already using it). Please find attached the proposed debdiff. ** Description changed: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] - for python3-protobuf: $ python3 -c "import google.protobuf" - - for python3-pymacaroon-bakery: make sure all the tests pass + - for python3-macaroonbakery: make sure all the tests pass [Regression Potential] - httmock, none has it's not in xenial - python3-protobuf, none has the python2 code was not edited TBC - pymacaroons, none has 0.12 is backcompatible with 0.9.2 - python3-protobuf, none has it's not in xenial. ** Patch added: "py-macaroon-bakery.debdiff" https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+attachment/5022116/+files/py-macaroon-bakery.debdiff ** Description changed: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] - for python3-protobuf: $ python3 -c "import google.protobuf" - for python3-macaroonbakery: make sure all the tests pass [Regression Potential] - httmock, none has it's not in xenial - python3-protobuf, none has the python2 code was not edited TBC - - pymacaroons, none has 0.12 is backcompatible with 0.9.2 + - pymacaroons, none has 0.12 is backward compatible with 0.9.2 - python3-protobuf, none has it's not in xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1735160 Title: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic Status in httmock package in Ubuntu: New Status in protobuf package in Ubuntu: New Status in pymacaroons package in Ubuntu: New Status in python-nacl package in Ubuntu: New Bug description: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] - for python3-protobuf: $ python3 -c "import google.protobuf" - for python3-macaroonbakery: make sure all the tests pass [Regression Potential] - httmock, none has it's not in xenial - python3-protobuf, none has the python2 code was not edited TBC - pymacaroons, none has 0.12 is backward compatible with 0.9.2 - python3-protobuf, none has it's not in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737846] Re: bash fails to redirect standard output of a pipeline to the input file of the fist pipeline's command
Don't consider this as a bash bug. It's a misunderstanding by myself of the pipeline operation. Maybe a comment should be included in the reference manual to cleary explain that the last command may try to open for writing the file still open for reading by the first command, and that such a situation obviously fails. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1737846 Title: bash fails to redirect standard output of a pipeline to the input file of the fist pipeline's command Status in bash package in Ubuntu: New Bug description: In a non-interactive bash session, redirecting the standard output to the file read by the pipeline's first command leads to random resuts : the redirection sometimes works, but generally the file is overwriten by an empty file. In an interactive session, the redirection works, which leads the user to look somewhere else to find a bug. However, when the last command is a user-writen function which simulates "cat", the resulting file is correct, as in an interactive session. Bash documentation does not prohibit such processing. Arbiel ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: bash 4.3-7ubuntu1.5 ProcVersionSignature: Ubuntu 3.13.0-106.153-generic 3.13.11-ckt39 Uname: Linux 3.13.0-106-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 CurrentDesktop: Unity Date: Tue Dec 12 23:51:22 2017 InstallationDate: Installed on 2014-05-30 (1292 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: LANGUAGE=fr_FR PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: bash UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1737846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic
** Description changed: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] - TBC + - for python3-protobuf: $ python3 -c "import google.protobuf" + - for python3-pymacaroon-bakery: make sure all the tests pass [Regression Potential] - httmock, none has it's not in xenial - python3-protobuf, none has the python2 code was not edited TBC - pymacaroons, none has 0.12 is backcompatible with 0.9.2 - python3-protobuf, none has it's not in xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1735160 Title: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic Status in httmock package in Ubuntu: New Status in protobuf package in Ubuntu: New Status in pymacaroons package in Ubuntu: New Status in python-nacl package in Ubuntu: New Bug description: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] - for python3-protobuf: $ python3 -c "import google.protobuf" - for python3-pymacaroon-bakery: make sure all the tests pass [Regression Potential] - httmock, none has it's not in xenial - python3-protobuf, none has the python2 code was not edited TBC - pymacaroons, none has 0.12 is backcompatible with 0.9.2 - python3-protobuf, none has it's not in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic
** Description changed: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - - backport python-nacl 1.1.2-1 [universe] from bionic - xenial has 1.0.1-1build1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] TBC [Regression Potential] - httmock, none has it's not in xenial - python3-protobuf, none has the python2 code was not edited TBC + - pymacaroons, none has 0.12 is backcompatible with 0.9.2 + - python3-protobuf, none has it's not in xenial. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1735160 Title: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic Status in httmock package in Ubuntu: New Status in protobuf package in Ubuntu: New Status in pymacaroons package in Ubuntu: New Status in python-nacl package in Ubuntu: New Bug description: [Impact] As part of allowing Ubuntu users to enable canonical-livepatch from software-properties GUI (https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite few changes: - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 0.9.2-0ubuntu1 - SRU some changes in google-apputils-python - https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 package is not built. [Test case] TBC [Regression Potential] - httmock, none has it's not in xenial - python3-protobuf, none has the python2 code was not edited TBC - pymacaroons, none has 0.12 is backcompatible with 0.9.2 - python3-protobuf, none has it's not in xenial. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
Same issue after an upgrade from 17.04 * I was using lightdm and ctrl+alt+L * After upgrade I was on gdm (oO ok~~~) Neither ctrl+alt+L or super+L worked * I switched to lightdm and changed shortcut from ctrl+alt+L to super+L and it works, hurray! I'm keeping it but meh... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737983] [NEW] after boot login box is not showed
Public bug reported: It is only visible on screen: "/dev/sda6: clean, 310791/3080192 files, 4546374/12317447 blocks" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 13 11:52:41 2017 DistUpgraded: 2017-11-30 14:37:36,148 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, i686: installed GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated Graphics Controller [103c:308f] Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [103c:308f] InstallationDate: Installed on 2013-10-26 (1508 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic root=UUID=be4cca24-adab-48e0-963f-fc3129e79d9b ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to artful on 2017-11-30 (12 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 308F0 Ver. F.18 dmi.board.name: 308F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 02.10 dmi.chassis.type: 10 dmi.chassis.vendor: Inventec dmi.modalias: dmi:bvnHewlett-Packard:bvr308F0Ver.F.18:bd10/06/2009:svnHewlett-Packard:pn:pvr03000:rvnHewlett-Packard:rn308F:rvrKBCVersion02.10:cvnInventec:ct10:cvr: dmi.product.family: 103C_5335KV dmi.product.version: 03000 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 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: Wed Dec 13 11:05:28 2017 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 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/1737983 Title: after boot login box is not showed Status in xorg package in Ubuntu: New Bug description: It is only visible on screen: "/dev/sda6: clean, 310791/3080192 files, 4546374/12317447 blocks" ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic i686 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.7-0ubuntu3.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Dec 13 11:52:41 2017 DistUpgraded: 2017-11-30 14:37:36,148 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Falló al ejecutar el proceso hijo «./xorg_fix_proprietary.py» (No existe el archivo o el directorio) (8)) DistroCodename: artful DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.10.0-38-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-17-generic, i686: installed bcmwl, 6.30.223.271+bdcom, 4.13.0-19-generic, i686: installed GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mobile 945GSE Express Integrated Graphics Controller [103c:308f] Subsystem: Hewlett-Packard Company Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [103c:308f] InstallationDate: Installed on 2013-10-26 (1508 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0
[Touch-packages] [Bug 1737979] [NEW] Wayland freezes with matplotlib
Public bug reported: Steps to reproduce problem: _ Using python and matplotlib to plot something _ When the plot appears, move the mouse to save icon _ Boom, it's freezed Wait several minutes for it to start moving again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 20:45:02 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:13dd] InstallationDate: Installed on 2017-11-03 (39 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. X451CAP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X451CAP.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X451CAP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X451CAP dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1 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 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful false-gpu-hang freeze ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1737979 Title: Wayland freezes with matplotlib Status in xorg package in Ubuntu: New Bug description: Steps to reproduce problem: _ Using python and matplotlib to plot something _ When the plot appears, move the mouse to save icon _ Boom, it's freezed Wait several minutes for it to start moving again. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 13 20:45:02 2017 DistUpgraded: Fresh install DistroCodename: artful DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller [1043:13dd] InstallationDate: Installed on 2017-11-03 (39 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: ASUSTeK COMPUTER INC. X451CAP ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X451CAP.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X451CAP dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnAS
[Touch-packages] [Bug 1732411] Re: On upgrade, daemon-reexec should only be issued if safe
>From our analysis, we indeed agree with the fact that it has nothing to do >with LXC (hence the report in the systemd tracker). We believe that only the package is faulty here and should not attempt to blindly reexec systemd on upgrade. -- 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/1732411 Title: On upgrade, daemon-reexec should only be issued if safe Status in lxc package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: Dear all, Following up the bug report #1713674, when executing systemd in a hardened LXC context, it might not be suitable to reexec systemd daemon, that would not be able to perform. For instance, in our LXC, we drop several capabilities, including sys_admin and we set /sys to read-only (in which, systemd will find its cgroups). This means, systemd cannot be reexecuted, it will fail to restart and will freeze (properly) at restart making the LXC container in frozen state (still working, but no new services startable, no interaction with systemd possible anymore). When upgrading systemd the debian package, as postinst, will always attempt to reexecute systemd, possibly breaking every other upgrade where a daemon restart is made in postinst, and leaving the system in a degraded state. It would likely be appropriate the check whether the reexecute can work will before performing it: checking capabilities, sys mount point perms, etc. If not applicable, not performing a reexucte and possibly print a message to the user. Occurs with Ubuntu Xenial 16.04.3 LTS and systemd 229-4ubuntu21. Cheers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1732411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1735158] Re: FTBFS with gcc7
The packages built, so obviously the FTBFS fix is applied. Marking as verified. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iproute2 in Ubuntu. https://bugs.launchpad.net/bugs/1735158 Title: FTBFS with gcc7 Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Artful: Fix Committed Bug description: tc CC tc_core.o tc_core.c: In function ‘tc_calc_size_table’: tc_core.c:190:29: error: ‘UINT16_MAX’ undeclared (first use in this function); did you mean ‘__INT16_MAX__’? if ((sz >> s->size_log) > UINT16_MAX) { ^~ __INT16_MAX__ tc_core.c:190:29: note: each undeclared identifier is reported only once for each function it appears in ../Config:40: recipe for target 'tc_core.o' failed make[3]: *** [tc_core.o] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1735158/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737969] [NEW] internal host was not resolved even the dhcp-assigned dns nameserver shows local dns
Public bug reported: https://askubuntu.com/questions/368435/how-do-i-fix-dns-resolving-which- doesnt-work-after-upgrading-to-ubuntu-13-10-s ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Wed Dec 13 16:02:49 2017 InstallationDate: Installed on 2017-07-11 (154 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-30 (44 days ago) ** Affects: resolvconf (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1737969 Title: internal host was not resolved even the dhcp-assigned dns nameserver shows local dns Status in resolvconf package in Ubuntu: New Bug description: https://askubuntu.com/questions/368435/how-do-i-fix-dns-resolving- which-doesnt-work-after-upgrading-to-ubuntu-13-10-s ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: resolvconf 1.79ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 Date: Wed Dec 13 16:02:49 2017 InstallationDate: Installed on 2017-07-11 (154 days ago) InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) PackageArchitecture: all SourcePackage: resolvconf UpgradeStatus: Upgraded to artful on 2017-10-30 (44 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1737969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737968] Re: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
** Tags removed: need-duplicate-check -- 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/1737968 Title: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: The error message appeared as soon as I logged in. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 12 08:53:10 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1737968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737968] [NEW] package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co
Public bug reported: The error message appeared as soon as I logged in. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 12 08:53:10 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1737968 Title: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: The error message appeared as soon as I logged in. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.13 Architecture: amd64 Date: Tue Dec 12 08:53:10 2017 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.10.0-42-generic 4.10.0-42.46~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1737968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp