[Touch-packages] [Bug 1348431] Re: -O inline_data not supported by Ubuntu e2fsprogs
Have verified that `mkfs.ext4 -O inline_data` works with the yakkety e2fsprogs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1348431 Title: -O inline_data not supported by Ubuntu e2fsprogs Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Since kernel version 3.8, ext4 supports the file system option inline_data to put file content into the inode itself as an extended attribute. However, this feature cannot be enabled using the included e2fsprogs in Trusty Tahr. If it has been enabled for a file system, boot e2fsck fails. Support for this is currently being worked on upstream in https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/log/?h=pu . Adding this bug to track when this is merged into mainline and/or the ubuntu e2fsprogs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1348431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348431] Re: -O inline_data not supported by Ubuntu e2fsprogs
This feature is in e2fsprogs 1.43, which is in yakkety (16.10). The bug can be closed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1348431 Title: -O inline_data not supported by Ubuntu e2fsprogs Status in e2fsprogs package in Ubuntu: Confirmed Bug description: Since kernel version 3.8, ext4 supports the file system option inline_data to put file content into the inode itself as an extended attribute. However, this feature cannot be enabled using the included e2fsprogs in Trusty Tahr. If it has been enabled for a file system, boot e2fsck fails. Support for this is currently being worked on upstream in https://git.kernel.org/cgit/fs/ext2/e2fsprogs.git/log/?h=pu . Adding this bug to track when this is merged into mainline and/or the ubuntu e2fsprogs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1348431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
Okay, I did a whole bunch of things tonight and I think I got mine working. Added " options snd-hda-intel model=auto " to /etc/modprobe.d/alsa-base.conf (https://forums.linuxmint.com/viewtopic.php?t=110209) Added " sudo apt-get install dkms " and downloading the most recent ALSA daily for 16.04 (https://wiki.ubuntu.com/Audio/UpgradingAlsa/DKMS) Added " rmmod snd_hda_intel " and " modprobe snd_hda_intel position_fix=1 " to /etc/rc.local (https://github.com/ValveSoftware/SteamOS/issues/221) Executed " sudo apt-get install --install-recommends linux-generic-lts-wily xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video-all-lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts-wily " (https://ubuntuforums.org/showthread.php?t=2293912) Installed hdajackretask [per mephi, #81 in this thread], selected Creative CA0132, and toggled Advanced override. Override Green Headphone, Front side. Set Device to Headphone and Channel (in group) to Front. Also the simple stuff like making sure your desired audio output device is set to default and not muted. Make sure to run alsamixer after each reboot because I find my output muted after every restart. Hope this helps someone! ** Bug watch added: github.com/ValveSoftware/SteamOS/issues #221 https://github.com/ValveSoftware/SteamOS/issues/221 -- 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/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686586] [NEW] crash
Public bug reported: 4-26-17 11:16 PM boot error ** Affects: debconf (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1686586 Title: crash Status in debconf package in Ubuntu: New Bug description: 4-26-17 11:16 PM boot error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1686586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686577] [NEW] package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: update issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 20:33:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-03-01 (56 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 65: Bad configuration option: X11UseForwarding /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check package-from-proposed xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1686577 Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: New Bug description: update issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.8.0-49.52~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-49-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 20:33:34 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-03-01 (56 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 65: Bad configuration option: X11UseForwarding /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1686577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1648183] Re: Crackling and popping sound when using headphones
I've managed to fix partially the problem or at least I can narrow it down. So , if I override all my other audio lines via hdajackretask module and only enable the headphone one, the sound is perfect. What happens though when I turn back on the line for the Internal speakers , it goes back to crackling and popping in the internal speakers and headphones. So basically this allows the user to use EITHER internal speakers OR headphones , NOT both. -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685271] Re: gnome-shell: corners are not rounded
** Description changed: Under gnome-shell apps have dark black squared top corners when they should be rounded. See attached screenshot. + + See also bug 1685272 ** No longer affects: light-themes (Ubuntu) ** No longer affects: light-themes (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685271 Title: gnome-shell: corners are not rounded Status in ubuntu-themes package in Ubuntu: Triaged Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell apps have dark black squared top corners when they should be rounded. See attached screenshot. See also bug 1685272 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1685271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685272] Re: gnome-shell: no window border
I was initially content with the terse description "no window border" because I thought there was only this one bug covering the shadows and titlebar corner issues. But it turns out a second bug 1685271 exists for the latter. So yes, this bug now needs a better description... ** Summary changed: - gnome-shell: no window border + gnome-shell: no window shadows ** Description changed: - Under gnome-shell, there are no window borders. See attached + Under gnome-shell, there are no window borders (shadows). See attached screenshot. + + See also bug 1685271 ** No longer affects: light-themes (Ubuntu) ** No longer affects: light-themes (Ubuntu Artful) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685272 Title: gnome-shell: no window shadows Status in ubuntu-themes package in Ubuntu: Triaged Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell, there are no window borders (shadows). See attached screenshot. See also bug 1685271 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1685272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686573] [NEW] USB Modem not displayed in network manager
Public bug reported: 4G USB WAN modem will not display in network manager, but is fully detected by the kernel and is displayed in ip link journal; Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: new high-speed USB device number 5 using xhci_hcd Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has an invalid interface number: 7 but max is 3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: config 1 has no interface number 2 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device found, idVendor=1199, idProduct=68a3 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: New USB device strings: Mfr=3, Product=2, SerialNumber=4 Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Product: AC760S Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Manufacturer: Sierra Wireless, Incorporated Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: SerialNumber: 359822042204515 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.0: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB0 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.1: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB1 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra 5-2:1.3: Sierra USB modem converter detected Apr 27 10:56:44 Paul-HP-Laptop kernel: usb 5-2: Sierra USB modem converter now attached to ttyUSB2 Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwan0: register 'sierra_net' at usb-:00:10.0-2, Sierra Wireless USB-to-WWAN Modem, ce:6b:97:53:02:07 Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: checking bus 5, device 5: "/sys/devices/pci:00/:00:10.0/usb5/5-2" Apr 27 10:56:44 Paul-HP-Laptop mtp-probe[19472]: bus: 5, device: 5 was not an MTP device Apr 27 10:56:44 Paul-HP-Laptop kernel: sierra_net 5-2:1.7 wwp0s16f0u2i7: renamed from wwan0 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4733] devices added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7 Apr 27 10:56:44 Paul-HP-Laptop NetworkManager[898]: [1493254604.4734] device added (path: /sys/devices/pci:00/:00:10.0/usb5/5-2/5-2:1.7/net/wwp0s16f0u2i7, iface: wwp0s16f0u2i7) Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB1): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB0): port attributes not fully set Apr 27 10:56:45 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Creating modem with plugin 'Sierra (legacy)' and '4' ports Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB1): 'Cannot add port 'tty/ttyUSB1', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Could not grab port (tty/ttyUSB0): 'Cannot add port 'tty/ttyUSB0', unhandled serial type' Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:56:57 Paul-HP-Laptop ModemManager[846]: Modem for device at '/sys/devices/pci:00/:00:10.0/usb5/5-2' successfully created Apr 27 10:57:01 Paul-HP-Laptop ModemManager[846]: Modem: state changed (unknown -> disabled) Apr 27 10:57:01 Paul-HP-Laptop NetworkManager[898]: [1493254621.9962] (ttyUSB2): modem state changed, 'disabled' --> 'enabling' (reason: user preference) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0002] manager: (ttyUSB2): new Broadband device (/org/freedesktop/NetworkManager/Devices/5) Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0043] device (ttyUSB2): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0065] device (ttyUSB2): modem state 'enabling' Apr 27 10:57:02 Paul-HP-Laptop NetworkManager[898]: [1493254622.0080] device (ttyUSB2): state change: unavailable -> disconnected (reason 'none') [20 30 0] Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: state changed (disabled -> enabling) Apr 27 10:57:02 Paul-HP-Laptop ModemManager[846]: (ttyUSB2): port attributes not fully set Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (unknown -> registering) Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: 3GPP Registration state changed (registering -> home) Apr 27 10:57:05 Paul-HP-Laptop ModemManager[846]: Modem /org/freedesktop/ModemManager1/Modem/1: state changed (enabling -> registered) Apr 27 10:57:06 Paul-HP-Laptop NetworkManager[898]: [1493254626.0016] (ttyUSB2): modem state changed, 'enabling' --> 'registered' (reason: user-requested) ip link; 6: wwp0s16f0u2i7:mtu 1500 qdisc noop state DOWN
[Touch-packages] [Bug 1166529] Re: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair
SB Recon3D Line Out does not work. I have a sound blaster zx running ubuntu 16.04 with kernerl 4.8.0 -46 My HDMI audio is working. I just plugged headphone in to the back of one of my monitors running and HDMI cord and sound is perfect... Would love to have my sound card working though -- 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/1166529 Title: Creative Recon3d & Sound Blaster Z (CA0132), No Sound At All; Broken Beyond All Repair Status in ALSA driver: Unknown Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Debian: New Bug description: [WORKAROUND] Run the following command: echo "options snd-hda-intel position_fix=1" | sudo tee -a /etc/modprobe.d/alsa-base.conf [EDIT] Workaround doesn't work anymore for me at least. I assume it only has a small possibility of working due to a firmware bug. [ORIGINAL REPORT] No sound, no jacks; It is detected by Linux however. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Mon Apr 8 18:56:44 2013 InstallationDate: Installed on 2013-04-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Creative failed Symptom_Card: HDA Creative - HDA Creative Symptom_Type: No sound at all Title: [To be filled by O.E.M., Creative CA0132, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: SABERTOOTH 990FX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd03/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnSABERTOOTH990FX:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1166529/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Bart van Deenan's solution worked for me under Ubuntu 16.10 but under 17.04 it seems to no longer fix the issue and headphones produce no sound. Dell XPS 15 9550 Ubuntu 17.04 4.10.0-20-generic -- 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 1678498] Re: Resolution options for external display/monitor are incomplete
** Summary changed: - Resolution options for external monitor are incomplete + Resolution options for external display/monitor are incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1678498 Title: Resolution options for external display/monitor are incomplete Status in xorg package in Ubuntu: New Bug description: Usually when I plug in an external monitor (when awake, or before waking from suspend), my external display is rendered with 1024x768 resolution, and this is the highest resolution displayed by xrandr: DP-2 connected 1024x768+1920+0 (normal left inverted right x axis y axis) 0mm x 0mm 1024x768 60.00* 800x600 60.3256.25 848x480 60.00 640x480 59.94 But in fact if I reboot I get the full set of options back (1680x) for that monitor. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-45.48-generic 4.8.17 Uname: Linux 4.8.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 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: Sat Apr 1 12:17:13 2017 DistUpgraded: 2017-01-21 16:13:06,191 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: yakkety DistroVariant: ubuntu DpkgLog: EcryptfsInUse: Yes ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] InstallationDate: Installed on 2016-02-12 (413 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-45-generic.efi.signed root=UUID=ea2fb511-8d62-4b96-bdaa-4b3f7bf79cc6 ro noprompt quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to yakkety on 2017-01-21 (69 days ago) dmi.bios.date: 11/06/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET54WW (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Sat Apr 1 09:52:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1678498/+subscriptions -- Mailing list: https://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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
On Wed, Apr 26, 2017 at 11:20:47PM -, Julian Andres Klode wrote: > pabs just mentioned in #debian-apt that we could probably drop the > ConditionACPower for the downloading service. I'm not sure why that was > originally added, if only to protect upgrades or to save power when > downloading, if anyone has an opinion, let me know. Agreed, it should be ok to drop this. I believe the original rationale is that you don't want to *apply* an upgrade while on battery, since running out of power during the upgrade is Very Bad. But downloads should be ok. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
Re systemd conflict handling, I can ask systemd ML tomorrow. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
pabs just mentioned in #debian-apt that we could probably drop the ConditionACPower for the downloading service. I'm not sure why that was originally added, if only to protect upgrades or to save power when downloading, if anyone has an opinion, let me know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554848] Re: Please randomise automatic updates over a longer period
See LP bug #1686470. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Confirmed Status in unattended-upgrades source package in Trusty: Confirmed Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Bug description: Load on the main Ubuntu archive servers is rather peakish, and tends to create a traffic peak on our Internet links at fairly regular times each day, preventing customers from accessing the archive. This impacts the cloud archive mirrors using the ubuntu-repository-cache charm also, because they are hitting a squid cache which is backed by the main archive. This effect will be even more pronounced under the recently-announced automatic update policy for xenial. One solution which would alleviate this to some extent would be to spread the load over a longer period by increasing the random sleep time in the daily update script from 30 minutes to, say, 1-2 hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1554848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686544] [NEW] sudo fails to retrieve groups in sudoUser
Public bug reported: Currently using sudo with sssd 1.13.4 on xenial to manage sudo rules, groups are not resolved since last update. I troubleshooted : - sudo with all@debug - sssd with [sudo] debug_level = 9 and [domain/domain.tld] debug_level = 9 - LDAP requests are correctly sent, and I can obtain correct rules - SSSD cache is correctly stored too, I can successfully ldbsearch into! I had to downgrade sudo (1.8.16-0ubuntu1.3) xenial to sudo (1.8.16-0ubuntu1) xenial, to get my groups working again. I tried sudo 1.8.19, with no luck. Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1: sudoCommand: /bin/mount sudoHost: ALL sudoUser: ALL Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1: sudoCommand: /bin/mount sudoHost: ALL sudoUser: #uid Broken since 1.8.16-0ubuntu1.3: sudoCommand: /bin/mount sudoHost: ALL sudoUser: %mygroup Broken in 1.8.16-0ubuntu1.3: sudoCommand: /bin/mount sudoHost: ALL sudoUser: myuser Patch sssd-doesnt-handle-netgroups.diff seems to break something... ** Affects: sudo (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sssd.conf" https://bugs.launchpad.net/bugs/1686544/+attachment/4868405/+files/sssd.conf -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1686544 Title: sudo fails to retrieve groups in sudoUser Status in sudo package in Ubuntu: New Bug description: Currently using sudo with sssd 1.13.4 on xenial to manage sudo rules, groups are not resolved since last update. I troubleshooted : - sudo with all@debug - sssd with [sudo] debug_level = 9 and [domain/domain.tld] debug_level = 9 - LDAP requests are correctly sent, and I can obtain correct rules - SSSD cache is correctly stored too, I can successfully ldbsearch into! I had to downgrade sudo (1.8.16-0ubuntu1.3) xenial to sudo (1.8.16-0ubuntu1) xenial, to get my groups working again. I tried sudo 1.8.19, with no luck. Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1: sudoCommand: /bin/mount sudoHost: ALL sudoUser: ALL Working in 1.8.16-0ubuntu1.3 and 1.8.16-0ubuntu1: sudoCommand: /bin/mount sudoHost: ALL sudoUser: #uid Broken since 1.8.16-0ubuntu1.3: sudoCommand: /bin/mount sudoHost: ALL sudoUser: %mygroup Broken in 1.8.16-0ubuntu1.3: sudoCommand: /bin/mount sudoHost: ALL sudoUser: myuser Patch sssd-doesnt-handle-netgroups.diff seems to break something... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1686544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day
done, thanks! ** Changed in: apt (Ubuntu Zesty) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: Won't Fix Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- Mailing list: https://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 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
On Wed, Apr 26, 2017 at 08:39:36PM -, Julian Andres Klode wrote: > I think the "locking" is already done by systemd. When units specify an > ordering, it seems that one unit will only start when the other has shut > down: > "Given two units with any ordering dependency between them, if one unit > is shut down and the other is started up, the shutdown is ordered before > the start-up" That language sounds very general; it's probably worth having someone explicitly check this for our case before committing to rely on systemd :) ** Summary changed: - Apt updates that are uniformally spread across all timezones, with predictable application windows + Apt updates that are uniformly spread across all timezones, with predictable application windows -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
xenial_openssl_lp1674399.debdiff ** Patch added: "xenial_openssl_lp1674399.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/+attachment/4868386/+files/xenial_openssl_lp1674399.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1674399 Title: OpenSSL CPU detection for AMD Ryzen CPUs Status in openssl package in Ubuntu: In Progress Status in openssl source package in Xenial: In Progress Status in openssl source package in Zesty: In Progress Status in openssl source package in Artful: In Progress Bug description: [Impact] * Context: AMD added support in their processors for SHA Extensions[1] (CPU flag: sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit only (Confirmed with AMD representative). Current OpenSSL version in Ryzens still calls SHA for SSSE3 routine as result a number of extensions were effectively masked on Ryzen and shows no improvement. [1] /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD Ryzen 5 1600 Six-Core Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse 4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold [2] - sha_ni: SHA1/SHA256 Instruction Extensions [3] - https://en.wikipedia.org/wiki/Ryzen ... All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5] ... * Program to performs the CPUID check: Reference : https://software.intel.com/en-us/articles/intel-sha-extensions ... Availability of the Intel® SHA Extensions on a particular processor can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function, using inline assembly, performs the CPUID check: -- int CheckForIntelShaExtensions() { int a, b, c, d; // Look for CPUID.7.0.EBX[29] // EAX = 7, ECX = 0 a = 7; c = 0; asm volatile ("cpuid" :"=a"(a), "=b"(b), "=c"(c), "=d"(d) :"a"(a), "c"(c) ); // Intel® SHA Extensions feature bit is EBX[29] return ((b >> 29) & 1); } -- On CPU with sha_ni the program return "1". Otherwise it return "0". [Test Case] * Reproducible with Xenial/Zesty/Artful release. * Generated a checksum of a big file (e.g. 5GB file) with openssl $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile SHA256(/var/tmp/5Gfile)= 8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8 real 0m12.835s user 0m12.344s sys 0m0.484s * Openssl speed $ openssl speed sha1 Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s OpenSSL 1.0.2g 1 Mar 2016 built on: reproducible build, date unspecified options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) blowfish(idx) compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55 The performance are clearly better when using the patch which take benefit of the sha extension. (See Regression Potential section for result with patch) [Regression Potential] * Note : IRC discussion with infinity : https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8 * Note from irc discussion with apw and rbasak : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2 * It basically allow openssl to take benefit of sha extension potential (mostly performance-wise) now that new AMD cpu starting to have the capability. * The code check the
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
zesty_openssl_lp1674399.debdiff ** Patch added: "zesty_openssl_lp1674399.debdiff" https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/+attachment/4868385/+files/zesty_openssl_lp1674399.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1674399 Title: OpenSSL CPU detection for AMD Ryzen CPUs Status in openssl package in Ubuntu: In Progress Status in openssl source package in Xenial: In Progress Status in openssl source package in Zesty: In Progress Status in openssl source package in Artful: In Progress Bug description: [Impact] * Context: AMD added support in their processors for SHA Extensions[1] (CPU flag: sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit only (Confirmed with AMD representative). Current OpenSSL version in Ryzens still calls SHA for SSSE3 routine as result a number of extensions were effectively masked on Ryzen and shows no improvement. [1] /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD Ryzen 5 1600 Six-Core Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse 4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold [2] - sha_ni: SHA1/SHA256 Instruction Extensions [3] - https://en.wikipedia.org/wiki/Ryzen ... All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5] ... * Program to performs the CPUID check: Reference : https://software.intel.com/en-us/articles/intel-sha-extensions ... Availability of the Intel® SHA Extensions on a particular processor can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function, using inline assembly, performs the CPUID check: -- int CheckForIntelShaExtensions() { int a, b, c, d; // Look for CPUID.7.0.EBX[29] // EAX = 7, ECX = 0 a = 7; c = 0; asm volatile ("cpuid" :"=a"(a), "=b"(b), "=c"(c), "=d"(d) :"a"(a), "c"(c) ); // Intel® SHA Extensions feature bit is EBX[29] return ((b >> 29) & 1); } -- On CPU with sha_ni the program return "1". Otherwise it return "0". [Test Case] * Reproducible with Xenial/Zesty/Artful release. * Generated a checksum of a big file (e.g. 5GB file) with openssl $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile SHA256(/var/tmp/5Gfile)= 8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8 real 0m12.835s user 0m12.344s sys 0m0.484s * Openssl speed $ openssl speed sha1 Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s OpenSSL 1.0.2g 1 Mar 2016 built on: reproducible build, date unspecified options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) blowfish(idx) compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55 The performance are clearly better when using the patch which take benefit of the sha extension. (See Regression Potential section for result with patch) [Regression Potential] * Note : IRC discussion with infinity : https://bugs.launchpad.net/ubuntu/xenial/+source/openssl/+bug/1674399/comments/8 * Note from irc discussion with apw and rbasak : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2 * It basically allow openssl to take benefit of sha extension potential (mostly performance-wise) now that new AMD cpu starting to have the capability. * The code check the
[Touch-packages] [Bug 1686522] [NEW] Network Manager frequently disconnects wlan0
Public bug reported: In syslog there are multiple lines: wlan0: CTRL-EVENT-DISCONNECTED reason=4 locally_generated=1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.3 ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39 Uname: Linux 3.13.0-117-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Wed Apr 26 16:56:26 2017 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-27 (242 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_IE:en TERM=linux PATH=(custom, no user) LANG=en_IE.UTF-8 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1686522 Title: Network Manager frequently disconnects wlan0 Status in network-manager package in Ubuntu: New Bug description: In syslog there are multiple lines: wlan0: CTRL-EVENT-DISCONNECTED reason=4 locally_generated=1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.3 ProcVersionSignature: Ubuntu 3.13.0-117.164-generic 3.13.11-ckt39 Uname: Linux 3.13.0-117-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Wed Apr 26 16:56:26 2017 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-08-27 (242 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IpRoute: default via 192.168.1.1 dev wlan0 proto static 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.3 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: LANGUAGE=en_IE:en TERM=linux PATH=(custom, no user) LANG=en_IE.UTF-8 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1686522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
Here's the highligh of the discussion I had in #ubuntu-release with infinity about my proposal in comment #6. For SRU, I had a talk with apw and rbasak about this bug a couples weeks ago LP: #1674399, could you please look at this bug and based on the Descriptions and comment #6 if this looks eligible for SRU in Stable release ? (note that this is a HW enablement, not a bug, this is why I'm requesting you to have a look at it) thanks in advance. slashd: I disagree with your reasoning for not fixing both 64 and 32. slashd: Lots of people run 64/32 multiarch and would benefit from fixing both. infinity, I'm fine with fixing 32bit, I proposed that approach cause apw wanted to self-contained the fix as much as possible That doesn't really contain it much. ;) infinity, so what if I do the same proposition but including 32-bit in stable release, would that work for you ? slashd: Conceptually, I have no issues with the plan (other than the "please do 32-bit too" comment). infinity, sure, I'm actually glad you are keen to see the 32-bit portion included slashd: Upload away, IMO. infinity, I'll then start the upload for Artful, note that starting next week I'll be gone for 2 weeks for sprints, and won't be able to do much testing, so do you think it's preferable we only start the SRU when I get back or we upload this week and worst case it will languish in -proposed for ~2weeks which will allow ppls to test with no stress (if any volunteer) slashd: I think letting it fester in proposed for two weeks to see if we get random negative feedback is entirely fine. Obviously, I'll delete/revert it if it breaks anything, but I don't need you around for that. slashd: 2 weeks of random user installations plus you executing a more precision test plan should give us solid confidence. ** Description changed: [Impact] * Context: AMD added support in their processors for SHA Extensions[1] (CPU flag: sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit only (Confirmed with AMD representative). Current OpenSSL version in Ryzens still calls SHA for SSSE3 routine as result a number of extensions were effectively masked on Ryzen and shows no improvement. [1] /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD Ryzen 5 1600 Six-Core Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse 4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold [2] - sha_ni: SHA1/SHA256 Instruction Extensions [3] - https://en.wikipedia.org/wiki/Ryzen ... All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5] ... * Program to performs the CPUID check: Reference : https://software.intel.com/en-us/articles/intel-sha-extensions ... Availability of the Intel® SHA Extensions on a particular processor can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function, using inline assembly, performs the CPUID check: -- int CheckForIntelShaExtensions() { int a, b, c, d; // Look for CPUID.7.0.EBX[29] // EAX = 7, ECX = 0 a = 7; c = 0; asm volatile ("cpuid" :"=a"(a), "=b"(b), "=c"(c), "=d"(d) :"a"(a), "c"(c) ); // Intel® SHA Extensions feature bit is EBX[29] return ((b >> 29) & 1); } -- On CPU with sha_ni the program return "1". Otherwise it return "0". [Test Case] * Reproducible with Xenial/Zesty/Artful release. * Generated a checksum of a big file (e.g. 5GB file) with openssl $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile SHA256(/var/tmp/5Gfile)= 8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8 real 0m12.835s user 0m12.344s sys 0m0.484s * Openssl speed $ openssl speed sha1 Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s OpenSSL 1.0.2g 1 Mar 2016 built on: reproducible build, date unspecified options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial)
[Touch-packages] [Bug 1686520] [NEW] package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: poging tot overschrijven van '/lib/systemd/system/console-setup.service', wat ook in pakket
Public bug reported: idk what happened ProblemType: Package DistroRelease: Kali 2017.1 Package: console-setup-linux 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Apr 26 22:58:33 2017 ErrorMessage: poging tot overschrijven van '/lib/systemd/system/console-setup.service', wat ook in pakket keyboard-configuration 1.108ubuntu15.2 zit InstallationDate: Installed on 2014-03-14 (1139 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.23kali1 apt 1.2.12~ubuntu16.04.1 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: poging tot overschrijven van '/lib/systemd/system/console-setup.service', wat ook in pakket keyboard-configuration 1.108ubuntu15.2 zit UpgradeStatus: Upgraded to kali-rolling on 2016-11-11 (166 days ago) ** Affects: console-setup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kali-rolling third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1686520 Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: poging tot overschrijven van '/lib/systemd/system/console- setup.service', wat ook in pakket keyboard-configuration 1.108ubuntu15.2 zit Status in console-setup package in Ubuntu: New Bug description: idk what happened ProblemType: Package DistroRelease: Kali 2017.1 Package: console-setup-linux 1.108ubuntu15.2 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Apr 26 22:58:33 2017 ErrorMessage: poging tot overschrijven van '/lib/systemd/system/console-setup.service', wat ook in pakket keyboard-configuration 1.108ubuntu15.2 zit InstallationDate: Installed on 2014-03-14 (1139 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.23kali1 apt 1.2.12~ubuntu16.04.1 SourcePackage: console-setup Title: package console-setup-linux 1.108ubuntu15.2 failed to install/upgrade: poging tot overschrijven van '/lib/systemd/system/console-setup.service', wat ook in pakket keyboard-configuration 1.108ubuntu15.2 zit UpgradeStatus: Upgraded to kali-rolling on 2016-11-11 (166 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1686520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682934] Re: python3 in /usr/local/bin can cause python3 packages to fail to install
** Summary changed: - package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 + python3 in /usr/local/bin can cause python3 packages to fail to install ** Changed in: python3-defaults (Ubuntu) Status: Confirmed => Triaged ** Changed in: python3-defaults (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: python3 in /usr/local/bin can cause python3 packages to fail to install Status in python3-defaults package in Ubuntu: Triaged Bug description: Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: Package DistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 864735] Re: [ATI HDMI] HDMI Audio Disabled by Default (since oneiric)
This problem has shown up in 16.04 with alsamixer v1.1.0. Did someone remove the patch or fail to integrate the fix into 16.04 had to run alsamixer from terminal and unmute the speaker from there. Muting and un-muting in rhythem box does not fix the HDMI sound problem. -- 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/864735 Title: [ATI HDMI] HDMI Audio Disabled by Default (since oneiric) Status in alsa-driver package in Ubuntu: Fix Released Bug description: Since kernel 3.0, upstream has disabled audio output for all ATI cards in the Radeon driver by default. === Workaround 1 === Edit /etc/default/grub and change this line: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to this line GRUB_CMDLINE_LINUX_DEFAULT="quiet splash radeon.audio=1" Now run "sudo update-grub", then reboot your computer. === Or workaround 2 === Install the proprietary Catalyst driver. === There's no sound at all and videos playback in fast forward when outputting through the HDMI controller. This is a regression since it worked well in previous releases. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: alsa-base 1.0.24+dfsg-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: melvin 8335 F pulseaudio /dev/snd/pcmC1D3p: melvin 8335 F...m pulseaudio /dev/snd/controlC0: melvin 8335 F pulseaudio Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe6f4000 irq 16' Mixer name : 'Realtek ALC1200' Components : 'HDA:10ec0888,10ec0888,00100101' Controls : 38 Simple ctrls : 21 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfe8e8000 irq 19' Mixer name : 'ATI RS690/780 HDMI' Components : 'HDA:1002791a,00791a00,0010' Controls : 4 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sun Oct 2 12:46:40 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110929) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: RS780 Azalia controller - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [GT5676, ATI RS690/780 HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7B3G1P04 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: Not Available dmi.board.vendor: Gateway dmi.board.version: Not Available dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gateway dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7B3G1P04:bd02/18/2008:svnGateway:pnGT5676:pvr7B3G1P04:rvnGateway:rnNotAvailable:rvrNotAvailable:cvnGateway:ct3:cvr1.0: dmi.product.name: GT5676 dmi.product.version: 7B3G1P04 dmi.sys.vendor: Gateway To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/864735/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
I think the "locking" is already done by systemd. When units specify an ordering, it seems that one unit will only start when the other has shut down: "Given two units with any ordering dependency between them, if one unit is shut down and the other is started up, the shutdown is ordered before the start-up" -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1674399 Title: OpenSSL CPU detection for AMD Ryzen CPUs Status in openssl package in Ubuntu: In Progress Status in openssl source package in Xenial: In Progress Status in openssl source package in Zesty: In Progress Status in openssl source package in Artful: In Progress Bug description: [Impact] * Context: AMD added support in their processors for SHA Extensions[1] (CPU flag: sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit only (Confirmed with AMD representative). Current OpenSSL version in Ryzens still calls SHA for SSSE3 routine as result a number of extensions were effectively masked on Ryzen and shows no improvement. [1] /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD Ryzen 5 1600 Six-Core Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse 4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold [2] - sha_ni: SHA1/SHA256 Instruction Extensions [3] - https://en.wikipedia.org/wiki/Ryzen ... All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5] ... * Program to performs the CPUID check: Reference : https://software.intel.com/en-us/articles/intel-sha-extensions ... Availability of the Intel® SHA Extensions on a particular processor can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function, using inline assembly, performs the CPUID check: -- int CheckForIntelShaExtensions() { int a, b, c, d; // Look for CPUID.7.0.EBX[29] // EAX = 7, ECX = 0 a = 7; c = 0; asm volatile ("cpuid" :"=a"(a), "=b"(b), "=c"(c), "=d"(d) :"a"(a), "c"(c) ); // Intel® SHA Extensions feature bit is EBX[29] return ((b >> 29) & 1); } -- On CPU with sha_ni the program return "1". Otherwise it return "0". [Test Case] * Reproducible with Xenial/Zesty/Artful release. * Generated a checksum of a big file (e.g. 5GB file) with openssl $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile SHA256(/var/tmp/5Gfile)= 8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8 real 0m12.835s user 0m12.344s sys 0m0.484s * Openssl speed $ openssl speed sha1 Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s OpenSSL 1.0.2g 1 Mar 2016 built on: reproducible build, date unspecified options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) blowfish(idx) compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55 The performance are clearly better when using the patch which take benefit of the sha extension. (See Regression Potential section for result with patch) [Regression Potential] * Note from irc discussion with apw and rbasak : [10:03:20] slashd, for me some new functionality like that is ok as long as it is very self-contained so easy to review and confirm is only used on the new h/w [10:03:52] one of our main goals is to avoid regressions [10:12:24] The SRU policy does explicitly permit hardware enablement in an LTS IIRC, though I'd expect ~ubuntu-sru to be involved in mitigating risk and making the final risk decision, FWIW. Full discussion: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2 * It basically allow openssl to take benefit of sha
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
APT maintains a multitude of internal time stamp files preventing updates occuring more than once per day. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
Justifications for twice a day: - to get motd updated & get upgrade popups on the desktop. - to have a better chance of having critical security fixes downloaded, before the next upgrade window. - in case of intermittent network losses, having two download attempts is better than one. - machines that are off overnight (office workers), with twice daily download have a better chance of downloading updates during office hours; instead of effectively always on boot. - i like it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
Why should apt update be run twice a day if the updates are only applied to the system once a day? This would be: - a no-op for any metadata that hasn't changed in the preceding 12h - a wasteful, redundant download for metadata that *has* changed in the preceding 12h - (in rare cases) very wasteful if two SRUs are published back-to-back in the same day, since the first will be downloaded but not applied. If the purpose is to ensure the updates being applied are never more than 12 hours out of date, that can be achieved with a single apt update scheduled in the 12h before 6am machine time. If the purpose is to ensure downloads are spread more evenly around the clock, that is better achieved by doing one apt update per day, with a 24h smear, instead of two per day. (And btw, we probably want locking between the two jobs, so that we don't try to run an 'apt update' /while/ unattended-upgrades are being applied, but instead wait for unattended-upgrades to finish) If your goal is to try to achieve some sort of balance between these goals, that at least makes sense why the design would be this way; but I think overall it's better to just do a single 24h smear and not try to compromise in a way that increases overall load on the mirrors with no major benefit to the users. Can you please also document this design on wiki.ubuntu.com, so that we have better history tracking of any further changes (vs. edits to a bug description) and can more easily refer to it rather than pointing to an (at some point) ancient bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
Attaching Artful debdiff ** Patch added: "artful_openssl_lp1674399.debdiff" https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/+attachment/4868343/+files/artful_openssl_lp1674399.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1674399 Title: OpenSSL CPU detection for AMD Ryzen CPUs Status in openssl package in Ubuntu: In Progress Status in openssl source package in Xenial: In Progress Status in openssl source package in Zesty: In Progress Status in openssl source package in Artful: In Progress Bug description: [Impact] * Context: AMD added support in their processors for SHA Extensions[1] (CPU flag: sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit only (Confirmed with AMD representative). Current OpenSSL version in Ryzens still calls SHA for SSSE3 routine as result a number of extensions were effectively masked on Ryzen and shows no improvement. [1] /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD Ryzen 5 1600 Six-Core Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse 4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold [2] - sha_ni: SHA1/SHA256 Instruction Extensions [3] - https://en.wikipedia.org/wiki/Ryzen ... All models support: x87, MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, AES, CLMUL, AVX, AVX2, FMA, CVT16/F16C, ABM, BMI1, BMI2, SHA.[5] ... * Program to performs the CPUID check: Reference : https://software.intel.com/en-us/articles/intel-sha-extensions ... Availability of the Intel® SHA Extensions on a particular processor can be determined by checking the SHA CPUID bit in CPUID.(EAX=07H, ECX=0):EBX.SHA [bit 29]. The following C function, using inline assembly, performs the CPUID check: -- int CheckForIntelShaExtensions() { int a, b, c, d; // Look for CPUID.7.0.EBX[29] // EAX = 7, ECX = 0 a = 7; c = 0; asm volatile ("cpuid" :"=a"(a), "=b"(b), "=c"(c), "=d"(d) :"a"(a), "c"(c) ); // Intel® SHA Extensions feature bit is EBX[29] return ((b >> 29) & 1); } -- On CPU with sha_ni the program return "1". Otherwise it return "0". [Test Case] * Reproducible with Xenial/Zesty/Artful release. * Generated a checksum of a big file (e.g. 5GB file) with openssl $ time /usr/bin/openssl dgst -sha256 /var/tmp/5Gfile SHA256(/var/tmp/5Gfile)= 8d448d81521cbc1bfdc04dd199d448bd3c49374221007bd0846d8d39a70dd4f8 real 0m12.835s user 0m12.344s sys 0m0.484s * Openssl speed $ openssl speed sha1 Doing sha1 for 3s on 16 size blocks: 9969152 sha1's in 3.00s Doing sha1 for 3s on 64 size blocks: 8019164 sha1's in 3.00s Doing sha1 for 3s on 256 size blocks: 5254219 sha1's in 2.99s Doing sha1 for 3s on 1024 size blocks: 2217067 sha1's in 3.00s Doing sha1 for 3s on 8192 size blocks: 347842 sha1's in 3.00s OpenSSL 1.0.2g 1 Mar 2016 built on: reproducible build, date unspecified options:bn(64,64) rc4(8x,int) des(idx,cisc,16,int) aes(partial) idea(int) blowfish(idx) compiler: gcc -I. -I.. -I../include -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H -Wa,--noexecstack -m64 -DL_ENDIAN -O3 -Wall -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DMD5_ASM -DAES_ASM -DVPAES_ASM -DBSAES_ASM -DWHIRLPOOL_ASM -DGHASH_ASM -DECP_NISTZ256_ASM The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha1 53168.81k 171075.50k 449859.55k 756758.87k 949840.55 The performance are clearly better when using the patch which take benefit of the sha extension. (See Regression Potential section for result with patch) [Regression Potential] * Note from irc discussion with apw and rbasak : [10:03:20] slashd, for me some new functionality like that is ok as long as it is very self-contained so easy to review and confirm is only used on the new h/w [10:03:52] one of our main goals is to avoid regressions [10:12:24] The SRU policy does explicitly permit hardware enablement in an LTS IIRC, though I'd expect ~ubuntu-sru to be involved in mitigating risk and making the
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
Fixed in ubuntu2. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
Hmm, seems I forgot to change the downloading to run when unattended- upgrades is configured. But this seems like a bad choice anyway with the current implementation. Maybe let's do something like if which unattended-upgrade >/dev/null 2>&1 && check_stamp $DOWNLOAD_UPGRADEABLE_STAMP $UnattendedUpgradeInterval; then if unattended-upgrade -d $XUUPOPT; then update_stamp $UPGRADE_STAMP debug_echo "unattended-upgrade -d (success)" else debug_echo "unattended-upgrade -d (error)" fi else debug_echo "unattended-upgrade -d (not run)" fi That is, don't download the upgrades with apt -d dist-upgrade, use unattended-upgrade -d. This uses the same stamp file as the current list-upgrade option, but compares it against the unattended-upgrades section, and contains the unattended-upgrade body, with -d appended. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day
@vorlon Also drop the zesty one from the unapproved queue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: In Progress Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686500] [NEW] package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned
Public bug reported: Just doing a new upgrade install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 11:42:04 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-06-22 (307 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-04-26 (0 days ago) ** Affects: hicolor-icon-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1686500 Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned Status in hicolor-icon-theme package in Ubuntu: New Bug description: Just doing a new upgrade install. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: hicolor-icon-theme 0.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59 Uname: Linux 4.4.0-75-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Wed Apr 26 11:42:04 2017 Dependencies: ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2016-06-22 (307 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.20 SourcePackage: hicolor-icon-theme Title: package hicolor-icon-theme 0.15-0ubuntu1 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to xenial on 2017-04-26 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1686500/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674399] Re: OpenSSL CPU detection for AMD Ryzen CPUs
[For SRU Verification team] Context : Previous IRC discussion with apw/rbasak about this case : https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1674399/comments/2 AMD released a new CPU called "Ryzen" that now support "Intel SHA extensions" technology. In current Ubuntu openssl package sha extension are masked on Ryzen CPU. Ryzen is available in 64-bit only CPU (Confimed with AMD representative). There are upstream patches that solve this situation and my test revealed that openssl has significant performance increase on a AMD CPU with sha extension capability. The upstream patches "f8418d8" & "1aed5e1" fix the situation by moving the extended feature detection from Label (.Lintel) to Label (.Lgeneric) in both 64-bit(crypto/x86_64cpuid.pl) & 32-bit (crypto/x86cpuid.pl) code where it should belongs now that non-intel CPU can also have the capability. I cannot strictly isolate the fix for Ryzen CPU only, meaning that this feature will enable sha extension for all CPUa that support the functionality, where prior this patch it was strictly reserved for Intel CPU only. Since I don't forsee a lot of users using the 32-bit package of opensssl on a 64-bit CPU with sha extension enabled and putting myself in a SRU mindset, I proposed the following : - SRU the 64-bit and 32-bit patch in development release (Artful/17.10) - SRU the 64 bit only in Stable release (Xenial/Zesty) - 32-bit code : Remain the same, thus no behavioural change - 64-bit code : Enable sha extension for 64-bit CPU that has the capabilities. The test that I proposed before "verification-done" (while package is in -proposed) -> Do a performance test using openssl speed[1] & generate a checksum on a big file[2] (e.g. 5GB) and capture the metric to compare before and after the patch on a 64-bit AMD system WITH sha extension capability (Ryzen). -> Do a performance test using openssl speed[1] & generate a checksum on a big file[2] (e.g. 5GB) and capture the metric to compare before and after the patch on a 64-bit AMD system WITHOUT sha extension capability. -> Do a performance test using openssl speed[1] & generate a checksum on a big file[2] (e.g. 5GB) and capture the metric to compare before and after the patch on a 64-bit Intel system WITH sha extension capability. -> Do a performance test using openssl speed[1] & generate a checksum on a big file[2] (e.g. 5GB) and capture the metric to compare before and after the patch on a 64-bit Intel system WITHOUT sha extension capability. -> In all the above tests, using perf record/annotate could also be done to validate if the sha instructions has been used or not depending on the above scenarios to conclude everything is working as expected. No extra testing will be needed for 32-bit package since no 32-bit code will be modified. On the other hand, if a user for some reason want to use openssl in 32-bit on a 64-bit with sha extension CPU capabilities, then this user won't have all the performance benefit of the 64-bit code fix. Considering that this request is a "HW enablement", thus not a bugfix and the above notes... Is this would be eligible for SRU in Stable Release ? [1] - Openssl speed measurement using sha1 $ openssl speed sha1 [2] - Measure time performance of generating a checksum of a big file (e.g. 5GB) $ time openssl dgst -sha256 /var/tmp/5Gfile -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1674399 Title: OpenSSL CPU detection for AMD Ryzen CPUs Status in openssl package in Ubuntu: In Progress Status in openssl source package in Xenial: In Progress Status in openssl source package in Zesty: In Progress Status in openssl source package in Artful: In Progress Bug description: [Impact] * Context: AMD added support in their processors for SHA Extensions[1] (CPU flag: sha_ni[2]) starting with Ryzen[3] CPU. Note that Ryzen CPU come in 64bit only (Confirmed with AMD representative). Current OpenSSL version in Ryzens still calls SHA for SSSE3 routine as result a number of extensions were effectively masked on Ryzen and shows no improvement. [1] /proc/cpuinfo processor : 0 vendor_id : AuthenticAMD cpu family : 23 model : 1 model name : AMD Ryzen 5 1600 Six-Core Processor flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclmulqdq monitor ssse3 fma cx16 sse 4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_l2 mwaitx hw_pstate vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflusho pt sha_ni xsaveopt xsavec xgetbv1 clzero arat npt lbrv svm_lock nrip_save
[Touch-packages] [Bug 1569719] Re: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3
*** This bug is a duplicate of bug 1682934 *** https://bugs.launchpad.net/bugs/1682934 ** This bug has been marked a duplicate of bug 1682934 package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1569719 Title: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3 Status in python3-defaults package in Ubuntu: Confirmed Bug description: Upgraded to Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 12 12:33:05 2016 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-01-16 (453 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to xenial on 2016-04-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1569719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day
I have removed the apt SRU from {xenial,yakkety}-proposed per the preceding comment. ** Changed in: apt (Ubuntu Xenial) Status: Fix Committed => Won't Fix ** Changed in: apt (Ubuntu Yakkety) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Won't Fix Status in apt source package in Yakkety: Won't Fix Status in apt source package in Zesty: In Progress Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682934] Re: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3
The problem here is that python's postinst scripts call python without a qualified path: (base)adconrad@nosferatu:~/py/python3.5-3.5.3$ rgrep '@PVER@ -E' debian/libPVER-testsuite.postinst.in: @PVER@ -E -S /usr/lib/@PVER@/py_compile.py $files debian/libPVER-testsuite.postinst.in: @PVER@ -E -S -O /usr/lib/@PVER@/py_compile.py $files debian/PVER-dbg.postinst.in:@PVER@ -E -S /usr/lib/@PVER@/py_compile.py $files debian/PVER-dbg.postinst.in:@PVER@ -E -S -O /usr/lib/@PVER@/py_compile.py $files debian/PVER-venv.postinst.in: @PVER@ -E -S /usr/lib/@PVER@/py_compile.py $files debian/PVER-venv.postinst.in: @PVER@ -E -S -O /usr/lib/@PVER@/py_compile.py $files debian/PVER-minimal.postinst.in:@PVER@ -E -S /usr/lib/@PVER@/py_compile.py $files debian/PVER-minimal.postinst.in:@PVER@ -E -S -O /usr/lib/@PVER@/py_compile.py $files debian/PVER.postinst.in:@PVER@ -E -S /usr/lib/@PVER@/py_compile.py $files debian/PVER.postinst.in:@PVER@ -E -S -O /usr/lib/@PVER@/py_compile.py $files All of those should have /usr/bin prepended to make sure we're getting the *right* python. Odds are this same bug is in all python versions (or, at least, all python3 versions), given they likely share common packaging, as evidenced by the magic @PVER@ substitution. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1682934 Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 Status in python3-defaults package in Ubuntu: Confirmed Bug description: Got this error while using "Transmageddon Video Transcoder" and again while updating 16.10 to 17.04. Seems to have something to do with needing that Python3 version for Teletext decoding in media that is in transport stream format (.ts). ProblemType: Package DistroRelease: Ubuntu 17.04 Package: python3 3.5.1-4 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Fri Apr 14 19:27:33 2017 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-05-01 (714 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: python3-defaults Title: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to zesty on 2017-04-14 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1682934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
Uploaded 1.4.1ubuntu1 to artful which introduces the apt-daily-upgrade timer and service matching the proposed default behavior. ** Changed in: apt (Ubuntu Artful) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Committed Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Fix Committed Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1586787] Re: Wrong colors on external TV
I managed to solve my issue: I found a passive DisplayPort to HDMI adapter that works (the colors on the TV are as expected). But I still think that there is a software issue, or an issue that ca be solved with software, since with the exact same hardware the colors are fine with certain software. -- 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/1586787 Title: Wrong colors on external TV Status in xorg package in Ubuntu: New Bug description: Hi, On a Lenovo Thinkpad T420, with an Intel Core i5-2520M CPU and integrated graphics, when using a Samsung UE40J5200AW 40in TV with a DisplayPort to HDMI adapter and an HDMI cable, the colors are very wrong on the TV. This happens on a brand new Ubuntu 16.04 installation made from scratch, and it does not happen when I boot from a Linux Mint 17.3 "Rosa" Cinnamon 64-bit live DVD. So same laptop, same adapter, same cable, same TV, and the colors are fine on the TV in this case (Mint live DVD). Also, when switching the laptop with a Dell running Windows 8.1 (so the same adapter, cable, and TV are used), the colors are again fine. I have attached a picture that shows the laptop screen in front of the TV screen with the display mirrored. So both screens should look the same in the picture. But it looks like only the white color is the same, while the rest of the colors are very different. Thanks for your help, Alin. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Date: Sun May 29 17:47:11 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller [17aa:21ce] InstallationDate: Installed on 2016-05-06 (22 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 4236BH1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/05/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 83ET76WW (1.46 ) dmi.board.asset.tag: Not Available dmi.board.name: 4236BH1 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr83ET76WW(1.46):bd07/05/2013:svnLENOVO:pn4236BH1:pvrThinkPadT420:rvnLENOVO:rn4236BH1:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 4236BH1 dmi.product.version: ThinkPad T420 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Sun May 29 17:45:29 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 738 vendor LGD xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1586787/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1684213] Re: Intel Wireless 7260 often crashes
Issue definitely persists on 4.11/upstream. I came across an interesting output in dmesg which may explain why bluetooth works while the WiFi doesn't: [17326.525545] iwlwifi :01:00.0: Could not load the [0] uCode section [17326.525697] iwlwifi :01:00.0: Failed to start INIT ucode: -5 [17326.525702] iwlwifi :01:00.0: Failed to run INIT ucode: -5 [17326.525705] iwlwifi :01:00.0: Failed to start RT ucode: -5 [17391.638774] usb 1-4: USB disconnect, device number 64 [17392.015275] usb 1-4: new full-speed USB device number 65 using xhci_hcd [17392.156505] usb 1-4: New USB device found, idVendor=8087, idProduct=07dc [17392.156520] usb 1-4: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [17392.179288] Bluetooth: hci0: read Intel version: 3707100180012d0d00 [17392.179426] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-hw-37.7.10-fw-1.80.1.2d.d.bseq [17392.367199] Bluetooth: hci0: Intel Bluetooth firmware patch completed and activated What's interesting is that iwlwifi "can't load" the uCode/firmware, causing the internet/wifi portion to fail, but Bluetooth uses a separate firmware file on the same card, which itself works fine. So this probably explains why the bluetooth still works. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1684213 Title: Intel Wireless 7260 often crashes Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Status in network-manager package in Ubuntu: New Bug description: Hardware: Acer CB3-131 Chromebook (GNAWTY) running Ubuntu Mate natively (BIOS enabled by SeaBIOS firmware from scripts here:https://mrchromebox.tech/). Uses Intel 7260 wifi, rev. bb: 01:00.0 Network controller: Intel Corporation Wireless 7260 (rev bb) Software: Ubuntu Mate 17.04, upgraded from 16.10. Currently, everything (kernel, firmware, etc.) is stock. Issue has persisted across multiple installations. Bug: Wifi/Bluetooth crashes and refuses to come back up, even after multiple reboots. Issue persists across distros (Arch, Ubuntu, etc.) When the wireless (Bluetooth and WiFi) works, it works flawlessly. However, upon boot, it is not uncommon for the wireless to stop working within two minutes of login time. Curiously, the GUI usually still shows being "connected", though trying to change anything with the wifi shows otherwise. Other times, upon system resume when wireless was previously working, the GUI will show "device not ready" and refuse to continue. Dmesg shows the following: [ 423.814823] Bluetooth: hci0 command 0x1403 tx timeout [ 424.172973] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 424.173062] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 424.173067] iwlwifi :01:00.0: Scan failed! ret -5 [ 425.194487] iwlwifi :01:00.0: Failed to wake NIC for hcmd [ 425.194589] iwlwifi :01:00.0: Error sending SCAN_OFFLOAD_REQUEST_CMD: enqueue_hcmd failed: -5 [ 425.194593] iwlwifi :01:00.0: Scan failed! ret -5 Solution: Rebooting doesn't fix the problem. Perhaps a different firmware version will work better? Configuration settings? etc.? Unknown. Thanks ahead of time for the help. Let me know if there's anything you need/commands I should run/solutions I can attempt. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bmueller 1669 F pulseaudio CurrentDesktop: MATE Date: Wed Apr 19 10:34:11 2017 InstallationDate: Installed on 2017-04-13 (6 days ago) InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Release amd64 (20161012.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:07dc Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Gnawty ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic root=UUID=45b1dd3f-10df-4a28-904c-74c694ef75a5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-04-16 (2 days ago) dmi.bios.date: 08/16/2015 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias:
[Touch-packages] [Bug 1681528] Re: Include information about python versions
Also as seen in bug 1682934 python versions in /usr/local/bin can also negatively affect package installations and removals. Apport should also check for these. ** Description changed: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... - File "/usr/bin/pyclean", line 63 - except (IOError, OSError), e: - ^ + File "/usr/bin/pyclean", line 63 + except (IOError, OSError), e: + ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are - symlinks to or doulbe check the versions of /usr/bin/python and + symlinks to or double check the versions of /usr/bin/python and /usr/bin/python3. -- 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/1681528 Title: Include information about python versions Status in apport package in Ubuntu: New Bug description: We are see lots of package installation failures that look like: package:apport:2.20.3-0ubuntu8 Preparing to unpack .../023-apport_2.20.3-0ubuntu8.2_all.deb ... File "/usr/bin/pyclean", line 63 except (IOError, OSError), e: ^ SyntaxError: invalid syntax One explanation for this is that pyclean is actually be run by python3 instead of python2.7. To confirm and invalidate reports like this apport should check to see what /usr/bin/python and /usr/bin/python3 are symlinks to or double check the versions of /usr/bin/python and /usr/bin/python3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1681528/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
(be?field.comment=(be ** Patch added: "diff -w diff" https://bugs.launchpad.net/ubuntu/artful/+source/unattended-upgrades/+bug/1686470/+attachment/4868325/+files/apt_lp1686470.diff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Triaged Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Triaged Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
I just do an if now instead of three files, and here is the implementation: https://github.com/Debian/apt/compare/master...julian- klode:lp1686470?diff=split=1=lp1686470 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Triaged Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Triaged Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591547] Re: Merge pcsc-lite 1.8.20-1 (main) from Debian testing (main)
Ping! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1591547 Title: Merge pcsc-lite 1.8.20-1 (main) from Debian testing (main) Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Please merge pcsc-lite 1.8.20-1 (main) from Debian testing (main) for bugs and security fixes. --- 1.8.20: Ludovic Rousseau 30 December 2016 - Fix a crash and potential security issue in pcscd 1.8.19: Ludovic Rousseau 9 December 2016 - SCardGetStatusChange(): Fix a (rare) race condition - Doxygen: . SCardGetStatusChange() may return SCARD_E_UNKNOWN_READER . SCardConnect() and SCardReconnect() will never return SCARD_E_NOT_READY - pcsc-spy: . fix display of execution time . log the thread number in the results - Some other minor improvements 1.8.18: Ludovic Rousseau 10 August 2016 - SCardDisconnect(): much faster with SCARD_UNPOWER_CARD - SCardConnect(): Fix a possible duplicated hCard context - Fix compilation on FreeBSD - Fix compilation on Solaris - Some other minor improvements 1.8.17: Ludovic Rousseau 29 May 2016 - Fix SCardEndTransaction() issue with a SCARD_SHARE_EXCLUSIVE connection - Fix an issue when used with systemd (problem in signal handler) - SCardGetAttrib(): set pcbAttrLen when buffer is too small - Doxygen: SCardGetAttrib() pbAttr can be NULL - Doxygen: SCardGetAttrib() *pcbAttrLen contains the buffer size - fix compilation warnings and link errors on SunOS - Some other minor improvements 1.8.16: Ludovic Rousseau 20 March 2016 - SCardCancel() was not correctly handled When a SCardGetStatusChange() was cancelled then a next PC/SC call after the SCardGetStatusChange() may fail with a strange error code if the event waited in SCardGetStatusChange() occurs. - Doxygen: fix different documentation issues - SCARD_SCOPE_GLOBAL is now defined in a public header (even if never used) - Enable Trace and Profile features using compiler flags and without modifying the source code - Some other minor improvements and bug corrections 1.8.15: Ludovic Rousseau 25 December 2015 - Add support of remove and/or customize PC/SC reader names using PCSCLITE_FILTER_IGNORE_READER_NAMES and PCSCLITE_FILTER_EXTEND_READER_NAMES See http://ludovicrousseau.blogspot.fr/2015/12/remove-andor-customize-pcsc-reader-names.html - Some other minor improvements and bug corrections - Explanation of the Ubuntu delta: * Merge new upstream release from Debian Unstable (LP: #1483750). - debian/rules: Move runtime libraries to /lib, for the benefit of wpasupplicant. (See Debian #531592) Sorry, my packaging skills are zero, so that I can't work on this merge. - Changelog entries since current yakkety version 1.8.14-1ubuntu1: pcsc-lite (1.8.20-1) unstable; urgency=medium * New upstream release -- Ludovic RousseauFri, 30 Dec 2016 18:17:58 +0100 pcsc-lite (1.8.19-1) unstable; urgency=medium * New upstream release -- Ludovic Rousseau Fri, 09 Dec 2016 10:11:15 +0100 pcsc-lite (1.8.18-1) unstable; urgency=medium * New upstream release -- Ludovic Rousseau Wed, 10 Aug 2016 20:56:54 +0200 pcsc-lite (1.8.17-1) unstable; urgency=medium * New upstream release * debian/control: Standards-Version: 3.9.7 -> 3.9.8. No change needed. -- Ludovic Rousseau Sun, 29 May 2016 17:30:12 +0200 pcsc-lite (1.8.16-1) unstable; urgency=medium * New upstream release * debian/control: fix lintian warning vcs-field-uses-insecure-uri vcs-browser Use https:// instead of http:// * debian/control: Standards-Version: 3.9.6 -> 3.9.7. No change needed. * debian/rules: use "hardening=+all" to harden even more the binaries -- Ludovic Rousseau Sun, 20 Mar 2016 17:28:29 +0100 pcsc-lite (1.8.15-1) unstable; urgency=medium * New upstream release -- Ludovic Rousseau Fri, 25 Dec 2015 21:28:30 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1591547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day
Please note this update will be soon superseded by https://launchpad.net/bugs/1686470 ** Tags added: regression-proposed ** Tags added: verification-failed ** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Status in apt source package in Zesty: In Progress Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686472] [NEW] package libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempti
Public bug reported: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Apr 26 08:35:07 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libkrb5support0:amd64:1.13.2+dfsg-5ubuntu2 Unpacking chromium-codecs-ffmpeg-extra (58.0.3029.81-0ubuntu0.16.04.1277) over (57.0.2987.98-0ubuntu0.16.04.1276) ... dpkg: error processing package libkrb5support0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-05-04 (357 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: krb5 Title: package libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: krb5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1686472 Title: package libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in krb5 package in Ubuntu: New Bug description: NA ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49 Uname: Linux 4.4.0-72-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Wed Apr 26 08:35:07 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu7 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libkrb5support0:amd64:1.13.2+dfsg-5ubuntu2 Unpacking chromium-codecs-ffmpeg-extra (58.0.3029.81-0ubuntu0.16.04.1277) over (57.0.2987.98-0ubuntu0.16.04.1276) ... dpkg: error processing package libkrb5support0:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-05-04 (357 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: krb5 Title: package libkrb5support0:amd64 1.13.2+dfsg-5ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1686472/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] Re: Apt updates that are uniformally spread across all timezones, with predictable application windows
I propose we simply split up the apt daily script and run that in two timers (one for fetching, the other for potentially destructive stuff like u-u and clean). /usr/lib/apt/apt.systemd.daily.common.sh The shell functions used by both scripts (top part of script), plus the variables (so right until the # update package lists part). /usr/lib/apt/apt.systemd.daily The middle part of the current script, until u-u /usr/lib/apt/apt.systemd.destructive-daily The final part of the script handling u-u, clean, and autoclean -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformally spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Triaged Status in unattended-upgrades package in Ubuntu: Triaged Status in apt source package in Xenial: Triaged Status in unattended-upgrades source package in Xenial: Triaged Status in apt source package in Yakkety: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in apt source package in Zesty: Triaged Status in unattended-upgrades source package in Zesty: Triaged Status in apt source package in Artful: Triaged Status in unattended-upgrades source package in Artful: Triaged Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686470] [NEW] Apt updates that are uniformally spread across all timezones, with predictable application windows
Public bug reported: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they preffer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 ** Affects: apt (Ubuntu) Importance: High Status: Triaged ** Affects: unattended-upgrades (Ubuntu) Importance: High Status: Triaged ** Affects: apt (Ubuntu Xenial) Importance: High Status: Triaged ** Affects: unattended-upgrades (Ubuntu Xenial) Importance: High Status: Triaged ** Affects: apt (Ubuntu Yakkety) Importance: High Status: Triaged ** Affects: unattended-upgrades (Ubuntu Yakkety) Importance: High Status: Triaged ** Affects: apt (Ubuntu Zesty) Importance: High Status: Triaged ** Affects: unattended-upgrades (Ubuntu Zesty) Importance: High Status: Triaged ** Affects: apt (Ubuntu Artful) Importance: High Status: Triaged ** Affects: unattended-upgrades (Ubuntu Artful) Importance: High Status: Triaged ** Also affects: apt (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: apt (Ubuntu Xenial) Status: New => Triaged ** Changed in: apt (Ubuntu Yakkety) Status: New => Triaged ** Changed in: apt (Ubuntu Zesty) Status: New => Triaged ** Changed in: apt (Ubuntu Artful) Status: New => Triaged ** Changed in: apt (Ubuntu Xenial) Importance: Undecided => High ** Changed in: apt (Ubuntu Yakkety) Importance: Undecided => High ** Changed in: apt (Ubuntu Zesty) Importance: Undecided => High ** Changed in: apt (Ubuntu Artful) Importance: Undecided => High ** Description changed: [ Impact ] - * unattended-upgrades are enabled by default in Ubuntu 16.04 and later - * Currently the following three things happen as a monolithic event: -- metadata updates: apt update -- download of updates: apt upgrade --download-only -- application of updates: apt upgrade + * unattended-upgrades are enabled by default in Ubuntu 16.04 and later - * For the long running instances, all of the above happens
[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1676547 *** https://bugs.launchpad.net/bugs/1676547 I was also affected by this after doing a release upgrade of my system. Very very annoying and I was searching for ever until I found this. -- 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/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682820] Re: While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3
*** This bug is a duplicate of bug 1682934 *** https://bugs.launchpad.net/bugs/1682934 You likely have a version of python3.5 installed in /usr/local/bin. Please remove that and then run 'sudo apt-get -f install.' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1682820 Title: While upgrading to 17.04: package python3 3.5.1-4 failed to install/upgrade: pre-dependency problem - not installing python3 Status in python3-defaults package in Ubuntu: Incomplete Bug description: I got this error while upgrading from 16.10 to 17.04, along with the same Python traceback as below. After a reboot, I seem to now be on 17.04. I had just successfully upgraded from 16.04 to 16.10 with no problems. When the error occurred, I was advised by a dialog to try the following command, which produced a very similar error, with traceback. $ sudo apt-get install -f [sudo] password for jhartley: Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: account-plugin-tools account-plugin-ubuntuone cgmanager comerr-dev dns-root-data dnsmasq-base gdebi-core gir1.2-accounts-1.0 gir1.2-signon-1.0 hwdata imagemagick-common krb5-multidev libavcodec-ffmpeg-extra56 libavfilter-ffmpeg5 libavformat-ffmpeg56 libavresample-ffmpeg2 libavutil-ffmpeg54 libbasicusageenvironment1 libbluray1 libbonobo2-0 libbonobo2-common libbonoboui2-0 libbonoboui2-common libboost-date-time1.61.0 libboost-filesystem1.61.0 libboost-iostreams1.61.0 libboost-locale1.61.0 libboost-log1.61.0 libboost-program-options1.61.0 libboost-regex1.61.0 libboost-serialization1.61.0 libboost-thread1.61.0 libcddb2 libchromaprint0 libdirectfb-1.2-9 libdvbpsi10 libebml4v5 libfwup0 libglade2-0 libglew1.13 libgnome-2-0 libgnome2-0 libgnome2-bin libgnome2-common libgnomecanvas2-0 libgnomecanvas2-common libgnomeui-0 libgnomeui-common libgnomevfs2-0 libgnomevfs2-common libgroupsock8 libgssrpc4 libiso9660-8 libjasper1 libjson-c3:i386 libjsoncpp1 libkadm5clnt-mit10 libkadm5clnt-mit11 libkadm5srv-mit10 libkadm5srv-mit11 libkdb5-8 liblircclient0 liblivemedia52 liblivemedia57 libllvm3.8 libllvm3.8:i386 liblouis10 libmatroska6v5 libmimic0 libmircommon6 libmirplatform13 libmirserver41 libonig2 libopencv-contrib2.4v5 libopencv-legacy2.4v5 libopencv-ml2.4v5 libopenjpeg5 libopenmpt-modplug1 liborbit-2-0 liborcus-0.11-0 libpam-cgfs libpay2 libperl5.22 libpoppler61 libpostproc-ffmpeg53 libraw15 libreoffice-style-human libresid-builder0c2a libsidplay2v5 libswresample-ffmpeg1 libswscale-ffmpeg3 libubuntu-app-launch3 libubuntuoneauth-2.0-0 libupnp6 libusageenvironment3 libvcdinfo0 libvlc-bin libvlc5 libvpx3 libwebp5 libx265-79 libx86-1 libxapian22v5 linux-image-4.4.0-72-generic linux-image-extra-4.4.0-72-generic lp-solve mir-platform-graphics-mesa-kms10 mir-platform-graphics-mesa-x10 mir-platform-input-evdev5 oxygen5-icon-theme pay-service pay-ui perl-modules-5.22 pm-utils qml-module-ubuntuone qtdeclarative5-ubuntu-web-plugin snap-confine system-config-printer-gnome ubuntu-push-client ubuntuone-credentials-common unity-scope-click vbetool vlc-bin vlc-data vlc-nox vlc-plugin-base Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: python3 Suggested packages: python3-doc python3-tk python3-venv The following packages will be upgraded: python3 1 to upgrade, 0 to newly install, 0 to remove and 0 not to upgrade. 12 not fully installed or removed. Need to get 0 B/8,696 B of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up python3.5-minimal (3.5.3-1) ... Traceback (most recent call last): File "/usr/lib/python3.5/py_compile.py", line 6, in import importlib._bootstrap_external File "/usr/lib/python3.5/importlib/__init__.py", line 57, in import types File "/usr/lib/python3.5/types.py", line 166, in import functools as _functools File "/usr/lib/python3.5/functools.py", line 23, in from weakref import WeakKeyDictionary File "/usr/lib/python3.5/weakref.py", line 12, in from _weakref import ( ImportError: cannot import name '_remove_dead_weakref' dpkg: error processing package python3.5-minimal (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of python3-minimal: python3-minimal depends on python3.5-minimal (>= 3.5.3-1~); however: Package python3.5-minimal is not configured yet. dpkg: error processing package python3-minimal (--configure): dependency problems -
[Touch-packages] [Bug 1685272] Re: gnome-shell: no window border
The bug as described is not a theme issue, AFAICS. The window borders are meant to look like that. Are you really complaining about the lack of shadows? That *is* a bug. As far as I can see that particular issue only happens for csd windows. For example, gnome-terminal looks fine. ** Changed in: ubuntu-themes (Ubuntu Artful) Status: Confirmed => Triaged ** Changed in: ubuntu-themes (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685272 Title: gnome-shell: no window border Status in light-themes package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Triaged Status in light-themes source package in Artful: Invalid Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell, there are no window borders. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685271] Re: gnome-shell: corners are not rounded
Also for csd windows only ** Changed in: ubuntu-themes (Ubuntu Artful) Status: Confirmed => Triaged ** Changed in: ubuntu-themes (Ubuntu Artful) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1685271 Title: gnome-shell: corners are not rounded Status in light-themes package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Triaged Status in light-themes source package in Artful: Invalid Status in ubuntu-themes source package in Artful: Triaged Bug description: Under gnome-shell apps have dark black squared top corners when they should be rounded. See attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/1685271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686192] Re: DHCP Relay not sending DHCP OFFER packets
Looks like they use a mailing list for bug reports: dnsmasq-disc...@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1686192 Title: DHCP Relay not sending DHCP OFFER packets Status in dnsmasq package in Ubuntu: New Bug description: In Ubuntu Server 17-04. DNSMASQ version 2.76-5 DHCP Relay option for DNSMASQ appears to be broken. The syslog states the file is allocating an IP address but TCPDUMP shows no DHCP OFFER is ever sent out on the receiving interface. Configuration is included with the bug report. This problem seems to occur in centOS as well. Looking at an strace it appears to be calling sendmsg however no outgoing DHCP packet is seen on the wire via TCPDUMP. jkary@DHCP-UBUNTU-SERVER:~$ sudo su - [sudo] password for jkary: root@DHCP-UBUNTU-SERVER:~# tcpdump -i ens160 port 67 or port 68 -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes 08:02:12.056671 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:b5:9b:0e, length 322 08:02:16.420010 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:65:e0:ea, length 322 08:02:21.522334 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:65:e0:ea, length 322 ^C 3 packets captured 3 packets received by filter 0 packets dropped by kernel root@DHCP-UBUNTU-SERVER:~# tail -50 /var/log/syslog Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 28 broadcast 10.168.102.255 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 3 router 10.168.102.1 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 6 dns-server 10.168.101.20 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 option: 82 agent-id 01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06... Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 available DHCP range: 10.168.102.100 -- 10.168.102.150 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 DHCPDISCOVER(ens160) 00:0c:29:65:e0:ea Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 tags: ens160 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 DHCPOFFER(ens160) 10.168.102.128 00:0c:29:65:e0:ea Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 1:netmask, 28:broadcast, 2:time-offset, 121:classless-static-route, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 15:domain-name, 6:dns-server, 12:hostname, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 40:nis-domain, 41:nis-server, 42:ntp-server, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 26:mtu, 119:domain-search, 3:router, 121:classless-static-route, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 249, 33:static-route, 252, 42:ntp-server Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 next server: 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 1 option: 53 message-type 2 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 54 server-identifier 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 51 lease-time 12h Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 58 T1 6h Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 59 T2 10h30m Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 1 netmask 255.255.255.0 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 28 broadcast 10.168.102.255 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 3 router 10.168.102.1 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 6 dns-server 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 option: 82 agent-id 01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06... Apr 25 08:02:29 DHCP-UBUNTU-SERVER kernel: [ 2251.45] device ens160 left promiscuous mode Apr 25 08:02:29 DHCP-UBUNTU-SERVER systemd-timesyncd[647]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 available DHCP range: 10.168.102.100 -- 10.168.102.150 Apr 25 08:02:35 DHCP-UBUNTU-SERVER
[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1
Dimitri, I have a question about the chosen nameservers. When using systemd 232-21-ubuntu3 or earlier, it was like this (systemd-resolve --status): Link 2 (eth0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 193.210.18.18 193.210.19.19 DNS Domain: dhcp.inet.fi When using systemd 233-5ubuntu1 (manual start), it is like this (systemd-resolve --status): Global DNS Servers: 8.8.8.8 8.8.4.4 2001:4860:4860:: 2001:4860:4860::8844 Note the different dns servers. The latter (8.8.8.8. ...) came from /run/systemd/resolve/resolv.conf I think dns servers 193.210.18.18 and 193.210.19.19 are the correct ones. Why are they different. -- 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/1685900 Title: On artful, no working dns after upgrading to systemd 233-5ubuntu1 Status in systemd package in Ubuntu: Incomplete Bug description: After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no nameserver (dns). This is very likely a DNS issue. As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS work fine. Or instead, I must manually start systemd-resolved: ~$ sudo service systemd-resolved restart So something odd has happened between these versions. Systemd-resolved is not starting automatically at boot anymore. My setup is a fully upgraded artful with proposed repo turned on. I use only Gnome DE with GDM. Everything else works fine, but not systemd 233-5ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk
Hi Christian, A more careful read through of the instructions you link to and I have spotted the required tag. Now added that as requested. I'll try to get the other two tested using lsc tomorrow. Tag now added. ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1630516 Title: Logrotate doesn't clean old system logs, allowing them to fill the disk Status in One Hundred Papercuts: Triaged Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Trusty: Fix Committed Status in logrotate source package in Xenial: Fix Committed Status in logrotate source package in Yakkety: Fix Committed Status in logrotate source package in Zesty: Fix Released Status in logrotate package in Debian: Fix Released Bug description: [Impact] Logrotate fails to rotate a log and then will continue to fail to rotate it until manual intervention takes place. If messaging has not been configured on the system there will be no warning issued to the user. The log will grow day by day until a user intervenes or the drive that the log is stored on is full. Very large log files can make it more difficult to find useful data. Full drives make the rest of the system fail to operate. Backporting a fix would prevent drives filling up on stable releases. [Test Case] Go to your logs area (/var/logs) and create a file with a name ending .2, as would be created part way through the logrotate process. So if you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz, /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your subsequent log rotate runs will fail. [Regression Potential] - I'd hope the potential is low as it only triggers under certain conditions that are special (target filename in the way). - So far in those conditions it failed to rotate - Yet If despite my hope there still manifests an issue I'd expect it could be renaming files it should not, so people would end up "missing" their logs - the good thing is that this is a rename, so they should find it at different names. - Another thing I consider possible is that some unexpected conditions cause e.g. a crash in the changed code, in that case the logs are not rotated, but since there is no unlink the logs will still exist. - Therefore I consider the Potential low enough to consider the fix. [Other Info] n/a --- Good afternoon. I have started seeing something very similar to Debian Dug 734688 "Logs are not rotated for a month" but in the latest Ubuntu LTS (16.04). I seem to have $ logrotate --version logrotate 3.8.7 bundled in it. A few weeks ago I started getting root emails such as this: > Subject: Crontest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/munin/munin-node.log.1: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 When I inspected the area of concern I was able to see that there was an existing .1 file. manager@warden:/var/log/munin$ ll total 580 drwxr-xr-x 2 munin adm 4096 Sep 27 06:31 ./ drwxr-xr-x 13 root syslog 4096 Oct 5 06:26 ../ -rw-r--r-- 1 root root 3440 Sep 26 13:39 munin-node-configure.log -rw-r--r-- 1 root root 490251 Oct 5 10:25 munin-node.log -rw-r--r-- 1 root root56598 Sep 21 02:01 munin-node.log.1 -rw-r--r-- 1 root root24576 Aug 31 02:01 munin-node.log.2 -rw-r--r-- 1 root root 1906 Sep 19 06:25 munin-node.log.8.gz The contents of the munin-node.log file seem to run from the 19th September until today. Unlike other parts of this bug the .1 and .2 files do not seem to be already compressed. I deleted all but the munin-node.log file to see if it would resolve the problem and was going to leave it at that. Then I noticed that I have had another Ubuntu machine which has been sending similar emails for the past week: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/syslog.1.gz: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 Different file, different machine but a very similar error message. Checking on the syslog file I can see that it better fits with other reports on this bug as my duplicated .1 files has a corresponding .1.gz file. manager@trac:/var/log$ ll syslog* -rw-r- 1 syslog adm 918492 Oct 5 10:30 syslog -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1 -rw-r- 1 syslog adm 20638 Oct 2 02:01 syslog.1.gz -rw-r- 1 syslog adm 41989 Sep 30 02:00 syslog.2.gz -rw-r- 1 syslog adm 18654 Sep 28 02:01 syslog.3.gz
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in basefiles for ubuntu
The difference here is a supported machine is up to date, even if it only has the minimum packages installed. Asking for another package to be installed to be "supported" is a small bit of friction that can be removed by delivering the script with basefiles. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in basefiles for ubuntu Status in base-files package in Ubuntu: Incomplete Bug description: [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
Hi, thanks for your answer. I had indeed tried it and it fails, unfortunately, with the following messages: cups-daemon is already the newest version (2.1.3-4). printer-driver-gutenprint is already the newest version (5.2.11-1). printer-driver-gutenprint set to manually installed. cups-filters is already the newest version (1.8.3-2ubuntu3.1). cups-filters set to manually installed. ghostscript is already the newest version (9.18~dfsg~0-0ubuntu2.3). cups-ppdc is already the newest version (2.1.3-4ubuntu0.2). cups-ppdc set to manually installed. cups is already the newest version (2.1.3-4ubuntu0.2). cups set to manually installed. cups-core-drivers is already the newest version (2.1.3-4ubuntu0.2). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed Depends: cups-daemon (>= 2.1.3-4ubuntu0.2) Depends: cups-client (>= 2.1.3-4ubuntu0.2) cups-bsd : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed Depends: cups-client (= 2.1.3-4ubuntu0.2) cups-core-drivers : Depends: libcups2 (= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed Depends: cups-daemon (>= 2.1.3-4ubuntu0.2) libcups2 : Breaks: libcups2:i386 (!= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed libcups2:i386 : Breaks: libcups2 (!= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed libcupscgi1 : Breaks: libcupscgi1:i386 (!= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed libcupscgi1:i386 : Breaks: libcupscgi1 (!= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed libcupsimage2 : Breaks: libcupsimage2:i386 (!= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed libcupsimage2:i386 : Breaks: libcupsimage2 (!= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed libcupsmime1 : Breaks: libcupsmime1:i386 (!= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed libcupsmime1:i386 : Breaks: libcupsmime1 (!= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed libcupsppdc1 : Breaks: libcupsppdc1:i386 (!= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed libcupsppdc1:i386 : Breaks: libcupsppdc1 (!= 2.1.3-4ubuntu0.2) but 2.1.3-4 is to be installed E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a solution). -- 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/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676977] Re: Login prompt never presented with ldap login and ldapi set with a name.
Thank you for the prompt testing. I'm marking a few potential src packages where the actual issue might lie. ** Also affects: accountsservice (Ubuntu) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Changed in: libpam-ldap (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1676977 Title: Login prompt never presented with ldap login and ldapi set with a name. Status in accountsservice package in Ubuntu: New Status in libpam-ldap package in Ubuntu: Invalid Status in systemd package in Ubuntu: New Bug description: I have a ldap login configuration that has worked with several Ubuntu versions. Unfortunately it doesn't work with 16.10. If I left my ldapi setting using a name as I used to, the login prompt never appears. If I change the ldapi setting to the IP of the authentication server, the login works perfectly. The authentication server name resolution works fine on 16.10 (after login) and on previous version even during login. It seems to me my problem is related to some ordering issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libpam-ldap 184-8.7ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 28 14:33:27 2017 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: libpam-ldap UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1676977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686192] Re: DHCP Relay not sending DHCP OFFER packets
I am happy to report this bug upstream however I've been unable to find a bug tracker for DNSMASQ specifically. Take Care Jason -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1686192 Title: DHCP Relay not sending DHCP OFFER packets Status in dnsmasq package in Ubuntu: New Bug description: In Ubuntu Server 17-04. DNSMASQ version 2.76-5 DHCP Relay option for DNSMASQ appears to be broken. The syslog states the file is allocating an IP address but TCPDUMP shows no DHCP OFFER is ever sent out on the receiving interface. Configuration is included with the bug report. This problem seems to occur in centOS as well. Looking at an strace it appears to be calling sendmsg however no outgoing DHCP packet is seen on the wire via TCPDUMP. jkary@DHCP-UBUNTU-SERVER:~$ sudo su - [sudo] password for jkary: root@DHCP-UBUNTU-SERVER:~# tcpdump -i ens160 port 67 or port 68 -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes 08:02:12.056671 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:b5:9b:0e, length 322 08:02:16.420010 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:65:e0:ea, length 322 08:02:21.522334 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:65:e0:ea, length 322 ^C 3 packets captured 3 packets received by filter 0 packets dropped by kernel root@DHCP-UBUNTU-SERVER:~# tail -50 /var/log/syslog Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 28 broadcast 10.168.102.255 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 3 router 10.168.102.1 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 6 dns-server 10.168.101.20 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 option: 82 agent-id 01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06... Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 available DHCP range: 10.168.102.100 -- 10.168.102.150 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 DHCPDISCOVER(ens160) 00:0c:29:65:e0:ea Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 tags: ens160 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 DHCPOFFER(ens160) 10.168.102.128 00:0c:29:65:e0:ea Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 1:netmask, 28:broadcast, 2:time-offset, 121:classless-static-route, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 15:domain-name, 6:dns-server, 12:hostname, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 40:nis-domain, 41:nis-server, 42:ntp-server, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 26:mtu, 119:domain-search, 3:router, 121:classless-static-route, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 249, 33:static-route, 252, 42:ntp-server Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 next server: 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 1 option: 53 message-type 2 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 54 server-identifier 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 51 lease-time 12h Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 58 T1 6h Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 59 T2 10h30m Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 1 netmask 255.255.255.0 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 28 broadcast 10.168.102.255 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 3 router 10.168.102.1 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 6 dns-server 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 option: 82 agent-id 01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06... Apr 25 08:02:29 DHCP-UBUNTU-SERVER kernel: [ 2251.45] device ens160 left promiscuous mode Apr 25 08:02:29 DHCP-UBUNTU-SERVER systemd-timesyncd[647]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 available DHCP range: 10.168.102.100 -- 10.168.102.150 Apr 25 08:02:35 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470
[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk
Hi Thomas, thanks for your ongoing work. Look at [1] - in this case you'd add verification-done-xenial now. Once all needed tags are added (+Trusty, +Yakkety) you'd also remove the verification-needed. [1]: https://wiki.ubuntu.com/QATeam/PerformingSRUVerification#Updating_the_bug_report -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1630516 Title: Logrotate doesn't clean old system logs, allowing them to fill the disk Status in One Hundred Papercuts: Triaged Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Trusty: Fix Committed Status in logrotate source package in Xenial: Fix Committed Status in logrotate source package in Yakkety: Fix Committed Status in logrotate source package in Zesty: Fix Released Status in logrotate package in Debian: Fix Released Bug description: [Impact] Logrotate fails to rotate a log and then will continue to fail to rotate it until manual intervention takes place. If messaging has not been configured on the system there will be no warning issued to the user. The log will grow day by day until a user intervenes or the drive that the log is stored on is full. Very large log files can make it more difficult to find useful data. Full drives make the rest of the system fail to operate. Backporting a fix would prevent drives filling up on stable releases. [Test Case] Go to your logs area (/var/logs) and create a file with a name ending .2, as would be created part way through the logrotate process. So if you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz, /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your subsequent log rotate runs will fail. [Regression Potential] - I'd hope the potential is low as it only triggers under certain conditions that are special (target filename in the way). - So far in those conditions it failed to rotate - Yet If despite my hope there still manifests an issue I'd expect it could be renaming files it should not, so people would end up "missing" their logs - the good thing is that this is a rename, so they should find it at different names. - Another thing I consider possible is that some unexpected conditions cause e.g. a crash in the changed code, in that case the logs are not rotated, but since there is no unlink the logs will still exist. - Therefore I consider the Potential low enough to consider the fix. [Other Info] n/a --- Good afternoon. I have started seeing something very similar to Debian Dug 734688 "Logs are not rotated for a month" but in the latest Ubuntu LTS (16.04). I seem to have $ logrotate --version logrotate 3.8.7 bundled in it. A few weeks ago I started getting root emails such as this: > Subject: Crontest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/munin/munin-node.log.1: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 When I inspected the area of concern I was able to see that there was an existing .1 file. manager@warden:/var/log/munin$ ll total 580 drwxr-xr-x 2 munin adm 4096 Sep 27 06:31 ./ drwxr-xr-x 13 root syslog 4096 Oct 5 06:26 ../ -rw-r--r-- 1 root root 3440 Sep 26 13:39 munin-node-configure.log -rw-r--r-- 1 root root 490251 Oct 5 10:25 munin-node.log -rw-r--r-- 1 root root56598 Sep 21 02:01 munin-node.log.1 -rw-r--r-- 1 root root24576 Aug 31 02:01 munin-node.log.2 -rw-r--r-- 1 root root 1906 Sep 19 06:25 munin-node.log.8.gz The contents of the munin-node.log file seem to run from the 19th September until today. Unlike other parts of this bug the .1 and .2 files do not seem to be already compressed. I deleted all but the munin-node.log file to see if it would resolve the problem and was going to leave it at that. Then I noticed that I have had another Ubuntu machine which has been sending similar emails for the past week: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/syslog.1.gz: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 Different file, different machine but a very similar error message. Checking on the syslog file I can see that it better fits with other reports on this bug as my duplicated .1 files has a corresponding .1.gz file. manager@trac:/var/log$ ll syslog* -rw-r- 1 syslog adm 918492 Oct 5 10:30 syslog -rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1 -rw-r- 1 syslog adm 20638 Oct 2 02:01 syslog.1.gz -rw-r- 1 syslog adm 41989 Sep 30 02:00 syslog.2.gz -rw-r- 1 syslog adm 18654
[Touch-packages] [Bug 1639203] Re: mouse cursor flashing on laptop screen after adding second monitor through usb 3.0 displaylink monitor
I confirm that the bug is still there... -- 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/1639203 Title: mouse cursor flashing on laptop screen after adding second monitor through usb 3.0 displaylink monitor Status in xorg package in Ubuntu: Confirmed Bug description: Mouse cursor flashes when moved on the laptop screen after connecting a second monitor via DisplayLink USB 3.0 interface. The cursor flashes both when connecting the screen via VGA and HDMI. However, when the screen is connected directly to the VGA or HDMI ports on laptop, bypassing the DisplayLink adapter, the flashing does not occur. Similarly, the cursor never flashes on the second screen. The system is Ubuntu 16.04 LTS on Dell Latitude E5470 with integrated Intel graphic card. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 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 Nov 4 11:40:32 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake Integrated Graphics [1028:06de] InstallationDate: Installed on 2016-08-22 (74 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude E5470 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-45-generic root=UUID=6b6cd5e0-5e92-462d-b229-6e50476e309d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.3 dmi.board.name: 0C8FKJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.3:bd06/15/2016:svnDellInc.:pnLatitudeE5470:pvr:rvnDellInc.:rn0C8FKJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E5470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri Nov 4 11:38:14 2016 xserver.configfile: default xserver.errors: modeset(G0): glamor initialization failed xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 61460 vendor DEL xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1639203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 921489] Re: Segmentation fault in slapd (related to GSSAPI?)
Hi Suho, Please could you file a new bug for your issue, ideally using apport (ubuntu-bug) so that the backtrace can be collected? I have been looking at a similar issue (https://bugs.debian.org/860947) recently and the additional info would be great. Thanks! ** Bug watch added: Debian Bug tracker #860947 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860947 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/921489 Title: Segmentation fault in slapd (related to GSSAPI?) Status in openldap package in Ubuntu: Confirmed Bug description: In our installation slapd will crash with a Segmentation Fault about once a week. It has been seen on the producer while the consumers connect but also on both producer and consumers at random. It seems to be related to authentication with GSSAPI. syslog produces the followig message: kernel: [513493.152760] slapd[1610]: segfault at 7fb242df9000 ip 7fb242ad7122 sp 7fb127ffd900 error 4 in libcrypto.so.0.9.8[7fb242a61000+168000] gdb: Core was generated by usr/sbin/slapd -d 0 -h ldap:/// ldaps:/// -f /local/sukat/conf/slapd.conf'. Program terminated with signal 11, Segmentation fault. #0 sha1_block_data_order () at sha1-x86_64.s:133 133 sha1-x86_64.s: No such file or directory. in sha1-x86_64.s (gdb) bt #0 sha1_block_data_order () at sha1-x86_64.s:133 #1 0x005e1700 in ?? () #2 0x1700 in ?? () #3 0x in ?? () The backtrace is incomplete as the debug packages are broken. Trying to reproduce this bug I trigger another segfault. I will file reports on thease issues in separate tickets. ProblemType: Bug Architecture: amd64 Date: Wed Jan 25 11:13:22 2012 Dependencies: adduser 3.112ubuntu1 base-files 5.0.0ubuntu20.10.04.4 base-passwd 3.5.22 coreutils 7.4-2ubuntu3 debconf 1.5.28ubuntu4 debconf-i18n 1.5.28ubuntu4 debianutils 3.2.2 dpkg 1.15.5.6ubuntu4.5 [modified: sbin/start-stop-daemon] findutils 4.4.2-1ubuntu1 gcc-4.4-base 4.4.3-4ubuntu5 libacl1 2.2.49-2 libattr1 1:2.4.44-1 libbz2-1.0 1.0.5-4ubuntu0.2 libc-bin 2.11.1-0ubuntu7.8 libc6 2.11.1-0ubuntu7.8 libcomerr2 1.41.11-1ubuntu2.1 libdb4.7 4.7.25-9 libdb4.8 4.8.24-1ubuntu1 libgcc1 1:4.4.3-4ubuntu5 libgcrypt11 1.4.4-5ubuntu2 libgdbm3 1.8.3-9 libgnutls26 2.8.5-2 libgpg-error0 1.6-1ubuntu2 libgssapi-krb5-2 1.8.1+dfsg-2ubuntu0.10 libk5crypto3 1.8.1+dfsg-2ubuntu0.10 libkeyutils1 1.2-12 libkrb5-3 1.8.1+dfsg-2ubuntu0.10 libkrb5support0 1.8.1+dfsg-2ubuntu0.10 libldap-2.4-2 2.4.21-0ubuntu5.6 liblocale-gettext-perl 1.05-6 libltdl7 2.2.6b-2ubuntu1 libncurses5 5.7+20090803-2ubuntu3 libpam-modules 1.1.1-2ubuntu5.4 libpam0g 1.1.1-2ubuntu5.4 libperl5.10 5.10.1-8ubuntu2.1 libreadline6 6.1-1 libsasl2-2 2.1.23.dfsg1-5ubuntu1 libselinux1 2.0.89-4 libslp1 1.2.1-7.6ubuntu0.1 libstdc++6 4.4.3-4ubuntu5 libtasn1-3 2.4-1 libtext-charwidth-perl 0.04-6 libtext-iconv-perl 1.7-2 libtext-wrapi18n-perl 0.06-7 libwrap0 7.6.q-18 lzma 4.43-14ubuntu2 odbcinst 2.2.11-21 odbcinst1debian1 2.2.11-21 passwd 1:4.1.4.2-1ubuntu2.2 perl 5.10.1-8ubuntu2.1 perl-base 5.10.1-8ubuntu2.1 perl-modules 5.10.1-8ubuntu2.1 psmisc 22.10-1 readline-common 6.1-1 sensible-utils 0.0.1ubuntu3 tzdata 2011n-0ubuntu0.10.04 unixodbc 2.2.11-21 zlib1g 1:1.2.3.3.dfsg-15ubuntu1 DistroRelease: Ubuntu 10.04 NonfreeKernelModules: openafs Package: slapd 2.4.21-0ubuntu5.6 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LC_CTYPE=en_GB.UTF-8 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 SourcePackage: openldap Tags: lucid Uname: Linux 2.6.32-37-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/921489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686192] Re: DHCP Relay not sending DHCP OFFER packets
Hi! Thanks for reporting this and including your configuration file. Given you are seeing this across distros I think this warrants an upstream report. Would you be willing to file something upstream and provide a link back in this bug report? Thanks! ** Tags added: needs-upstream-report -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1686192 Title: DHCP Relay not sending DHCP OFFER packets Status in dnsmasq package in Ubuntu: New Bug description: In Ubuntu Server 17-04. DNSMASQ version 2.76-5 DHCP Relay option for DNSMASQ appears to be broken. The syslog states the file is allocating an IP address but TCPDUMP shows no DHCP OFFER is ever sent out on the receiving interface. Configuration is included with the bug report. This problem seems to occur in centOS as well. Looking at an strace it appears to be calling sendmsg however no outgoing DHCP packet is seen on the wire via TCPDUMP. jkary@DHCP-UBUNTU-SERVER:~$ sudo su - [sudo] password for jkary: root@DHCP-UBUNTU-SERVER:~# tcpdump -i ens160 port 67 or port 68 -n tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on ens160, link-type EN10MB (Ethernet), capture size 262144 bytes 08:02:12.056671 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:b5:9b:0e, length 322 08:02:16.420010 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:65:e0:ea, length 322 08:02:21.522334 IP 10.168.102.1.67 > 10.168.101.20.67: BOOTP/DHCP, Request from 00:0c:29:65:e0:ea, length 322 ^C 3 packets captured 3 packets received by filter 0 packets dropped by kernel root@DHCP-UBUNTU-SERVER:~# tail -50 /var/log/syslog Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 28 broadcast 10.168.102.255 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 3 router 10.168.102.1 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 6 dns-server 10.168.101.20 Apr 25 08:02:19 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 option: 82 agent-id 01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06... Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 available DHCP range: 10.168.102.100 -- 10.168.102.150 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 DHCPDISCOVER(ens160) 00:0c:29:65:e0:ea Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 tags: ens160 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 DHCPOFFER(ens160) 10.168.102.128 00:0c:29:65:e0:ea Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 1:netmask, 28:broadcast, 2:time-offset, 121:classless-static-route, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 15:domain-name, 6:dns-server, 12:hostname, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 40:nis-domain, 41:nis-server, 42:ntp-server, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 26:mtu, 119:domain-search, 3:router, 121:classless-static-route, Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 requested options: 249, 33:static-route, 252, 42:ntp-server Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 next server: 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 1 option: 53 message-type 2 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 54 server-identifier 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 51 lease-time 12h Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 58 T1 6h Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 59 T2 10h30m Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 1 netmask 255.255.255.0 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 28 broadcast 10.168.102.255 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 3 router 10.168.102.1 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 4 option: 6 dns-server 10.168.101.20 Apr 25 08:02:21 DHCP-UBUNTU-SERVER dnsmasq-dhcp[2241]: 3576154470 sent size: 20 option: 82 agent-id 01:0a:01:08:00:06:00:4c:4f:2a:00:2f:02:06... Apr 25 08:02:29 DHCP-UBUNTU-SERVER kernel: [ 2251.45] device ens160 left promiscuous mode Apr 25 08:02:29 DHCP-UBUNTU-SERVER systemd-timesyncd[647]: Timed out waiting for reply from 91.189.91.157:123 (ntp.ubuntu.com). Apr 25 08:02:35 DHCP-UBUNTU-SERVER
[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd
@bryanquigley - no. i had opened one for networkmanager (or planned on it, don't remember how far i got), but in the end to provide meaningful details i'd have to *run* it. Stop trying to get me to run it. Thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Triaged Status in lxc-android-config package in Ubuntu: Triaged Status in ubuntu-touch-meta package in Ubuntu: Triaged Status in ubuntu-touch-session package in Ubuntu: Triaged Status in unity8-desktop-session package in Ubuntu: Triaged Status in upstart package in Ubuntu: Triaged Status in upstart-watchdog package in Ubuntu: Triaged Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), * unity (for libupstart-dev) https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283 https://bileto.ubuntu.com/#/ticket/2730 $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686036] Re: strange behavior after restore snapshot
** Changed in: lxc (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1686036 Title: strange behavior after restore snapshot Status in lxc package in Ubuntu: In Progress Bug description: uname -a Linux lxd2-chel1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lxd: 2.12-0ubuntu3~ubuntu16.04.1~ppa1 zfsutils-linux: 0.6.5.6-0ubuntu16 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial after restore container from shapshot cannot add new snapshot or restore again until restart container example: # lxc image list +---+--++--++-+--+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | +---+--++--++-+--+ | debian/jessie | ba43812c4cb9 | no | Debian jessie amd64 (20170423_22:42) | x86_64 | 94.14MB | Apr 24, 2017 at 9:07am (UTC) | +---+--++--++-+--+ # lxc launch debian/jessie Creating popular-kitten The container you are starting doesn't have any network attached to it. To create a new network, use: lxc network create To attach a network to a container, use: lxc network attach Starting popular-kitten # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running Type: persistent Profiles: default Pid: 6965 Ips: lo: inet127.0.0.1 lo: inet6 ::1 Resources: Processes: 7 Disk usage: root: 1.48MB CPU usage: CPU usage (in seconds): 25 Memory usage: Memory (current): 16.22MB Memory (peak): 23.01MB Network usage: lo: Bytes received: 0B Bytes sent: 0B Packets received: 0 Packets sent: 0 # lxc profile show default config: {} description: Default LXD profile devices: root: path: / pool: main-pool type: disk name: default used_by: - /1.0/containers/popular-kitten # lxc snapshot popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # lxc restore popular-kitten snap0 # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted no - # lxc snapshot popular-kitten error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy # lxc restore popular-kitten snap0 error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy but container still work: # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running ... # lxc exec popular-kitten bash root@popular-kitten:~# uptime 07:34:06 up 8 min, 0 users, load average: 0.00, 0.02, 0.03 after restart container: # lxc restart popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - on another server this problem missmatch: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety # lxd --version 2.4.1 zfsutils-linux: 0.6.5.8-0ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1686036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1682913] Re: [radeon] corrupt gfx with Faeria/Payday 2
** Summary changed: - corrupt gfx with Faeria/Payday 2 on Radeon + [radeon] corrupt gfx with Faeria/Payday 2 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1682913 Title: [radeon] corrupt gfx with Faeria/Payday 2 Status in mesa package in Ubuntu: Triaged Bug description: I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed graphical issues in some games, that render partially black. E.g.: - menu of Payday 2: https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/ - menu of Faeria: https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/ I've traced the issue to a missing lib, libgles1, which for some reason has been removed from the 17.04 repos, as using Oibaf's PPA and manually installing the lib from it fixes the issues on these games. So, please build a version for Mesa 17.0.3 and put it in the repos, it's needed by some games. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1682913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686058] Re: bridge-utils all-regex does not capture network devices
Hi! Thanks for looking into this and determining what was going on. Based on the documentation I agree that it is not capturing enp* network devices. However, as the man page says you can add a regex if you want to capture other types of interfaces: bridge_ports regex enp.* If you desire to change the behavior of the 'all' wildcard, then I would suggest filing an upstream bug report to change this behavior. I will mark this as a wishlist bug. ** Changed in: bridge-utils (Ubuntu) Status: New => Confirmed ** Changed in: bridge-utils (Ubuntu) Importance: Undecided => Wishlist -- 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/1686058 Title: bridge-utils all-regex does not capture network devices Status in bridge-utils package in Ubuntu: Confirmed Bug description: from bridge-utils-interfaces(5) bridge-ports ... Specifying "all" is short for "regex eth.* em.* p[0-9].* noregex" and will get all the ethX and biosdevname-format (emX and pX) interfaces added to the bridge. This will NOT capture device names like enp* and network init will hang. No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty bridge-utils: Installed: 1.5-9ubuntu2 Candidate: 1.5-9ubuntu2 Version table: *** 1.5-9ubuntu2 500 500 http://de.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1686058/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629226] Re: systemd's service killed by cgroup controller pids
** Also affects: ubuntu-power-systems Importance: Undecided Status: New -- 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/1629226 Title: systemd's service killed by cgroup controller pids Status in The Ubuntu-power-systems project: New Status in bash package in Ubuntu: New Bug description: Problem Description === I write a simple systemd service which will fork child processes fiercely. But quickly the service failed: % sudo systemctl status reproducer.service ? reproducer.service - Reproducer of systemd services killed by ips Loaded: loaded (/etc/systemd/system/reproducer.service; disabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2016-03-18 06:58:37 CDT; 2min 43s ago Process: 5103 ExecStart=/home/hpt/reproducer/reproducer.sh (code=exited, status=0/SUCCESS) Main PID: 5105 (code=exited, status=254) Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: /home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable Mar 18 06:58:36 pinelp3 reproducer.sh[5103]: /home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: /home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: /home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: /home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: /home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Main process exited, code=exited, status=254/n/a Mar 18 06:58:37 pinelp3 reproducer.sh[5103]: /home/hpt/reproducer/reproducer.sh: fork: Resource temporarily unavailable Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Unit entered failed state. Mar 18 06:58:37 pinelp3 systemd[1]: reproducer.service: Failed with result 'exit-code'. The default task limit of systemd services is 512. Looks like the service is terminated by the kernel's ips cgroup controller. I think this isn't correct. Child processes cannot be forked shouldn't cause parent to die. % cat /etc/systemd/system/reproducer.service [Unit] Description=Reproducer of systemd services killed by ips After=multi-user.target [Service] ExecStart=/home/hpt/reproducer/reproducer.sh Type=forking [Install] WantedBy=multi-user.target % cat /home/hpt/reproducer/reproducer.sh #!/bin/bash foo() { #exec sh -c "echo $1: \$\$;sleep 60" echo $1: sleep 60 } bar() { c=1 while true do for ((i=1;i<=2048;i++)) do foo $c & ((c++)) done wait c=1 done } # main bar & disown -a exit 0 ---uname output--- Linux pinelp3 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:40:38 UTC 2016 ppc64le ppc64le ppc64le GNU/Linux Machine Type = IBM,8408-E8E,lpar Steps to Reproduce 1. install the simple service in "Problem description" 2. sudo systemctl start reproducer.service 3. wait 2~3 minutes == Comment: #3 - Vaishnavi Bhat- 2016-03-22 11:21:55 == From the machine, root@pinelp3:~# ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 48192 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 48192 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited root@pinelp3:~# ps aux | wc -l ->While the service is running 1084 root@pinelp3:~# ps aux | wc -l " 1084 root@pinelp3:~# ps aux | wc -l " 1084 root@pinelp3:~# ps aux | wc -l " 1084 root@pinelp3:~# ps aux | wc -l-->While the service is not running. 572 root@pinelp3:~# free -m --> While service is running totalusedfree shared buff/cache available Mem: 12117 628 459 22 11029
[Touch-packages] [Bug 1682913] Re: Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games
I can reproduce the black screen thing with Faerie on radeon hw, but installing libgles1-mesa doesn't help. So it's just a bug in the radeon DRI driver. ** Changed in: mesa (Ubuntu) Status: Won't Fix => Triaged ** Summary changed: - Missing libgles1 in Ubuntu 17.04 repos triggers issues with some games + corrupt gfx with Faeria/Payday 2 on Radeon -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1682913 Title: corrupt gfx with Faeria/Payday 2 on Radeon Status in mesa package in Ubuntu: Triaged Bug description: I've just upgraded Ubuntu from 16.10 to 17.04. Afterwards, I noticed graphical issues in some games, that render partially black. E.g.: - menu of Payday 2: https://steamuserimages-a.akamaihd.net/ugc/156906385546364727/C1182DAE4DA1A6CB638A2D42FA33541629F2/ - menu of Faeria: https://steamuserimages-a.akamaihd.net/ugc/156906385546272628/52E8E6F366A54299597774C22D78771EA0F074ED/ I've traced the issue to a missing lib, libgles1, which for some reason has been removed from the 17.04 repos, as using Oibaf's PPA and manually installing the lib from it fixes the issues on these games. So, please build a version for Mesa 17.0.3 and put it in the repos, it's needed by some games. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1682913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1649310] Re: RM Upstart, obsolete, superseded by systemd
@serge-hallyn That's what I was looking for - the reason you were staying on upstart. Do you have a bug describing the power usage differences you've noted so it can be fixed? @khurshid-alam Even on a fresh install check out /etc/init/. There are plenty of upstart scripts/support still in place. FWICT, Since 16.04 all of them have been inert, except those for a desktop session. But to your point, once upstart is removed we likely want to clear them all out. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1649310 Title: RM Upstart, obsolete, superseded by systemd Status in cgmanager package in Ubuntu: Triaged Status in lxc-android-config package in Ubuntu: Triaged Status in ubuntu-touch-meta package in Ubuntu: Triaged Status in ubuntu-touch-session package in Ubuntu: Triaged Status in unity8-desktop-session package in Ubuntu: Triaged Status in upstart package in Ubuntu: Triaged Status in upstart-watchdog package in Ubuntu: Triaged Bug description: In 18.04 LTS src:upstart should not be part of Ubuntu. It has already been removed from Debian. And most products have migrated to systemd. This is a tracking bug to remove a collection of packages that need to go away together with upstart. Some of these have been ported to systemd under different names, or no longer at all required. = Removal order = * ubuntu-touch-meta * unity8-desktop-session * ubuntu-touch-session * upstart-watchdog * lxc-android-config * upstart * cgmanager = Reverse depends checks = $ reverse-depends -b src:upstart Reverse-Build-Depends = * tarantool (for upstart) ./debian/control: dh-systemd (>= 1.22) | sysvinit (<< 2.88dsf-59) | upstart (<< 1.13), * unity (for libupstart-dev) https://code.launchpad.net/~xnox/unity/no-more-upstart-dep/+merge/322283 https://bileto.ubuntu.com/#/ticket/2730 $ reverse-depends src:upstart Reverse-Depends === * ubuntu-touch-session (for upstart) * unity8-desktop-session(for upstart) * upstart-watchdog (for upstart) $ reverse-depends src:ubuntu-touch-session Reverse-Depends === * ubuntu-touch (for ubuntu-touch-session) $ reverse-depends -b src:ubuntu-touch-session No reverse dependencies found $ reverse-depends upstart-watchdog Reverse-Depends === * ubuntu-touch $ reverse-depends -b src:upstart-watchdog No reverse dependencies found $ reverse-depends src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends -b src:ubuntu-touch-meta No reverse dependencies found $ reverse-depends src:unity8-desktop-session No reverse dependencies found $ reverse-depends -b src:unity8-desktop-session No reverse dependencies found $ reverse-depends src:cgmanager Reverse-Depends === * lxc-android-config(for cgmanager) * numad (for cgmanager) ./debian/control:Depends: systemd-sysv | cgmanager * upstart [amd64 arm64 armhf i386 ppc64el] (for libcgmanager0) $ reverse-depends -b src:cgmanager Reverse-Build-Depends = * upstart (for libcgmanager-dev) $ reverse-depends src:lxc-android-config Reverse-Depends === * ubuntu-touch (for lxc-android-config) $ reverse-depends -b src:lxc-android-config No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1649310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1574045] Re: Can't install account-plugin-google; kaccounts-providers already provides /usr/share/accounts/providers/google.provider
*** This bug is a duplicate of bug 1451728 *** https://bugs.launchpad.net/bugs/1451728 if you need a quick fix solution to this here it is: ``` $ sudo dpkg --remove kaccounts-providers ``` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1574045 Title: Can't install account-plugin-google; kaccounts-providers already provides /usr/share/accounts/providers/google.provider Status in Online Accounts: Account plugins: New Status in kaccounts-providers: Fix Released Status in account-plugins package in Ubuntu: Confirmed Status in kaccounts-providers package in Ubuntu: Fix Released Bug description: I installed Kubuntu 16.04, later tried to install unity with `sudo apt-get install unity` which has a dependency (unity-scope-gdrive) requiring account-plugin-google and that wouldn't install since '/usr/share/accounts/providers/google.provider' is already provided by kaccounts-providers: $ sudo apt-get install unity Reading package lists... Done Building dependency tree Reading state information... Done unity is already the newest version (7.4.0+16.04.20160415-0ubuntu1). You might want to run 'apt-get -f install' to correct these: The following packages have unmet dependencies: unity-scope-gdrive : Depends: account-plugin-google but it is not going to be installed $ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following additional packages will be installed: account-plugin-google The following NEW packages will be installed: account-plugin-google 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 250 not fully installed or removed. Need to get 0 B/3,368 B of archives. After this operation, 29.7 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 214947 files and directories currently installed.) Preparing to unpack .../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ... Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1Preparing to unpack .../account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb ... Unpacking account-plugin-google (0.12+16.04.20160126-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb (--unpack): trying to overwrite '/usr/share/accounts/providers/google.provider', which is also in package kaccounts-providers 4:15.12.3-0ubuntu1 Errors were encountered while processing: /var/cache/apt/archives/account-plugin-google_0.12+16.04.20160126-0ubuntu1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: account-plugin-google (not installed) 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 CurrentDesktop: KDE Date: Sat Apr 23 11:09:16 2016 InstallationDate: Installed on 2016-04-23 (0 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160417.1) SourcePackage: account-plugins UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1574045/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
Clémence have you tried Ed's solution (https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/comments/14) ? It worked for me. -- 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/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676621] Re: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed
Running # apt-get upgrade has given me the following errors for one month now: cups : Depends: cups-daemon (>= 2.1.3-4ubuntu0.2) cups-core-drivers : Depends: cups-daemon (>= 2.1.3-4ubuntu0.2) cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is installed As a result I have not been able to install or update a single package for one month. This makes this a very important bug from my point of view. Is there a simple solution that will allow me to install packages without tinkering with packages versions? I will not try any solution that implies temporarily removing cups as it is a requisite for my job and I cannot risk not being able to print. -- 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/1676621 Title: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Status in cups package in Ubuntu: Confirmed Bug description: This is related to this bug https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642790 After `sudo apt-get -f install`, it removed cups and marked a bunch of cups packages as unnecessary `sudo apt-get autoremove` removed them. Now when I try to re-install cups, I get this error: ``` ☀ sudo apt-get install cups cups-daemon cups-core-drivers Mod master Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: cups : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupscgi1 (>= 1.4.2) but it is not going to be installed Depends: libcupsmime1 (>= 1.4.0) but it is not going to be installed Recommends: printer-driver-gutenprint but it is not going to be installed cups-core-drivers : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed cups-daemon : Depends: libcups2 (= 2.1.3-4) but 2.1.3-4ubuntu0.2 is to be installed Depends: libcupsmime1 (>= 1.5.0) but it is not going to be installed Recommends: cups-browsed but it is not going to be installed E: Unable to correct problems, you have held broken packages. ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676621/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686388] Re: Hold to resolve mirror spikes
** Changed in: apt (Ubuntu Zesty) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: apt (Ubuntu Yakkety) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: apt (Ubuntu Xenial) Assignee: (unassigned) => Steve Langasek (vorlon) ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686388 Title: Hold to resolve mirror spikes Status in apt package in Ubuntu: New Status in apt source package in Xenial: New Status in apt source package in Yakkety: New Status in apt source package in Zesty: New Bug description: Hold to resolve mirror spikes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615482] Please test proposed package
Hello John, or anyone else affected, Accepted apt into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.3.6 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Status in apt source package in Zesty: In Progress Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1615482] Re: apt-daily timer runs at random hours of the day
Hello John, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.21 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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: apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed ** Changed in: apt (Ubuntu Yakkety) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1615482 Title: apt-daily timer runs at random hours of the day Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Status in apt source package in Zesty: In Progress Bug description: apt, from 1.2.10 onwards (ie any version in Xenial, onwards) uses a systemd timer instead of a cron.daily job. This is a good thing, decoupling apt daily runs from the rest of cron, and ensuring other cron.daily jobs are not blocked by up to half an hour by the default settings of unattended-upgrades. However the policy chosen is to have the apt daily script run at a random hour of the day in a wrong headed attempt to reduce server load. This has the side effect of running unattended-upgrades at random hours of the day — such as business hours — rather than being confined to between 6:25am and 6:55am, using the defaults. A better policy would be to have the script activate at 6:00am plus an interval of 20 minutes at one second intervals reducing the impact of timezone population spikes, while still allowing unattended-upgrades to run within a predictable interval, before 7am. At the very least, some sort of note in the NEWS file detailing the new behaviour would be welcome. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1615482/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672710] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted apt into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.3.6 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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 apt in Ubuntu. https://bugs.launchpad.net/bugs/1672710 Title: apt fails to verify keys when Dir has space, and set via cmdline Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: When Dir has a space, and it is set via APT_CONFIG file, keys are found and validated correctly. When Dir is set without a space via cmdline, keys are found and validated correctly. When Dir is set with a space via cmdline, keys are not found and repositories are not verified. [Test case] Please see attached reproducer, which works on xenial system (gpg1) but not on zesty system (gpg2) $ bash reproducer.sh ++ mktemp -d + tmpdir=/tmp/tmp.sFipy6h5yL + pushd /tmp/tmp.sFipy6h5yL /tmp/tmp.sFipy6h5yL ~ + mkdir 'Sub Dir' + pushd 'Sub Dir' /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~ + mkdir -p etc/apt/apt.conf.d + mkdir -p etc/apt/trusted.gpg.d + mkdir -p etc/apt/preferences.d + mkdir -p var/lib/apt/lists/partial + mkdir -p var/lib/dpkg + touch var/lib/dpkg/status + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg etc/apt/trusted.gpg.d/ + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main' + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";' + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + cat /tmp/tmp.sFipy6h5yL/apt.conf Dir "/tmp/tmp.sFipy6h5yL/Sub Dir"; + : + : == list available keys == + apt-key list /tmp/tmp.sFipy6h5yL/Sub Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg - pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012)+ : + : == update with environ APT_CONFIG setting the Dir variable == + apt update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB] Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B] Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB] Fetched 1,410 kB in 0s (1,959 kB/s) Reading package lists... Done Building dependency tree... Done All packages are up to date. + unset APT_CONFIG + : + : == update with cmdline Dir option setting Dir to relative pwd == + apt -o Dir=./ update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Reading package lists... Done Building dependency tree... Done All packages are up to date. + : + : == update with cmdline Dir option setting Dir to absolute pwd with space == + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Reading package lists... Done Building dependency tree... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Some index files failed to download.
[Touch-packages] [Bug 1672710] Re: apt fails to verify keys when Dir has space, and set via cmdline
Hello Dimitri, or anyone else affected, Accepted apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apt/1.2.21 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 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 to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. 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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1672710 Title: apt fails to verify keys when Dir has space, and set via cmdline Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Yakkety: Fix Committed Bug description: When Dir has a space, and it is set via APT_CONFIG file, keys are found and validated correctly. When Dir is set without a space via cmdline, keys are found and validated correctly. When Dir is set with a space via cmdline, keys are not found and repositories are not verified. [Test case] Please see attached reproducer, which works on xenial system (gpg1) but not on zesty system (gpg2) $ bash reproducer.sh ++ mktemp -d + tmpdir=/tmp/tmp.sFipy6h5yL + pushd /tmp/tmp.sFipy6h5yL /tmp/tmp.sFipy6h5yL ~ + mkdir 'Sub Dir' + pushd 'Sub Dir' /tmp/tmp.sFipy6h5yL/Sub Dir /tmp/tmp.sFipy6h5yL ~ + mkdir -p etc/apt/apt.conf.d + mkdir -p etc/apt/trusted.gpg.d + mkdir -p etc/apt/preferences.d + mkdir -p var/lib/apt/lists/partial + mkdir -p var/lib/dpkg + touch var/lib/dpkg/status + cp /etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg etc/apt/trusted.gpg.d/ + echo 'deb http://archive.ubuntu.com/ubuntu/ trusty main' + echo 'Dir "/tmp/tmp.sFipy6h5yL/Sub Dir";' + export APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + APT_CONFIG=/tmp/tmp.sFipy6h5yL/apt.conf + cat /tmp/tmp.sFipy6h5yL/apt.conf Dir "/tmp/tmp.sFipy6h5yL/Sub Dir"; + : + : == list available keys == + apt-key list /tmp/tmp.sFipy6h5yL/Sub Dir/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg - pub rsa4096 2012-05-11 [SC] 790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32 uid [ unknown] Ubuntu Archive Automatic Signing Key (2012)+ : + : == update with environ APT_CONFIG setting the Dir variable == + apt update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Get:2 http://archive.ubuntu.com/ubuntu trusty Release [58.5 kB] Get:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg [933 B] Get:4 http://archive.ubuntu.com/ubuntu trusty/main amd64 Packages [1,350 kB] Fetched 1,410 kB in 0s (1,959 kB/s) Reading package lists... Done Building dependency tree... Done All packages are up to date. + unset APT_CONFIG + : + : == update with cmdline Dir option setting Dir to relative pwd == + apt -o Dir=./ update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Reading package lists... Done Building dependency tree... Done All packages are up to date. + : + : == update with cmdline Dir option setting Dir to absolute pwd with space == + apt -o 'Dir=/tmp/tmp.sFipy6h5yL/Sub Dir' update Ign:1 http://archive.ubuntu.com/ubuntu trusty InRelease Hit:2 http://archive.ubuntu.com/ubuntu trusty Release Err:3 http://archive.ubuntu.com/ubuntu trusty Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 Reading package lists... Done Building dependency tree... Done All packages are up to date. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.ubuntu.com/ubuntu trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/trusty/Release.gpg The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32 W:
[Touch-packages] [Bug 1686388] [NEW] Hold to resolve mirror spikes
Public bug reported: Hold to resolve mirror spikes ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Affects: apt (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: apt (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Tags: block-proposed regression-proposed ** Also affects: apt (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: apt (Ubuntu Xenial) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686388 Title: Hold to resolve mirror spikes Status in apt package in Ubuntu: New Status in apt source package in Xenial: New Status in apt source package in Yakkety: New Status in apt source package in Zesty: New Bug description: Hold to resolve mirror spikes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686189] Re: External monitor connecting problem
Sorry for spamming everyone, as this started happening after a kernel upgrade is it a Kernel bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1686189 Title: External monitor connecting problem Status in xorg package in Ubuntu: Confirmed Bug description: I am facing a problem with Intel Graphics driver. I have external monitor and in display settings the second monitor is detecting but it's not working, so could you email me a solution. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.4.25-040425-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Apr 25 21:45:16 2017 DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9] InstallationDate: Installed on 2017-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) MachineType: Dell Inc. Inspiron 3537 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago) dmi.bios.date: 04/30/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 03JPPR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 3537 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Tue Apr 25 21:37:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 17900 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in basefiles for ubuntu
This introduces a python dependency to base-files, which I think is incorrect. I think the decision to choose base-files should be reevaluated. >From the point of view of end-users, regardless if the script is in base-files or in its own package, the same number of apt commands will be needed either way. It's either: apt-get update apt-get dist-upgrade ubuntu-advantage enable-esm or: apt-get update apt-get install ubuntu-advantage ubuntu-advantage enable-esm In its own package it can have its own copyright, manpage, correct dependencies, its own source tarball, tests (which were stripped from the debdiff here), upstream url, nice description, etc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1686183 Title: Ship ubuntu-advantage in basefiles for ubuntu Status in base-files package in Ubuntu: Incomplete Bug description: [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686036] Re: strange behavior after restore snapshot
** Changed in: lxc (Ubuntu) Status: New => In Progress ** Changed in: lxc (Ubuntu) Assignee: (unassigned) => Christian Brauner (cbrauner) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1686036 Title: strange behavior after restore snapshot Status in lxc package in Ubuntu: In Progress Bug description: uname -a Linux lxd2-chel1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lxd: 2.12-0ubuntu3~ubuntu16.04.1~ppa1 zfsutils-linux: 0.6.5.6-0ubuntu16 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial after restore container from shapshot cannot add new snapshot or restore again until restart container example: # lxc image list +---+--++--++-+--+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | +---+--++--++-+--+ | debian/jessie | ba43812c4cb9 | no | Debian jessie amd64 (20170423_22:42) | x86_64 | 94.14MB | Apr 24, 2017 at 9:07am (UTC) | +---+--++--++-+--+ # lxc launch debian/jessie Creating popular-kitten The container you are starting doesn't have any network attached to it. To create a new network, use: lxc network create To attach a network to a container, use: lxc network attach Starting popular-kitten # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running Type: persistent Profiles: default Pid: 6965 Ips: lo: inet127.0.0.1 lo: inet6 ::1 Resources: Processes: 7 Disk usage: root: 1.48MB CPU usage: CPU usage (in seconds): 25 Memory usage: Memory (current): 16.22MB Memory (peak): 23.01MB Network usage: lo: Bytes received: 0B Bytes sent: 0B Packets received: 0 Packets sent: 0 # lxc profile show default config: {} description: Default LXD profile devices: root: path: / pool: main-pool type: disk name: default used_by: - /1.0/containers/popular-kitten # lxc snapshot popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # lxc restore popular-kitten snap0 # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted no - # lxc snapshot popular-kitten error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy # lxc restore popular-kitten snap0 error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy but container still work: # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running ... # lxc exec popular-kitten bash root@popular-kitten:~# uptime 07:34:06 up 8 min, 0 users, load average: 0.00, 0.02, 0.03 after restart container: # lxc restart popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - on another server this problem missmatch: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety # lxd --version 2.4.1 zfsutils-linux: 0.6.5.8-0ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1686036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container
The attachment "0001-main-improve-RLIMIT_NOFILE-handling-5795.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1686361 Title: systemd does not respect nofile ulimit when running in container Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Confirmed Bug description: When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g. 10 systemd will lower it to 65536 since this value is hard-coded into systemd. I've pushed a patch to systemd upstream that will try to set the nofile limit to the allowed kernel maximum. If this fails, it will compute the minimum of the current set value (the limit that is set on the container) and the maximum value as soft limit and the currently set maximum value as the maximum value. This way it retains the limit set on the container. It would be great if we could backport this patch to have system adhere to nofile limits set for the container. This is especially important since user namespaces will allow you to lower the limit but not raise it back up afterwards. The upstream patch is appended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
I dup'ed another bug onto this, as I think they are essentially the same. While Martin worked on the domain-restricted cases the reporter and others outlined that this is not what this bug is about. TL;DR: - anything (like vpn) provides new DNS servers on an extra link - lets call them "internal" and "external" sources of DNS info - systemd-resolved asks ALL local interfaces concurrently and takes the fastest answer - now we have two breaking use cases: - if "internal" and "external" are intentionally configured to report differently (override a DNS name to internal host) you can no more rely on getting the internal resolution - by asking "external" even if "internal" holds an answer is a dns leak as in [1] At least for the VPN cases - and most here seem to be that - what we would need is a way to "disable" the DNS resolving on the original interface. >From man systemd-resolved: Multi-label names are routed to all local interfaces that have a DNS sever configured, plus the globally configured DNS server if there is one. [...] If lookups are routed to multiple interfaces, the first successful response is returned (thus effectively merging the lookup zones on all matching interfaces). If the lookup failed on all interfaces, the last failing response is returned. >From the bug I dupped we have the output of $ systemd-resolve --status (There is also tcpdump data there) Both confirms that is lists all links and their DNS Link 4 (tun0) Current Scopes: DNS [...] DNS Servers: 209.222.18.222 209.222.18.218 Link 3 (wlp3s0) Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6 [...] DNS Servers: 192.168.0.1 Combined with the concurrent-quere-prefer-first behavior above that might be the root cause for all or most of the people chiming in here. [1]: https://www.dnsleaktest.com/ ** Changed in: systemd (Ubuntu) Importance: Medium => High ** Tags added: zesty -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS
Stephan, it is response time dependent - if your campus has a slow DNS answer then the others e.g. on your normal uplink will be preferred. -- 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/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1683237] Re: krb5-user: kinit fails for OTP user when using kdc discovery via DNS
This bug was fixed in the package krb5 - 1.15-2 Sponsored for ChristianEhrhardt (paelzer) --- krb5 (1.15-2) experimental; urgency=medium * Upstream patches to fix startup if getaddrinfo() returns a wildcard v6 address, and to fix handling of explicitly specified v4 wildcard address; regression over previous versions, Closes: #860767 * Fix SRV lookups to respect udp_preference_limit, regression over previous versions with OTP, Closes: #856307 -- Sam HartmanWed, 19 Apr 2017 16:50:01 -0400 ** Changed in: krb5 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to krb5 in Ubuntu. https://bugs.launchpad.net/bugs/1683237 Title: krb5-user: kinit fails for OTP user when using kdc discovery via DNS Status in krb5 package in Ubuntu: Fix Released Status in krb5 source package in Zesty: Triaged Status in krb5 package in Debian: Fix Released Bug description: Zesty is now affected, please see the debian bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856307 and upstream bug http://krbdev.mit.edu/rt/Ticket/Display.html?id=8554 Would it be possible to get 1.15.1 (already released upstream) in zesty/zesty-updates? Thanks Jochen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1683237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686036] Re: strange behavior after restore snapshot
bug on valid repo: https://github.com/lxc/lxd/issues/3228 ** Bug watch added: LXD bug tracker #3228 https://github.com/lxc/lxd/issues/3228 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1686036 Title: strange behavior after restore snapshot Status in lxc package in Ubuntu: New Bug description: uname -a Linux lxd2-chel1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lxd: 2.12-0ubuntu3~ubuntu16.04.1~ppa1 zfsutils-linux: 0.6.5.6-0ubuntu16 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial after restore container from shapshot cannot add new snapshot or restore again until restart container example: # lxc image list +---+--++--++-+--+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | +---+--++--++-+--+ | debian/jessie | ba43812c4cb9 | no | Debian jessie amd64 (20170423_22:42) | x86_64 | 94.14MB | Apr 24, 2017 at 9:07am (UTC) | +---+--++--++-+--+ # lxc launch debian/jessie Creating popular-kitten The container you are starting doesn't have any network attached to it. To create a new network, use: lxc network create To attach a network to a container, use: lxc network attach Starting popular-kitten # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running Type: persistent Profiles: default Pid: 6965 Ips: lo: inet127.0.0.1 lo: inet6 ::1 Resources: Processes: 7 Disk usage: root: 1.48MB CPU usage: CPU usage (in seconds): 25 Memory usage: Memory (current): 16.22MB Memory (peak): 23.01MB Network usage: lo: Bytes received: 0B Bytes sent: 0B Packets received: 0 Packets sent: 0 # lxc profile show default config: {} description: Default LXD profile devices: root: path: / pool: main-pool type: disk name: default used_by: - /1.0/containers/popular-kitten # lxc snapshot popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # lxc restore popular-kitten snap0 # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted no - # lxc snapshot popular-kitten error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy # lxc restore popular-kitten snap0 error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy but container still work: # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running ... # lxc exec popular-kitten bash root@popular-kitten:~# uptime 07:34:06 up 8 min, 0 users, load average: 0.00, 0.02, 0.03 after restart container: # lxc restart popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - on another server this problem missmatch: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety # lxd --version 2.4.1 zfsutils-linux: 0.6.5.8-0ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1686036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1686361] Re: systemd does not respect nofile ulimit when running in container
** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Artful) Importance: Undecided Assignee: Dimitri John Ledkov (xnox) Status: Confirmed ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Yakkety) 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/1686361 Title: systemd does not respect nofile ulimit when running in container Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: New Status in systemd source package in Yakkety: New Status in systemd source package in Zesty: New Status in systemd source package in Artful: Confirmed Bug description: When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g. 10 systemd will lower it to 65536 since this value is hard-coded into systemd. I've pushed a patch to systemd upstream that will try to set the nofile limit to the allowed kernel maximum. If this fails, it will compute the minimum of the current set value (the limit that is set on the container) and the maximum value as soft limit and the currently set maximum value as the maximum value. This way it retains the limit set on the container. It would be great if we could backport this patch to have system adhere to nofile limits set for the container. This is especially important since user namespaces will allow you to lower the limit but not raise it back up afterwards. The upstream patch is appended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+subscriptions -- Mailing list: https://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 1686243] Re: NVIDIA driver
Hi. Thanks for quick response. You're mentioning that I need to use prime-select. Do you have a link on how I should proceed with on terminal or in a different fashion. My concern is that I have a built machine and really want to use Ubuntu/Linux distro. Nvidia drivers is for my need to do video and photo edit while also gaming for my kids. Much appreciated Best regards Sebastian Carter 26. apr. 2017 7:41 a.m. skrev "Timo Aaltonen": you're using an unofficial ppa which could mess things up, besides your machine is a hybrid machine so you need to use prime-select in order to switch to nvidia ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1686243 Title: NVIDIA driver Status in xorg package in Ubuntu: Invalid Bug description: Trying for days to install an nvidia driver ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17 Uname: Linux 4.8.0-49-lowlatency x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/ screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 26 01:19:29 2017 DistUpgraded: 2017-04-26 01:05:13,339 DEBUG icon theme changed, re-reading DistroCodename: yakkety DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.8.0-49-lowlatency, x86_64: installed nvidia-378, 378.13, 4.8.0-49-lowlatency, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] InstallationDate: Installed on 2017-04-24 (1 days ago) InstallationMedia: Ubuntu-Studio 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-49-lowlatency root=UUID=65af2065-0769-48de-9408-1d7d5313f54e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to yakkety on 2017-04-25 (0 days ago) dmi.bios.date: 11/11/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2801:bd11/11/2015:svnASUS: pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97- A:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.80+git20170420.691a2157-0ubuntu0ricotz~xenial version.libgl1-mesa-dri: libgl1-mesa-dri 17.1.0~git20170425+17.1. 2bf79cb2-0ubuntu0ricotz~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.1.0~git20170425+17.1. 2bf79cb2-0ubuntu0ricotz~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Apr 26 01:05:56 2017 xserver.configfile: default xserver.errors: Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) Failed to load module "fbdev" (module does not exist, 0) Failed to load module "vesa" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1686243/+subscriptions -- 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/1686243 Title: NVIDIA driver Status in xorg package in Ubuntu: Invalid Bug description: Trying for days to install an nvidia driver ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-49.52-lowlatency 4.8.17 Uname: Linux 4.8.0-49-lowlatency x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64
[Touch-packages] [Bug 1686057] Re: Sync libdrm 2.4.80-1 (main) from Debian experimental (main)
This bug was fixed in the package libdrm - 2.4.80-1 --- libdrm (2.4.80-1) experimental; urgency=medium * New upstream release. * Bump libdrm-amdgpu1's and libdrm-etnaviv1's symbols and shlibs. * Remove libpthread-stubs0-dev build-dep per configure.ac. -- Andreas BollWed, 19 Apr 2017 15:35:21 +0200 libdrm (2.4.77-1) experimental; urgency=medium * Team upload. * New upstream release. * Bump libdrm-amdgpu1 symbols. * Update debian/upstream/signing-key.asc -- Jordan Justen Wed, 05 Apr 2017 02:30:35 -0700 ** Changed in: libdrm (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1686057 Title: Sync libdrm 2.4.80-1 (main) from Debian experimental (main) Status in libdrm package in Ubuntu: Fix Released Bug description: Please sync libdrm 2.4.80-1 (main) from Debian experimental (main) Changelog entries since current artful version 2.4.76-1: libdrm (2.4.80-1) experimental; urgency=medium * New upstream release. * Bump libdrm-amdgpu1's and libdrm-etnaviv1's symbols and shlibs. * Remove libpthread-stubs0-dev build-dep per configure.ac. -- Andreas Boll Wed, 19 Apr 2017 15:35:21 +0200 libdrm (2.4.77-1) experimental; urgency=medium * Team upload. * New upstream release. * Bump libdrm-amdgpu1 symbols. * Update debian/upstream/signing-key.asc -- Jordan Justen Wed, 05 Apr 2017 02:30:35 -0700 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1686057/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686036] Re: strange behavior after restore snapshot
created on github: https://github.com/zfsonlinux/zfs/issues/6070 ** Bug watch added: Github Issue Tracker for ZFS #6070 https://github.com/zfsonlinux/zfs/issues/6070 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1686036 Title: strange behavior after restore snapshot Status in lxc package in Ubuntu: New Bug description: uname -a Linux lxd2-chel1 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux lxd: 2.12-0ubuntu3~ubuntu16.04.1~ppa1 zfsutils-linux: 0.6.5.6-0ubuntu16 # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial after restore container from shapshot cannot add new snapshot or restore again until restart container example: # lxc image list +---+--++--++-+--+ | ALIAS | FINGERPRINT | PUBLIC | DESCRIPTION | ARCH | SIZE | UPLOAD DATE | +---+--++--++-+--+ | debian/jessie | ba43812c4cb9 | no | Debian jessie amd64 (20170423_22:42) | x86_64 | 94.14MB | Apr 24, 2017 at 9:07am (UTC) | +---+--++--++-+--+ # lxc launch debian/jessie Creating popular-kitten The container you are starting doesn't have any network attached to it. To create a new network, use: lxc network create To attach a network to a container, use: lxc network attach Starting popular-kitten # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running Type: persistent Profiles: default Pid: 6965 Ips: lo: inet127.0.0.1 lo: inet6 ::1 Resources: Processes: 7 Disk usage: root: 1.48MB CPU usage: CPU usage (in seconds): 25 Memory usage: Memory (current): 16.22MB Memory (peak): 23.01MB Network usage: lo: Bytes received: 0B Bytes sent: 0B Packets received: 0 Packets sent: 0 # lxc profile show default config: {} description: Default LXD profile devices: root: path: / pool: main-pool type: disk name: default used_by: - /1.0/containers/popular-kitten # lxc snapshot popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # lxc restore popular-kitten snap0 # zfs get mounted main-pool/snapshots/popular-kitten NAMEPROPERTY VALUESOURCE main-pool/snapshots/popular-kitten mounted yes - # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted no - # lxc snapshot popular-kitten error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy # lxc restore popular-kitten snap0 error: Failed to mount ZFS filesystem: filesystem 'main-pool/containers/popular-kitten' is already mounted cannot mount 'main-pool/containers/popular-kitten': mountpoint or dataset is busy but container still work: # lxc info popular-kitten Name: popular-kitten Remote: unix:/var/lib/lxd/unix.socket Architecture: x86_64 Created: 2017/04/25 07:17 UTC Status: Running ... # lxc exec popular-kitten bash root@popular-kitten:~# uptime 07:34:06 up 8 min, 0 users, load average: 0.00, 0.02, 0.03 after restart container: # lxc restart popular-kitten # zfs get mounted main-pool/containers/popular-kitten NAME PROPERTY VALUESOURCE main-pool/containers/popular-kitten mounted yes - on another server this problem missmatch: # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.10 Release:16.10 Codename: yakkety # lxd --version 2.4.1 zfsutils-linux: 0.6.5.8-0ubuntu4.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1686036/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1630516] Re: Logrotate doesn't clean old system logs, allowing them to fill the disk
Looks to me like everything worked fine overnight. $ ls -l /var/log/syslog* -rw-r- 1 syslog adm 587351 Apr 26 12:10 /var/log/syslog -rw-r- 1 syslog adm 1824727 Apr 26 07:38 /var/log/syslog.1 -rw-r--r-- 1 root root 0 Apr 25 15:48 /var/log/syslog.2 -rw-r- 1 syslog adm37783 Apr 25 07:35 /var/log/syslog.2.gz -rw-r- 1 syslog adm26955 Apr 24 07:35 /var/log/syslog.3.gz -rw-r- 1 syslog adm26695 Apr 23 07:35 /var/log/syslog.4.gz -rw-r- 1 syslog adm31307 Apr 22 07:35 /var/log/syslog.5.gz -rw-r- 1 syslog adm32909 Apr 21 07:35 /var/log/syslog.6.gz -rw-r- 1 syslog adm39182 Apr 20 07:35 /var/log/syslog.7.gz The presence of the inconveniently named file looks to have been ignored and the log rotations continued unabated. > change the tag from verification-needed to verification-done I have only verified this on Xenia so far. I think that means I leave the tags alone for now right? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1630516 Title: Logrotate doesn't clean old system logs, allowing them to fill the disk Status in One Hundred Papercuts: Triaged Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Trusty: Fix Committed Status in logrotate source package in Xenial: Fix Committed Status in logrotate source package in Yakkety: Fix Committed Status in logrotate source package in Zesty: Fix Released Status in logrotate package in Debian: Fix Released Bug description: [Impact] Logrotate fails to rotate a log and then will continue to fail to rotate it until manual intervention takes place. If messaging has not been configured on the system there will be no warning issued to the user. The log will grow day by day until a user intervenes or the drive that the log is stored on is full. Very large log files can make it more difficult to find useful data. Full drives make the rest of the system fail to operate. Backporting a fix would prevent drives filling up on stable releases. [Test Case] Go to your logs area (/var/logs) and create a file with a name ending .2, as would be created part way through the logrotate process. So if you have /var/log/syslog, /var/log/syslog.1, /var/log/syslog.2.gz, /var/log/syslog.3.gz; create a new file named /var/log/syslog.2. Your subsequent log rotate runs will fail. [Regression Potential] - I'd hope the potential is low as it only triggers under certain conditions that are special (target filename in the way). - So far in those conditions it failed to rotate - Yet If despite my hope there still manifests an issue I'd expect it could be renaming files it should not, so people would end up "missing" their logs - the good thing is that this is a rename, so they should find it at different names. - Another thing I consider possible is that some unexpected conditions cause e.g. a crash in the changed code, in that case the logs are not rotated, but since there is no unlink the logs will still exist. - Therefore I consider the Potential low enough to consider the fix. [Other Info] n/a --- Good afternoon. I have started seeing something very similar to Debian Dug 734688 "Logs are not rotated for a month" but in the latest Ubuntu LTS (16.04). I seem to have $ logrotate --version logrotate 3.8.7 bundled in it. A few weeks ago I started getting root emails such as this: > Subject: Crontest -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > > /etc/cron.daily/logrotate: > error: error creating output file /var/log/munin/munin-node.log.1: File exists > run-parts: /etc/cron.daily/logrotate exited with return code 1 When I inspected the area of concern I was able to see that there was an existing .1 file. manager@warden:/var/log/munin$ ll total 580 drwxr-xr-x 2 munin adm 4096 Sep 27 06:31 ./ drwxr-xr-x 13 root syslog 4096 Oct 5 06:26 ../ -rw-r--r-- 1 root root 3440 Sep 26 13:39 munin-node-configure.log -rw-r--r-- 1 root root 490251 Oct 5 10:25 munin-node.log -rw-r--r-- 1 root root56598 Sep 21 02:01 munin-node.log.1 -rw-r--r-- 1 root root24576 Aug 31 02:01 munin-node.log.2 -rw-r--r-- 1 root root 1906 Sep 19 06:25 munin-node.log.8.gz The contents of the munin-node.log file seem to run from the 19th September until today. Unlike other parts of this bug the .1 and .2 files do not seem to be already compressed. I deleted all but the munin-node.log file to see if it would resolve the problem and was going to leave it at that. Then I noticed that I have had another Ubuntu machine which has been sending similar emails for the past week: > Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) > >
[Touch-packages] [Bug 1686344] Re: Mesa 17.0.x stable release
** Description changed: [Impact] Mesa stable release for zesty & backport to xenial. [Test case] Install, run desktop session, test xonotic. the important hw drivers to test: - i965 (Intel) - radeonsi (AMD) [Regression potential] Spec compliance test suites are already run by Intel and others, so feature regressions should not be possible. GLESv1 support has been dropped from the packaging though, but packages that depend on libgles1-mesa have been pushed to proposed to drop the dependency, see bug 1676845 (applies to xenial). + 17.0.x has been available for xenial and yakkety users for a while, and + so far no-one has complained about driver regressions. + [Other info] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1686344 Title: Mesa 17.0.x stable release Status in mesa package in Ubuntu: New Bug description: [Impact] Mesa stable release for zesty & backport to xenial. [Test case] Install, run desktop session, test xonotic. the important hw drivers to test: - i965 (Intel) - radeonsi (AMD) [Regression potential] Spec compliance test suites are already run by Intel and others, so feature regressions should not be possible. GLESv1 support has been dropped from the packaging though, but packages that depend on libgles1-mesa have been pushed to proposed to drop the dependency, see bug 1676845 (applies to xenial). 17.0.x has been available for xenial and yakkety users for a while, and so far no-one has complained about driver regressions. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1686344/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1685900] Re: On artful, no working dns after upgrading to systemd 233-5ubuntu1
** Description changed: - After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no network. + After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no nameserver (dns). This is very likely a DNS issue. As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS work fine. + Or instead, I must manually start systemd-resolved: + ~$ sudo service systemd-resolved restart So something odd has happened between these versions. + Systemd-resolved is not starting automatically at boot anymore. My setup is a fully upgraded artful with proposed repo turned on. I use only Gnome DE with GDM. Everything else works fine, but not systemd 233-5ubuntu1. -- 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/1685900 Title: On artful, no working dns after upgrading to systemd 233-5ubuntu1 Status in systemd package in Ubuntu: Incomplete Bug description: After upgrading to the newest systemd 233-5ubuntu1 (in artful proposed) I got no nameserver (dns). This is very likely a DNS issue. As a workaround downgrading back to systemd 232-21ubuntu3 the network and DNS work fine. Or instead, I must manually start systemd-resolved: ~$ sudo service systemd-resolved restart So something odd has happened between these versions. Systemd-resolved is not starting automatically at boot anymore. My setup is a fully upgraded artful with proposed repo turned on. I use only Gnome DE with GDM. Everything else works fine, but not systemd 233-5ubuntu1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1685900/+subscriptions -- Mailing list: https://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 1686361] Re: systemd does not respect nofile ulimit when running in container
Would be good if we could also SRU that to Xenial as well since this is likely what users will be using most of the time as image in their container. Adding stgraber to this thread. -- 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/1686361 Title: systemd does not respect nofile ulimit when running in container Status in systemd package in Ubuntu: Confirmed Bug description: When systemd currently starts in a container that has RLIMIT_NOFILE set to e.g. 10 systemd will lower it to 65536 since this value is hard-coded into systemd. I've pushed a patch to systemd upstream that will try to set the nofile limit to the allowed kernel maximum. If this fails, it will compute the minimum of the current set value (the limit that is set on the container) and the maximum value as soft limit and the currently set maximum value as the maximum value. This way it retains the limit set on the container. It would be great if we could backport this patch to have system adhere to nofile limits set for the container. This is especially important since user namespaces will allow you to lower the limit but not raise it back up afterwards. The upstream patch is appended. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 921489] Re: Segmentation fault in slapd (related to GSSAPI?)
I have a similar problem on a freshly installed 16.04 machine: slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080 error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000] I'm using the server as Slave LDAP-Server and sync replication with kerberos authentication. The service either starts and runs successfully or it fails with segmentation fault and 100% cpu. slapd 2.4.42+dfsg-2ubuntu3.1 libsasl2-2:amd64 2.1.26.dfsg1-14build1 libsasl2-modules:amd64 2.1.26.dfsg1-14build1 libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1 Any suggestions or ideas? Br -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/921489 Title: Segmentation fault in slapd (related to GSSAPI?) Status in openldap package in Ubuntu: Confirmed Bug description: In our installation slapd will crash with a Segmentation Fault about once a week. It has been seen on the producer while the consumers connect but also on both producer and consumers at random. It seems to be related to authentication with GSSAPI. syslog produces the followig message: kernel: [513493.152760] slapd[1610]: segfault at 7fb242df9000 ip 7fb242ad7122 sp 7fb127ffd900 error 4 in libcrypto.so.0.9.8[7fb242a61000+168000] gdb: Core was generated by usr/sbin/slapd -d 0 -h ldap:/// ldaps:/// -f /local/sukat/conf/slapd.conf'. Program terminated with signal 11, Segmentation fault. #0 sha1_block_data_order () at sha1-x86_64.s:133 133 sha1-x86_64.s: No such file or directory. in sha1-x86_64.s (gdb) bt #0 sha1_block_data_order () at sha1-x86_64.s:133 #1 0x005e1700 in ?? () #2 0x1700 in ?? () #3 0x in ?? () The backtrace is incomplete as the debug packages are broken. Trying to reproduce this bug I trigger another segfault. I will file reports on thease issues in separate tickets. ProblemType: Bug Architecture: amd64 Date: Wed Jan 25 11:13:22 2012 Dependencies: adduser 3.112ubuntu1 base-files 5.0.0ubuntu20.10.04.4 base-passwd 3.5.22 coreutils 7.4-2ubuntu3 debconf 1.5.28ubuntu4 debconf-i18n 1.5.28ubuntu4 debianutils 3.2.2 dpkg 1.15.5.6ubuntu4.5 [modified: sbin/start-stop-daemon] findutils 4.4.2-1ubuntu1 gcc-4.4-base 4.4.3-4ubuntu5 libacl1 2.2.49-2 libattr1 1:2.4.44-1 libbz2-1.0 1.0.5-4ubuntu0.2 libc-bin 2.11.1-0ubuntu7.8 libc6 2.11.1-0ubuntu7.8 libcomerr2 1.41.11-1ubuntu2.1 libdb4.7 4.7.25-9 libdb4.8 4.8.24-1ubuntu1 libgcc1 1:4.4.3-4ubuntu5 libgcrypt11 1.4.4-5ubuntu2 libgdbm3 1.8.3-9 libgnutls26 2.8.5-2 libgpg-error0 1.6-1ubuntu2 libgssapi-krb5-2 1.8.1+dfsg-2ubuntu0.10 libk5crypto3 1.8.1+dfsg-2ubuntu0.10 libkeyutils1 1.2-12 libkrb5-3 1.8.1+dfsg-2ubuntu0.10 libkrb5support0 1.8.1+dfsg-2ubuntu0.10 libldap-2.4-2 2.4.21-0ubuntu5.6 liblocale-gettext-perl 1.05-6 libltdl7 2.2.6b-2ubuntu1 libncurses5 5.7+20090803-2ubuntu3 libpam-modules 1.1.1-2ubuntu5.4 libpam0g 1.1.1-2ubuntu5.4 libperl5.10 5.10.1-8ubuntu2.1 libreadline6 6.1-1 libsasl2-2 2.1.23.dfsg1-5ubuntu1 libselinux1 2.0.89-4 libslp1 1.2.1-7.6ubuntu0.1 libstdc++6 4.4.3-4ubuntu5 libtasn1-3 2.4-1 libtext-charwidth-perl 0.04-6 libtext-iconv-perl 1.7-2 libtext-wrapi18n-perl 0.06-7 libwrap0 7.6.q-18 lzma 4.43-14ubuntu2 odbcinst 2.2.11-21 odbcinst1debian1 2.2.11-21 passwd 1:4.1.4.2-1ubuntu2.2 perl 5.10.1-8ubuntu2.1 perl-base 5.10.1-8ubuntu2.1 perl-modules 5.10.1-8ubuntu2.1 psmisc 22.10-1 readline-common 6.1-1 sensible-utils 0.0.1ubuntu3 tzdata 2011n-0ubuntu0.10.04 unixodbc 2.2.11-21 zlib1g 1:1.2.3.3.dfsg-15ubuntu1 DistroRelease: Ubuntu 10.04 NonfreeKernelModules: openafs Package: slapd 2.4.21-0ubuntu5.6 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LC_CTYPE=en_GB.UTF-8 ProcVersionSignature: Ubuntu 2.6.32-37.81-generic 2.6.32.49+drm33.21 SourcePackage: openldap Tags: lucid Uname: Linux 2.6.32-37-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/921489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp