[Touch-packages] [Bug 1950806] [NEW] package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1
Public bug reported: No details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ufw 0.36-6ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 12 15:00:27 2021 DuplicateSignature: package:ufw:0.36-6ubuntu1 Setting up ufw (0.36-6ubuntu1) ... [Errno 5] Input/output error dpkg: error processing package ufw (--configure): installed ufw package post-installation script subprocess returned error exit status 1 ErrorMessage: installed ufw package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-21 (143 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: ufw Title: package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1950806 Title: package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1 Status in ufw package in Ubuntu: New Bug description: No details ProblemType: Package DistroRelease: Ubuntu 20.04 Package: ufw 0.36-6ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Nov 12 15:00:27 2021 DuplicateSignature: package:ufw:0.36-6ubuntu1 Setting up ufw (0.36-6ubuntu1) ... [Errno 5] Input/output error dpkg: error processing package ufw (--configure): installed ufw package post-installation script subprocess returned error exit status 1 ErrorMessage: installed ufw package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-06-21 (143 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: ufw Title: package ufw 0.36-6ubuntu1 failed to install/upgrade: installed ufw package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1950806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1544251] Re: mount ignores exec option for 'users' mounts
same bug in 18.04LTS, it seems -- 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/1544251 Title: mount ignores exec option for 'users' mounts Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Trusty: New Bug description: The version of 'mount' included in Ubuntu 14.04 LTS and 12.04 LTS has a bug wherein the 'exec' option in /etc/fstab is ignored on mounts with the 'user' or 'users' options when they are mounted by root. For example: $ grep 48tb2d /etc/fstab labdisk.site.com:/Public4 /mnt/lab_48tb2d nfs users,exec,nosuid 0 0 $ sudo mount /mnt/lab_48tb2d $ mount | grep 48tb2d labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs (rw,nosuid,nodev,noexec,addr=172.16.222.158) $ umount /mnt/lab_48tb2d $ mount /mnt/lab_48tb2d $ mount | grep 48tb2d labdisk.site.com:/Public4 on /mnt/lab_48tb2d type nfs (rw,nosuid,nodev,addr=172.16.222.158) This bug was fixed upstream several years ago and I believe therefore doesn't affect 15.10, but seems not to have made it into the current LTS releases of ubuntu. https://git.kernel.org/cgit/utils/util-linux/util-linux.git/commit/mount/mount.c?id=a4c0cc75ff9744299f108c259efab1bd30c8007a https://bugzilla.redhat.com/show_bug.cgi?id=769636 System info: Ubuntu 14.04.3 LTS, util-linux 2.20.1-5.1ubuntu20.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1544251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
I also have issues with "HSP/HFP" profile detection in apps. I have to close an app, then manually switch profile to "HSP/HFP", then start an app. Only then I can use microphone. -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1665749] Re: Hp PSC 1510 not working anymore
This was a very long time ago. I have a totally new computer now. Thank you. On Sun, Aug 26, 2018 at 3:30 PM gf <1665...@bugs.launchpad.net> wrote: > Hello Shannon, > Thank you for submitting this bug and reporting a problem with cups. You > made this bug report some time ago and Ubuntu and cups have been updated > since then. > > Could you confirm that this is no longer a problem and that we can close > the ticket? > If it is still a problem, are you still interested in finding a solution > to this bug? > If you are, could you let us know and, in the current version, could you > run the following (only once): > apport-collect 1665749 > and upload the updated logs and and any other logs that are relevant for > this particular issue. > > Thank you again for helping make Ubuntu and cups better. > G > > ** Changed in: cups (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1665749 > > Title: > Hp PSC 1510 not working anymore > > Status in cups package in Ubuntu: > Incomplete > > Bug description: > I'm on 14.04 > I'm fairly new. I feel like I've tried everything! Printer was working > last week. Now It just says "Held" or pending then disappears with no > print. > I've downloaded the latest drivers. > > Searching on USB bus... > hp-setup[3668]: debug: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation > 2.0 root hub > Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) > [Bluetooth Controller] > Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub > > error: No devices found on bus: usb > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1665749/+subscriptions > -- 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/1665749 Title: Hp PSC 1510 not working anymore Status in cups package in Ubuntu: Incomplete Bug description: I'm on 14.04 I'm fairly new. I feel like I've tried everything! Printer was working last week. Now It just says "Held" or pending then disappears with no print. I've downloaded the latest drivers. Searching on USB bus... hp-setup[3668]: debug: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub error: No devices found on bus: usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1665749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771454] [NEW] package udev 229-4ubuntu21.2 failed to install/upgrade: package udev is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: im new to this .i just keep getting a notification for this issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21.2 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-lowlatency 4.13.16 Uname: Linux 4.13.0-41-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CustomUdevRuleFiles: 70-snap.vlc.rules 70-snap.core.rules Date: Mon May 7 12:39:52 2018 DuplicateSignature: package:udev:229-4ubuntu21.2 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package udev (--configure): package udev is not ready for configuration ErrorMessage: package udev is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-22 (23 days ago) InstallationMedia: Ubuntu-Studio 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-lowlatency root=UUID=a37ad82e-7984-4719-a835-1cf59ee97750 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: systemd Title: package udev 229-4ubuntu21.2 failed to install/upgrade: package udev is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068B12000320491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068B12000320491620100 dmi.sys.vendor: Hewlett-Packard ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771454 Title: package udev 229-4ubuntu21.2 failed to install/upgrade: package udev is not ready for configuration cannot configure (current status 'half-installed') Status in systemd package in Ubuntu: New Bug description: im new to this .i just keep getting a notification for this issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: udev 229-4ubuntu21.2 ProcVersionSignature: Ubuntu 4.13.0-41.46~16.04.1-lowlatency 4.13.16 Uname: Linux 4.13.0-41-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CustomUdevRuleFiles: 70-snap.vlc.rules 70-snap.core.rules Date: Mon May 7 12:39:52 2018 DuplicateSignature: package:udev:229-4ubuntu21.2 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1) ... dpkg: error processing package udev (--configure): package udev is not ready for configuration ErrorMessage: package udev is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2018-04-22 (23 days ago) InstallationMedia: Ubuntu-Studio 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: Hewlett-Packard Presario CQ57 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-41-lowlatency root=UUID=a37ad82e-7984-4719-a835-1cf59ee97750 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.26 SourcePackage: systemd Title: package udev 229-4ubuntu21.2 failed to install/upgrade: package udev is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/17/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.47 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3577 dmi.board.vendor: Hewlett-Packard dmi.board.version: 24.49 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.47:bd12/17/2011:svnHewlett-Packard:pnPresarioCQ57NotebookPC:pvr068B12000320491620100:rvnHewlett-Packard:rn3577:rvr24.49:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=CO S=PRE dmi.product.name: Presario CQ57 Notebook PC dmi.product.version: 068B12000320491620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages
Re: [Touch-packages] [Bug 1748723] Re: HP Laserjet1018 detected by 17.10 but not print anything
** Attachment added: "Printer-issue01.pdf" https://bugs.launchpad.net/bugs/1748723/+attachment/5080510/+files/Printer-issue01.pdf -- 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/1748723 Title: HP Laserjet1018 detected by 17.10 but not print anything Status in cups package in Ubuntu: New Bug description: Cuos and HPLIB are installed but HP-Check show errors The Printer HP Laserjet1018 has been detected by Ubuntu 17.01 an is defined as standard printer I can start a print request, it goes in the print queue and finished without printing. On Ubuntu 16.04 everything works fine after install HPLIP See same in attachment THANKS cyborg2058@cyborg2058-Z370-HD3P:~$ hp-check Saving output in log file: /home/cyborg2058/hp-check.log HP Linux Imaging and Printing System (ver. 3.17.7) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: 12-17.10 version is not supported. Using 12-17.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Host: cyborg2058-Z370-HD3P Proc: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Distribution: 12 17.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.17.7 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for 12 distro 17.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.17.7 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=yes gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=yes foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.17.7 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no apparmor_build=no Current contents of '/var/lib/hp/hplip.state' file: Plugins are not installed. Could not access file: No such file or directory Current contents of '~/.hplip/hplip.conf' file: [installation] date_time = 02/11/18 10:25:05 version = 3.17.7 - | External Dependencies | - error: cups CUPS - Common Unix Printing System REQUIRED1.1 - INCOMPAT 'CUPS may not be installed or not running' gs GhostScript - PostScript and PDF language interpreter and previewer RE
[Touch-packages] [Bug 1748723] Re: HP Laserjet1018 detected by 17.10 but not print anything
** Package changed: ubuntu => cups (Ubuntu) -- 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/1748723 Title: HP Laserjet1018 detected by 17.10 but not print anything Status in cups package in Ubuntu: New Bug description: Cuos and HPLIB are installed but HP-Check show errors The Printer HP Laserjet1018 has been detected by Ubuntu 17.01 an is defined as standard printer I can start a print request, it goes in the print queue and finished without printing. On Ubuntu 16.04 everything works fine after install HPLIP See same in attachment THANKS cyborg2058@cyborg2058-Z370-HD3P:~$ hp-check Saving output in log file: /home/cyborg2058/hp-check.log HP Linux Imaging and Printing System (ver. 3.17.7) Dependency/Version Check Utility ver. 15.1 Copyright (c) 2001-15 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. Note: hp-check can be run in three modes: 1. Compile-time check mode (-c or --compile): Use this mode before compiling the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper dependencies are installed to successfully compile HPLIP. 2. Run-time check mode (-r or --run): Use this mode to determine if a distro supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball has the proper dependencies installed to successfully run. 3. Both compile- and run-time check mode (-b or --both) (Default): This mode will check both of the above cases (both compile- and run-time dependencies). Check types: a. EXTERNALDEP - External Dependencies b. GENERALDEP - General Dependencies (required both at compile and run time) c. COMPILEDEP - Compile time Dependencies d. [All are run-time checks] PYEXT SCANCONF QUEUES PERMISSION Status Types: OK MISSING - Missing Dependency or Permission or Plug-in INCOMPAT - Incompatible dependency-version or Plugin-version warning: 12-17.10 version is not supported. Using 12-17.04 versions dependencies to verify and install... --- | SYSTEM INFO | --- Kernel: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Host: cyborg2058-Z370-HD3P Proc: 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 25 09:13:46 UTC 2018 GNU/Linux Distribution: 12 17.10 Bitness: 64 bit --- | HPLIP CONFIGURATION | --- HPLIP-Version: HPLIP 3.17.7 HPLIP-Home: /usr/share/hplip warning: HPLIP-Installation: Auto installation is not supported for 12 distro 17.10 version Current contents of '/etc/hp/hplip.conf' file: # hplip.conf. Generated from hplip.conf.in by configure. [hplip] version=3.17.7 [dirs] home=/usr/share/hplip run=/var/run ppd=/usr/share/ppd/hplip/HP ppdbase=/usr/share/ppd/hplip doc=/usr/share/doc/hplip html=/usr/share/doc/hplip-doc icon=no cupsbackend=/usr/lib/cups/backend cupsfilter=/usr/lib/cups/filter drv=/usr/share/cups/drv bin=/usr/bin apparmor=/etc/apparmor.d # Following values are determined at configure time and cannot be changed. [configure] network-build=yes libusb01-build=no pp-build=yes gui-build=yes scanner-build=yes fax-build=yes dbus-build=yes cups11-build=no doc-build=yes shadow-build=no hpijs-install=yes foomatic-drv-install=yes foomatic-ppd-install=yes foomatic-rip-hplip-install=no hpcups-install=yes cups-drv-install=yes cups-ppd-install=no internal-tag=3.17.7 restricted-build=no ui-toolkit=qt5 qt3=no qt4=no qt5=yes policy-kit=yes lite-build=no udev_sysfs_rules=no hpcups-only-build=no hpijs-only-build=no apparmor_build=no Current contents of '/var/lib/hp/hplip.state' file: Plugins are not installed. Could not access file: No such file or directory Current contents of '~/.hplip/hplip.conf' file: [installation] date_time = 02/11/18 10:25:05 version = 3.17.7 - | External Dependencies | - error: cups CUPS - Common Unix Printing System REQUIRED1.1 - INCOMPAT 'CUPS may not be installed or not running' gs GhostScript - PostScript and PDF language interpreter and previewer REQUIRED7.059.21OK - error: xsane xsane -
[Touch-packages] [Bug 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.
I also ran into this issue yesterday on a Dell XPS13. It is nothing Audacity specific and you can easily trigger this yourself by just running 'amixer -c 0 set "Headphone Mic" cap' or starting alsamixer, switching to the capture devices and activating the "Headphone Mic" by pressing Space on it. Similarly, you can get your headphone sound back by instead capturing from the internal mic. All in all, there is no bug anywhere. It's just that Audacity handles mics in a bad (though not buggy) manner. -- 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/1257956 Title: Headphones stopped working after use of Audacity. They are detected, but no sound is produced. Status in alsa-driver package in Ubuntu: Expired Bug description: I'm running 13.10 and the latest GNOME. I've just fresh installed everything and the problem has occured again the same way. I would like to be able to use audacity, but I suppose in the mean time I will just reinstall everything. Steps to reproduce : 1) Install audacity 2.0.3 from official Ubuntu repositories 2) Open Audacity and play something with it 3) That's it : no more headphones sound. - alsa log created with 'alsa-info.sh' (https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/ - pulse log when I plug in my headphones, I run a MP3 file with VLC, close VLC then unplug headphones (https://wiki.ubuntu.com/PulseAudio/Log) : http://paste.ubuntu.com/7131713/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567697] Re: libcurl is missing http2 support
I had to backport from Debian Sid: mkdir curl wget http://http.debian.net/debian/pool/main/c/curl/curl_7.52.1-3.dsc http://http.debian.net/debian/pool/main/c/curl/curl_7.52.1.orig.tar.gz http://http.debian.net/debian/pool/main/c/curl/curl_7.52.1-3.debian.tar.xz sudo apt-get install autoconf automake libgnutls28-dev libidn2-0-dev libkrb5-dev libldap2-dev libnss3-dev libpsl-dev librtmp-dev libtool quilt stunnel4 libnghttp2-dev libssh2-1-dev cd curl-7.52.1 dpkg-buildpackage -b -j4 # if you want to skip tests # DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -b -j4 sudo dpkg -i ../curl_7.52.1-3_amd64.deb ../libcurl3_7.52.1-3_amd64.deb -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1567697 Title: libcurl is missing http2 support Status in curl package in Ubuntu: Confirmed Bug description: libcurl supports HTTP/2.0 through libnghttp2, but the package on Ubuntu is not compiled with it. Alternatively, a libcurl4-(gnutls|openssl)-nghttp2 might be a good idea. See also: https://curl.haxx.se/docs/http2.html curl CLI tool should not need an update, as it already has the commandline switches, but when you use them it comes back with unsupported protocol. drwilco@eris:~$ curl --http2 www.google.com curl: (1) Unsupported protocol drwilco@eris:~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@eris:~# apt-cache policy libcurl3 libcurl3: Installed: 7.47.0-1ubuntu2 Candidate: 7.47.0-1ubuntu2 Version table: *** 7.47.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1567697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1567697] Re: libcurl is missing http2 support
Also looking for http2 curl support in Xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1567697 Title: libcurl is missing http2 support Status in curl package in Ubuntu: Confirmed Bug description: libcurl supports HTTP/2.0 through libnghttp2, but the package on Ubuntu is not compiled with it. Alternatively, a libcurl4-(gnutls|openssl)-nghttp2 might be a good idea. See also: https://curl.haxx.se/docs/http2.html curl CLI tool should not need an update, as it already has the commandline switches, but when you use them it comes back with unsupported protocol. drwilco@eris:~$ curl --http2 www.google.com curl: (1) Unsupported protocol drwilco@eris:~$ lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@eris:~# apt-cache policy libcurl3 libcurl3: Installed: 7.47.0-1ubuntu2 Candidate: 7.47.0-1ubuntu2 Version table: *** 7.47.0-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1567697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Still doesn't work for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Xenial: Triaged Status in unattended-upgrades source package in Yakkety: Triaged Status in unattended-upgrades package in Debian: New Bug description: [SRU justification] This fix is needed to make sure that the system does not hang on shutdown when /var is a speparate file system [Impact] System can hang up to 10 minutes if not fixed. [Fix] Change the systemd unit's ExecStart to an ExecStop so the unit is correctly sequenced. [Test Case] In a VM with /var separated from the / file system, shutdown the VM. It will hang for 10 minutes [Regression] None to be expected. A ExecStop unit will be sequenced before the Before= units which is earlier than previously. [Original description of the problem] The systemd unit file unattended-upgrades.service is used to stop a running unattended-upgrade process during shutdown. This unit file is running together with all filesystem unmount services. The unattended-upgrades service checks if the lockfile for unattended-upgrade (in /var/run) exists, and if it does, there is an unattended-upgrade in progress and the service will wait until it finishes (and therefore automatically wait at shutdown). However, if /var is a separate filesystem, it will get unmounted even though /var/run is a tmpfs that's still mounted on top of the /var/run directory in the /var filesystem. The unattended-upgrade script will fail to find lockfile, sleeps for 5 seconds, and tries to check the lockfile again. After 10 minutes (the default timeout), it will finally exit and the system will continue shutdown. The problem is the error handling in /usr/share/unattended-upgrades/unattended-upgrade-shutdown where it tries to lock itself: while True: res = apt_pkg.get_lock(options.lock_file) logging.debug("get_lock returned %i" % res) # exit here if there is no lock if res > 0: logging.debug("lock not taken") break lock_was_taken = True The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an error. File descriptors are just C file descriptors, so they are always positive integers. The code should check the result to be negative, not positive. I have attached a patch to reverse the logic. Additional information: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) unattended-upgrades: Installed: 0.90ubuntu0.3 Candidate: 0.90ubuntu0.3 Version table: *** 0.90ubuntu0.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) Fast reboot 4) Very slow reboot (after a 10 minutes timeout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
@louis-bouchard I'd love to help you, but I'm in rush on my current job. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Yakkety: Fix Committed Status in unattended-upgrades package in Debian: New Bug description: [SRU justification] This fix is needed to make sure that the system does not hang on shutdown when /var is a speparate file system [Impact] System can hang up to 10 minutes if not fixed. [Fix] Change the systemd unit's ExecStart to an ExecStop so the unit is correctly sequenced. [Test Case] In a VM with /var separated from the / file system, shutdown the VM. It will hang for 10 minutes [Regression] None to be expected. A ExecStop unit will be sequenced before the Before= units which is earlier than previously. [Original description of the problem] The systemd unit file unattended-upgrades.service is used to stop a running unattended-upgrade process during shutdown. This unit file is running together with all filesystem unmount services. The unattended-upgrades service checks if the lockfile for unattended-upgrade (in /var/run) exists, and if it does, there is an unattended-upgrade in progress and the service will wait until it finishes (and therefore automatically wait at shutdown). However, if /var is a separate filesystem, it will get unmounted even though /var/run is a tmpfs that's still mounted on top of the /var/run directory in the /var filesystem. The unattended-upgrade script will fail to find lockfile, sleeps for 5 seconds, and tries to check the lockfile again. After 10 minutes (the default timeout), it will finally exit and the system will continue shutdown. The problem is the error handling in /usr/share/unattended-upgrades/unattended-upgrade-shutdown where it tries to lock itself: while True: res = apt_pkg.get_lock(options.lock_file) logging.debug("get_lock returned %i" % res) # exit here if there is no lock if res > 0: logging.debug("lock not taken") break lock_was_taken = True The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an error. File descriptors are just C file descriptors, so they are always positive integers. The code should check the result to be negative, not positive. I have attached a patch to reverse the logic. Additional information: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) unattended-upgrades: Installed: 0.90ubuntu0.3 Candidate: 0.90ubuntu0.3 Version table: *** 0.90ubuntu0.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) Fast reboot 4) Very slow reboot (after a 10 minutes timeout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
BTW, KVM allows you to use serial console you can use it for debugging. But you have explicitly specify the order of defined "console" kernel parameters, i.e.: this will specify VGA console as default output: console=ttyS0 console=tty1 this will specify serial console as default output: console=tty1 console=ttyS0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Yakkety: Fix Committed Status in unattended-upgrades package in Debian: New Bug description: [SRU justification] This fix is needed to make sure that the system does not hang on shutdown when /var is a speparate file system [Impact] System can hang up to 10 minutes if not fixed. [Fix] Change the systemd unit's ExecStart to an ExecStop so the unit is correctly sequenced. [Test Case] In a VM with /var separated from the / file system, shutdown the VM. It will hang for 10 minutes [Regression] None to be expected. A ExecStop unit will be sequenced before the Before= units which is earlier than previously. [Original description of the problem] The systemd unit file unattended-upgrades.service is used to stop a running unattended-upgrade process during shutdown. This unit file is running together with all filesystem unmount services. The unattended-upgrades service checks if the lockfile for unattended-upgrade (in /var/run) exists, and if it does, there is an unattended-upgrade in progress and the service will wait until it finishes (and therefore automatically wait at shutdown). However, if /var is a separate filesystem, it will get unmounted even though /var/run is a tmpfs that's still mounted on top of the /var/run directory in the /var filesystem. The unattended-upgrade script will fail to find lockfile, sleeps for 5 seconds, and tries to check the lockfile again. After 10 minutes (the default timeout), it will finally exit and the system will continue shutdown. The problem is the error handling in /usr/share/unattended-upgrades/unattended-upgrade-shutdown where it tries to lock itself: while True: res = apt_pkg.get_lock(options.lock_file) logging.debug("get_lock returned %i" % res) # exit here if there is no lock if res > 0: logging.debug("lock not taken") break lock_was_taken = True The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an error. File descriptors are just C file descriptors, so they are always positive integers. The code should check the result to be negative, not positive. I have attached a patch to reverse the logic. Additional information: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) unattended-upgrades: Installed: 0.90ubuntu0.3 Candidate: 0.90ubuntu0.3 Version table: *** 0.90ubuntu0.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) Fast reboot 4) Very slow reboot (after a 10 minutes timeout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
@louis-bouchard "Started Unattended Upgrades Shutdown." means that the unit was started. Since the patch assumes that we don't use "ExecStart" this means nothing. Upgrade procedure should be executed on "ExecStop". But it is not happening. I tried to set debug info inside the "ExecStop" instead of executing "unattended-upgrade-shutdown", but it doesn't work. I can provide you with the detailed step-by-step instructions on how to 100% reproduce the issue, but it will require KVM host, and running my scripts which will deploy VM with LVM. Basic steps: * follow https://github.com/kayrus/deploy-vm docs * git clone https://github.com/kayrus/deploy-vm * cd deploy-vm * ./deploy_vms_cluster.sh -o ubuntu -c xenial * follow https://github.com/kayrus/rescue-initramfs docs * and reinstall VM from initramfs using "deploy_os_lvm.sh" script Then your Xenial VM will stuck at reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Yakkety: Fix Committed Status in unattended-upgrades package in Debian: New Bug description: [SRU justification] This fix is needed to make sure that the system does not hang on shutdown when /var is a speparate file system [Impact] System can hang up to 10 minutes if not fixed. [Fix] Change the systemd unit's ExecStart to an ExecStop so the unit is correctly sequenced. [Test Case] In a VM with /var separated from the / file system, shutdown the VM. It will hang for 10 minutes [Regression] None to be expected. A ExecStop unit will be sequenced before the Before= units which is earlier than previously. [Original description of the problem] The systemd unit file unattended-upgrades.service is used to stop a running unattended-upgrade process during shutdown. This unit file is running together with all filesystem unmount services. The unattended-upgrades service checks if the lockfile for unattended-upgrade (in /var/run) exists, and if it does, there is an unattended-upgrade in progress and the service will wait until it finishes (and therefore automatically wait at shutdown). However, if /var is a separate filesystem, it will get unmounted even though /var/run is a tmpfs that's still mounted on top of the /var/run directory in the /var filesystem. The unattended-upgrade script will fail to find lockfile, sleeps for 5 seconds, and tries to check the lockfile again. After 10 minutes (the default timeout), it will finally exit and the system will continue shutdown. The problem is the error handling in /usr/share/unattended-upgrades/unattended-upgrade-shutdown where it tries to lock itself: while True: res = apt_pkg.get_lock(options.lock_file) logging.debug("get_lock returned %i" % res) # exit here if there is no lock if res > 0: logging.debug("lock not taken") break lock_was_taken = True The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an error. File descriptors are just C file descriptors, so they are always positive integers. The code should check the result to be negative, not positive. I have attached a patch to reverse the logic. Additional information: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) unattended-upgrades: Installed: 0.90ubuntu0.3 Candidate: 0.90ubuntu0.3 Version table: *** 0.90ubuntu0.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) Fast reboot 4) Very slow reboot (after a 10 minutes timeout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
@arges, I already noticed that upgrade procedure doesn't start at all with the new change. But actual shutdown/reboot hang has disappeared. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1654600 Title: unattended-upgrade-shutdown hangs when /var is a separate filesystem Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in unattended-upgrades source package in Yakkety: Fix Committed Status in unattended-upgrades package in Debian: New Bug description: [SRU justification] This fix is needed to make sure that the system does not hang on shutdown when /var is a speparate file system [Impact] System can hang up to 10 minutes if not fixed. [Fix] Change the systemd unit's ExecStart to an ExecStop so the unit is correctly sequenced. [Test Case] In a VM with /var separated from the / file system, shutdown the VM. It will hang for 10 minutes [Regression] None to be expected. A ExecStop unit will be sequenced before the Before= units which is earlier than previously. [Original description of the problem] The systemd unit file unattended-upgrades.service is used to stop a running unattended-upgrade process during shutdown. This unit file is running together with all filesystem unmount services. The unattended-upgrades service checks if the lockfile for unattended-upgrade (in /var/run) exists, and if it does, there is an unattended-upgrade in progress and the service will wait until it finishes (and therefore automatically wait at shutdown). However, if /var is a separate filesystem, it will get unmounted even though /var/run is a tmpfs that's still mounted on top of the /var/run directory in the /var filesystem. The unattended-upgrade script will fail to find lockfile, sleeps for 5 seconds, and tries to check the lockfile again. After 10 minutes (the default timeout), it will finally exit and the system will continue shutdown. The problem is the error handling in /usr/share/unattended-upgrades/unattended-upgrade-shutdown where it tries to lock itself: while True: res = apt_pkg.get_lock(options.lock_file) logging.debug("get_lock returned %i" % res) # exit here if there is no lock if res > 0: logging.debug("lock not taken") break lock_was_taken = True The function apt_pkg.get_lock() either returns a file descriptor, or -1 on an error. File descriptors are just C file descriptors, so they are always positive integers. The code should check the result to be negative, not positive. I have attached a patch to reverse the logic. Additional information: 1) Description: Ubuntu 16.04.1 LTS Release: 16.04 2) unattended-upgrades: Installed: 0.90ubuntu0.3 Candidate: 0.90ubuntu0.3 Version table: *** 0.90ubuntu0.3 500 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial-updates/main i386 Packages 100 /var/lib/dpkg/status 0.90 500 500 http://nl.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 500 http://nl.archive.ubuntu.com/ubuntu xenial/main i386 Packages 3) Fast reboot 4) Very slow reboot (after a 10 minutes timeout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1654600/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654600] Re: unattended-upgrade-shutdown hangs when /var is a separate filesystem
Tested the fix. It works. Thanks! quick fix: sed -i "s#ExecStart=#RemainAfterExit=yes\nExecStop=#;" /lib/systemd/system/unattended-upgrades.service But now it seems that it doesn't run it on shutdown. I used the following debug service: ExecStop=/bin/bash -c 'echo -e "\nhello##\n" > /dev/ttyS0' And it doesn't print message in serial console. But when you start and stop this unit manually - it prints. [ OK ] Stopped target Graphical Interface. Stopping Accounts Service... Stopping User Manager for UID 1000... Stopping Session 1 of user ubuntu. Stopping ACPI event daemon... [ OK ] Stopped target Cloud-init target. [ OK ] Stopped Execute cloud user/final scripts. [ OK ] Stopped target Multi-User System. Stopping Deferred execution scheduler... Stopping LXD - container startup/shutdown... Stopping D-Bus System Message Bus... Stopping LSB: daemon to balance interrupts for SMP systems... Stopping LSB: Set the CPU Frequency Scaling governor to "ondemand"... Stopping LSB: MD monitoring daemon... Stopping Regular background program processing daemon... Stopping FUSE filesystem for LXC... Stopping OpenBSD Secure Shell server... Stopping LSB: Record successful boot for GRUB... [ OK ] Stopped target Timers. [ OK ] Stopped Timer to automatically refresh installed snaps. [ OK ] Stopped Daily apt activities. [ OK ] Stopped Daily Cleanup of Temporary Directories. [ OK ] Stopped target Login Prompts. Stopping Getty on tty1... Stopping Serial Getty on ttyS0... [ OK ] Stopped Apply the settings specified in cloud-config. [ OK ] Stopped target Cloud-config availability. Stopping Snappy daemon... Stopping System Logging Service... [ OK ] Stopped target System Time Synchronized. Stopping LSB: automatic crash report generation... [ OK ] Closed Load/Save RF Kill Switch Status /dev/rfkill Watch. Stopping Authenticate and Authorize Users to Run Privileged Tasks... [ OK ] Unmounted /var/lib/lxcfs. [ OK ] Stopped System Logging Service. [ OK ] Stopped Deferred execution scheduler. [ OK ] Stopped OpenBSD Secure Shell server. [ OK ] Stopped Accounts Service. [ OK ] Stopped Snappy daemon. [ OK ] Stopped ACPI event daemon. [ OK ] Stopped Authenticate and Authorize Users to Run Privileged Tasks. [ OK ] Stopped Serial Getty on ttyS0. [ OK ] Stopped Regular background program processing daemon. [ OK ] Stopped Getty on tty1. [ OK ] Stopped User Manager for UID 1000. [ OK ] Stopped Session 1 of user ubuntu. [ OK ] Stopped D-Bus System Message Bus. [ OK ] Stopped FUSE filesystem for LXC. [ OK ] Stopped LXD - container startup/shutdown. [ OK ] Stopped LSB: MD monitoring daemon. [ OK ] Stopped LSB: Record successful boot for GRUB. [ OK ] Stopped LSB: daemon to balance interrupts for SMP systems. [ OK ] Stopped LSB: automatic crash report generation. [ OK ] Stopped LSB: Set the CPU Frequency Scaling governor to "ondemand". [ OK ] Stopped User Manager for UID 1000. [ OK ] Removed slice User Slice of ubuntu. Stopping Login Service... [ OK ] Removed slice system-getty.slice. [ OK ] Removed slice system-serial\x2dgetty.slice. [ OK ] Stopped /etc/rc.local Compatibility. Stopping Permit User Sessions... [ OK ] Stopped Login Service. [ OK ] Stopped Permit User Sessions. [ OK ] Stopped target Remote File Systems. [ OK ] Stopped target Remote File Systems (Pre). Stopping Login to default iSCSI targets... [ OK ] Stopped target User and Group Name Lookups. [ OK ] Stopped target Basic System. [ OK ] Stopped target Paths. [ OK ] Stopped Forward Password Requests to Wall Directory Watch. [ OK ] Stopped Trigger resolvconf update for networkd DNS. [ OK ] Stopped Dispatch Password Requests to Console Directory Watch. [ OK ] Stopped ACPI Events Check. [ OK ] Stopped target Slices. [ OK ] Removed slice User and Session Slice. [ OK ] Stopped target Sockets. [ OK ] Closed ACPID Listen Socket. [ OK ] Closed UUID daemon activation socket. [ OK ] Closed LXD - unix socket. [ OK ] Closed Syslog Socket. [ OK ] Closed D-Bus System Message Bus Socket. [ OK ] Closed Socket activation for snappy daemon. [ OK ] Stopped target System Initialization. Stopping Network Time Synchronization... [ OK ] Stopped target Encrypted Volumes. Stopping Load/Save Random Seed... [ OK ] Stopped target Swap. [ OK ] Stopped Network Time Synchronization. [ OK ] Stopped Load/Save Random Seed. [ OK ] Stopped Create Volatile Files and Directories. [ OK ] Unmounted /home. [ OK ] Unmounted /boot. [ OK ] Stopped Login to default iSCSI targets. Stopping iSCSI initiator daemon (iscsid)... [ OK ] Stopped iSCSI initiator daemon (iscsid). [ OK ] Stopped target Network is Online. [ OK ] Stopped target Network. [ OK
[Touch-packages] [Bug 1661611] Re: apt/unattended-upgrades stalls shutdown
It doesn't relate to "/usr/share/unattended-upgrades/unattended-upgrade- shutdown" file at all. When you "fix" it - it just fails because of the invalid python syntax. And shutdown just works. The real problem is systemd dependencies. Here is the log of the shutdown process: Unattended upgrades should be started before filesystem unmount, but it starts after unmount: [ OK ] Unmounted /home. [ OK ] Stopped File System Check on /dev/mapper/VG-home. [ OK ] Unmounted /var. [ OK ] Stopped File System Check on /dev/mapper/VG-var. [ OK ] Unmounted /boot. [ OK ] Stopped File System Check on /dev/mapper/VG-boot. [ OK ] Removed slice system-systemd\x2dfsck.slice. [ OK ] Stopped Login to default iSCSI targets. Stopping iSCSI initiator daemon (iscsid)... [ OK ] Stopped iSCSI initiator daemon (iscsid). [ OK ] Stopped target Network is Online. [ OK ] Stopped target Network. [ OK ] Stopped Initial cloud-init job (metadata service crawler). Stopping Raise network interfaces... [ OK ] Stopped Raise network interfaces. [ OK ] Stopped target Local File Systems. Unmounting /run/user/1000... Starting Unattended Upgrades Shutdown... [ OK ] Stopped Apply Kernel Variables. [ OK ] Stopped target Network (Pre). [ OK ] Stopped Initial cloud-init job (pre-networking). [ OK ] Stopped Load Kernel Modules. [ OK ] Unmounted /run/user/1000. [ OK ] Reached target Unmount All Filesystems. [ OK ] Stopped target Local File Systems (Pre). [ OK ] Stopped Create Static Device Nodes in /dev. Stopping Monitoring of LVM2 mirrors... dmeventd or progress polling... [ OK ] Stopped Remount Root and Kernel File Systems. [ OK ] Stopped Monitoring of LVM2 mirrors,...ng dmeventd or progress polling. Stopping LVM2 metadata daemon... [ OK ] Stopped LVM2 metadata daemon. And it is reproducible with LVM only. Have to spend some time on investigation. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1661611 Title: apt/unattended-upgrades stalls shutdown Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When unattended-upgrades is installed, 9 out of 10 shutdowns/reboots hang while "starting unattended upgrades shutdown". This hang stalls the shutdown process for 5-10 mins. If I disable unnattended-upgrades via the /etc/apt/apt.conf.d/20auto- upgrades and/or 50unattended-upgrades, the problems occurs. If I terminate the service before shutdown/reboot (sudo service unattended-upgrades stop) the problem still occurs. If I remove the package (sudo apt remove unattended-upgrades) the problem no longer occurs. This occurs on a freshly installed version of Ubuntu Server 16.04.1 (both unattended-upgrades installed via install GUI or manual install of unattended-upgrades) Both Kern.log & syslog do not show the shutdown process (I believe because the filesystems have already unmounted) Original report: http://askubuntu.com/questions/878630/apt-unattended- upgrades-stalls-shutdown To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1661611/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666993] Re: Make all drop downs / Lists searchable
That's a fair point, for languages at least. On the other hand most people do speak English and a search mask that only accepts Latin letters (I haven't seen a keyboard without Latin letters yet) is better than none at all. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666993 Title: Make all drop downs / Lists searchable Status in Ubuntu UX: New Status in ubuntu-ui-toolkit package in Ubuntu: New Status in unity8 package in Ubuntu: Incomplete Bug description: Sometimes I encounter a list, like "Display Language" and immediate get annoyed, when the only way to get to my item (in this case country) by scrolling, especially if it is a long list. Every list should be searchable via an input field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1666993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1666993] [NEW] Make all drop downs / Lists searchable
Public bug reported: Sometimes I encounter a list, like "Display Language" and immediate get annoyed, when the only way to get to my item (in this case country) by scrolling, especially if it is a long list. Every list should be searchable via an input field ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1666993 Title: Make all drop downs / Lists searchable Status in unity8 package in Ubuntu: New Bug description: Sometimes I encounter a list, like "Display Language" and immediate get annoyed, when the only way to get to my item (in this case country) by scrolling, especially if it is a long list. Every list should be searchable via an input field To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1666993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1665749] [NEW] Hp PSC 1510 not working anymore
Public bug reported: I'm on 14.04 I'm fairly new. I feel like I've tried everything! Printer was working last week. Now It just says "Held" or pending then disappears with no print. I've downloaded the latest drivers. Searching on USB bus... hp-setup[3668]: debug: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub error: No devices found on bus: usb ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1665749 Title: Hp PSC 1510 not working anymore Status in cups package in Ubuntu: New Bug description: I'm on 14.04 I'm fairly new. I feel like I've tried everything! Printer was working last week. Now It just says "Held" or pending then disappears with no print. I've downloaded the latest drivers. Searching on USB bus... hp-setup[3668]: debug: Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. BCM2045B (BDC-2) [Bluetooth Controller] Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub error: No devices found on bus: usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1665749/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581560] Re: system crash when attaching external display
Have resolved the issue by installing yakkety kernel: sudo add-apt-repository ppa:canonical-kernel-team/ppa sudo apt update sudo apt install linux-image-generic-lts-yakkety -- 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/1581560 Title: system crash when attaching external display Status in xorg package in Ubuntu: Expired Bug description: After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes and reboots when I attach an external display. Process: - put laptop to sleep. - come into work the next day - open up laptop - plug in external display - observe bug Expected behavior: I can attach the external display Observed behavior: system shows black screen on both laptop and display and after a minute or two reboots. Laptop drives external display fine after reboot. I ssh to the laptop from another machine and monitored /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors. All I see in those files before the lockup is this, from Xorg.0.log: [ 34289.447] (II) intel(0): Enabled output DP1-8 [ 34289.448] (II) intel(0): Enabled output DP1-1 [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440 [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 0, (0, 0), rotation normal, reflection none ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 13 09:24:07 2016 DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-09-10 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BS0031US ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago) dmi.bios.date: 05/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET29W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS0031US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS0031US dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO drirc: version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 13 09:04:56 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4669 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+sour
[Touch-packages] [Bug 1642259] [NEW] [Design Suggestion] App Settings on desktop
Public bug reported: I think that Unity 8 app settings in look weird on desktop, especially when the window is larger. My suggestion is that at a certain size the menu stays where it is instead of stretching across the screen, so that it would look like in the attached image (made an example of the Terminal app). ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: app apps mir settings unity8 ** Attachment added: "Unity8MenuDesktop.png" https://bugs.launchpad.net/bugs/1642259/+attachment/4778127/+files/Unity8MenuDesktop.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1642259 Title: [Design Suggestion] App Settings on desktop Status in unity8 package in Ubuntu: New Bug description: I think that Unity 8 app settings in look weird on desktop, especially when the window is larger. My suggestion is that at a certain size the menu stays where it is instead of stretching across the screen, so that it would look like in the attached image (made an example of the Terminal app). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1642259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581560] Re: system crash when attaching external display
Why did you close the issue? I still have to power off my laptop instead of suspending. -- 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/1581560 Title: system crash when attaching external display Status in xorg package in Ubuntu: Expired Bug description: After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes and reboots when I attach an external display. Process: - put laptop to sleep. - come into work the next day - open up laptop - plug in external display - observe bug Expected behavior: I can attach the external display Observed behavior: system shows black screen on both laptop and display and after a minute or two reboots. Laptop drives external display fine after reboot. I ssh to the laptop from another machine and monitored /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors. All I see in those files before the lockup is this, from Xorg.0.log: [ 34289.447] (II) intel(0): Enabled output DP1-8 [ 34289.448] (II) intel(0): Enabled output DP1-1 [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440 [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 0, (0, 0), rotation normal, reflection none ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 13 09:24:07 2016 DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-09-10 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BS0031US ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago) dmi.bios.date: 05/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET29W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS0031US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS0031US dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO drirc: version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 13 09:04:56 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4669 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581560/+subscriptions -- Mailing list: https://launchpad.net/~touch-pac
[Touch-packages] [Bug 1636305] [NEW] [Feature Request] Emoticon Menu For Text Fields In Desktop Mode
Public bug reported: When in desktop mode it's difficult to enter emojis when typing. I propose that when you right-click in a text field an additional field in the menu pop ups, where you can choose an emoticon either from a big list or categorized in sub menus. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1636305 Title: [Feature Request] Emoticon Menu For Text Fields In Desktop Mode Status in unity8 package in Ubuntu: New Bug description: When in desktop mode it's difficult to enter emojis when typing. I propose that when you right-click in a text field an additional field in the menu pop ups, where you can choose an emoticon either from a big list or categorized in sub menus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1636305/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581560] Re: system crash when attaching external display
I don't know why my attachments were removed, but this issue was fixed by upgrading the kernel to http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.8-rc6/ -- 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/1581560 Title: system crash when attaching external display Status in xorg package in Ubuntu: Incomplete Bug description: After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes and reboots when I attach an external display. Process: - put laptop to sleep. - come into work the next day - open up laptop - plug in external display - observe bug Expected behavior: I can attach the external display Observed behavior: system shows black screen on both laptop and display and after a minute or two reboots. Laptop drives external display fine after reboot. I ssh to the laptop from another machine and monitored /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors. All I see in those files before the lockup is this, from Xorg.0.log: [ 34289.447] (II) intel(0): Enabled output DP1-8 [ 34289.448] (II) intel(0): Enabled output DP1-1 [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440 [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 0, (0, 0), rotation normal, reflection none ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 13 09:24:07 2016 DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-09-10 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BS0031US ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago) dmi.bios.date: 05/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET29W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS0031US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS0031US dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO drirc: version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 13 09:04:56 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4669 vendor AUO xserver.version: 2:1.18.3-1ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581
[Touch-packages] [Bug 1581560] Re: system crash when attaching external display
Not sure whether it's related to xorg, but not intel driver or something else. Here is my dmesg when I just boot the laptop with the attached dock station. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581560/+attachment/4729829/+files/dmesg.log -- 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/1581560 Title: system crash when attaching external display Status in xorg package in Ubuntu: Incomplete Bug description: After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes and reboots when I attach an external display. Process: - put laptop to sleep. - come into work the next day - open up laptop - plug in external display - observe bug Expected behavior: I can attach the external display Observed behavior: system shows black screen on both laptop and display and after a minute or two reboots. Laptop drives external display fine after reboot. I ssh to the laptop from another machine and monitored /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors. All I see in those files before the lockup is this, from Xorg.0.log: [ 34289.447] (II) intel(0): Enabled output DP1-8 [ 34289.448] (II) intel(0): Enabled output DP1-1 [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440 [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 0, (0, 0), rotation normal, reflection none ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 13 09:24:07 2016 DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-09-10 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BS0031US ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago) dmi.bios.date: 05/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET29W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS0031US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS0031US dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO drirc: version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 13 09:04:56 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4669 vendor AUO
[Touch-packages] [Bug 1617456] [NEW] [Feature Request] Gaming Mode for Unity
Public bug reported: Gaming is an important part for the desktop and besides workstations the most important and popular thing you can do with it. This is why Ubuntu should treat them well and I think they can do that with little effort. Unity 8 should not get in the way while playing a game, you can achieve this in several ways: - Suppress Notifications Problem: Gamer on Windows often complain about unwanted notifications, like system updates or other apps wanting attention. Notifications can be annoying while playing a game and cause a drop in FPS. Solution: So, Unity 8 should not display the at all during a game. Maybe a sound could inform the user instead? - Disable Keys That Throw You To The Desktop Problem: Accidentally hitting the SUPER- or ALT-key could throw you to the desktop Solution: they should be disabled and the user should instead just use ALT + TAB to get to the desktop. Maybe even provide a native steam-like Unity overlay? where you hit a Keyboard combination and can do stuff on your PC while having the game in sight. I'm sure there are things also things that could improve performance, if you have any other ideas feel free to post them below. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: annoyances games gaming notifications performance unity ** Tags added: gaming ** Tags added: unity ** Tags added: annoyances games performance ** Tags added: notifications -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1617456 Title: [Feature Request] Gaming Mode for Unity Status in unity8 package in Ubuntu: New Bug description: Gaming is an important part for the desktop and besides workstations the most important and popular thing you can do with it. This is why Ubuntu should treat them well and I think they can do that with little effort. Unity 8 should not get in the way while playing a game, you can achieve this in several ways: - Suppress Notifications Problem: Gamer on Windows often complain about unwanted notifications, like system updates or other apps wanting attention. Notifications can be annoying while playing a game and cause a drop in FPS. Solution: So, Unity 8 should not display the at all during a game. Maybe a sound could inform the user instead? - Disable Keys That Throw You To The Desktop Problem: Accidentally hitting the SUPER- or ALT-key could throw you to the desktop Solution: they should be disabled and the user should instead just use ALT + TAB to get to the desktop. Maybe even provide a native steam- like Unity overlay? where you hit a Keyboard combination and can do stuff on your PC while having the game in sight. I'm sure there are things also things that could improve performance, if you have any other ideas feel free to post them below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1617456/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581560] Re: system crash when attaching external display
I have the same issue on Ubuntu 16.04 4.4.0-34-generic and Lenovo x260 If it was suspended with two screens, it would not wake up. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1581560/+attachment/4727743/+files/dmesg.log -- 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/1581560 Title: system crash when attaching external display Status in xorg package in Ubuntu: Incomplete Bug description: After upgrading to 16.04, my thinkpad x1 carbon (3rd edition) freezes and reboots when I attach an external display. Process: - put laptop to sleep. - come into work the next day - open up laptop - plug in external display - observe bug Expected behavior: I can attach the external display Observed behavior: system shows black screen on both laptop and display and after a minute or two reboots. Laptop drives external display fine after reboot. I ssh to the laptop from another machine and monitored /var/log/syslog, /var/log/Xorg.0.log, and ~/.xsession-errors. All I see in those files before the lockup is this, from Xorg.0.log: [ 34289.447] (II) intel(0): Enabled output DP1-8 [ 34289.448] (II) intel(0): Enabled output DP1-1 [ 34289.460] (II) intel(0): resizing framebuffer to 2560x1440 [ 34289.482] (II) intel(0): switch to mode 2560x1440@60.0 on DP1-8 using pipe 0, (0, 0), rotation normal, reflection none ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri May 13 09:24:07 2016 DistUpgraded: 2016-04-21 20:51:13,846 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.18, 4.2.0-30-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-21-generic, x86_64: installed virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Broadwell-U Integrated Graphics [17aa:2227] InstallationDate: Installed on 2015-09-10 (245 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 20BS0031US ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2016-04-22 (21 days ago) dmi.bios.date: 05/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET29W (1.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BS0031US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET29W(1.07):bd05/08/2015:svnLENOVO:pn20BS0031US:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BS0031US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BS0031US dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO drirc: version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 13 09:04:56 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4669 vendor AUO xserver.version: 2:1.18.3-
[Touch-packages] [Bug 1547999] Re: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn
It still doesn't work even in Xenial. When I use 'push "dhcp-option DNS 10.25.8.1 *"', network manager prints "none" in log, when it actually should use this DNS as a global DNS. -- 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/1547999 Title: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn Status in network-manager package in Ubuntu: Fix Released Bug description: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src /dns-manager/nm-dns-dnsmasq.c (where split FALSE / TRUE used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547999] Re: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn
That is obvious, but what about 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/1547999 Title: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn Status in network-manager package in Ubuntu: Fix Released Bug description: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src /dns-manager/nm-dns-dnsmasq.c (where split FALSE / TRUE used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1548052] Re: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault
@penalvch, looks like I sent the dump. But i'm not sure. ubuntu-bug didn't confirm whether the dump was sent. -- 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/1548052 Title: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault Status in xorg package in Ubuntu: Invalid Bug description: Two monitors KDE env (laptop LCD + external moinitor). Installed new wily LTS kernel with the video driver: sudo apt-get install --install-recommends linux-generic-lts-wily xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video- all-lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts- wily libgl1-mesa-glx-lts-wily libgl1-mesa-glx-lts-wily:i386 libglapi- mesa-lts-wily:i386 After 4 hours of working in Chromium (with --disable-gpu flag) I got segmentation fault: [ 11249.976] (EE) [ 11249.976] (EE) Backtrace: [ 11249.977] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x5611c75a5308] [ 11249.977] (EE) 1: /usr/bin/X (0x5611c7404000+0x1a5359) [0x5611c75a9359] [ 11249.977] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fda90346000+0x36d40) [0x7fda9037cd40] [ 11249.977] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x259dc) [0x7fda8c15b9dc] [ 11249.977] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x26b3f) [0x7fda8c15cb3f] [ 11249.977] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a2a8) [0x7fda8c1802a8] [ 11249.977] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a874) [0x7fda8c180874] [ 11249.977] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x591d6) [0x7fda8c18f1d6] [ 11249.977] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x59649) [0x7fda8c18f649] [ 11249.977] (EE) 9: /usr/bin/X (0x5611c7404000+0x13021d) [0x5611c753421d] [ 11249.978] (EE) 10: /usr/bin/X (0x5611c7404000+0x51205) [0x5611c7455205] [ 11249.978] (EE) 11: /usr/bin/X (0x5611c7404000+0x5433e) [0x5611c745833e] [ 11249.978] (EE) 12: /usr/bin/X (0x5611c7404000+0x5818b) [0x5611c745c18b] [ 11249.978] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fda90367ec5] [ 11249.978] (EE) 14: /usr/bin/X (0x5611c7404000+0x4370e) [0x5611c744770e] [ 11249.978] (EE) [ 11249.978] (EE) Segmentation fault at address 0x7fd8e21dbde0 [ 11249.978] (EE) Fatal server error: [ 11249.978] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 11249.978] (EE) [ 11249.978] (EE) Full log attached. kernel cmdline: cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 cat /proc/version_signature Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nutnat21760 F pulseaudio DistroRelease: Ubuntu 14.04 MachineType: Hewlett-Packard HP EliteBook 2170p Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-27-generic N/A linux-backports-modules-4.2.0-27-generic N/A linux-firmware1.127.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 4.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: pkcs11 WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/07/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IMT Ver. F.61 dmi.board.name: 1815 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.1C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IMTVer.F.61:bd04/07/2015:svnHewlett-Packard:pnHPEliteBook2170p:pvrA1009D11:rvnHewlett-Packard:rn1815:rvrKBCVersion63.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2170p dmi.product.version: A1009D11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1548052] Re: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault
@penalvch, yep, it was not sent. Have just resent it. Now it should be available for you. -- 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/1548052 Title: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault Status in xorg package in Ubuntu: Invalid Bug description: Two monitors KDE env (laptop LCD + external moinitor). Installed new wily LTS kernel with the video driver: sudo apt-get install --install-recommends linux-generic-lts-wily xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video- all-lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts- wily libgl1-mesa-glx-lts-wily libgl1-mesa-glx-lts-wily:i386 libglapi- mesa-lts-wily:i386 After 4 hours of working in Chromium (with --disable-gpu flag) I got segmentation fault: [ 11249.976] (EE) [ 11249.976] (EE) Backtrace: [ 11249.977] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x5611c75a5308] [ 11249.977] (EE) 1: /usr/bin/X (0x5611c7404000+0x1a5359) [0x5611c75a9359] [ 11249.977] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fda90346000+0x36d40) [0x7fda9037cd40] [ 11249.977] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x259dc) [0x7fda8c15b9dc] [ 11249.977] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x26b3f) [0x7fda8c15cb3f] [ 11249.977] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a2a8) [0x7fda8c1802a8] [ 11249.977] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a874) [0x7fda8c180874] [ 11249.977] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x591d6) [0x7fda8c18f1d6] [ 11249.977] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x59649) [0x7fda8c18f649] [ 11249.977] (EE) 9: /usr/bin/X (0x5611c7404000+0x13021d) [0x5611c753421d] [ 11249.978] (EE) 10: /usr/bin/X (0x5611c7404000+0x51205) [0x5611c7455205] [ 11249.978] (EE) 11: /usr/bin/X (0x5611c7404000+0x5433e) [0x5611c745833e] [ 11249.978] (EE) 12: /usr/bin/X (0x5611c7404000+0x5818b) [0x5611c745c18b] [ 11249.978] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fda90367ec5] [ 11249.978] (EE) 14: /usr/bin/X (0x5611c7404000+0x4370e) [0x5611c744770e] [ 11249.978] (EE) [ 11249.978] (EE) Segmentation fault at address 0x7fd8e21dbde0 [ 11249.978] (EE) Fatal server error: [ 11249.978] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 11249.978] (EE) [ 11249.978] (EE) Full log attached. kernel cmdline: cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 cat /proc/version_signature Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nutnat21760 F pulseaudio DistroRelease: Ubuntu 14.04 MachineType: Hewlett-Packard HP EliteBook 2170p Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-27-generic N/A linux-backports-modules-4.2.0-27-generic N/A linux-firmware1.127.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 4.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: pkcs11 WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/07/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IMT Ver. F.61 dmi.board.name: 1815 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.1C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IMTVer.F.61:bd04/07/2015:svnHewlett-Packard:pnHPEliteBook2170p:pvrA1009D11:rvnHewlett-Packard:rn1815:rvrKBCVersion63.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2170p dmi.product.version: A1009D11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554455] [NEW] "update-initramfs" is executed several times when you remove old kernels
Public bug reported: Here is an example. I had several old kernels: linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic I used apt-get autoremove and here is the result: apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED: grub-pc-bin linux-headers-3.19.0-49 linux-headers-3.19.0-49-generic linux-image-3.19.0-49-generic linux-image-4.2.0-25-generic linux-image-extra-3.19.0-49-generic linux-image-extra-4.2.0-25-generic linux-signed-image-3.19.0-49-generic linux-signed-image-4.2.0-25-generic 0 upgraded, 0 newly installed, 9 to remove and 0 not upgraded. After this operation, 502 MB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ... 211099 files and directories currently installed.) Removing grub-pc-bin (2.02~beta2-9ubuntu1.7) ... Removing linux-headers-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Removing linux-headers-3.19.0-49 (3.19.0-49.55~14.04.1) ... Removing linux-signed-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-extra-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Generating /boot/initrd.img-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-3.19.0-49-generic Found initrd image: /boot/initrd.img-3.19.0-49-generic Found Windows Boot Manager on /dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi Found Ubuntu Xenial Xerus (development branch) (16.04) on /dev/mapper/VG-root Adding boot menu entry for EFI firmware configuration done Removing linux-image-3.19.0-49-generic (3.19.0-49.55~14.04.1) ... Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic update-initramfs: Deleting /boot/initrd.img-3.19.0-49-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.19.0-49-generic /boot/vmlinuz-3.19.0-49-generic Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-generic Found initrd image: /boot/initrd.img-3.19.0-51-generic Found linux image: /boot/vmlinuz-4.2.0-30-generic Found initrd image: /boot/initrd.img-4.2.0-30-generic Found linux image: /boot/vmlinuz-4.2.0-27-generic Found initrd image: /boot/initrd.img-4.2.0-27-generic Found linux image: /boot/vmlinuz-3.19.0-51-
[Touch-packages] [Bug 1553678] Re: os-prober doesn't detect Windows properly with EFI and MBR partition
** Package changed: xorg (Ubuntu) => os-prober (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1553678 Title: os-prober doesn't detect Windows properly with EFI and MBR partition Status in os-prober package in Ubuntu: New Bug description: https://anonscm.debian.org/cgit/d-i/os-prober.git/tree/os- probes/mounted/x86/05efi#n42..n45 Disk has regular MBR table. It has Windows 7 and Ubuntu installed on different partitions. Os-prober doesn't detect EFI partition on MBR table because "udevadm info" returns "dos" partition scheme instead of expected "msdos". $ udevadm info /dev/sda1 | grep dos E: ID_PART_ENTRY_SCHEME=dos E: ID_PART_TABLE_TYPE=dos $ fdisk -lu /dev/sda | grep -B1 -A1 ef Device Boot Start End Blocks Id System /dev/sda1 *2048 616447 307200 ef EFI (FAT-12/16/32) /dev/sda2 616448 128134439637589967 HPFS/NTFS/exFAT Fixing conditions below resolves the issue: - \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != msdos \) -o \ + \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != dos \) -o \ \( "$ID_PART_ENTRY_SCHEME" = gpt -a "$ID_PART_ENTRY_TYPE" != c12a7328-f81f-11d2-ba4b-00a0c93ec93b \) -o \ - \( "$ID_PART_ENTRY_SCHEME" = msdos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then + \( "$ID_PART_ENTRY_SCHEME" = dos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/1553678/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1548052] Re: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault
_usr_bin_Xorg.0.crash -- 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/1548052 Title: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault Status in xorg package in Ubuntu: Incomplete Bug description: Two monitors KDE env (laptop LCD + external moinitor). Installed new wily LTS kernel with the video driver: sudo apt-get install --install-recommends linux-generic-lts-wily xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video- all-lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts- wily libgl1-mesa-glx-lts-wily libgl1-mesa-glx-lts-wily:i386 libglapi- mesa-lts-wily:i386 After 4 hours of working in Chromium (with --disable-gpu flag) I got segmentation fault: [ 11249.976] (EE) [ 11249.976] (EE) Backtrace: [ 11249.977] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x5611c75a5308] [ 11249.977] (EE) 1: /usr/bin/X (0x5611c7404000+0x1a5359) [0x5611c75a9359] [ 11249.977] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fda90346000+0x36d40) [0x7fda9037cd40] [ 11249.977] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x259dc) [0x7fda8c15b9dc] [ 11249.977] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x26b3f) [0x7fda8c15cb3f] [ 11249.977] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a2a8) [0x7fda8c1802a8] [ 11249.977] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a874) [0x7fda8c180874] [ 11249.977] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x591d6) [0x7fda8c18f1d6] [ 11249.977] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x59649) [0x7fda8c18f649] [ 11249.977] (EE) 9: /usr/bin/X (0x5611c7404000+0x13021d) [0x5611c753421d] [ 11249.978] (EE) 10: /usr/bin/X (0x5611c7404000+0x51205) [0x5611c7455205] [ 11249.978] (EE) 11: /usr/bin/X (0x5611c7404000+0x5433e) [0x5611c745833e] [ 11249.978] (EE) 12: /usr/bin/X (0x5611c7404000+0x5818b) [0x5611c745c18b] [ 11249.978] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fda90367ec5] [ 11249.978] (EE) 14: /usr/bin/X (0x5611c7404000+0x4370e) [0x5611c744770e] [ 11249.978] (EE) [ 11249.978] (EE) Segmentation fault at address 0x7fd8e21dbde0 [ 11249.978] (EE) Fatal server error: [ 11249.978] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 11249.978] (EE) [ 11249.978] (EE) Full log attached. kernel cmdline: cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 cat /proc/version_signature Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nutnat21760 F pulseaudio DistroRelease: Ubuntu 14.04 MachineType: Hewlett-Packard HP EliteBook 2170p Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-27-generic N/A linux-backports-modules-4.2.0-27-generic N/A linux-firmware1.127.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 4.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: pkcs11 WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/07/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IMT Ver. F.61 dmi.board.name: 1815 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.1C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IMTVer.F.61:bd04/07/2015:svnHewlett-Packard:pnHPEliteBook2170p:pvrA1009D11:rvnHewlett-Packard:rn1815:rvrKBCVersion63.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2170p dmi.product.version: A1009D11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1553678] [NEW] os-prober doesn't detect Windows properly with EFI and MBR partition
Public bug reported: https://anonscm.debian.org/cgit/d-i/os-prober.git/tree/os- probes/mounted/x86/05efi#n42..n45 Disk has regular MBR table. It has Windows 7 and Ubuntu installed on different partitions. Os-prober doesn't detect EFI partition on MBR table because "udevadm info" returns "dos" partition scheme instead of expected "msdos". $ udevadm info /dev/sda1 | grep dos E: ID_PART_ENTRY_SCHEME=dos E: ID_PART_TABLE_TYPE=dos $ fdisk -lu /dev/sda | grep -B1 -A1 ef Device Boot Start End Blocks Id System /dev/sda1 *2048 616447 307200 ef EFI (FAT-12/16/32) /dev/sda2 616448 128134439637589967 HPFS/NTFS/exFAT Fixing conditions below resolves the issue: - \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != msdos \) -o \ + \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != dos \) -o \ \( "$ID_PART_ENTRY_SCHEME" = gpt -a "$ID_PART_ENTRY_TYPE" != c12a7328-f81f-11d2-ba4b-00a0c93ec93b \) -o \ - \( "$ID_PART_ENTRY_SCHEME" = msdos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then + \( "$ID_PART_ENTRY_SCHEME" = dos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: efi mbr windows -- 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/1553678 Title: os-prober doesn't detect Windows properly with EFI and MBR partition Status in xorg package in Ubuntu: New Bug description: https://anonscm.debian.org/cgit/d-i/os-prober.git/tree/os- probes/mounted/x86/05efi#n42..n45 Disk has regular MBR table. It has Windows 7 and Ubuntu installed on different partitions. Os-prober doesn't detect EFI partition on MBR table because "udevadm info" returns "dos" partition scheme instead of expected "msdos". $ udevadm info /dev/sda1 | grep dos E: ID_PART_ENTRY_SCHEME=dos E: ID_PART_TABLE_TYPE=dos $ fdisk -lu /dev/sda | grep -B1 -A1 ef Device Boot Start End Blocks Id System /dev/sda1 *2048 616447 307200 ef EFI (FAT-12/16/32) /dev/sda2 616448 128134439637589967 HPFS/NTFS/exFAT Fixing conditions below resolves the issue: - \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != msdos \) -o \ + \( "$ID_PART_ENTRY_SCHEME" != gpt -a "$ID_PART_ENTRY_SCHEME" != dos \) -o \ \( "$ID_PART_ENTRY_SCHEME" = gpt -a "$ID_PART_ENTRY_TYPE" != c12a7328-f81f-11d2-ba4b-00a0c93ec93b \) -o \ - \( "$ID_PART_ENTRY_SCHEME" = msdos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then + \( "$ID_PART_ENTRY_SCHEME" = dos -a "$ID_PART_ENTRY_TYPE" != 0xef \) ]; then To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1553678/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1548052] Re: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault
penalvch, yes, I have. bzipped file is 20M long. Does it contain sensitive data? Is it safe to public it? -- 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/1548052 Title: New Ubuntu 14.04.4 LTS intel video driver Xorg segmentation fault Status in xorg package in Ubuntu: Incomplete Bug description: Two monitors KDE env (laptop LCD + external moinitor). Installed new wily LTS kernel with the video driver: sudo apt-get install --install-recommends linux-generic-lts-wily xserver-xorg-core-lts-wily xserver-xorg-lts-wily xserver-xorg-video- all-lts-wily xserver-xorg-input-all-lts-wily libwayland-egl1-mesa-lts- wily libgl1-mesa-glx-lts-wily libgl1-mesa-glx-lts-wily:i386 libglapi- mesa-lts-wily:i386 After 4 hours of working in Chromium (with --disable-gpu flag) I got segmentation fault: [ 11249.976] (EE) [ 11249.976] (EE) Backtrace: [ 11249.977] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x5611c75a5308] [ 11249.977] (EE) 1: /usr/bin/X (0x5611c7404000+0x1a5359) [0x5611c75a9359] [ 11249.977] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fda90346000+0x36d40) [0x7fda9037cd40] [ 11249.977] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x259dc) [0x7fda8c15b9dc] [ 11249.977] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x26b3f) [0x7fda8c15cb3f] [ 11249.977] (EE) 5: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a2a8) [0x7fda8c1802a8] [ 11249.977] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x4a874) [0x7fda8c180874] [ 11249.977] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x591d6) [0x7fda8c18f1d6] [ 11249.977] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x7fda8c136000+0x59649) [0x7fda8c18f649] [ 11249.977] (EE) 9: /usr/bin/X (0x5611c7404000+0x13021d) [0x5611c753421d] [ 11249.978] (EE) 10: /usr/bin/X (0x5611c7404000+0x51205) [0x5611c7455205] [ 11249.978] (EE) 11: /usr/bin/X (0x5611c7404000+0x5433e) [0x5611c745833e] [ 11249.978] (EE) 12: /usr/bin/X (0x5611c7404000+0x5818b) [0x5611c745c18b] [ 11249.978] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fda90367ec5] [ 11249.978] (EE) 14: /usr/bin/X (0x5611c7404000+0x4370e) [0x5611c744770e] [ 11249.978] (EE) [ 11249.978] (EE) Segmentation fault at address 0x7fd8e21dbde0 [ 11249.978] (EE) Fatal server error: [ 11249.978] (EE) Caught signal 11 (Segmentation fault). Server aborting [ 11249.978] (EE) [ 11249.978] (EE) Full log attached. kernel cmdline: cat /proc/cmdline BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 cat /proc/version_signature Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nutnat21760 F pulseaudio DistroRelease: Ubuntu 14.04 MachineType: Hewlett-Packard HP EliteBook 2170p Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-27-generic root=/dev/mapper/VG-root ro quiet splash tpm_tis.interrupts=0 video=efifb vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-27.32~14.04.1-generic 4.2.8-ckt1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.2.0-27-generic N/A linux-backports-modules-4.2.0-27-generic N/A linux-firmware1.127.20 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: trusty Uname: Linux 4.2.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: pkcs11 WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/07/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IMT Ver. F.61 dmi.board.name: 1815 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 63.1C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IMTVer.F.61:bd04/07/2015:svnHewlett-Packard:pnHPEliteBook2170p:pvrA1009D11:rvnHewlett-Packard:rn1815:rvrKBCVersion63.1C:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 2170p dmi.product.version: A1009D11 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1548052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1552230] [NEW] gdb man page doesn't mention option "--args"
Public bug reported: gdb manpage doesn't list --args as a possible command line argument. This very important option allows one to pass an executable name with /its/ command line, and is possibly one of the most generally useful of gdb's arguments. It is documented in the info file, but unaccountably missing from the man page. Description:Ubuntu 15.10 Release:15.10 gdb: Installed: 7.10-1ubuntu2 Candidate: 7.10-1ubuntu2 Version table: *** 7.10-1ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gdb (Ubuntu) Importance: Undecided Status: New ** Tags: manpage -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1552230 Title: gdb man page doesn't mention option "--args" Status in gdb package in Ubuntu: New Bug description: gdb manpage doesn't list --args as a possible command line argument. This very important option allows one to pass an executable name with /its/ command line, and is possibly one of the most generally useful of gdb's arguments. It is documented in the info file, but unaccountably missing from the man page. Description:Ubuntu 15.10 Release:15.10 gdb: Installed: 7.10-1ubuntu2 Candidate: 7.10-1ubuntu2 Version table: *** 7.10-1ubuntu2 0 500 http://gb.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1552230/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547999] Re: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn
Looks like it was fixed here: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/src /dns-manager/nm-dns- dnsmasq.c?id=ae9e82354a9c1b2247b7d071ed62acd9e83ae27b -- 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/1547999 Title: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn Status in network-manager package in Ubuntu: New Bug description: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src /dns-manager/nm-dns-dnsmasq.c (where split FALSE / TRUE used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547999] Re: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn
In case when openvpn server has this configuration: push "dhcp-option DNS 10.25.8.1 *" -- 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/1547999 Title: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn Status in network-manager package in Ubuntu: New Bug description: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src /dns-manager/nm-dns-dnsmasq.c (where split FALSE / TRUE used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547999] [NEW] Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn
Public bug reported: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src/dns- manager/nm-dns-dnsmasq.c ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: dns ipv6 networkmanager openvpn reverse-dns ** Description changed: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa - But it should create only one: + But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src/dns- manager/nm-dns-dnsmasq.c -- 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/1547999 Title: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn Status in network-manager package in Ubuntu: New Bug description: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src /dns-manager/nm-dns-dnsmasq.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1547999] Re: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn
** Description changed: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src/dns- - manager/nm-dns-dnsmasq.c + manager/nm-dns-dnsmasq.c (where split FALSE / TRUE used) -- 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/1547999 Title: Network manager adds "reverse-DNS" for DNS IP when there are more than one IP address provided by openvpn Status in network-manager package in Ubuntu: New Bug description: Server side configuration: server 10.25.8.0 255.255.255.0 server-ipv6 2001:db8:0:123:8000::/65 push redirect-gateway push "dhcp-option DNS 10.25.8.1" push "route-ipv6 2000::/3" push redirect-gateway ipv6 NetworkManager creates this entry for dnsmasq: dnsmasq[5628]: setting upstream servers from DBus dnsmasq[5628]: using nameserver 10.25.8.1#53 for domain 10.in-addr.arpa But it should create this one: dnsmasq[5628]: using nameserver 10.25.8.1#53 When you comment-out ipv6 related strings on server side, NetworkManager works as expected. NetworkManager version 0.9.8.8 Bug is somewhere there... https://cgit.freedesktop.org/NetworkManager/NetworkManager/log/src /dns-manager/nm-dns-dnsmasq.c (where split FALSE / TRUE used) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1547999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1537399] [NEW] [Feature Request] Xmir icon generation
Public bug reported: Old non-mir apps have ugly icons which don't fit to the other mir native apps. A solution could be that unity 8 generates the icon background itself (maybe with a slight gradient touch or other style) so that it fits at least with the same icon size and shape. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1537399 Title: [Feature Request] Xmir icon generation Status in unity8 package in Ubuntu: New Bug description: Old non-mir apps have ugly icons which don't fit to the other mir native apps. A solution could be that unity 8 generates the icon background itself (maybe with a slight gradient touch or other style) so that it fits at least with the same icon size and shape. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1537399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1527304] [NEW] Yakuake package for Xenial
Public bug reported: There is no yakuake package which could be installed in new Ubuntu Xenial. There is a port which could be compiled from this source: git://anongit.kde.org/yakuake.git#branch=frameworks I've already recompiled yakuake package from this source and it works. Here is a screenshot. ** Affects: yakuake (Ubuntu) Importance: Undecided Status: New ** Tags: plasma5 xenial yakuake ** Attachment added: "yakuake.png" https://bugs.launchpad.net/bugs/1527304/+attachment/4536298/+files/yakuake.png ** Package changed: gtk+2.0 (Ubuntu) => ubuntu ** Package changed: ubuntu => yakuake (Ubuntu) ** Tags added: plasma5 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1527304 Title: Yakuake package for Xenial Status in yakuake package in Ubuntu: New Bug description: There is no yakuake package which could be installed in new Ubuntu Xenial. There is a port which could be compiled from this source: git://anongit.kde.org/yakuake.git#branch=frameworks I've already recompiled yakuake package from this source and it works. Here is a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yakuake/+bug/1527304/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1219337] Re: Users can change the clock without authenticating, allowing them to locally exploit sudo.
A solution could be setting one clock for users, which can be set to their prefered timezone and one for the system (root) which is used by cron jobs etc -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1219337 Title: Users can change the clock without authenticating, allowing them to locally exploit sudo. Status in GNOME Control Center: Unknown Status in sudo: Unknown Status in Unity: Invalid Status in policykit-desktop-privileges package in Ubuntu: Opinion Status in sudo package in Ubuntu: Triaged Status in policykit-desktop-privileges source package in Precise: Opinion Status in sudo source package in Precise: Triaged Status in policykit-desktop-privileges source package in Trusty: Opinion Status in sudo source package in Trusty: Triaged Status in policykit-desktop-privileges source package in Utopic: Opinion Status in sudo source package in Utopic: Triaged Status in policykit-desktop-privileges source package in Vivid: Opinion Status in sudo source package in Vivid: Triaged Bug description: Under unity and cinnamon, it is possible for a user to turn off network-syncronized time and then change the time on the system. It is also possible to "cat /var/log/auth.log" and find the last time a user authenticated with sudo, along with which pty they used. If a user had used a terminal and successfully authenticated with sudo anytime in the past, and left the sudo file in "/var/lib/sudo//", a malicious user could walk up to an unlocked, logged in machine and gain sudo without knowing the password for the computer. To do this, a user would only need to launch a few terminals, figure out which pty they were on via "tty", find the an instance in /var/log/auth.log where sudo was used on that PTY, and set the clock to that time. Once this is done, they can run (for example) "sudo -s" and have a full access terminal. 1) This has been observed on Ubuntu 13.04, and may work on other versions. 2) This may have an effect on various window managers, but I confirmed it on Unity and Cinnamon 3) I expected to have to authenticate when I changed the time and date, as I do on Gnome and KDE. I also expected to be denied permission to auth.log 4) I was able to change the system time to whatever I wanted, and view auth.log. This was sufficient to access sudo without having to type my password. Note: This bug also affects any version of OS X, though the mechanism is different. Some versions don't require you to authenticate to change the time through the GUI, but some do. No version I've seen requires authentication to use the "systemsetup" command, which can alter the time from the command line. This may be an overall bug in sudo. Why can I bypass security by changing the time?! To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1219337/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 223133] Re: wrong volume interactions
What I find really stupid is that for *some* reason Windows can handle sound rather consistently across all sound cards. If Windows, of all operating systems, can, then why can't Pulseaudio? -- 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/223133 Title: wrong volume interactions Status in “pulseaudio” package in Ubuntu: Won't Fix Bug description: Binary package hint: pulseaudio I have the front slider at maximum volume. I have the PCM slider at 72% volume. I have the VLC internal slider at maximum volume. In PulseAudio Volume Control when I put a volume for VLC to 27% it's to loud, than I put a volume at 26% an I don't have any sound !! The volume will be probably added instance of multiply. And it will be grate to have volumes in dB ;-) For example we can have a fader from -80 dB to 0 dB with a linear part for to first "8.68588963806504 dB" to don't have any angle. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/223133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354306]
(In reply to comment #1) > Note that, due to a firmware change, the m400 rule should use "gpio_keys" > instead of "gpio-keys". Here is the new rule: > > SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="platform", > KERNELS=="gpio_keys.6", PROGRAM="/bin/grep '^HP ProLiant m400 Server > Cartridge$' /proc/device-tree/model", TAG+="power-switch" That's a neat hack, but in no way upstreamable. Upstream udev dev will not read the device information from /proc, and will also not call any external tools like grep. This all needs to be solved properly on the kernel side, to export real devices and allow efficient and reliable matching from userspace tools. -- 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/1354306 Title: gpio shutdown trigger for ProLiant m400 cartridges Status in systemd: Confirmed Status in “systemd” package in Ubuntu: Triaged Status in “systemd” source package in Trusty: Triaged Status in “systemd” source package in Utopic: Triaged Bug description: Similar to the m800 case in LP: #1347776, udev/systemd also needs to know how to trigger a graceful shutdown on ProLiant m400 cartridges. [Impact] Without this change, the power down button will not initiate an OS shutdown on this platform. [Test Case] Push button. Watch poweroff occur. [Regression Potential] The new rule is pretty tightly bound to the m400 system - so the risk of this rule matching and impacting behavior on a different platform is minimal. This will presumably cause new code to run and read /proc/device-tree/model on other platforms - but this is already done for the m800 system in both utopic and trusty. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1354306/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347776]
(In reply to comment #1) > Note that, due to a firmware change, the m400 rule should use "gpio_keys" > instead of "gpio-keys". Here is the new rule: > > SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="platform", > KERNELS=="gpio_keys.6", PROGRAM="/bin/grep '^HP ProLiant m400 Server > Cartridge$' /proc/device-tree/model", TAG+="power-switch" That's a neat hack, but in no way upstreamable. Upstream udev dev will not read the device information from /proc, and will also not call any external tools like grep. This all needs to be solved properly on the kernel side, to export real devices and allow efficient and reliable matching from userspace tools. -- 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/1347776 Title: shutdown trigger on gpio_keys.X for armhf hardware Status in systemd: Confirmed Status in “systemd” package in Ubuntu: Fix Released Status in “systemd” source package in Trusty: Fix Committed Status in “systemd” source package in Utopic: Fix Released Bug description: Some ARM board uses GPIO gpio_key.12 for power control (key=116). The proposed patch adds entry to logind's 70-power-switch.rules to initiate soft shutdown of the cartridge from ilo. Here is the udevadm output for /dev/input/event0 sudo udevadm info --query=all --name=/dev/input/event0 --attribute- walk Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/soc.3/gpio_keys.12/input/input0/event0': KERNEL=="event0" SUBSYSTEM=="input" DRIVER=="" looking at parent device '/devices/soc.3/gpio_keys.12/input/input0': KERNELS=="input0" SUBSYSTEMS=="input" DRIVERS=="" ATTRS{name}=="gpio_keys.12" ATTRS{phys}=="gpio-keys/input0" ATTRS{uniq}=="" ATTRS{properties}=="0" looking at parent device '/devices/soc.3/gpio_keys.12': KERNELS=="gpio_keys.12" SUBSYSTEMS=="platform" DRIVERS=="gpio-keys" ATTRS{keys}=="116" ATTRS{switches}=="" ATTRS{disabled_keys}=="" ATTRS{disabled_switches}=="" looking at parent device '/devices/soc.3': KERNELS=="soc.3" SUBSYSTEMS=="platform" DRIVERS=="" Regarding the possibility of gpio_key.12 being used by other systems to map to some other trigger, I put in the check that the gpio_key.12 is associated with power control (keys=116). '116' is supposedly linux generic power control in DTS. There is no uniq idSystem or idVendor for device /dev/input/event0 as you can see from udevadm output, therefore I tried to use the best available combination as a safety check. This patch will enable power control for any system vendor (Other than the one the patch in intended for) that describes in DTS, the trigger gpio_key.12 as power control (116). SRU Request == [Impact] * User won't be able to initiate a soft shutdown from the chassis manager. [Test Case] * To reproduce this bug, initiate a soft shutdown from the chassis manager, for example from ilo you could do set node power off shutdown [Test Result] == BEFORE PATCH == $ cat /lib/udev/rules.d/70-power-switch.rules # This file is part of systemd. # # systemd is free software; you can redistribute it and/or modify it # under the terms of the GNU Lesser General Public License as published by # the Free Software Foundation; either version 2.1 of the License, or # (at your option) any later version. ACTION=="remove", GOTO="power_switch_end" SUBSYSTEM=="input", KERNEL=="event*", SUBSYSTEMS=="acpi", TAG+="power-switch" SUBSYSTEM=="input", KERNEL=="event*", KERNELS=="thinkpad_acpi", TAG+="power-switch" LABEL="power_switch_end" $ hpiLO-> set node power off shutdown c3n2 c3: #Cartridge 3 c3n2: #Node 2 Shutting node down gracefully hpiLO-> show node list Slot ID Proc Manufacturer Architecture Memory Power Health - -- -- - -- 3 c3n1 ARM Architecture 8 GB On OK 3 c3n2 ARM Architecture 8 GB On OK 3 c3n3 ARM Architecture 8 GB On OK 3 c3n4 ARM Architecture 8 GB Off OK hpiLO-> == AFTER PATCH == hpiLO-> set node power off shutdown c3n1 c3: #Cartridge 3 c3n1: #Node 1 Shutting node down gracefully hpiLO-> show node list Slot ID Proc Manufacturer Architecture Memory Power Health - -- -- - -- 3 c3n1 ARM Architecture 8 GB Off OK 3 c3n2 ARM Architecture 8 GB On OK 3 c3n3 ARM Architecture 8 GB On OK 3 c3n