[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Actually I was able to make it work! I needed to remove "options snd-hda-intel dmic_detect=0" from /etc/modprobe.d/alsa-base.conf -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
This does not work for me. My Hardware Devices were listed as follows List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 0/1 Subdevice #0: subdevice #0 Added to line to /etc/modprobe.d/alsa-base.conf and my internal microphone did not work. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
I have the hp spectre x360 13 convertible and the update to 20.04 did not work for me either. -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779129] [NEW] package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for co
Public bug reported: i was installing latex-maker and as it ended i got that error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 28 07:03:23 2018 DpkgTerminalLog: dpkg: error processing package libfdisk1:amd64 (--configure): package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: util-linux Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1779129 Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux- gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') Status in util-linux package in Ubuntu: New Bug description: i was installing latex-maker and as it ended i got that error. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Thu Jun 28 07:03:23 2018 DpkgTerminalLog: dpkg: error processing package libfdisk1:amd64 (--configure): package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-06-18 (10 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: util-linux Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1779129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654448] Re: XPS 13 9360, Realtek ALC3246, Headphone audio hiss
@frail-knight, the right people are already subscribed to this bug. Please *stop* changing bugs to affect dell-sputnik ** Changed in: dell-sputnik Status: New => Incomplete ** Changed in: dell-sputnik Status: Incomplete => Invalid -- 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/1654448 Title: XPS 13 9360, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: Invalid Status in alsa-driver package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
DKMS is a Dell project but not Project Sputnik. Marking as invalid for dell-sputnik. ** Changed in: dell-sputnik Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in Dell Sputnik: Invalid Status in dkms package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms package in Debian: New Bug description: One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688317] Re: PCI/internal sound card not detected
You're running a non-OEM version of Ubuntu 16.04.1, which is too old to fully support this platform. Canonical maintains driver backports for this platform only for factory-installed Ubuntu 16.04, and that includes backport DKMS packages. Either wait until this is backported to a later Ubuntu 16.04 point release, use a later version of Ubuntu or purchase with Ubuntu pre-installed instead of Windows. ** Changed in: dell-sputnik Status: New => Invalid ** Changed in: alsa-driver (Ubuntu) Status: New => Invalid -- 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/1688317 Title: PCI/internal sound card not detected Status in Dell Sputnik: Invalid Status in alsa-driver package in Ubuntu: Invalid Bug description: No sound card detected at all, no sound for laptop/bluetooth headphones ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-77.98-generic 4.4.59 Uname: Linux 4.4.0-77-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu May 4 10:41:20 2017 InstallationDate: Installed on 2017-01-25 (98 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 0T3FTF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1688317/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1650259] Re: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack
Have you checked in the system settings GUI whether the headphone jack shows as an output option? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1650259 Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all from the headphone jack Status in Dell Sputnik: New Status in pulseaudio package in Ubuntu: Confirmed Bug description: The problem is that there is no sound at the jack for the headphones. Internal speaker are silenced when inserted a headphone jack but there is no sound output. Tested a live MS windows and sound worked! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-53.74-generic 4.4.30 Uname: Linux 4.4.0-53-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaki 2355 F pulseaudio CurrentDesktop: Unity Date: Thu Dec 15 12:41:55 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150720-0 InstallationDate: Installed on 2016-06-25 (173 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150720-04:06 ProcEnviron: LANGUAGE=it PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaki 2355 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS 13 9350, Realtek ALC3246, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to xenial on 2016-09-07 (98 days ago) dmi.bios.date: 06/14/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.4 dmi.board.name: 0H67KH dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0H67KH:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1650259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1651433] Re: bluetooth mouse random disconnects
It looks like on OEM systems, we tweak /etc/bluetooth/main.conf by adding "AutoEnable=true". Can you check what that's set to on your system? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1651433 Title: bluetooth mouse random disconnects Status in bluez package in Ubuntu: Confirmed Bug description: I received the Dell XPS 13 DE (9350) accompanied by the WD15 docking station last September. Ever since I used it with my Logitech MX Master bluetooth mouse. This worked very well and reliably for September through November. But Since about start of December, it disconnects frequently and without any apparent reason. I can get it back to order by disabling and re-enabling the bluetooth radio of the notebook. After I re-enable the bt radio and move the mouse it work immediately without any delay. Sometimes it disconnects after 10 seconds. Sometimes I can work for 10 hours without any disconnect. For the entire lifetime the device has been running xenial. Currently I'm on kernel Linux XPS13ulr 4.4.0-53-generic #74-Ubuntu SMP Because the issue started happening at a certain date, I strongly believe that it was caused by and upgrade, possibly kernel. I wanted to see if the same disconnects also happen with other BT devices. But for as long as I had the Jabra Halo 2 headset connected, also the mouse worked reliably. The mouse is my only BT LE device. Maybe that makes a difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1651433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1643717] [NEW] package tar 1.27.1-1ubuntu0.1 failed to install/upgrade
Public bug reported: I'm new to bug reporting so please forgive me if I'm doing it wrong. I was trying to run apt-get updgrade and it crashed. There appears to be something wrong with tar, but I don't know what or how. My system is pretty hosed at the moment. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tar 1.27.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Nov 22 12:14:59 2016 DuplicateSignature: package:tar:1.27.1-1ubuntu0.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-10-22 (761 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: tar Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2016-08-07 (106 days ago) ** Affects: tar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tar in Ubuntu. https://bugs.launchpad.net/bugs/1643717 Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade Status in tar package in Ubuntu: New Bug description: I'm new to bug reporting so please forgive me if I'm doing it wrong. I was trying to run apt-get updgrade and it crashed. There appears to be something wrong with tar, but I don't know what or how. My system is pretty hosed at the moment. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: tar 1.27.1-1ubuntu0.1 ProcVersionSignature: Ubuntu 3.13.0-101.148-generic 3.13.11-ckt39 Uname: Linux 3.13.0-101-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Tue Nov 22 12:14:59 2016 DuplicateSignature: package:tar:1.27.1-1ubuntu0.1:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-10-22 (761 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.15 SourcePackage: tar Title: package tar 1.27.1-1ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to trusty on 2016-08-07 (106 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tar/+bug/1643717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379427] Re: /etc/network/if-up.d/upstart emits static-network-up too early
** Summary changed: - /etc/network/if-up.d/upstart emits static-network-up to early + /etc/network/if-up.d/upstart emits static-network-up too early -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1379427 Title: /etc/network/if-up.d/upstart emits static-network-up too early Status in ifupdown package in Ubuntu: Triaged Bug description: I came across this when debugging bug 1352255. as implemented right now (trusty and utopic) the 'static-network-up' event is emitted when each 'auto' interface has had *an* address configured, as opposed to *all* addresses configured. Heres why: ifupdown calls runparts on /etc/network/if-up.d/ after each stanza for a network inteface, rather than once after *all* stanzas are executed. The result is that things that were waiting on 'static-network-up', expecting that would provide them with expected networking are not actually guaranteed anything other than the first stanza for each interface. (note also that this happens to cause strange behavior in bug 1352255). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ifupdown 0.7.47.2ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 Date: Thu Oct 9 12:37:10 2014 InstallationDate: Installed on 2011-12-06 (1037 days ago) InstallationMedia: Ubuntu-Server 11.10 "Oneiric Ocelot" - Release amd64 (20111011) ProcEnviron: TERM=screen-bce PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ifupdown UpgradeStatus: Upgraded to trusty on 2014-08-01 (69 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1379427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603406] Re: /etc/init.d/networking restart
*** This bug is a duplicate of bug 1301015 *** https://bugs.launchpad.net/bugs/1301015 ** This bug has been marked a duplicate of bug 1301015 Networking does not restart -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1603406 Title: /etc/init.d/networking restart Status in ifupdown package in Ubuntu: New Bug description: stop: Job failed while stopping start: Job is already running: networking To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1603406/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1556419] Re: nf_conntrack: automatic helper assignment is deprecated
** Tags added: yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1556419 Title: nf_conntrack: automatic helper assignment is deprecated Status in iptables package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Get this logged into journalctl (since a moment): kernel: nf_conntrack: automatic helper assignment is deprecated and it will be removed soon. Use the iptables CT target to attach helpers instead. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-13-generic 4.4.0-13.29 ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5 Uname: Linux 4.4.0-13-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: oem1942 F pulseaudio /dev/snd/pcmC0D0p: oem1942 F...m pulseaudio /dev/snd/controlC0: oem1942 F pulseaudio CurrentDesktop: GNOME Date: Sat Mar 12 14:52:09 2016 HibernationDevice: RESUME=UUID=0a9ca7f0-6eeb-4b21-b70f-670fa600de16 IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic root=UUID=7c755ed6-51cc-4b75-88ac-9c75acf82749 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-13-generic N/A linux-backports-modules-4.4.0-13-generic N/A linux-firmware1.156 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1556419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1591411] Re: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay
We have some servers that host git mirrors accessed via SSH that are affected by this. Restarting systemd-logind via cron every 5 minutes works for us (no full system restart necessary.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1591411 Title: systemd-logind must be restarted every ~1000 SSH logins to prevent a ~25 second delay Status in D-Bus: Unknown Status in systemd: Unknown Status in dbus package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in dbus source package in Xenial: Confirmed Status in systemd source package in Xenial: Invalid Bug description: I noticed on a system that accepts large numbers of SSH connections that after awhile, SSH sessions were taking ~25 seconds to complete. Looking in /var/log/auth.log, systemd-logind starts failing with the following: Jun 10 23:55:28 test sshd[3666]: pam_unix(sshd:session): session opened for user ubuntu by (uid=0) Jun 10 23:55:28 test systemd-logind[105]: New session c1052 of user ubuntu. Jun 10 23:55:28 test systemd-logind[105]: Failed to abandon session scope: Transport endpoint is not connected Jun 10 23:55:28 test sshd[3666]: pam_systemd(sshd:session): Failed to create session: Message recipient disconnected from message bus without replying I reproduced this in an LXD container by doing something like: lxc launch ubuntu:x test lxc exec test -- login -f ubuntu ssh-import-id Then ran a script as follows (passing in ubuntu@): while [ 1 ]; do (time ssh $1 "echo OK > /dev/null") 2>&1 | grep ^real >> log done In my case, after 1052 logins, the 1053rd and thereafter were taking 25+ seconds to complete. Here are some snippets from the log file: $ cat log | grep 0m0 | wc -l 1052 $ cat log | grep 0m25 | wc -l 4 $ tail -5 log real 0m0.222s real 0m25.232s real 0m25.235s real 0m25.236s real 0m25.239s ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sat Jun 11 00:09:34 2016 MachineType: Notebook W230SS ProcEnviron: TERM=xterm-256color PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W230SS dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/15/2014:svnNotebook:pnW230SS:pvrNotApplicable:rvnNotebook:rnW230SS:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.name: W230SS dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1591411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file
One thing I've noticed that may be of interest is that this only occurs for me now during boot up. If manually started with the command "sudo systemctl start isc-dhcp-server.service" it starts up fine with no errors. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file
I'm also still seeing this on 16.04 LTS with systemd. This is an upgrade, not a fresh install. Aug 26 12:30:52 Host sh[4059]: Can't open /var/lib/dhcp/dhcpd.leases for append. Aug 26 12:30:52 Host dhcpd[4059]: Copyright 2004-2015 Internet Systems Consortium. Aug 26 12:30:52 Host kernel: [ 55.961181] audit: type=1400 audit(1472239852.640:16): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=4059 comm="dhcpd" capability=1 capname="dac_override" Aug 26 12:30:52 Host dhcpd[4059]: All rights reserved. Aug 26 12:30:52 Host dhcpd[4059]: For info, please visit https://www.isc.org/software/dhcp/ Aug 26 12:30:52 Host dhcpd[4059]: Can't open /var/lib/dhcp/dhcpd.leases for append. Aug 26 12:30:52 Host dhcpd[4059]: Aug 26 12:30:52 Host dhcpd[4059]: If you think you have received this message due to a bug rather Aug 26 12:30:52 Host dhcpd[4059]: than a configuration issue please read the section on submitting Aug 26 12:30:52 Host dhcpd[4059]: bugs on either our web page at www.isc.org or in the README file Aug 26 12:30:52 Host dhcpd[4059]: before submitting a bug. These pages explain the proper Aug 26 12:30:52 Host dhcpd[4059]: process and the information we find helpful for debugging.. Aug 26 12:30:52 Host dhcpd[4059]: Aug 26 12:30:52 Host dhcpd[4059]: exiting. Aug 26 12:30:52 Host systemd[1]: isc-dhcp-server.service: Main process exited, code=exited, status=1/FAILURE Aug 26 12:30:52 Host systemd[1]: isc-dhcp-server.service: Unit entered failed state. Aug 26 12:30:52 Host systemd[1]: isc-dhcp-server.service: Failed with result 'exit-code'. ** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Triaged Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1475850] Re: Several update-rc.d/insserv warnings
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to insserv in Ubuntu. https://bugs.launchpad.net/bugs/1475850 Title: Several update-rc.d/insserv warnings Status in insserv package in Ubuntu: Confirmed Status in sysvinit package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 15.10 dev with insserv 1.14.0-5ubuntu3 and sysv-rc 2.88dsf-59.2ubuntu1 and on configuring packages I have seen now for some time several update-rc.d/insserv warnings. If I'm reconfiguring all packages installed on my system they appear on: - cron 3.0pl1-127ubuntu1: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: stop runlevel arguments (1) do not match cron Default-Stop values (none) insserv: warning: current stop runlevel(s) (1) of script `cron' overrides LSB defaults (empty). - cryptsetup 2:1.6.1-1ubuntu7: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - grub-common 2.02~beta2-26ubuntu3: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - keyboard-configuration 1.108ubuntu5: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - ntp 1:4.2.6.p5+dfsg-3ubuntu6: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - procps 1:3.3.9-1ubuntu8: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults - x11-common 1:7.7+7ubuntu4: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/insserv/+bug/1475850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579246] [NEW] Ubuntu 16.04 nm-applet-Message: No keyring secrets found for
Public bug reported: If you use a 802.1x autentication in NetworkManager, the NetworkManager never save password on /etc/NetworkManager/system- connections/MySecureNetworkAlias, As a workarround you can add the password manualy in file /etc/NetworkManager/system-connections/MySecureNetworkAlias (using $ sudo vi) [802-1x] altsubject-matches= ca-cert=/mycert.cer eap=peap; identity=DOMAIN\\USER password=MyPassword <--- this is the line phase2-altsubject-matches= phase2-auth=mschapv2 The log is: may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8763] device (enp8s0): state change: need-auth -> prepare (reason 'none') [60 40 0] may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8767] device (enp8s0): state change: prepare -> config (reason 'none') [40 50 0] may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8770] device (enp8s0): Activation: (ethernet) connection 'MySecureNetworkAlias' has security, but secrets are required. may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8770] device (enp8s0): state change: config -> need-auth (reason 'none') [50 60 0] may 06 16:24:07 jared-laptop gnome-session[1599]: nm-applet-Message: No keyring secrets found for Produban/802-1x; asking user. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1579246 Title: Ubuntu 16.04 nm-applet-Message: No keyring secrets found for Status in network-manager package in Ubuntu: New Bug description: If you use a 802.1x autentication in NetworkManager, the NetworkManager never save password on /etc/NetworkManager/system- connections/MySecureNetworkAlias, As a workarround you can add the password manualy in file /etc/NetworkManager/system-connections/MySecureNetworkAlias (using $ sudo vi) [802-1x] altsubject-matches= ca-cert=/mycert.cer eap=peap; identity=DOMAIN\\USER password=MyPassword <--- this is the line phase2-altsubject-matches= phase2-auth=mschapv2 The log is: may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8763] device (enp8s0): state change: need-auth -> prepare (reason 'none') [60 40 0] may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8767] device (enp8s0): state change: prepare -> config (reason 'none') [40 50 0] may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8770] device (enp8s0): Activation: (ethernet) connection 'MySecureNetworkAlias' has security, but secrets are required. may 06 16:24:06 jared-laptop NetworkManager[976]: [1462569846.8770] device (enp8s0): state change: config -> need-auth (reason 'none') [50 60 0] may 06 16:24:07 jared-laptop gnome-session[1599]: nm-applet-Message: No keyring secrets found for Produban/802-1x; asking user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579246/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time
Correction, I was able to get gmoutso's solution to work. I realized that I needed to create a separate boot partition that didn't use lvm caching. In retrospect, this makes a lot of sense. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551518 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1550538 Title: periodically after suspend/resume wpasupplicant fails to authenticate Status in wpa package in Ubuntu: New Bug description: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550504] Re: lightdm unresponsive after suspend
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551514 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1550504 Title: lightdm unresponsive after suspend Status in lightdm package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
Also tracked at https://bugs.launchpad.net/somerville/+bug/1551516 -- 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/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /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/1550490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
Note that trying to turn on and off the wireless card using the wireless hotkey did not help. As can be seen from the logs, NM reports wifi's killswitch status change but still does not see any APs or try reconnecting. -- 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/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /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/1550490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550538] Re: periodically after suspend/resume wpasupplicant fails to authenticate
The failure was seen with WPA2 Personal with an Aruba access point. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1550538 Title: periodically after suspend/resume wpasupplicant fails to authenticate Status in wpa package in Ubuntu: New Bug description: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
This occurred about every five to ten reboots. -- 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/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /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/1550490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550504] Re: lightdm unresponsive after suspend
I can't reproduce on a system with the FHD panel. It may be restricted to the UHD model. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1550504 Title: lightdm unresponsive after suspend Status in lightdm package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550490] Re: network-manager unresponsive after suspend
The failure was seen with WPA2 Personal with an Aruba access point. -- 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/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /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/1550490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550538] [NEW] periodically after suspend/resume wpasupplicant fails to authenticate
Public bug reported: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (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 wpa in Ubuntu. https://bugs.launchpad.net/bugs/1550538 Title: periodically after suspend/resume wpasupplicant fails to authenticate Status in wpa package in Ubuntu: New Bug description: After suspending and resuming, periodically wpasupplicant fails to reauthenticate. I'm prompted for a password to reconnect. I enabled debugging for wpasupplicant. Something that draws attention is seeing "wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect". This is with the Ubuntu 14.04 OEM image for the Dell Precision 5510. All updates have been installed. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: wpasupplicant 2.1-0ubuntu1.4 [modified: usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service] ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 13:38:06 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1550538/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550504] [NEW] lightdm unresponsive after suspend
Public bug reported: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1550504 Title: lightdm unresponsive after suspend Status in lightdm package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back (or also after failing to suspend), lightdm does not show a password field, and selecting my username does not bring up a password field. If I click on the gear in the upper right corner, I can choose to switch accounts; doing that, after several seconds, lightdm comes back, and I can unlock the user session. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.6-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:53:36 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 LightdmConfig: [SeatDefaults] autologin-guest=false autologin-user-timeout=0 autologin-session=lightdm-autologin SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1550504/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1550490] [NEW] network-manager unresponsive after suspend
Public bug reported: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /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/1550490 Title: network-manager unresponsive after suspend Status in network-manager package in Ubuntu: New Bug description: I'm using an Ubuntu OEM image on the Dell Precision 5510. After unboxing and applying all updates (running apt-get update/upgrade multiple times), if I suspend the system, when it comes back, networking shows as "disabled". The network interfaces however are still up. Once I kill the NetworkManager process, networking comes back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: network-manager 0.9.8.8-0ubuntu7.2 ProcVersionSignature: Ubuntu 3.19.0-33.38~14.04.1-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 26 11:43:28 2016 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-osp1-20150721-1 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2016-02-25 (1 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20150721-23:28 IpRoute: default via 172.24.64.1 dev wlan0 proto static 172.24.64.0/19 dev wlan0 proto kernel scope link src 172.24.67.197 metric 9 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMPTIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH sfo3 aa8c189d-e8dd-429b-948f-025579dfbe33 802-11-wireless 1456515772 Fri 26 Feb 2016 11:42:52 AM PSTyes no /org/freedesktop/NetworkManager/Settings/0 nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running
[Touch-packages] [Bug 1423796] Re: Unable to mount lvmcache root device at boot time
I'm running Ubuntu 15.10 and I was unable to get gmoutso's solution working. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1423796 Title: Unable to mount lvmcache root device at boot time Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: Confirmed Bug description: I'm experimenting with Vivid Vervet on a virtual machine and tried a new LVM feature, lvmcache. I made a cache for the root file system, rebuilt the initrd and rebooted the VM. At boot time, the system failed to activate the root LV. After some investigation, I found out, it's because the initrd is missing some essential stuff needed for activating a cached LV. The initrd was missing the dm-cache module. I regenerated the initrd with explicitly listing dm-cache in /etc/initramfs-tools/modules, but the system still can't boot up, because now it is missing the /usr/sbin/cache_check utility. As SSDs are becoming more and more common, I think it will be common to use them as cache for root file systems, thus it is mandatory to make sure that an initrd can mount an lvmcached root device when necessary, preferably without /etc/initramfs-tools/modules and other manual initrd hacking. System details: Linux lvmvm 3.18.0-13-generic #14-Ubuntu SMP Fri Feb 6 09:55:14 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux Distributor ID: Ubuntu Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 Codename: vivid LVM version: 2.02.111(2) (2014-09-01) Library version: 1.02.90 (2014-09-01) Driver version: 4.28.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1423796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 459730] Re: rsyslog doesn't create /dev/xconsole
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
Status in One Hundred Papercuts:
Triaged
Status in rsyslog package in Ubuntu:
Triaged
Bug description:
Binary package hint: rsyslog
Looks like this was missed in the move to upstart.
This function was called in init.d/rsyslog start:
create_xconsole() {
if [ ! -e /dev/xconsole ]
then
mknod -m 640 /dev/xconsole p
chown root:adm /dev/xconsole
[ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
fi
}
I can't find any reference to it now. If this is old school then it should be
re
moved from the config.
rsyslog:
Installed: 4.2.0-2ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369493] Re: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults
** Tags added: xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1369493 Title: update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults Status in sysvinit package in Ubuntu: Confirmed Bug description: Upgrading xorg on Utopic (booted with upstart), the install dialog-box have displayed this warning: Setting up x11-common (1:7.7+7ubuntu2) ... update-rc.d: warning: start and stop actions are no longer supported; falling back to defaults * Setting up X socket directories...[ OK ] ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: sysv-rc 2.88dsf-41ubuntu18 ProcVersionSignature: Ubuntu 3.16.0-14.20-generic 3.16.2 Uname: Linux 3.16.0-14-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 15 12:12:53 2014 PackageArchitecture: all SourcePackage: sysvinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1369493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file
** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Trusty: Confirmed Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452941] Re: PPTP VPN fails to connect in 15.04, but works in 14.04/14.10
Scratch that, loading the modules allows it to work with a *single* IPv4 route, but I get the same error if I try to connect with multiple roots. My NetworkManager output to syslog is attached. ** Attachment added: "NetworkManager.log" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452941/+attachment/4542372/+files/NetworkManager.log -- 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/1452941 Title: PPTP VPN fails to connect in 15.04, but works in 14.04/14.10 Status in network-manager package in Ubuntu: Confirmed Bug description: I can create a PPTP VPN connection and connect to a remote network in Ubuntu 14.04/14.10 (Unity live boot DVD) but the connection does not work in Ubuntu 15.04 (Unity live boot USB), even though I am using the exact same GUI configuration settings in the Network-Manager (I have confirmed this several times). In addition to the live boot instances, the PPTP VPN connected without problems for me on my 14.04/14.10 installs, but failed on a fresh harddisk install of Ubuntu MATE 15.04. The error that I get in a notification pop-up window when trying to connect on 15.04 is: "The VPN connection 'VPN connection 1' failed because the VPN service returned invalid configuration." ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 ubuntu@ubuntu:~$ apt-cache policy network-manager network-manager: Installed: 0.9.10.0-4ubuntu15 Candidate: 0.9.10.0-4ubuntu15 Version table: *** 0.9.10.0-4ubuntu15 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CurrentDesktop: Unity Date: Thu May 7 22:55:12 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.20 207.173.246.134 via 192.168.0.1 dev wlan0 src 192.168.0.20 LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 LANbeforetime 1fefef93-2d1c-41eb-ad55-3f6c234d7023 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1452941] Re: PPTP VPN fails to connect in 15.04, but works in 14.04/14.10
I needed to load all three of these modules to get it to work: nf_nat_pptp, nf_conntrack_pptp, nf_conntrack_proto_gre -- 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/1452941 Title: PPTP VPN fails to connect in 15.04, but works in 14.04/14.10 Status in network-manager package in Ubuntu: Confirmed Bug description: I can create a PPTP VPN connection and connect to a remote network in Ubuntu 14.04/14.10 (Unity live boot DVD) but the connection does not work in Ubuntu 15.04 (Unity live boot USB), even though I am using the exact same GUI configuration settings in the Network-Manager (I have confirmed this several times). In addition to the live boot instances, the PPTP VPN connected without problems for me on my 14.04/14.10 installs, but failed on a fresh harddisk install of Ubuntu MATE 15.04. The error that I get in a notification pop-up window when trying to connect on 15.04 is: "The VPN connection 'VPN connection 1' failed because the VPN service returned invalid configuration." ubuntu@ubuntu:~$ lsb_release -rd Description: Ubuntu 15.04 Release: 15.04 ubuntu@ubuntu:~$ apt-cache policy network-manager network-manager: Installed: 0.9.10.0-4ubuntu15 Candidate: 0.9.10.0-4ubuntu15 Version table: *** 0.9.10.0-4ubuntu15 0 500 http://archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CasperVersion: 1.360 CurrentDesktop: Unity Date: Thu May 7 22:55:12 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.20 207.173.246.134 via 192.168.0.1 dev wlan0 src 192.168.0.20 LiveMediaBuild: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 LANbeforetime 1fefef93-2d1c-41eb-ad55-3f6c234d7023 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1452941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 459730] Re: rsyslog doesn't create /dev/xconsole
** Tags added: wily
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/459730
Title:
rsyslog doesn't create /dev/xconsole
Status in One Hundred Papercuts:
Triaged
Status in rsyslog package in Ubuntu:
Triaged
Bug description:
Binary package hint: rsyslog
Looks like this was missed in the move to upstart.
This function was called in init.d/rsyslog start:
create_xconsole() {
if [ ! -e /dev/xconsole ]
then
mknod -m 640 /dev/xconsole p
chown root:adm /dev/xconsole
[ -x /sbin/restorecon ] && /sbin/restorecon /dev/xconsole
fi
}
I can't find any reference to it now. If this is old school then it should be
re
moved from the config.
rsyslog:
Installed: 4.2.0-2ubuntu5
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/459730/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1510339] Re: 5GHz network is not available after suspend by closing lid
** Also affects: dell-sputnik Importance: Undecided Status: New -- 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/1510339 Title: 5GHz network is not available after suspend by closing lid Status in Dell Sputnik: New Status in network-manager package in Ubuntu: New Bug description: Model: Dell XPS 13 - 9343 Network controller: Broadcom Corporation BCM4352 802.11ac Wireless Network Adapter (rev 03) Action: close lid of laptop to suspend, open lid to resume Expected behavior: Wireless would resume with access to 2.4Ghz and 5Ghz networks Actual Behavior: Wireless resumes, but 5Ghz networks are not detected ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.3 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Oct 26 21:08:17 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-10-25 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) IpRoute: default via 192.168.1.1 dev eth0 proto static metric 100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.1.0/24 dev eth0 proto kernel scope link metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH Wired connection 1 6c91668c-4496-4a76-b636-2aba7ee0fdac 802-3-ethernet 1445907849 Mon 26 Oct 2015 09:04:09 PM EDT yes no /org/freedesktop/NetworkManager/Settings/0 yes eth0activated /org/freedesktop/NetworkManager/ActiveConnection/3 Nexus 4 Network 4c6152f2-6c3a-425e-a91d-13faad5ed602 bluetooth 0 neverno no /org/freedesktop/NetworkManager/Settings/3 no -- -- -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 6c91668c-4496-4a76-b636-2aba7ee0fdac /org/freedesktop/NetworkManager/ActiveConnection/3 98:D6:F7:2E:39:53 btdisconnected /org/freedesktop/NetworkManager/Devices/5 -- -- -- wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1510339/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
Still occurs in Wily. ** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1500387] Re: System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored
** Also affects: dell-sputnik Importance: Undecided Status: New -- 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/1500387 Title: System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored Status in Dell Sputnik: New Status in xorg package in Ubuntu: Incomplete Bug description: [Summary] System boots to a black screen and the customer has to close the lid and reopen it to trigger a DPMS event and then video is restored [Reproduce Steps] 1. System boots to a black screen 2. Close the lid and reopen it [Results] Expected: Normal boot Actual: Blank screen [Additional Information] CID: Base Image: Product Name: "Ubuntu 14.04.3 LTS" on Dell XPS 13 9343 BIOS Version: A05 Kernel Version: 3.13.0-63-generic CPU: Intel(R) Core(TM) i5-5200U CPU @ 2.20GHz GPU: Intel Corporation Broadwell-U Integrated Graphics (rev 09) To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1500387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374759] Re: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
** Tags added: wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1374759 Title: >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Triaged Status in os-prober package in Ubuntu: Confirmed Bug description: [ 556.734157] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 556.746268] JFS: nTxBlock = 8192, nTxLock = 65536 [ 556.763789] ntfs: driver 2.1.30 [Flags: R/O MODULE]. [ 556.792231] QNX4 filesystem 0.2.3 registered. [ 557.922469] EXT4-fs (sda4): unable to read superblock [ 557.925868] EXT4-fs (sda4): unable to read superblock [ 557.928967] EXT4-fs (sda4): unable to read superblock [ 557.931784] FAT-fs (sda4): bogus number of reserved sectors [ 557.931791] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.946740] XFS (sda4): Invalid superblock magic number [ 557.951904] FAT-fs (sda4): bogus number of reserved sectors [ 557.951911] FAT-fs (sda4): Can't find a valid FAT filesystem [ 557.959099] MINIX-fs: unable to read superblock [ 557.965712] attempt to access beyond end of device [ 557.965721] sda4: rw=16, want=3, limit=2 [ 557.965725] hfsplus: unable to find HFS+ superblock [ 557.968487] qnx4: no qnx4 filesystem (no root dir). [ 557.971203] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 557.974459] hfs: can't find a HFS filesystem on dev sda4 [ 564.034208] EXT4-fs (sda4): unable to read superblock [ 564.040322] EXT4-fs (sda4): unable to read superblock [ 564.043485] EXT4-fs (sda4): unable to read superblock [ 564.047076] FAT-fs (sda4): bogus number of reserved sectors [ 564.047083] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.059578] XFS (sda4): Invalid superblock magic number [ 564.064473] FAT-fs (sda4): bogus number of reserved sectors [ 564.064489] FAT-fs (sda4): Can't find a valid FAT filesystem [ 564.072080] MINIX-fs: unable to read superblock [ 564.074564] attempt to access beyond end of device [ 564.074571] sda4: rw=16, want=3, limit=2 [ 564.074576] hfsplus: unable to find HFS+ superblock [ 564.076688] qnx4: no qnx4 filesystem (no root dir). [ 564.078847] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 564.080902] hfs: can't find a HFS filesystem on dev sda4 [ 570.554296] EXT4-fs (sda4): unable to read superblock [ 570.557647] EXT4-fs (sda4): unable to read superblock [ 570.560516] EXT4-fs (sda4): unable to read superblock [ 570.563451] FAT-fs (sda4): bogus number of reserved sectors [ 570.563460] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.574953] XFS (sda4): Invalid superblock magic number [ 570.580796] FAT-fs (sda4): bogus number of reserved sectors [ 570.580806] FAT-fs (sda4): Can't find a valid FAT filesystem [ 570.588340] MINIX-fs: unable to read superblock [ 570.590983] attempt to access beyond end of device [ 570.590993] sda4: rw=16, want=3, limit=2 [ 570.590999] hfsplus: unable to find HFS+ superblock [ 570.593321] qnx4: no qnx4 filesystem (no root dir). [ 570.595556] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 570.597775] hfs: can't find a HFS filesystem on dev sda4 [ 576.795014] EXT4-fs (sda4): unable to read superblock [ 576.797554] EXT4-fs (sda4): unable to read superblock [ 576.800063] EXT4-fs (sda4): unable to read superblock [ 576.802647] FAT-fs (sda4): bogus number of reserved sectors [ 576.802655] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.813305] XFS (sda4): Invalid superblock magic number [ 576.820257] FAT-fs (sda4): bogus number of reserved sectors [ 576.820276] FAT-fs (sda4): Can't find a valid FAT filesystem [ 576.830945] MINIX-fs: unable to read superblock [ 576.834108] attempt to access beyond end of device [ 576.834119] sda4: rw=16, want=3, limit=2 [ 576.834125] hfsplus: unable to find HFS+ superblock [ 576.837264] qnx4: no qnx4 filesystem (no root dir). [ 576.840408] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep |nextstep-cd|openstep ... >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default
[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
s/Utopic/Vivid/ ** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
** This bug is no longer a duplicate of bug 985417 dhcpd cannot write /var/run/dhcpd.pid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied
*** This bug is a duplicate of bug 985417 *** https://bugs.launchpad.net/bugs/985417 I don't think it was correct to mark this as a duplicate of #985417. That bug affected Precise and Quantal and was fixed back in 2012. This bug is currently affecting users of Utopic in 2015. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1448657 Title: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied Status in isc-dhcp package in Ubuntu: Confirmed Bug description: Just upgraded from 14-10 to 15-04, and now see the following in syslog: Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 audit(1430045408.725:8): apparmor="DENIED" operation="capable" profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1 capname="dac_ove rride" Apr 26 10:50:08 server sh[8619]: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied. Description:Ubuntu 15.04 Release:15.04 isc-dhcp-server: Installed: 4.3.1-5ubuntu2 --- 8x - # cat /etc/default/isc-dhcp-server # Defaults for isc-dhcp-server initscript # sourced by /etc/init.d/isc-dhcp-server # installed at /etc/default/isc-dhcp-server by the maintainer scripts # # This is a POSIX shell fragment # # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf). #DHCPD_CONF=/etc/dhcp/dhcpd.conf # Path to dhcpd's PID file (default: /var/run/dhcpd.pid). #DHCPD_PID=/var/run/dhcpd.pid # Additional options to start dhcpd with. # Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead #OPTIONS="" # On what interfaces should the DHCP server (dhcpd) serve DHCP requests? # Separate multiple interfaces with spaces, e.g. "eth0 eth1". INTERFACES="" --- 8x - # ls -la /var/run lrwxrwxrwx 1 root root 4 Oct 24 2013 /var/run -> /run # ls -la /run/dhcp-server/ total 0 drwxr-xr-x 2 dhcpd dhcpd 40 Apr 26 10:59 . drwxr-xr-x 34 root root 1060 Apr 26 11:33 .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Trusty: Confirmed Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478173] Re: Ambiance Radiance themes are missing a background-color for tooltip elements (needed for GTK3-enabled Firefox Nightly)
I have not had a change to test this on older Ubuntus with the new
nightly firefox yet but I can confirm this is a issue with 15.04 15.10
. And since when this hits in the latest firefox (that will be shipped
on nearly all supported Ubuntu builds) this fix may need to be tested
and applied to older and newer builds of Ambaince Themes (EG one in
14.04 , 12.04 etc.) I am not sure yet however.
--
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/1478173
Title:
Ambiance Radiance themes are missing a background-color for
tooltip elements (needed for GTK3-enabled Firefox Nightly)
Status in ubuntu-themes package in Ubuntu:
Confirmed
Bug description:
Firefox Nightlies recently became GTK3-enabled, and that uncovered an
issue with Ubuntu's Ambiance Radiance GTK3 themes.
They're missing a background-color for the .tooltip {...} CSS rule
in their config files. They have a tooltip_bg_color variable, which
they use to set up a background-image (really a gradient), but there's
no background-color.
This causes problems for GTK3-enabled Firefox, because it reads back some
system-colors by setting up a dummy tooltip and reading the
(currently-not-useful) background-color and the foreground-color. Right now,
this produces unreadable output (for the user) with
white-text-on-a-white-background, as shown in this screenshot:
https://bug1187203.bmoattachments.org/attachment.cgi?id=8638351
The solution is simple -- just add this one line to the .tooltip CSS rule
in gtk-widgets.css:
background-color: @tooltip_bg_color;
For more details, see bug
https://bugzilla.mozilla.org/show_bug.cgi?id=1187203
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: light-themes 14.04+15.04.20150410-0ubuntu1
ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2
Uname: Linux 3.19.0-23-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Jul 24 17:35:25 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-18 (67 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1478173/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450588] [NEW] /var/log/dmesg No Longer Being Updated
Public bug reported: After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: dmesg log vivid -- 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/1450588 Title: /var/log/dmesg No Longer Being Updated Status in systemd package in Ubuntu: New Bug description: After upgrading to Ubuntu 15.04 Vivid, /var/log/dmesg is no longer updated after boot. It appears that this was previously done via /etc/init/dmesg.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1450588/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
I'm also affected by this bug on my Asus Eee PC X101
(Specs: {
CPU: Dual Core Intel Atom CPU N435 @ 1.33GHz,
Graphics: Intel Corporation Atom Processor D4xx/D5xx/N4xx/N5xx Integrated
Graphics Controller
}),
running elementary os Freya.
Along with this, some animations are very choppy (very low, like 2 fps).
Animations affected:
1. When minimizing/maximizing a window
2. When navigating with breadcrumbs in files
3. When navigating in System Settings
4. When navigating Applications menu
Some other animations run buttery smooth though, like the Multitasking View,
and Plank autohide.
@sachintha, funny enough, your trick works for me. While it works as a
temporary symptomatic relief, it does not fix the problem, or its cause, or the
choppy animations. Also, even after I use your trick, the cursor behaves funny
(blinks at very low res) when for example I drag an icon in Files, but it
returns to normal after I release the icon.
Hope this report helps the devs find a cure to this hideous bug.
To me it seems like it lies in some odd interaction between graphics
driver/kernel and X11
cheers
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1390625
Title:
mouse cursor gets corrupted
Status in elementary OS:
Confirmed
Status in Mesa:
New
Status in Unity:
Invalid
Status in unity package in Ubuntu:
Confirmed
Status in xorg-lts-utopic package in Ubuntu:
Confirmed
Bug description:
In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain
occasions. It then looks flipped, sheared or shows fragments of a
previous cursor.
* when switching the cursor them forth and back in Gnome Tweak Tool
* when dragdropping a document icon
Maybe related, the cursor does not always show the correct image scale
on a high-dpi display (this was working right in 14.04). For example
after login, or when hovering specific areas, or on mouse down to
start a dragdrop, the cursor appears 1/4 the expected size.
Attached is a photo of a corrupted cursor (whereas a screenshot with
Gimp showed the uncorrupted cursor).
ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: unity 7.3.1+14.10.20141016-0ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
.tmp.unity.support.test.0:
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
BootLog:
* Setting up X socket directories... [400G
[394G[ OK ]
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 7 22:12:52 2014
DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job
DistroCodename: utopic
DistroVariant: ubuntu
EcryptfsInUse: Yes
GraphicsCard:
Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:3978]
InstallationDate: Installed on 2014-02-02 (278 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 Trusty Tahr - Alpha amd64 (20140201)
MachineType: LENOVO 20266
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed
root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash
acpi_backlight=vendor
SourcePackage: unity
UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago)
dmi.bios.date: 10/31/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 76CN31WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Yoga2
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 2 Pro
dmi.modalias:
dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro:
dmi.product.name: 20266
dmi.product.version: Lenovo Yoga 2 Pro
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.914-1~exp1ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
1:1.0.11-1ubuntu2
xserver.bootTime: Fri Nov 7 14:54:59 2014
xserver.configfile: /etc/X11/xorg.conf
xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1
[Touch-packages] [Bug 1186662] Re: isc-dhcp-server fails to renew lease file
Issue persists in 15.04 Vivid ** Tags added: vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1186662 Title: isc-dhcp-server fails to renew lease file Status in isc-dhcp package in Ubuntu: Triaged Status in isc-dhcp source package in Trusty: Confirmed Bug description: After raring upgrade, the dhcp server fails to renew lease file when it tries to (about every hour). The syslog says: dhcpd: Can't create new lease file: Permission denied It looks like a permission problem, because # chown -R dhcpd:dhcpd /var/lib/dhcp the above command temporarily solves the issue, until dhcpd is restarted: at that time, the ownership of the directory and the lease file is set back to root:root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437814] Re: artifacting in some apps
Sorry for the errors I meant 15.04, Thinking ahead already :) -- 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/1437814 Title: artifacting in some apps Status in Themes for Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Triaged Bug description: The Problem: Some Gnome Shell applications do not display as the should. the best example is the Displays dailog in Gnome Control Centre which ive attached in an image where the background is black instead of white In most of the settings ( possibly all , i did not check). also in many CSD using apps there are small black triangles in the top corners where the window edges have been rounded ( also visible in the attachment) My OS version (lsb_release -rd): Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 The Package version: Installed: 14.04+15.04.20150320-0ubuntu1 What is supposed to happen: It appears the corners are intended to be rounded and there to be no black bits around the edges. The background of the settings Dialgues should be white like the main menu of Gnome Control Center ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: light-themes 14.04+15.04.20150320-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 29 04:23:44 2015 InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1437814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437814] Re: artifacting in some apps
However A big issue still remains. A proper Gnome Shell 3 Window Theme needs to be written for Ambiance! users of GnomeShell can not resize windows at all. No borders. And there is still that back stuff where the edges are meant to rounded. On Nautualis in GnomeShell/ Unified Window mode. See screen-shot. I know GnomeShell is not the priority however this will make GTK 3.14 Apps with unified window/header bar work. It is 90% there so good job. I know Mark wanted GTK 3.14 Apps to be In full fancy dress for 15.10 to obtain this the GTK 3.14 Unified/Header Menubar Black artifacts need to be fixed and a window border needs to be written for Gnomeshell so widnows can be resized I think. I am gonna see what I can do to help but I don't know how fast I can be. I work alot and have university. (6 Days) -- 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/1437814 Title: artifacting in some apps Status in Themes for Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Triaged Bug description: The Problem: Some Gnome Shell applications do not display as the should. the best example is the Displays dailog in Gnome Control Centre which ive attached in an image where the background is black instead of white In most of the settings ( possibly all , i did not check). also in many CSD using apps there are small black triangles in the top corners where the window edges have been rounded ( also visible in the attachment) My OS version (lsb_release -rd): Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 The Package version: Installed: 14.04+15.04.20150320-0ubuntu1 What is supposed to happen: It appears the corners are intended to be rounded and there to be no black bits around the edges. The background of the settings Dialgues should be white like the main menu of Gnome Control Center ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: light-themes 14.04+15.04.20150320-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 29 04:23:44 2015 InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1437814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437814] Re: artifacting in some apps
Ok I found out something. The Black background in Gnome Settings and any app you see be fixed by disabling overlay scroll-bars... To Disable Overlay Open terminal and run this command: gsettings set com.canonical.desktop.interface scrollbar-mode normal If you want to get back overlay Scrollbars, enter this command: gsettings reset com.canonical.desktop.interface scrollbar-mode This must be done on a user by user basis to disable overlay. Ideally this should not happen but it may be a bigger bug in overlay it's self it only effects certin apps. but not sure if a fix will be easy. -- 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/1437814 Title: artifacting in some apps Status in Themes for Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Triaged Bug description: The Problem: Some Gnome Shell applications do not display as the should. the best example is the Displays dailog in Gnome Control Centre which ive attached in an image where the background is black instead of white In most of the settings ( possibly all , i did not check). also in many CSD using apps there are small black triangles in the top corners where the window edges have been rounded ( also visible in the attachment) My OS version (lsb_release -rd): Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 The Package version: Installed: 14.04+15.04.20150320-0ubuntu1 What is supposed to happen: It appears the corners are intended to be rounded and there to be no black bits around the edges. The background of the settings Dialgues should be white like the main menu of Gnome Control Center ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: light-themes 14.04+15.04.20150320-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 29 04:23:44 2015 InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1437814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437814] Re: artifacting in some apps
Yes this is indeed a issue or two issues not sure but the themes need to be updated to fix this, There is all black in those apps and as mentioned black on the corners of some gtk 3.14 apps that should be rounded. -- 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/1437814 Title: artifacting in some apps Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: The Problem: Some Gnome Shell applications do not display as the should. the best example is the Displays dailog in Gnome Control Centre which ive attached in an image where the background is black instead of white In most of the settings ( possibly all , i did not check). also in many CSD using apps there are small black triangles in the top corners where the window edges have been rounded ( also visible in the attachment) My OS version (lsb_release -rd): Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 The Package version: Installed: 14.04+15.04.20150320-0ubuntu1 What is supposed to happen: It appears the corners are intended to be rounded and there to be no black bits around the edges. The background of the settings Dialgues should be white like the main menu of Gnome Control Center ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: light-themes 14.04+15.04.20150320-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Mar 29 04:23:44 2015 InstallationDate: Installed on 2015-03-29 (0 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Beta amd64 (20150326) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1437814/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423415] Re: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04
** Summary changed: - [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.10 + [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04 -- 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/1423415 Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.04 Status in Dell Sputnik: New Status in alsa-driver package in Ubuntu: New Bug description: Volume hotkeys were working and now they're not. A coworker has another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week, and the hotkeys function, so it seems like the bug came up sometime in the past week. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:49:30 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423415] [NEW] [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.10
Public bug reported: Volume hotkeys were working and now they're not. A coworker has another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week, and the hotkeys function, so it seems like the bug came up sometime in the past week. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:49:30 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: dell-sputnik Importance: Undecided Status: New ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Also affects: dell-sputnik Importance: Undecided Status: New -- 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/1423415 Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Volume hotkeys stopped working in Ubuntu 15.10 Status in Dell Sputnik: New Status in alsa-driver package in Ubuntu: New Bug description: Volume hotkeys were working and now they're not. A coworker has another 2015 XPS 13 (model 9343) with Ubuntu 15.04. He hasn't updated in a week, and the hotkeys function, so it seems like the bug came up sometime in the past week. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:49:30 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [XPS 13 9343, Realtek ALC3263, Speaker, Internal] Playback problem UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1423415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1423413] [NEW] [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all
Public bug reported: Note that I am forcing the audio into HDA mode. (It has two modes: HDA and I2S.) In HDA mode, audio out works. The mic is known with a previous version of ALSA (Sept 3 2014 snapshot). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/pcmC1D0p: jared 2929 F...m pulseaudio /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:40:01 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 2 2 : a u d i o o p e n e r r o r : D e v i c e o r r e s o u r c e b u s y Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0c: jared 4299 F...m arecord /dev/snd/controlC1: jared 2929 F pulseaudio /dev/snd/controlC0: jared 2929 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0144PA:rvrX04:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: dell-sputnik Importance: Undecided Status: New ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Also affects: dell-sputnik Importance: Undecided Status: New ** Description changed: Note that I am forcing the audio into HDA mode. (It has two modes: HDA and I2S.) In HDA mode, audio out works. The mic is known with a previous - version of ALSA. + version of ALSA (Sept 3 2014 snapshot). ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5 Uname: Linux 3.18.0-13-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC1D0c: jared 4299 F...m arecord - /dev/snd/pcmC1D0p: jared 2929 F...m pulseaudio - /dev/snd/controlC1: jared 2929 F pulseaudio - /dev/snd/controlC0: jared 2929 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0c: jared 4299 F...m arecord + /dev/snd/pcmC1D0p: jared 2929 F...m pulseaudio + /dev/snd/controlC1: jared 2929 F pulseaudio + /dev/snd/controlC0: jared 2929 F pulseaudio CurrentDesktop: Unity Date: Wed Feb 18 19:40:01 2015 InstallationDate: Installed on 2014-11-03 (107 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingPlaybackStderr: o p e n ( ) : N o s u c h f i l e o r d i r e c t o r y Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : m a i n : 7 2 2 : a u d i o o p e n e r r o r : D e v i c e o r r e s o u r c e b u s y Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/pcmC1D0c: jared 4299 F...m arecord - /dev/snd/controlC1: jared 2929 F pulseaudio - /dev/snd/controlC0: jared 2929 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/pcmC1D0c: jared 4299 F...m arecord + /dev/snd/controlC1: jared 2929 F pulseaudio + /dev/snd/controlC0: jared 2929 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [XPS 13 9343, Realtek ALC3263, Mic, Internal] No sound at all UpgradeStatus: Upgraded to vivid on 2015-01-08 (41 days ago) dmi.bios.date: 02/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A01 dmi.board.name: 0144PA dmi.board.vendor: Dell Inc. dmi.board.version: X04 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA01:bd02/03/2015:svnDellInc
[Touch-packages] [Bug 504705] Re: cups restart every morning
I found this bug because I was seeing AppArmor entries in my daily report from LogWatch: -- Kernel -- 1 Time(s): audit: type=1400 audit(1419776817.080:38): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=23157 comm=apparmor_parser 1 Time(s): audit: type=1400 audit(1419776817.080:39): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=23157 comm=apparmor_parser 1 Time(s): audit: type=1400 audit(1419776817.096:40): apparmor=STATUS operation=profile_replace profile=unconfined name=third_party pid=23157 comm=apparmor_parser -- I believe this is being caused by the daily Cups restart this bug is referring to. -- 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/504705 Title: cups restart every morning Status in cups package in Ubuntu: Confirmed Bug description: lsb_release Description: Ubuntu 9.04 Release: 9.04 cups: 1.3.9-17ubuntu3.2 Something restarts cups every morning, and I don't know what is it. This is a big problem for us, because every month we have to print a very big print job (thousands of pages), so we launch the printing in the evening, put new paper in the printer the next morning, and expect the job continues. But the job restarts from the beginning. I sent a /var/log/cups/error_log file to cups.org and this is their answer : Well, the main problem is the daily CUPS restart at 07:36. This stops all jobs; the scheduler starts all not yet completed jobs from the beginning. BTW, your system seems not to do a well behaved restart, as the messages Scheduler shutting down normally and Savinf job cache file ... are missing in your error_log. As I have no Ubuntu system available to look into, I do not know how the restart is scheduled - I suggest to look into the documentation regarding system administration or ask for more info in the various Ubuntu forums. I post in the forum https://answers.launchpad.net/ubuntu/+source/cups/+question/96428 but get no advice. I don't understand what is happening Can you help me Gilles To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/504705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315770] Re: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Strong background noise
** Also affects: dell-sputnik Importance: Undecided Status: New -- 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/1315770 Title: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Strong background noise Status in Dell Sputnik: New Status in “alsa-driver” package in Ubuntu: Confirmed Status in Fedora: New Bug description: When I connect the headphones, there is a strong hissing in both left and right side. It does not amplify or reduce along with the master volume. Instead, if I completely mute the master volume, the hissing disappears. It comes back as soon as I unmute the master volume. The internal speakers of the laptop are not affected: when headphones are not connected, there is no background hissing noise. Standard four questions: 1) Ubuntu release: 14.04 LTS 2) Package affected: kernel? (linux-image-3.13.0-24-generic) or maybe alsa-driver? 3) Unless I play music, I expect no to hear anything in the headphones 4) I get a background hissing noise in the headphones Thanks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sun1875 F pulseaudio /dev/snd/controlC1: sun1875 F pulseaudio CurrentDesktop: Unity Date: Sun May 4 02:46:01 2014 InstallationDate: Installed on 2014-05-02 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: High background noise, or volume is too low Title: [Dell Precision M3800, Realtek ALC668, Black Headphone Out, Left] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: Dell Precision M3800 dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/06/2014:svnDellInc.:pnDellPrecisionM3800:pvrA03:rvnDellInc.:rnDellPrecisionM3800:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Dell Precision M3800 dmi.product.version: A03 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1315770/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386721] Re: Graphics Slow After Upgrade 14.04 - 14.10
My Wine based games are so much choppy after upgrading from 14.04 to 14.10. -- 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/1386721 Title: Graphics Slow After Upgrade 14.04 - 14.10 Status in “xorg” package in Ubuntu: Confirmed Bug description: Using Gnome Ubuntu 14.10, Dell XPS 13, intel 915 Graphics After upgrading from 14.04 to 14.10 there are a lot of places where the graphics are working much slower than they were before: - Gnome Shell Interface is very sluggish, visible chops (redrawing) when pressing the [Super] key. - Selecting text in Gedit takes a full second pr. line Experiences some subjective improvement when I booted kernel 3.13.0-37 instead of 3.16.0-23, but that may be my imagination as the problem persists. I've searched google, forums, found a couple of relevant links that point to the issue being the Intel drivers. http://askubuntu.com/questions/53962...E2%86%92-14-10 http://www.webupd8.org/2014/10/ubunt...ent-1652086424 But the drivers currently in 14.10 should be newer than those supplied by Intel to 14.04 so that doesn't make sense to me. As one Intel developer wrote: I would like to point out that since what we do is bring more ecent versions of the software to the target distributions than they ship with, a 14.04 targeted installer is unlikely to bring much to a 14.10 installation, which most likely has the same or more recent versions already anyway. Source: https://01.org/linuxgraphics/node/375 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Tue Oct 28 15:24:30 2014 DistUpgraded: 2014-10-25 20:59:36,052 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu DkmsStatus: i915-3.15-3.13, 0.01, 3.13.0-37-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:060a] InstallationDate: Installed on 2014-06-14 (135 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS Trusty Tahr - Release amd64 (20140416.2) MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-23-generic root=UUID=105bbbd1-365e-4063-bdca-fc5431faf5dc ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to utopic on 2014-10-25 (2 days ago) dmi.bios.date: 12/11/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0GFTRT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/11/2013:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0GFTRT:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Tue Oct 28 13:44:57 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4933 vendor CMN xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1386721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347859] Re: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems
** Changed in: biosdevname (Ubuntu) Status: New = Opinion ** Changed in: systemd (Ubuntu) Status: New = Opinion ** Changed in: udev (Ubuntu) Status: New = Opinion -- 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/1347859 Title: Introduction of Predictable Network Interface Names (aka biosdevname) breaks working systems Status in “biosdevname” package in Ubuntu: Opinion Status in “systemd” package in Ubuntu: Opinion Status in “udev” package in Ubuntu: Opinion Bug description: Relatively recent linux distribution upgrades have been causing computers' ethernet devices to be unexpectedly renamed. While I understand that consistent device naming solves problems on some systems (mostly multi-NIC servers and a few specialty embedded devices), unilaterally forcing these changes on everyone is causing a lot of frustration. Here are some of the problems I've encountered: Interface names that were easily recognized as abbreviations for their device type have been replaced by cryptic names that have no obvious meaning whatsoever. It's easy to guess that eth0 is short for ethernet #0. What the heck is p4p1 supposed to mean? How is a human supposed to guess that the first p stands for PCI slot, that the second p stands for port number, and that the whole mysterious string represents an ethernet interface? This new naming convention is inferior to the old one in at least one significant respect: it makes things more difficult to understand. One of the more useful examples of consistency that unix-like systems have enjoyed for decades has been thrown out: the extremely well-known ethernet device names. This creates yet another hurtle for users and admins when switching between different operating systems or trying to apply general-purpose unix knowledge. A lot of documentation has been broken. I have no idea how many manuals, forum posts, bug reports, printed instructions, email messages, personal notes, books, and other forms of documentation in the world refer to a unix ethernet device as eth0, but I'll bet the number is huge. All that valuable guidance has just been rendered misleading or even useless to anyone who doesn't keep up with the latest distribution-specific device naming experiments; in other words: the people who need it most. Well-established workflows have been broken. The change trips up users and admins who have for years been getting tasks done quickly with commands that they could recall and execute without a second thought. They are suddenly finding that their workflows no longer work. This interrupts tasks that should have been quick and easy, forcing people figure out why known-good procedures are broken, think about how to modify their memorized commands to work on the affected systems, and train their fingers to type those new commands as quickly as they did the old ones. Beyond being irritating, it can eat up a bunch of time that some of us don't have to spare. Working systems have been broken. Tools and automation scripts, especially those developed for site-specific use, often make the difference between a computer that does real work and a useless generic OS installation. Sometimes they even make the difference between a malfunctioning headless box that can be fixed over the network and an expensive brick. It is quite common for such software to make some minimal assumptions about its runtime environment, like assuming that the name of the only network device that has ever been or will ever be present will not suddenly change after being stable for months or years. There are also applications (e.g. Matlab) and configuration files (e.g. smb.conf, dhclient.conf, isc-dhcp-server) that might depend on references to eth0. Renaming a critical and ubiquitous device like this is so very likely to cause problems that it should never, ever be done in an upgrade without the admin's explicit consent. Sufficient warning of the change was not given. On one of my machines, eth0 was renamed to p4p1 when I upgraded to Ubuntu 14.04 (trusty), yet I don't see any mention of it in the Trusty release notes, nor in any of the notes for releases of the previous several years. Is it buried in fine print someplace that I missed? Having to figure out for myself what changed, why, and how to revert it (in multiple ways on each machine) was a significant waste of my time. Multiply that by all the other people who were affected similarly, and I'll bet we'd get an embarrassing number of needlessly wasted person-months that could have been saved with a simple announcement and link to documentation. In short, the way this feature was forced on the world was an irresponsible blunder. It doesn't matter that the change was meant to
