[Touch-packages] [Bug 1677125] Re: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode")
... which work perfectly for Mir. Just Xorg fails to start. -- 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/1677125 Title: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode") Status in xorg package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: zesty can't get to the login screen when a Geforce GT210 card is installed I just get an unclickable dialog "The system is running in low- graphics mode" and stuck. Although if I VT switch and log in by SSH I find mir-demos all run nicely. So this is just a problem with Xorg/lightdm. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Mar 29 14:08:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1313] InstallationDate: Installed on 2016-11-03 (146 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=9a004175-205d-430e-bd14-8d796f0d18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Wed Mar 29 14:03:29 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677125] Re: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode")
Probably blame the nvidia driver used : (EE) Failed to load module "nvidia" (module does not exist, 0) There is buggy nvidia-375 (at least) from the archive; i'm using nvidia-378 fromm the X ppa, and it works well. note: reports against nvidia drivers exist on launchpad. What happen with 'nouveau' ? -- 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/1677125 Title: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode") Status in xorg package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: zesty can't get to the login screen when a Geforce GT210 card is installed I just get an unclickable dialog "The system is running in low- graphics mode" and stuck. Although if I VT switch and log in by SSH I find mir-demos all run nicely. So this is just a problem with Xorg/lightdm. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Mar 29 14:08:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1313] InstallationDate: Installed on 2016-11-03 (146 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=9a004175-205d-430e-bd14-8d796f0d18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Wed Mar 29 14:03:29 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677125] Re: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode")
I'm not using the nvidia driver, I'm testing the built-in open source drivers :) -- 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/1677125 Title: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode") Status in xorg package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: zesty can't get to the login screen when a Geforce GT210 card is installed I just get an unclickable dialog "The system is running in low- graphics mode" and stuck. Although if I VT switch and log in by SSH I find mir-demos all run nicely. So this is just a problem with Xorg/lightdm. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Mar 29 14:08:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1313] InstallationDate: Installed on 2016-11-03 (146 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=9a004175-205d-430e-bd14-8d796f0d18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Wed Mar 29 14:03:29 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)
This is the traceback from the logs in 16.04: apt.systemd.daily[957]: Traceback (most recent call last): apt.systemd.daily[957]: File "/usr/bin/unattended-upgrade", line 1473, in apt.systemd.daily[957]: main(options) apt.systemd.daily[957]: File "/usr/bin/unattended-upgrade", line 1411, in main apt.systemd.daily[957]: log_content = get_dpkg_log_content(logfile_dpkg, install_start_time) apt.systemd.daily[957]: File "/usr/bin/unattended-upgrade", line 1079, in get_dpkg_log_content apt.systemd.daily[957]: for line in fp.readlines(): apt.systemd.daily[957]: File "/usr/lib/python3.5/codecs.py", line 321, in decode apt.systemd.daily[957]: (result, consumed) = self._buffer_decode(data, self.errors, final) apt.systemd.daily[957]: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xfc in position 758: invalid start byte Could it be that dpkg logs according to locale settings? These are the ones on this host: LANG=de_DE LANGUAGE=de_DE: LC_CTYPE=de_DE.UTF-8 LC_NUMERIC="de_DE" LC_TIME="de_DE" LC_COLLATE="de_DE" LC_MONETARY="de_DE" LC_MESSAGES="de_DE" LC_PAPER="de_DE" LC_NAME="de_DE" LC_ADDRESS="de_DE" LC_TELEPHONE="de_DE" LC_MEASUREMENT="de_DE" LC_IDENTIFICATION="de_DE" LC_ALL= -- 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/1554365 Title: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128) Status in unattended-upgrades package in Ubuntu: New Bug description: I got this in the mail: From: Cron Daemon To: root@... Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET) /etc/cron.daily/apt: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1255, in main(options) File "/usr/bin/unattended-upgrade", line 1205, in main pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg) File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail body += fp.read() File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128) According to /var/log/apt/history.log.1.gz, the packages upgraded that day were Start-Date: 2016-02-25 02:06:22 Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17) End-Date: 2016-02-25 02:06:36 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.4 Uname: Linux 2.6.32-042stab108.8 x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue Mar 8 08:26:05 2016 PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=lt_LT.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677125] Re: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode")
Actually IIRC the exact same error happened last time I plugged in a radeon card too. -- 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/1677125 Title: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode") Status in xorg package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: zesty can't get to the login screen when a Geforce GT210 card is installed I just get an unclickable dialog "The system is running in low- graphics mode" and stuck. Although if I VT switch and log in by SSH I find mir-demos all run nicely. So this is just a problem with Xorg/lightdm. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Mar 29 14:08:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1313] InstallationDate: Installed on 2016-11-03 (146 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=9a004175-205d-430e-bd14-8d796f0d18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Wed Mar 29 14:03:29 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554365] Re: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128)
This still exists in 16.04 and is hitting uns every day. -- 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/1554365 Title: UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128) Status in unattended-upgrades package in Ubuntu: New Bug description: I got this in the mail: From: Cron Daemon To: root@... Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) Date: Thu, 25 Feb 2016 02:11:47 +0200 (EET) /etc/cron.daily/apt: Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1255, in main(options) File "/usr/bin/unattended-upgrade", line 1205, in main pkgs, pkg_install_success, pkgs_kept_back, mem_log, logfile_dpkg) File "/usr/bin/unattended-upgrade", line 752, in send_summary_mail body += fp.read() File "/usr/lib/python3.4/encodings/ascii.py", line 26, in decode return codecs.ascii_decode(input, self.errors)[0] UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 2886: ordinal not in range(128) According to /var/log/apt/history.log.1.gz, the packages upgraded that day were Start-Date: 2016-02-25 02:06:22 Upgrade: libgnutls-openssl27:amd64 (2.12.23-12ubuntu2.4, 2.12.23-12ubuntu2.5), libssl1.0.0:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17), libvirt0:amd64 (1.2.2-0ubuntu13.1.16, 1.2.2-0ubuntu13.1.17), libssl-dev:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17), ca-certificates:amd64 (20141019ubuntu0.14.04.1, 20160104ubuntu0.14.04.1), libgnutls26:amd64 (2.12.23-12ubuntu2.4, 2.12.23-12ubuntu2.5), libssl-doc:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17), openssl:amd64 (1.0.1f-1ubuntu2.16, 1.0.1f-1ubuntu2.17) End-Date: 2016-02-25 02:06:36 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.4 Uname: Linux 2.6.32-042stab108.8 x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Tue Mar 8 08:26:05 2016 PackageArchitecture: all ProcEnviron: LC_CTYPE=lt_LT.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=lt_LT.UTF-8 SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to trusty on 2016-02-06 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554365/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677125] [NEW] zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode")
Public bug reported: zesty can't get to the login screen when a Geforce GT210 card is installed I just get an unclickable dialog "The system is running in low-graphics mode" and stuck. Although if I VT switch and log in by SSH I find mir-demos all run nicely. So this is just a problem with Xorg/lightdm. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Mar 29 14:08:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1313] InstallationDate: Installed on 2016-11-03 (146 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=9a004175-205d-430e-bd14-8d796f0d18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTB6AUS:bd08/02/2015:svnLENOVO:pn30AJS05700:pvrThinkStationP300:rvnLENOVO:rnSHARKBAY:rvrSDK0E50519PRO:cvnToBeFilledByO.E.M.:ct7:cvrToBeFilledByO.E.M.: dmi.product.name: 30AJS05700 dmi.product.version: ThinkStation P300 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.75-2 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1 xserver.bootTime: Wed Mar 29 14:03:29 2017 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-1ubuntu9 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu zesty ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1677125 Title: zesty can't get to the login screen when a Geforce GT210 card is installed ("The system is running in low-graphics mode") Status in xorg package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: zesty can't get to the login screen when a Geforce GT210 card is installed I just get an unclickable dialog "The system is running in low- graphics mode" and stuck. Although if I VT switch and log in by SSH I find mir-demos all run nicely. So this is just a problem with Xorg/lightdm. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Mar 29 14:08:04 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. GT218 [GeForce 210] [3842:1313] InstallationDate: Installed on 2016-11-03 (146 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161102) MachineType: LENOVO 30AJS05700 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=9a004175-205d-430e-bd14-8d796f0d18e5 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2015 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTB6AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: SDK0E50519 PRO dmi.chassis.type: 7 dmi.chassis.vendor: To Be Filled By O.E.M
[Touch-packages] [Bug 1676912] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1676912 Title: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676912] Re: Suspend - Freezing of tasks failed
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676912 Title: Suspend - Freezing of tasks failed Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Recently I replaced Ubuntu 16.04 on my Lenovo Yoga 3 11 with Ubuntu Gnome 17.04 and since then sometimes my Laptop won't suspend when I close the lid. The power led does not blink like it is supposed to do and when I open the Laptop the lockscreen appears but freezes after a short time, followed by a blackscreen until eventually it reappears and allows me to unlock it. After that certain application can not be started anymore and would freeze if they were running before. These include Chrome, Gedit and Gnome System Monitor for example. Also my Laptop will not connect to my WLAN until I restart it. In syslog I found the line: "Freezing of tasks failed after 20.005 seconds (18 tasks refusing to freeze, wq_busy=0):" According to syslog network-nanaeger whoopsie cups-browsed wpa-supplicant geoclue packagekitd several evolution-related processes goa-daemon gnome-software geary dropbox deja-dup-monitor are responsible. I tried disabling some of them, but it did not solve the problem. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-19 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Mar 28 16:27:34 2017 InstallationDate: Installed on 2017-03-24 (3 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) MachineType: LENOVO 80J8 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic.efi.signed root=UUID=8c63f102-527f-412a-bafe-7b9075ea6b56 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: LENOVO dmi.bios.version: B8CN31WW(V2.09) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Paganini dmi.board.vendor: LENOVO dmi.board.version: 31900058 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 3 11 dmi.modalias: dmi:bvnLENOVO:bvrB8CN31WW(V2.09):bd07/15/2015:svnLENOVO:pn80J8:pvrLenovoYoga311:rvnLENOVO:rnPaganini:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga311: dmi.product.name: 80J8 dmi.product.version: Lenovo Yoga 3 11 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend
** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. - --- + + I'm currently testing Kernel 4.8 from the mainline ppa because of this + other suspend resume bug, that appeared only with 17.04: + + https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 + + --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676918] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1676918/+attachment/4849418/+files/JournalErrors.txt -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend
apport information ** Tags added: apport-collected wayland-session zesty ** Description changed: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. + --- + ApportVersion: 2.20.4-0ubuntu2 + Architecture: amd64 + CurrentDesktop: GNOME + DistroRelease: Ubuntu 17.04 + InstallationDate: Installed on 2017-03-24 (4 days ago) + InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) + Package: systemd 232-19 + PackageArchitecture: amd64 + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + Tags: zesty wayland-session + Uname: Linux 4.8.17-040817-generic x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1676918/+attachment/4849417/+files/Dependencies.txt -- 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/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. I'm currently testing Kernel 4.8 from the mainline ppa because of this other suspend resume bug, that appeared only with 17.04: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1676912 --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-03-24 (4 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) Package: systemd 232-19 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash Tags: zesty wayland-session Uname: Linux 4.8.17-040817-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677050] Re: Youtube video will not run
15.04 is long obsolete (support ended over a year ago), so there's probably no flash player updates to it anymore. Upgrade or reinstall. not an X bug anyway ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1677050 Title: Youtube video will not run Status in xorg package in Ubuntu: Invalid Bug description: When I first set up ubuntu I was able to look at youtube videos, but then they just stopped running. I have no real idea why. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-82.90-generic 3.19.8-ckt22 Uname: Linux 3.19.0-82-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 28 16:44:30 2017 DistUpgraded: 2017-02-13 13:49:16,446 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a5e] InstallationDate: Installed on 2015-12-03 (481 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion GC670AA-ABA a6120n ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-82-generic root=UUID=38cc240f-f1a8-40ed-98a0-6c59680dea14 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2017-02-13 (43 days ago) dmi.bios.date: 06/07/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.20 dmi.board.name: Leonite2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 6.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.20:bd06/07/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC670AA-ABA a6120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Mar 28 15:50:33 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputGenPS/2 Genius Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 27137 vendor VSC xserver.version: 2:1.17.1-0ubuntu3.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1677050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676918] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1676918 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676918] Re: blackscreen when trying to resume from suspend
** Package changed: ubuntu => linux (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1676918 Title: blackscreen when trying to resume from suspend Status in gnome-power-manager package in Ubuntu: New Status in linux package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: When trying to resume after suspending my Lenovo Yoga 3 11, sometimes the screen remains black. The power LED switches from blinking to continuous light like it should but nothing else happens. The system does not react to anything. I tried to find something in the logs, but at least kern.log syslog and xorg.log never have any entries from this event. This problem appeared with Ubuntu 16.04 and 17.04 with Xorg and Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1676918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677117] [NEW] package libperl5.22 5.22.2-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches ver
Public bug reported: attempted to instal hP scanner ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 28 21:34:35 2017 ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist InstallationDate: Installed on 2017-03-19 (9 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1677117 Title: package libperl5.22 5.22.2-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist Status in perl package in Ubuntu: New Bug description: attempted to instal hP scanner ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libperl5.22 5.22.2-3 ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 28 21:34:35 2017 ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist InstallationDate: Installed on 2017-03-19 (9 days ago) InstallationMedia: Lubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: perl Title: package libperl5.22 5.22.2-3 failed to install/upgrade: Versuch, gemeinsam benutztes »/usr/share/doc/libperl5.22/changelog.Debian.gz« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libperl5.22:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1677117/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers
Marking the SRU as verification-done. I've also confirmed that the SRU when installed outside of a container doesn't skip the device creation code and so doesn't regress it's usual behavior in that regard. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Committed Status in makedev source package in Trusty: Fix Committed Status in makedev source package in Xenial: Fix Committed Status in makedev source package in Yakkety: Fix Committed Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers
root@makedev-17-04:~# apt install makedev Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: makedev 0 upgraded, 1 newly installed, 0 to remove and 23 not upgraded. Need to get 24.4 kB of archives. After this operation, 98.3 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu zesty/universe amd64 makedev all 2.3.1-93ubuntu2 [24.4 kB] Fetched 24.4 kB in 0s (91.9 kB/s) Selecting previously unselected package makedev. (Reading database ... 13236 files and directories currently installed.) Preparing to unpack .../makedev_2.3.1-93ubuntu2_all.deb ... Unpacking makedev (2.3.1-93ubuntu2) ... Setting up makedev (2.3.1-93ubuntu2) ... LXC container detected, aborting due to LXC managed /dev. root@makedev-17-04:~# Ubuntu 17.04 too. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Committed Status in makedev source package in Trusty: Fix Committed Status in makedev source package in Xenial: Fix Committed Status in makedev source package in Yakkety: Fix Committed Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers
root@makedev-16-10:~# apt install makedev Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: makedev 0 upgraded, 1 newly installed, 0 to remove and 15 not upgraded. Need to get 24.4 kB of archives. After this operation, 98.3 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu yakkety-proposed/universe amd64 makedev all 2.3.1-93ubuntu2~ubuntu16.10.1 [24.4 kB] Fetched 24.4 kB in 0s (56.8 kB/s) Selecting previously unselected package makedev. (Reading database ... 13163 files and directories currently installed.) Preparing to unpack .../makedev_2.3.1-93ubuntu2~ubuntu16.10.1_all.deb ... Unpacking makedev (2.3.1-93ubuntu2~ubuntu16.10.1) ... Setting up makedev (2.3.1-93ubuntu2~ubuntu16.10.1) ... LXC container detected, aborting due to LXC managed /dev. root@makedev-16-10:~# Ubuntu 16.10 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Committed Status in makedev source package in Trusty: Fix Committed Status in makedev source package in Xenial: Fix Committed Status in makedev source package in Yakkety: Fix Committed Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers
root@makedev-14-04:~# apt install makedev Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: makedev 1 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. Need to get 24.5 kB of archives. After this operation, 1024 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main makedev all 2.3.1-93ubuntu2~ubuntu14.04.1 [24.5 kB] Fetched 24.5 kB in 0s (66.7 kB/s) (Reading database ... 14748 files and directories currently installed.) Preparing to unpack .../makedev_2.3.1-93ubuntu2~ubuntu14.04.1_all.deb ... Unpacking makedev (2.3.1-93ubuntu2~ubuntu14.04.1) over (2.3.1-93ubuntu1) ... Setting up makedev (2.3.1-93ubuntu2~ubuntu14.04.1) ... LXC container detected, aborting due to LXC managed /dev. root@makedev-14-04:~# Ubuntu 14.04 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Committed Status in makedev source package in Trusty: Fix Committed Status in makedev source package in Xenial: Fix Committed Status in makedev source package in Yakkety: Fix Committed Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers
root@makedev-16-04:~# apt install makedev Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: makedev 1 upgraded, 0 newly installed, 0 to remove and 12 not upgraded. Need to get 24.4 kB of archives. After this operation, 29.7 kB disk space will be freed. Get:1 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 makedev all 2.3.1-93ubuntu2~ubuntu16.04.1 [24.4 kB] Fetched 24.4 kB in 0s (55.5 kB/s) (Reading database ... 13025 files and directories currently installed.) Preparing to unpack .../makedev_2.3.1-93ubuntu2~ubuntu16.04.1_all.deb ... Unpacking makedev (2.3.1-93ubuntu2~ubuntu16.04.1) over (2.3.1-93ubuntu1) ... Setting up makedev (2.3.1-93ubuntu2~ubuntu16.04.1) ... LXC container detected, aborting due to LXC managed /dev. root@makedev-16-04:~# Ubuntu 16.04 too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Committed Status in makedev source package in Trusty: Fix Committed Status in makedev source package in Xenial: Fix Committed Status in makedev source package in Yakkety: Fix Committed Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675163] Re: Don't attempt to create devices in LXC containers
root@makedev-12-04:~# apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: makedev 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 27.7 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue [Y/n]? Get:1 http://archive.ubuntu.com/ubuntu/ precise-proposed/main makedev all 2.3.1-89ubuntu3 [27.7 kB] Fetched 27.7 kB in 0s (93.2 kB/s) (Reading database ... 12624 files and directories currently installed.) Preparing to replace makedev 2.3.1-89ubuntu2 (using .../makedev_2.3.1-89ubuntu3_all.deb) ... Unpacking replacement makedev ... Setting up makedev (2.3.1-89ubuntu3) ... LXC container detected, aborting due to LXC managed /dev. root@makedev-12-04:~# So Ubuntu 12.04 looks good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to makedev in Ubuntu. https://bugs.launchpad.net/bugs/1675163 Title: Don't attempt to create devices in LXC containers Status in makedev package in Ubuntu: Fix Released Status in makedev source package in Precise: Fix Committed Status in makedev source package in Trusty: Fix Committed Status in makedev source package in Xenial: Fix Committed Status in makedev source package in Yakkety: Fix Committed Status in makedev source package in Zesty: Fix Released Bug description: Right now the "makedev" postinst script will attempt to create a number of devices in /dev, failing the package upgrade should any of those mknod calls fail. LXC containers, especially unprivileged ones do not allow the use of mknod, making it impossible to upgrade makedev in those containers and preventing Ubuntu release upgrades. The fix is quite simple, detect that we are running in an LXC container and skip the rest of the postinst script as is done in a number of other cases. = SRU == Rationale This issue prevents release to release upgrades in unprivileged LXC containers when makedev is part of the upgraded set. This is currently visible when upgrading from Ubuntu 12.04 to Ubuntu 14.04. == Testcase Install the new package in an unprivileged container. With LXD, simply use "lxc launch ubuntu: test" to create the container. Prior to this fix, the upgrade will fail on some mknod errors, after it, it'll go on after printing a message indicating that LXC was detected. == Regression potential The detection logic is based on PID 1's environment containing a container=lxc entry. If a non-LXC system somehow had that set, it'd lead to the makedev upgrade no longer creating extra devices. This is unlikely to really matter though since the system is clearly already functioning properly at that point. Similarly, some privileged LXC containers can be configured in a way where mknod is possible, this update will still disable the postinst for those cases as short of attempting every mknod ahead of time, there is no reliable way to detect any seccomp or apparmor policy in play. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedev/+bug/1675163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585295] Re: package openssh-client 1:7.2p2-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
[Expired for openssh (Ubuntu) because there has been no activity for 60 days.] ** Changed in: openssh (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1585295 Title: package openssh-client 1:7.2p2-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in openssh package in Ubuntu: Expired Bug description: os updates failed ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-client 1:7.2p2-4 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Tue May 24 19:54:34 2016 DuplicateSignature: Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package openssh-client (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-12-13 (163 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:7.2p2-4 SSHClientVersion: OpenSSH_7.2p2 Ubuntu-4, OpenSSL 1.0.2g-fips 1 Mar 2016 SourcePackage: openssh Title: package openssh-client 1:7.2p2-4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to xenial on 2016-04-23 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1585295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1655166] Re: [PageStack] Inactive pages should not receive keyboard events
[Expired for ubuntu-ui-toolkit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1655166 Title: [PageStack] Inactive pages should not receive keyboard events Status in ubuntu-ui-toolkit package in Ubuntu: Expired Bug description: I have a page that handles key events like this: Keys.onPressed: { do_something } And at some point I push to a PageStack another page which is supposed to handle keyboard events too, but instead, the page underneath continue to receive keyboard events. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1655166/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1646525] Re: FAIL! : components::CrossFadeImage::test_fade(row 0) 'wait for signal statusChanged' returned FALSE. ()
[Expired for ubuntu-ui-toolkit (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1646525 Title: FAIL! : components::CrossFadeImage::test_fade(row 0) 'wait for signal statusChanged' returned FALSE. () Status in ubuntu-ui-toolkit package in Ubuntu: Expired Bug description: Failure on CI. See https://jenkins.ubuntu.com/ubuntu-sdk/job/ubuntu- ui-toolkit-ci-amd64-devel/1364/consoleFull Blocks landing https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit /examples-depend-models/+merge/312256 to staging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1646525/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677115] Re: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676881 *** https://bugs.launchpad.net/bugs/1676881 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1676881, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1676881 package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 -- 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/1677115 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: whenever i boot up my laptop, after login, a window pops up saying system failed : report it.Thats it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.8.0-44.47~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 23:36:16 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-25 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1657110] Re: webbrowser crashes on startup.. hybris linker for android SDK version 19
[Expired for webbrowser-app (Ubuntu) because there has been no activity for 60 days.] ** Changed in: webbrowser-app (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1657110 Title: webbrowser crashes on startup.. hybris linker for android SDK version 19 Status in webbrowser-app package in Ubuntu: Expired Bug description: getting following error in logs ubuntu touch loaded on Nexus 5 ERROR: Failed to load hybris linker for Android SDK version 19 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1657110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677115] [NEW] package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676881 *** https://bugs.launchpad.net/bugs/1676881 Public bug reported: whenever i boot up my laptop, after login, a window pops up saying system failed : report it.Thats it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.8.0-44.47~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 23:36:16 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-25 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1677115 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: whenever i boot up my laptop, after login, a window pops up saying system failed : report it.Thats it ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.8.0-44.47~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 23:36:16 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-25 (3 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1576341] Re: systemd in degraded state on startup in LXD containers
Thanks, Nish. My thoughts: 1.a sounds good 1.b i'd like another way to do that, but not sure what a better way would be. 1.c does lvm also fail in privileged containers? I can see no use to running it (for now) in an unprivileged container, so the same solution as 1.a seems reasonable. 1.d CAP_ADMIN_READ is not a real capability. So if 1.d is fixed by that, then something else is wrong. -- 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/1576341 Title: systemd in degraded state on startup in LXD containers Status in lvm2 package in Ubuntu: Confirmed Status in lxd package in Ubuntu: Invalid Status in open-iscsi package in Ubuntu: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: The ubuntu:xenial image shows 'degraded' state in lxd on initial boot. $ lxc launch xenial x1 $ sleep 10 $ lxc file pull x1/etc/cloud/build.info - build_name: server serial: 20160420-145324 $ lxc exec x1 systemctl is-system-running degraded $ lxc exec x1 -- systemctl --state=failed UNIT LOAD ACTIVE SUBDESCRIPTION ● dev-hugepages.mount loaded failed failed Huge Pages File System ● iscsid.serviceloaded failed failed iSCSI initiator daemon (iscsid) ● open-iscsi.serviceloaded failed failed Login to default iSCSI targets ● systemd-remount-fs.serviceloaded failed failed Remount Root and Kernel File Systems ● systemd-sysctl.serviceloaded failed failed Apply Kernel Variables ● lvm2-lvmetad.socket loaded failed failed LVM2 metadata daemon socket ● systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB= The low-level unit activation state, values depend on unit type. 7 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: open-iscsi 2.0.873+git0.3b4b4500-14ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu Apr 28 17:28:04 2016 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) SourcePackage: open-iscsi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1576341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671991] Re: systemctl rescue leaves system inaccessible unless run from within active desktop session
Debian stretch has the opposite issue: there, rescue only works if no desktop session is active. Otherwise, whether systemctl is run from within that session or not, the console is left completely unusable; not even Ctrl+Alt+Del works. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858162 exists for that, but the Xenial issue is completely different: the console never becomes unresponsive. Instead, the system is stuck in some intermediate state where the normal getty is stlil alive, but login is not allowed, and the actual rescue prompt is never reached. ** Bug watch added: Debian Bug tracker #858162 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858162 -- 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/1671991 Title: systemctl rescue leaves system inaccessible unless run from within active desktop session Status in systemd package in Ubuntu: New Bug description: I don't think it's just me, as I'm able to reproduce this on 2 physical systems as well as a vanilla qemu/kvm instance, immediately after fresh installs from both ubuntu-16.04.1-desktop-amd64.iso and ubuntu-16.04.2-desktop-amd64.iso When I run 'sudo init 1' or 'sudo telinit 1' from any virtual console, the system never gets to single-user mode. Instead, I am presented with a non-functioning login prompt and no way to actually interact with the machine except Ctrl-Alt-Del, which luckily still works. The login prompts look normal, but only appear on two virtual consoles: tty1 always, plus the one I was using (if it wasn't tty1). All others are blank. Typing my username results in the message "System is going down," instead of a password prompt. After a couple of minutes, it will clear the screen and draw a fresh prompt, with the same results; otherwise, nothing changes until I give the three- fingered salute to reboot. I've attached a screenshot from the VM. This happens regardless of whether I first log out of my desktop, stop the lightdm service entirely, or neither. The truly bizarre part is that if I enter the command from inside a gnome-terminal running on the desktop, it works as expected. It's a little unbelievable, but seems to be reliably reproduceable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: init 1.29ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 10 22:10:34 2017 InstallationDate: Installed on 2017-03-11 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671991] Re: systemctl rescue leaves system inaccessible unless run from within active desktop session
** Summary changed: - init 1 locks you out of system immediately when run from virtual console + systemctl rescue leaves system inaccessible unless run from within active desktop session -- 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/1671991 Title: systemctl rescue leaves system inaccessible unless run from within active desktop session Status in systemd package in Ubuntu: New Bug description: I don't think it's just me, as I'm able to reproduce this on 2 physical systems as well as a vanilla qemu/kvm instance, immediately after fresh installs from both ubuntu-16.04.1-desktop-amd64.iso and ubuntu-16.04.2-desktop-amd64.iso When I run 'sudo init 1' or 'sudo telinit 1' from any virtual console, the system never gets to single-user mode. Instead, I am presented with a non-functioning login prompt and no way to actually interact with the machine except Ctrl-Alt-Del, which luckily still works. The login prompts look normal, but only appear on two virtual consoles: tty1 always, plus the one I was using (if it wasn't tty1). All others are blank. Typing my username results in the message "System is going down," instead of a password prompt. After a couple of minutes, it will clear the screen and draw a fresh prompt, with the same results; otherwise, nothing changes until I give the three- fingered salute to reboot. I've attached a screenshot from the VM. This happens regardless of whether I first log out of my desktop, stop the lightdm service entirely, or neither. The truly bizarre part is that if I enter the command from inside a gnome-terminal running on the desktop, it works as expected. It's a little unbelievable, but seems to be reliably reproduceable. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: init 1.29ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11 Uname: Linux 4.8.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 10 22:10:34 2017 InstallationDate: Installed on 2017-03-11 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: init-system-helpers UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671991/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442505] Re: /usr/sbin/unity-system-compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor:
Incomplete. Crash last seen in 15.10 ** Changed in: mir Status: Confirmed => Incomplete ** Changed in: mir (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity-system-compositor (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1442505 Title: /usr/sbin/unity-system- compositor:11:mir::frontend::SessionMediator::create_screencast:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch:mir::frontend::detail::SocketConnection::on_new_message:mir::frontend::detail::SocketConnection::on_read_size Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity-system-compositor package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/f97c1aceb8c847481ec0aed856e113739a423e7b contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1442505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442508] Re: /usr/sbin/unity-system-compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::Protob
Incomplete. Crash last seen in 15.10 ** Changed in: mir Status: Confirmed => Incomplete ** Changed in: mir (Ubuntu) Status: Confirmed => Incomplete ** Changed in: unity-system-compositor (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1442508 Title: /usr/sbin/unity-system- compositor:11:Add:add_surface_pixel_format:mir::frontend::SessionMediator::connect:mir::frontend::detail::invoke:mir::frontend::detail::ProtobufMessageProcessor::dispatch Status in Mir: Incomplete Status in mir package in Ubuntu: Incomplete Status in unity-system-compositor package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+15.04.20150227-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/009ff218f16e78b57614e9a3a0e4ddae9cb0750a contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1442508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1479030] Re: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish
Incomplete. Crash last seen in 16.10 ** Changed in: unity-system-compositor Status: Confirmed => Incomplete ** Changed in: unity-system-compositor (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1479030 Title: unity-system-compositor crashes with SIGABRT in google::protobuf::internal::LogMessage::Finish Status in Unity System Compositor: Incomplete Status in unity-system-compositor package in Ubuntu: Incomplete Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with version 0.0.5+15.10.20150722-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/17e8c095201d404cdb3a785f4870e95f200fea1d contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1479030/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566172] Re: [SUGGESTION] [OSK] Use the space bar for moving the text cursor
** Summary changed: - [SUGGESTION] Use the space bar for moving the text cursor + [SUGGESTION] [OSK] Use the space bar for moving the text cursor ** Tags added: osk unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1566172 Title: [SUGGESTION] [OSK] Use the space bar for moving the text cursor Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-keyboard package in Ubuntu: Fix Committed Bug description: I have an idea which maybe considered to be implemented. What if we use the space bar for moving the text cursor horizontally or even vertically. Currently, moving the cursor is quite hard and inaccurate. Space bar is quite big and makes it a good place to swipe to move the cursor. With this approach, we're not using more space and instead use a big part of the keyboard that is only there mostly for inserting spaces. The sensitivity is critical though because you don't want unintended movement of the cursor but I think it's very much doable. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1536662] Re: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random
** Changed in: mir/0.21 Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1536662 Title: [regression] Black screen: Mir hangs and then crashes on startup/login due to reading from /dev/random Status in Mir: Fix Released Status in Mir 0.19 series: Won't Fix Status in Mir 0.20 series: Won't Fix Status in Mir 0.21 series: Won't Fix Status in Unity System Compositor: Fix Released Status in mir package in Ubuntu: Fix Released Status in unity-system-compositor package in Ubuntu: Fix Released Bug description: cookie_factory attempts to read data from /dev/random at boot, and blocks until it has enough random data or timesout after 30 seconds. How I can reproduce 1. Run the Unity8 greeter as a mir server 2. Reboot Expected behavior: Greeter is displayed as mir && USC run happily Actual behavior: Mir throws an exception after 30 seconds Work-around: Before logging in, move the mouse around lots, for at least 20 seconds. And after logging in, while you're looking at a black screen, move the mouse around furiously. This will populate the kernel entropy pool sufficiently to avoid the hang and crash. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1536662/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1613601] Re: [MIR] unity-system-compositor
** Tags added: unity8-desktop -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1613601 Title: [MIR] unity-system-compositor Status in unity-system-compositor package in Ubuntu: Fix Released Bug description: Note that a much older version of unity-system-compositor had been previously accepted into main: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1203588 [Availability] * Available in universe [Rationale] * This package is the system compositor for our convergence effort * Used by default on phablet images and in the Unity8 session on the desktop [Security] * No known security issues at this time * A security review is recommended. The package had been reviewed in the past by the security team for use on the phone, but it has changed significantly since then. [Quality assurance] * This package has unit and integration tests that run with each package build * CI is used during development [Dependencies] * All dependencies are in main * It 'Suggests' repowerd which already has a MIR: https://bugs.launchpad.net/ubuntu/+source/repowerd/+bug/1613585 [Standards compliance] * Follows FHS and Debian Policy. * This package uses cmake. [Maintenance] * This package is maintained by Canonical and actively in use on the phone images * mir-development-team/unity-system-compositor-team are subscribed to project and ubuntu package bugs respectively (The unity-system-compositor developers are the Mir developers) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-system-compositor/+bug/1613601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668409] Re: Firefox fails to launch in unity8 zesty
or "to not try to use X11 when it's using pure GTK". As far as Mir is concerned X11 and GTK are alternatives to each other. Given the choice we should choose pure GTK. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1668409 Title: Firefox fails to launch in unity8 zesty Status in Canonical System Image: Incomplete Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: daily iso of zesty exploring clean u8 to repro 1) open app drawer 2) find ff icon, click to launch journal shows the following http://pastebin.ubuntu.com/24080554/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668409] Re: Firefox fails to launch in unity8 zesty
or "try to use X11 when it's using pure GTK" :) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1668409 Title: Firefox fails to launch in unity8 zesty Status in Canonical System Image: Incomplete Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: daily iso of zesty exploring clean u8 to repro 1) open app drawer 2) find ff icon, click to launch journal shows the following http://pastebin.ubuntu.com/24080554/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673550] Re: system-settings not remembering previous size on unity8
** Tags added: unity8-desktop -- 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/1673550 Title: system-settings not remembering previous size on unity8 Status in Canonical System Image: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: running u8 desktop session Steps to reproduce: - open u-s-s - resize the window to 2 column mode - close the app with X from window control - restart the app Expected results: - u-s-s should open at the size it was last closed at Actutual results: - u-s-s window is smaller only showing one column This may be related to limiting the max size which we used to have? I think we should remove all max sizing restrictions on the app, and bring back the maximize button which is not displayed either. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676881] Re: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1676881 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: when i update ubuntu 16.04, there are error when download. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 21:39:48 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-05 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676881/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677085] Re: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676881 *** https://bugs.launchpad.net/bugs/1676881 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1676881, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1676881 package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 -- 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/1677085 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I was just booting up and got the error... and the options to report a bug... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 08:56:36 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676860] Re: launcher menu is listing closed windows
** Tags added: unity8-desktop -- 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/1676860 Title: launcher menu is listing closed windows Status in Canonical System Image: New Status in unity8 package in Ubuntu: New Bug description: Ubuntu 17.04 Unity8 + silo 2626 launcher menu is listing closed windows, mostly with gtk3 apps (without Xmir) and mostly the About window (see screenshot). launch sol, eog, files (without mir), from menu Help\About to open the about window, close the window, not right click on the apps icon on the launcher, you'll see the About window listed but the window is closed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676854] Re: apps launched from the launcher menu doesn't seem to work
** Tags added: unity8-desktop -- 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/1676854 Title: apps launched from the launcher menu doesn't seem to work Status in Canonical System Image: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: apps launched from the launcher menu doesn't seem to work at least on my pc (ubuntu 17.04 Unity8 + silo 2626) right click on some random app from the launcher, click on the apps name to launch does nothing here To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676850] Re: Distorted menus in a lot of Qt apps
** Summary changed: - distorted context menu in a lot of qt apps + Distorted menus in a lot of Qt apps ** Tags added: unity8-desktop visual-quality ** Summary changed: - Distorted menus in a lot of Qt apps + Distorted menus in a lot of Qt apps under Unity8 -- 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/1676850 Title: Distorted menus in a lot of Qt apps under Unity8 Status in Canonical System Image: New Status in qtmir package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Ubuntu 17.04 Unity8 distorted context menu in a lot of qt apps (see attached screenshots) it happens fairly often and mostly the first time i launch/use the app launch without Xmir qupzilla, kate, kmines and right click on stuff, also try to move the mouse a bit to the left when you click. if i hover the distored menu with the mouse it seems to resize to the proper size To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676879] Re: Broken stack of modal dialogs
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Also affects: miral Importance: Undecided Status: New ** Also affects: miral (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/1676879 Title: Broken stack of modal dialogs Status in Canonical System Image: New Status in MirAL: New Status in miral package in Ubuntu: New Status in qtubuntu package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When multiple modal dialogs are stacked on top of each other, the topmost one is missing the window decoration (see https://imgur.com/0kVtLUB). Furthermore, after closing it, the middle modal dialog is hidden, preventing input from the main window. Launcher pips and context menu suggests the dialog is still there, albeit hidden. Results in a crash of the app after a few seconds. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676879/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677085] [NEW] package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676881 *** https://bugs.launchpad.net/bugs/1676881 Public bug reported: I was just booting up and got the error... and the options to report a bug... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 08:56:36 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cups (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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1677085 Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I was just booting up and got the error... and the options to report a bug... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon (not installed) ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 08:56:36 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon (not installed) failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676878] Re: Not using Ubuntu font family and suru icons in Qt widget apps
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1676878 Title: Not using Ubuntu font family and suru icons in Qt widget apps Status in Canonical System Image: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: Widget apps (as opposed to QML apps using UITK) don't correctly default to the Ubuntu font family or suru icon theme, resulting e.g. in lots of missing toolbar icons in Qt apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676878/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677072] Re: Super shortcuts breaks application keyboard input
Could be related to Mir bug 1536279, which has not been Fix Released yet. ** Tags added: unity8-desktop -- 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/1677072 Title: Super shortcuts breaks application keyboard input Status in unity8 package in Ubuntu: New Bug description: Pressing Super+A results in focus being taken from applications without the release key event being sent for the Super key. This means that when focus is restored to an application it believes that the Super key is permanently being held down unless the user presses it again. The effects of this can be seen in most applications that accept keyboard input, for example in the terminal cursor input stops working instead just inserting A/B/C/D characters, in the webbrowser keyboard shortcuts no longer work, in Kate cursor movement stops working, etc. Steps to reproduce: 1. Run the following QML: import QtQuick 2.4 import Ubuntu.Components 1.3 MainView { property bool superPress: false focus: true Label { anchors.centerIn: parent text: "Super pressed? " + (superPress ? "True" : "False") } Keys.onPressed: { if (event.key == Qt.Key_Super_L) { superPress = true } } Keys.onReleased: { if (event.key == Qt.Key_Super_L) { superPress = false } } } 2. Hold Super+A until the app drawer opens 3. Click on the QML application to restore its focus Expected result: QML application should be showing: "Super pressed? False" Actual result: QML application shows: "Super pressed? True" because the release event was never sent to the application when the application drawer took focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1677072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676931] Re: logs are not included in bugs automatically reported to Ubuntu using apport
** Tags added: unity8-desktop ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => In Progress ** Changed in: canonical-devices-system-image Importance: Undecided => Medium ** Summary changed: - logs are not included in bugs automatically reported to Ubuntu using apport + logs are not included in unity-system-compositor bugs automatically reported to Ubuntu using apport ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Stephen M. Webb (bregma) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1676931 Title: logs are not included in unity-system-compositor bugs automatically reported to Ubuntu using apport Status in Canonical System Image: In Progress Status in Unity System Compositor: In Progress Status in unity-system-compositor package in Ubuntu: In Progress Bug description: When a crash in unity-system-compositor is automatically reported to the Ubuntu bug tracker using the apport tool, additional information should be included to make analysis easier. At the very least, /var/log/lightdm/unity-system-compositor.log should be included. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676547] Re: No network connectivity after upgrade from 16.04 to 16.10
I'm reasonably certain that I can fix this in NM directly; for now I've uploaded a new version of network-manager for yakkety to my PPA (ppa:cyphermox/sru) to do the upgrade testing from Xenial to Yakkety. It involves first making sure xenial is fully updated to network-manager 1.2.6. ** Changed in: ubuntu-release-upgrader (Ubuntu) Milestone: None => ubuntu-17.04 ** Package changed: ubuntu-release-upgrader (Ubuntu) => network-manager (Ubuntu) -- 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/1676547 Title: No network connectivity after upgrade from 16.04 to 16.10 Status in network-manager package in Ubuntu: In Progress Bug description: nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1676547/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661836] Re: supertux 2 can't start with SDL_VIDEODRIVER=mir [Couldn't initialize SDL: Failed to connect to the mir server]
*** This bug is a duplicate of bug 1605478 *** https://bugs.launchpad.net/bugs/1605478 ** This bug has been marked a duplicate of bug 1605478 supertux2 segfaults on native Mir with SDL_VIDEODRIVER=mir trying to call glXQueryVersion -- 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/1661836 Title: supertux 2 can't start with SDL_VIDEODRIVER=mir [Couldn't initialize SDL: Failed to connect to the mir server] Status in Canonical System Image: Incomplete Status in Mir: Invalid Status in libsdl2 package in Ubuntu: Incomplete Status in supertux package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Bug description: 17.04 / unity8 session from what i understand this is an SDL2 app and should work on unity8, it did before $ journalctl --user-unit ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service -- Logs begin at Sat 2017-02-04 14:24:38 EET, end at Sat 2017-02-04 14:55:01 EET. -- Feb 04 14:53:00 pixel-desktop systemd[3969]: Starting ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service... Feb 04 14:53:01 pixel-desktop supertux2[8395]: [2017-02-04 14:53:01.377093] MirConnectionAPI: Caught exception at client library boundary (in mir_connection_release): /build/mir-1Sl_GZ/mir-0.26.0 Feb 04 14:53:01 pixel-desktop supertux2[8395]: Dynamic exception type: boost::exception_detail::clone_impl > Feb 04 14:53:01 pixel-desktop supertux2[8395]: std::exception::what: Failed to send message to server: Broken pipe Feb 04 14:53:01 pixel-desktop supertux2[8395]: [boost::errinfo_errno_*] = 32, "Broken pipe" Feb 04 14:53:01 pixel-desktop supertux2[8395]: [FATAL] /build/supertux-LmXSob/supertux-0.5.1/src/supertux/main.cpp:510 Unexpected exception: Couldn't initialize SDL: Failed to connect to the mir server: Feb 04 14:53:01 pixel-desktop systemd[3969]: ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Main process exited, code=exited, status=1/FAILURE Feb 04 14:53:01 pixel-desktop systemd[3969]: Failed to start ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service. Feb 04 14:53:01 pixel-desktop systemd[3969]: ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Unit entered failed state. Feb 04 14:53:01 pixel-desktop systemd[3969]: ubuntu-app-launch-application-legacy-supertux2-1486212780752430.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677066] Re: Missing dependency on libertine-xmir-tools
Invalid for Xmir. Libertine depends on Xmir and not vice-versa. I've done all my Xmir development without a 'pasted' so that can't be a problem. And not should it be. If it's a requirement for U8 desktop then some part of the U8 desktop should depend on pasted/libertine. ** Summary changed: - [Xmir] Missing dependency on libertine-xmir-tools + Missing dependency on libertine-xmir-tools ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- 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/1677066 Title: Missing dependency on libertine-xmir-tools Status in unity8 package in Ubuntu: New Status in xorg-server package in Ubuntu: Invalid Bug description: XMir applications fail to launch from the unity8 application drawer if pasted (provided by libertine-xmir-tools) isn't installed, so this needs to be added as a dependency (either to the xmir package itself or to unity8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1677066/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676547] [NEW] No network connectivity after upgrade from 16.04 to 16.10
You have been subscribed to a public bug: nplan was installed during the upgrade process but I had no network connectivity after upgrading. Apparently, no package wanted to manage my ethernet connection. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-release-upgrader-core 1:16.10.10 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Mar 27 11:34:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2013-01-16 (1531 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130116) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to yakkety on 2017-03-17 (10 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.update-manager.meta-release: [modified] mtime.conffile..etc.update-manager.meta-release: 2013-10-08T06:39:09.818913 ** Affects: network-manager (Ubuntu) Importance: Critical Assignee: Mathieu Trudel-Lapierre (cyphermox) Status: In Progress ** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial2yakkety yakkety -- No network connectivity after upgrade from 16.04 to 16.10 https://bugs.launchpad.net/bugs/1676547 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1598300] Re: CUPS web interface stops responding after a while
I just ran into this bug today when I went to use the official cups package for the first time. Or at least I'm pretty sure I did. Google landed me here when I went to search for the output of "service cups status", of which my test system's output looks very similar to the output of the person who opened this ticket and the described behavior is identical to what I'm running into. This bug makes the cups package for Ubuntu useless for initial configuration from the comfort of a standard desktop - a common enough scenario, IMO. I just can't believe it's taken almost 9 months to still not have a fix pushed out everywhere, but there you have it. Directly running the command being run by the system service (/usr/sbin/cupsd -l) has identical behavior - the software self-terminates after a few minutes of inactivity. I'm testing the -f option and I'm hoping that it will resolve the issue for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1598300 Title: CUPS web interface stops responding after a while Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Triaged Bug description: after 6 minutes or so, cups is not responding. it do not produce error on the log, just stop working, worse, it exit with 0 ⌌—⌍ |root@cupsmachine :~# systemctl status cups | |● cups.service - CUPS Scheduler | | Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)| | Active: inactive (dead) since ven. 2016-07-01 10:31:32 TAHT; 2min 16s ago | | Docs: man:cupsd(8) | | Process: 28686 ExecStart=/usr/sbin/cupsd -l (code=exited, status=0/SUCCESS)| | Main PID: 28686 (code=exited, status=0/SUCCESS) | | | |juil. 01 10:30:01 appli-client systemd[1]: Started CUPS Scheduler. | ⌎—⌏ I got to launch it again, so I have finish with a cron job like */10 * * * * systemctl status cups.service|grep -q 'inactive (dead)' && systemctl start cups but it is a dirty solution. I have no idea of what make it stop. NB: I have seen problems related to apparmor, this machine has no apparmor package. [Impact] If you want to use the CUPS web interface in Xenial and therefore set "WebInterface Yes" in /etc/cups/cupsd.conf, CUPS could auto-shutdown when it is idle and then an attempt to access http://localhost:631/ via a web browser fails. People get confused as other access to CUPS [Testcase] Take a CUPS setup on Xenial with no shared print queues and CUPS only listening on the domain socket. Activate the web interface via cupsctl WebInterface=Yes Now you are able to access the web interface via http://localhost:631/. Wait for some minutes without accessing CUPS until the CUPS daemon shuts down automatically. Try to open the web interface again and it will not work. With the fixed CUPS package CUPS will not auto-shutdown when the web interface is activated. [Regression Potential] Low, as we are removing a simple distro patch to get back to the original, upstream behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1598300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677072] Re: Super shortcuts breaks application keyboard input
The same issue can be triggered if you hold the super key to reveal the launcher and then click on an application icon, or if you use any of the super+1/2/3/etc. short cuts to launch an application. ** Summary changed: - Super+A shortcut breaks application keyboard input + Super shortcuts breaks application keyboard input -- 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/1677072 Title: Super shortcuts breaks application keyboard input Status in unity8 package in Ubuntu: New Bug description: Pressing Super+A results in focus being taken from applications without the release key event being sent for the Super key. This means that when focus is restored to an application it believes that the Super key is permanently being held down unless the user presses it again. The effects of this can be seen in most applications that accept keyboard input, for example in the terminal cursor input stops working instead just inserting A/B/C/D characters, in the webbrowser keyboard shortcuts no longer work, in Kate cursor movement stops working, etc. Steps to reproduce: 1. Run the following QML: import QtQuick 2.4 import Ubuntu.Components 1.3 MainView { property bool superPress: false focus: true Label { anchors.centerIn: parent text: "Super pressed? " + (superPress ? "True" : "False") } Keys.onPressed: { if (event.key == Qt.Key_Super_L) { superPress = true } } Keys.onReleased: { if (event.key == Qt.Key_Super_L) { superPress = false } } } 2. Hold Super+A until the app drawer opens 3. Click on the QML application to restore its focus Expected result: QML application should be showing: "Super pressed? False" Actual result: QML application shows: "Super pressed? True" because the release event was never sent to the application when the application drawer took focus. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1677072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677072] [NEW] Super+A shortcut breaks application keyboard input
Public bug reported: Pressing Super+A results in focus being taken from applications without the release key event being sent for the Super key. This means that when focus is restored to an application it believes that the Super key is permanently being held down unless the user presses it again. The effects of this can be seen in most applications that accept keyboard input, for example in the terminal cursor input stops working instead just inserting A/B/C/D characters, in the webbrowser keyboard shortcuts no longer work, in Kate cursor movement stops working, etc. Steps to reproduce: 1. Run the following QML: import QtQuick 2.4 import Ubuntu.Components 1.3 MainView { property bool superPress: false focus: true Label { anchors.centerIn: parent text: "Super pressed? " + (superPress ? "True" : "False") } Keys.onPressed: { if (event.key == Qt.Key_Super_L) { superPress = true } } Keys.onReleased: { if (event.key == Qt.Key_Super_L) { superPress = false } } } 2. Hold Super+A until the app drawer opens 3. Click on the QML application to restore its focus Expected result: QML application should be showing: "Super pressed? False" Actual result: QML application shows: "Super pressed? True" because the release event was never sent to the application when the application drawer took focus. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Description changed: Pressing Super+A results in focus being taken from applications without the release key event being sent for the Super key. This means that when focus is restored to an application it believes that the Super key is permanently being held down unless the user presses it again. The effects of this can be seen in most applications that accept keyboard input, for example in the terminal cursor input stops working instead just inserting A/B/C/D characters, in the webbrowser keyboard shortcuts no longer work, in Kate cursor movement stops working, etc. Steps to reproduce: 1. Run the following QML: import QtQuick 2.4 import Ubuntu.Components 1.3 MainView { - property bool superPress: false - focus: true + property bool superPress: false + focus: true - Label { - anchors.centerIn: parent - text: "Super pressed? " + (superPress ? "True" : "False") - } + Label { + anchors.centerIn: parent + text: "Super pressed? " + (superPress ? "True" : "False") + } - Keys.onPressed: { - if (event.key == Qt.Key_Super_L) { - superPress = true - } - } + Keys.onPressed: { + if (event.key == Qt.Key_Super_L) { + superPress = true + } + } - Keys.onReleased: { - if (event.key == Qt.Key_Super_L) { - superPress = false - } - } + Keys.onReleased: { + if (event.key == Qt.Key_Super_L) { + superPress = false + } + } } 2. Hold Super+A until the app drawer opens - 3. Click on the QML application + 3. Click on the QML application to restore its focus Expected result: QML application should be showing: "Super pressed? False" Actual result: QML application shows: "Super pressed? True" because the release event was never sent to the application when the application drawer took focus. -- 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/1677072 Title: Super+A shortcut breaks application keyboard input Status in unity8 package in Ubuntu: New Bug description: Pressing Super+A results in focus being taken from applications without the release key event being sent for the Super key. This means that when focus is restored to an application it believes that the Super key is permanently being held down unless the user presses it again. The effects of this can be seen in most applications that accept keyboard input, for example in the terminal cursor input stops working instead just inserting A/B/C/D characters, in the webbrowser keyboard shortcuts no longer work, in Kate cursor movement stops working, etc. Steps to reproduce: 1. Run the following QML: import QtQuick 2.4 import Ubuntu.Components 1.3 MainView { property bool superPress: false focus: true Label { anchors.centerIn: parent text: "Super pressed? " + (superPress ? "True" : "False") } Keys.onPressed: { if (event.key == Qt.Key_Super_L) { superPress = true } } Keys.onReleased: { if (event.key == Qt.Key_Super_L) { superPress = false } } } 2. Hold Super+A until the app drawer opens 3. Click on the QML application
[Touch-packages] [Bug 1667352] Re: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync
** Changed in: mir/0.26 Milestone: 0.26.3 => None ** Changed in: mir Milestone: 1.0.0 => None -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/1667352 Title: SDL apps either "Failed to connect to the mir server: ..." or segfault in protobuf via mir_connect_sync Status in Canonical System Image: Fix Released Status in Mir: Invalid Status in Mir 0.26 series: Invalid Status in libsdl2 package in Ubuntu: Invalid Status in protobuf package in Ubuntu: Fix Released Bug description: ubuntu 17.04 unity8, trying to run neverball game Feb 23 17:46:43 pixel-desktop systemd[2629]: Starting ubuntu-app-launch-application-legacy-neverball-1487864803635991.service... Feb 23 17:46:44 pixel-desktop neverball[3591]: Failure to initialize SDL (Failed to connect to the mir server: std::bad_alloc) Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Main process exited, code=exited, status=1/FAI Feb 23 17:46:44 pixel-desktop systemd[2629]: Failed to start ubuntu-app-launch-application-legacy-neverball-1487864803635991.service. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Unit entered failed state. Feb 23 17:46:44 pixel-desktop systemd[2629]: ubuntu-app-launch-application-legacy-neverball-1487864803635991.service: Failed with result 'exit-code'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1667352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677066] [NEW] [Xmir] Missing dependency on libertine-xmir-tools
Public bug reported: XMir applications fail to launch from the unity8 application drawer if pasted (provided by libertine-xmir-tools) isn't installed, so this needs to be added as a dependency (either to the xmir package itself or to unity8). ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Missing dependency on libertine-xmir-tools + [Xmir] Missing dependency on libertine-xmir-tools ** Also affects: xorg-server (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/1677066 Title: [Xmir] Missing dependency on libertine-xmir-tools Status in unity8 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: XMir applications fail to launch from the unity8 application drawer if pasted (provided by libertine-xmir-tools) isn't installed, so this needs to be added as a dependency (either to the xmir package itself or to unity8). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1677066/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673557] Re: /proc/cpuinfo should be collected
Actually given that we already have /proc/cpuinfo when the report is being created we could just collapse that down in python with something like: short_list = [] for item in reversed(report['ProcCpuinfo'].split('\n')): short_list.append(item) if item.startswith('processor\t:'): break short_list = reversed(short_list) report['ShortProcCpuinfo'] = '\n'.join(short_list) This still ends up catching Hardware, Revision, and Serial from arm and will display the greatest processor number instead of 0 which might be nice too. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1673557 Title: /proc/cpuinfo should be collected Status in apport package in Ubuntu: Triaged Status in whoopsie package in Ubuntu: Triaged Bug description: apport does not currently collect data from /proc/cpuinfo and this would be useful to determine how many users can only run the i386 version of Ubuntu. The general Ubuntu hook, possibly add_kernel_info() could be used, should be modified such that the contents of /proc/cpuinfo are gathered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1673557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning
I'm still seeing this on trunk. Mar 28 22:58:05 skylake dhclient[4804]: no link-local IPv6 address for eno1 Mar 28 22:58:05 skylake dhclient[4804]: Mar 28 22:58:05 skylake dhclient[4804]: If you think you have received this message due to a bug rather Mar 28 22:58:05 skylake dhclient[4804]: than a configuration issue please read the section on submitting Mar 28 22:58:05 skylake dhclient[4804]: bugs on either our web page at www.isc.org or in the README file Mar 28 22:58:05 skylake dhclient[4804]: before submitting a bug. These pages explain the proper Mar 28 22:58:05 skylake dhclient[4804]: process and the information we find helpful for debugging.. Mar 28 22:58:05 skylake dhclient[4804]: Mar 28 22:58:05 skylake dhclient[4804]: exiting. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1640147 Title: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning Status in MAAS: Fix Released Status in MAAS 2.1 series: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Bug description: When commissioning, /var/log/maas/rsyslog/ is flooded with the repeated messages below with over 30,000 lines. Nov 8 11:57:54 bunyip dhclient[4734]: no link-local IPv6 address for enp4s0f0 Nov 8 11:57:54 bunyip dhclient[4734]: Nov 8 11:57:54 bunyip dhclient[4734]: If you think you have received this message due to a bug rather Nov 8 11:57:54 bunyip dhclient[4734]: than a configuration issue please read the section on submitting Nov 8 11:57:54 bunyip dhclient[4734]: bugs on either our web page at www.isc.org or in the README file Nov 8 11:57:54 bunyip dhclient[4734]: before submitting a bug. These pages explain the proper Nov 8 11:57:54 bunyip dhclient[4734]: process and the information we find helpful for debugging.. Nov 8 11:57:54 bunyip dhclient[4734]: Nov 8 11:57:54 bunyip dhclient[4734]: exiting. $ wc -l /var/log/maas/rsyslog/bunyip/2016-11-08/messages 39278 /var/log/maas/rsyslog/bunyip/2016-11-08/messages It would be nice to suppress those lines if those could be safely ignored. It would make troubleshooting easier when something wrong happened on commissioning. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1640147] Re: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning
Note, this is NOT a case where IPv6 has been disabled explicitly; this is the case where I have a link-down interface. (`ip link` reports NO- CARRIER.) 3: eno1: mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000 link/ether 0c:c4:7a:c0:31:fa brd ff:ff:ff:ff:ff:ff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1640147 Title: [2.1] rsyslog is flooded with "no link-local IPv6 address for $IFACE" on commissioning Status in MAAS: Fix Released Status in MAAS 2.1 series: Fix Released Status in isc-dhcp package in Ubuntu: Invalid Bug description: When commissioning, /var/log/maas/rsyslog/ is flooded with the repeated messages below with over 30,000 lines. Nov 8 11:57:54 bunyip dhclient[4734]: no link-local IPv6 address for enp4s0f0 Nov 8 11:57:54 bunyip dhclient[4734]: Nov 8 11:57:54 bunyip dhclient[4734]: If you think you have received this message due to a bug rather Nov 8 11:57:54 bunyip dhclient[4734]: than a configuration issue please read the section on submitting Nov 8 11:57:54 bunyip dhclient[4734]: bugs on either our web page at www.isc.org or in the README file Nov 8 11:57:54 bunyip dhclient[4734]: before submitting a bug. These pages explain the proper Nov 8 11:57:54 bunyip dhclient[4734]: process and the information we find helpful for debugging.. Nov 8 11:57:54 bunyip dhclient[4734]: Nov 8 11:57:54 bunyip dhclient[4734]: exiting. $ wc -l /var/log/maas/rsyslog/bunyip/2016-11-08/messages 39278 /var/log/maas/rsyslog/bunyip/2016-11-08/messages It would be nice to suppress those lines if those could be safely ignored. It would make troubleshooting easier when something wrong happened on commissioning. To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1640147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672941] Re: FTBFS with older versions of OpenSSL
** Changed in: cyrus-sasl2 (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1672941 Title: FTBFS with older versions of OpenSSL Status in cyrus-sasl2 package in Ubuntu: Fix Committed Bug description: cyrus-sasl2 currently FTBFS in Zesty because we have an older version of OpenSSL than in Debian (1.0.2 vs 1.1.0). There was a patch upstream to fix this: https://github.com/cyrusimap/cyrus- sasl/commit/ccb394dc857c0f1ef03a6be5011b5aedc1dbf042 debdiff attached. Tested building with pbuilder. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1672941/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677055] [NEW] Lintian fails with "E: libfontconfig1-dev: doc-base-file-references-missing-file fontconfig-devel:16 /usr/share/doc/libfontconfig1-dev/fontconfig-devel/index.html"
Public bug reported: during debuild -us -uc -b ... Now running lintian... W: fontconfig-config: command-with-path-in-maintainer-script postrm:9 /usr/bin/ucf E: libfontconfig1-dev: doc-base-file-references-missing-file fontconfig-devel:16 /usr/share/doc/libfontconfig1-dev/fontconfig-devel/index.html E: fontconfig: malformed-override Override of package-needs-versioned-debhelper-build-depends for package type source (expecting binary) at line 1 W: fontconfig-udeb udeb: package-name-doesnt-match-sonames libfontconfig1 Finished running lintian. Looking in doc/fontconfig-devel it does seem that there's no index.html. Adding an index.html manages to get to the next failure ( doc /fontconfig-user.html ): Ubuntu: yakkety 16.10 fontconfig: 2.11.94-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libfontconfig1 2.11.94-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 28 18:53:10 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (993 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) SourcePackage: fontconfig UpgradeStatus: Upgraded to yakkety on 2016-10-16 (163 days ago) ** Affects: fontconfig (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1677055 Title: Lintian fails with "E: libfontconfig1-dev: doc-base-file-references- missing-file fontconfig-devel:16 /usr/share/doc/libfontconfig1-dev /fontconfig-devel/index.html" Status in fontconfig package in Ubuntu: New Bug description: during debuild -us -uc -b ... Now running lintian... W: fontconfig-config: command-with-path-in-maintainer-script postrm:9 /usr/bin/ucf E: libfontconfig1-dev: doc-base-file-references-missing-file fontconfig-devel:16 /usr/share/doc/libfontconfig1-dev/fontconfig-devel/index.html E: fontconfig: malformed-override Override of package-needs-versioned-debhelper-build-depends for package type source (expecting binary) at line 1 W: fontconfig-udeb udeb: package-name-doesnt-match-sonames libfontconfig1 Finished running lintian. Looking in doc/fontconfig-devel it does seem that there's no index.html. Adding an index.html manages to get to the next failure ( doc/fontconfig-user.html ): Ubuntu: yakkety 16.10 fontconfig: 2.11.94-0ubuntu2 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libfontconfig1 2.11.94-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Mar 28 18:53:10 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2014-07-09 (993 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140708) SourcePackage: fontconfig UpgradeStatus: Upgraded to yakkety on 2016-10-16 (163 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1677055/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1568364] Re: it fails to install set some modem setups to help me access the internet connectivity easily
What about it fails to install/setup? Was there any error message? ** Changed in: fontconfig (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fontconfig in Ubuntu. https://bugs.launchpad.net/bugs/1568364 Title: it fails to install set some modem setups to help me access the internet connectivity easily Status in fontconfig package in Ubuntu: Incomplete Bug description: it fails to install setups for moderation demoderation which will help me full access to the internet easily. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1568364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1546310] Re: In CAR bluetooth not working
Hello, Is there any update this bug? I have an Aquaris 4.5 on OTA-15 and I am still having that same issue with my new Pioneer car audo. Can pick up calls but sound is not routed through car speakers and car microphone does not seem to record sound. I had the same issue with an Alpine care audio before and it never worked. Would be nice to see some progress here. Cheers, Thomas -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1546310 Title: In CAR bluetooth not working Status in Canonical System Image: Fix Released Status in bluez package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Bug description: I have paired my phone with my car as always (connection did work in the past). Connection runs as expected and everything like display, phone book, ... but this evening I wanted to place a call from my car and it did not work. I was then also not able to take a call (I could not hear the conterpart and the counterpart could not hear me). Since yesterday I am on: current build number: 259 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2016-02-16 12:09:18 version version: 259 version ubuntu: 20160216 version device: 20160108-efc96d8 version custom: 20160111-926-36--vivid With OTA9 I did not have the issue. I have attached my logs. I have enabled the following bug-settings for bluetooth: sudo sed -i 's/exec \/usr\/sbin\/bluetoothd/exec \/usr\/sbin\/bluetoothd -d/g' /etc/init/bluetooth.conf sudo sed -i 's/--start/--start --log-level=debug/g' /usr/share/upstart/sessions/pulseaudio.conf I have modified the line in ofono.override to: exec ofonod -P -d provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap I hope my reporting helps to trace down this issue. Uranicus To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1546310/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method
*** This bug is a duplicate of bug 1658921 *** https://bugs.launchpad.net/bugs/1658921 I did a fresh install of 16.04 and an upgrade to 16.1 with no other changes. I too lost the wired connection completely (including the applet). I can confirm that fix #6 worked flawlessly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1638842 Title: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method Status in network-manager package in Ubuntu: Won't Fix Bug description: Hello, I installed Ubuntu 16.10 using a chroot. I use network-manager to manage connections. My system is up-to-date (so I use network-manager 1.2.4-0ubuntu1). Wifi works perfectly but I cannot connect to wired networks and using my phone's Bluetooth connection. Corresponding devices are said to be unmanaged by network-manager. nmcli dev outputs: DEVICETYPE STATE CONNECTION enp1s0ethernet unmanaged -- wlp2s0wifi disconnected -- 6C:9B:02:2C:EE:2C btunmanaged -- hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C gsm unmanaged -- loloopback unmanaged -- The following command has no effect: sudo nmcli dev set enp1s0 managed yes I can connect to a wired connection by doing: ifconfig enp1s0 up dhclient enp1s0 There is nothing in the file /etc/network/interfaces. Everything works perfectly if I downgrade network-manager to this version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb (http://packages.ubuntu.com/xenial-updates/amd64/network- manager/download). I had to install libreadline6 and downgrade nplan to meet dependencies. I don't know what to join to this bug report so please ask in case anything is needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677054] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- 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/1677054 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I'm new to Ubuntu, no clue what happened. Just tried to install an OS update from the software manager. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Tue Mar 28 01:29:54 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-01-21 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: MSI MS-7641 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=dc5ab334-a489-4fc8-beca-72fce6981c05 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=dc5ab334-a489-4fc8-beca-72fce6981c05 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd05/28/2013:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677054] [NEW] package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: I'm new to Ubuntu, no clue what happened. Just tried to install an OS update from the software manager. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Tue Mar 28 01:29:54 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-01-21 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: MSI MS-7641 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=dc5ab334-a489-4fc8-beca-72fce6981c05 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=dc5ab334-a489-4fc8-beca-72fce6981c05 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd05/28/2013:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- 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/1677054 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: New Bug description: I'm new to Ubuntu, no clue what happened. Just tried to install an OS update from the software manager. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Tue Mar 28 01:29:54 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-01-21 (65 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. MachineType: MSI MS-7641 Papersize: letter ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=dc5ab334-a489-4fc8-beca-72fce6981c05 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=dc5ab334-a489-4fc8-beca-72fce6981c05 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V25.0 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 760GMA-P34(FX) (MS-7641) dmi.board.vendor: MSI dmi.board.version: 5.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 5.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV25.0:bd05/28/2013:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0: dmi.product.name: MS-7641 dmi.product.version: 5.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1677054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676249] Re: Guest session shouldn't require auth for wifi
Lets call invalid as option to allow all users will allow guest wifi automatically. Whether this should be the default setting would be the only possible bug, not sure that matters ** Changed in: lightdm (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1676249 Title: Guest session shouldn't require auth for wifi Status in lightdm package in Ubuntu: Invalid Bug description: Likely not network-manager but it's affected & got to start somewhere. Test case: Boot up to greeter & login to guest session. Click on network indicator, choose wifi network used by main user What happens: Password to network must be entered, then a keyring must be created. What should happen: Upon logging in wifi should be enabled with no guest user interaction needed. This is the correct current behavior in 14.04.x. 16.04.x is broken in this regard, at least for many users/user's hardware. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: network-manager 1.4.4-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Sun Mar 26 22:02:49 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-03-26 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170326) IpRoute: default via 192.168.1.1 dev wlp8s0 proto static metric 600 169.254.0.0/16 dev wlp8s0 scope link metric 1000 192.168.1.0/24 dev wlp8s0 proto kernel scope link src 192.168.1.6 metric 600 NetworkManager.conf: [main] plugins=ifupdown,keyfile [ifupdown] managed=false NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH 06F21A 957649c7-c710-4d40-9aed-b33776d3c84d 802-11-wireless 1490580159 Sun 26 Mar 2017 10:02:39 PM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/1 yes wlp8s0 activated /org/freedesktop/NetworkManager/ActiveConnection/7 Wired connection 1 64e15934-77b8-36e1-961a-5065243bc6ca 802-3-ethernet 1490579550 Sun 26 Mar 2017 09:52:30 PM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/0 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp8s0 wifi connected/org/freedesktop/NetworkManager/Devices/2 06F21A 957649c7-c710-4d40-9aed-b33776d3c84d /org/freedesktop/NetworkManager/ActiveConnection/7 enp7s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.4.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1676249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1674295] Re: No wifi access for guest unless a user is already logged in
Lets call invalid as option to allow all users will allow guest wifi automatically. Whether this should be the default setting would be the only possible bug, not sure that matters ** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1674295 Title: No wifi access for guest unless a user is already logged in Status in lightdm package in Ubuntu: Invalid Bug description: In 16.04.x guest sessions get no wifi access unless a user is already logged in, i.e. one has to open a guest session from a user session. In 14.04 wifi is automatically enabled for a guest session, in 17.04 a guest needs to enter wifi password & create a keyring. Test case: Boot up to a machine using wifi that's password protected, at greeter choose guest. Once logged in notice nm-applet is running but no connection. Click on icon, choose a network, click on it. What happens: nothing ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 20 07:23:48 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 600 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.6 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [modified] mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2017-01-08T20:36:09.732047 nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATHACTIVE DEVICE STATE ACTIVE-PATH 06F21A 1ce53caa-53f9-48d9-8bf1-0da97c1ac332 802-11-wireless 1490008954 Mon 20 Mar 2017 07:22:34 AM EDT yes 0 no/org/freedesktop/NetworkManager/Settings/6 yes wlan0 activated /org/freedesktop/NetworkManager/ActiveConnection/1 Wired connection 1 b2b79c5d-61cd-3fa0-a0fc-05217e735e06 802-3-ethernet 1490006436 Mon 20 Mar 2017 06:40:36 AM EDT yes 4294966297 no/org/freedesktop/NetworkManager/Settings/11 no -- -- -- nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/0 06F21A 1ce53caa-53f9-48d9-8bf1-0da97c1ac332 /org/freedesktop/NetworkManager/ActiveConnection/1 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/2 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1674295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676993] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 ** This bug has been marked a duplicate of bug 1676380 Update to cups-daemon 2.1.3-4ubuntu0.2 results in maintainer script failures -- 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/1676993 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 21:45:47 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-18 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: device for HP-Officejet-Pro-6830: usb://HP/Officejet%20Pro%206830?serial=TH58M8112P&interface=1 Lsusb: Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 003: ID 1058:10b8 Western Digital Technologies, Inc. Elements Portable (WDBU6Y, WDBUZG) Bus 001 Device 002: ID 0c45:6300 Microdia PC Microscope camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Compaq-Presario KQ368AA-ABD SR5421DE Papersize: a4 PpdFiles: HP-Officejet-Pro-6830: HP Officejet Pro 6830, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.10 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.10:bd02/21/2008:svnCompaq-Presario:pnKQ368AA-ABDSR5421DE:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KQ368AA-ABD SR5421DE dmi.sys.vendor: Compaq-Presario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671449] Re: Unity8 window shadows have gone missing
This in QA queue now: https://bileto.ubuntu.com/#/ticket/2647 ** Changed in: canonical-devices-system-image Status: Fix Released => In Progress ** Changed in: unity8 (Ubuntu) Status: Confirmed => Invalid ** Changed in: canonical-devices-system-image Milestone: u8c-1 => u8c-z -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1671449 Title: Unity8 window shadows have gone missing Status in Canonical System Image: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: Invalid Bug description: [unity8] windows don't have shadow i see this on both 16.04 and 17.04 unity8 after the last update i think? i've also seen this before by installing silo 2540 see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677050] [NEW] Youtube video will not run
Public bug reported: When I first set up ubuntu I was able to look at youtube videos, but then they just stopped running. I have no real idea why. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-82.90-generic 3.19.8-ckt22 Uname: Linux 3.19.0-82-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 28 16:44:30 2017 DistUpgraded: 2017-02-13 13:49:16,446 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a5e] InstallationDate: Installed on 2015-12-03 (481 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: HP-Pavilion GC670AA-ABA a6120n ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-82-generic root=UUID=38cc240f-f1a8-40ed-98a0-6c59680dea14 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to vivid on 2017-02-13 (43 days ago) dmi.bios.date: 06/07/2007 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.20 dmi.board.name: Leonite2 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 6.00 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.20:bd06/07/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: GC670AA-ABA a6120n dmi.sys.vendor: HP-Pavilion version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.9-2ubuntu1~vivid2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.9-2ubuntu1~vivid2 version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2build1 xserver.bootTime: Tue Mar 28 15:50:33 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputAT Translated Set 2 keyboard KEYBOARD, id 8 inputGenPS/2 Genius Mouse MOUSE, id 9 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 27137 vendor VSC xserver.version: 2:1.17.1-0ubuntu3.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubuntu vivid -- 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/1677050 Title: Youtube video will not run Status in xorg package in Ubuntu: New Bug description: When I first set up ubuntu I was able to look at youtube videos, but then they just stopped running. I have no real idea why. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-82.90-generic 3.19.8-ckt22 Uname: Linux 3.19.0-82-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Mar 28 16:44:30 2017 DistUpgraded: 2017-02-13 13:49:16,446 DEBUG enabling apt cron job DistroCodename: vivid DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:2a5e] InstallationDate: Installed on 2015-12-03 (481 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hu
[Touch-packages] [Bug 1676995] Re: [regression] App switcher does not respond to tab events
** Summary changed: - App switcher does not respond to tab events + [regression] App switcher does not respond to tab events ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Michael Zanetti (mzanetti) ** Changed in: canonical-devices-system-image Milestone: None => u8c-z -- 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/1676995 Title: [regression] App switcher does not respond to tab events Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: 17.04 deb based unity8 session running in VM. unity8: 8.15+17.04.20170321-0ubuntu1 To reproduce: 1) Boot up unity8 deb based session. 2) Load an application either from launcher or app drawer, e.g. System Settings 3) Press Alt+Tab to display task switcher and then release Tab key to leave switcher showing. 4) Press Tab again. Expected result: Pressing Tab should cycle through the available apps. Actual result: The selected app does not change using the Tab key. Note: Once the unity8 session has been locked and unlocked, the Tab key selection will work again. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676996] Re: unity8-tests is installed as a depends of unity8-common, but unity8-tests does not seem like a package most users need
** Branch linked: lp:~saviq/unity8/common-nodep-tests -- 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/1676996 Title: unity8-tests is installed as a depends of unity8-common, but unity8-tests does not seem like a package most users need Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: unity8-common depends on unity8-tests, but it seems like unity8-tests and its dependencies are not necessary on most users' systems. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676996] Re: unity8-tests is installed as a depends of unity8-common, but unity8-tests does not seem like a package most users need
** Changed in: canonical-devices-system-image Status: Triaged => In Progress ** Changed in: unity8 (Ubuntu) Status: Triaged => In Progress -- 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/1676996 Title: unity8-tests is installed as a depends of unity8-common, but unity8-tests does not seem like a package most users need Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: unity8-common depends on unity8-tests, but it seems like unity8-tests and its dependencies are not necessary on most users' systems. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Changed in: cups (Ubuntu Xenial) Status: Confirmed => Triaged -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Triaged Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676996] Re: unity8-tests is installed as a depends of unity8-common, but unity8-tests does not seem like a package most users need
The actual dependency is: > unity8-tests | unity-application-impl, So in production environment it's qtdeclaratvie5-qtmir-plugin that fulfils this dep, but I agree, this is left from when unity8-fakeenv was still usable, and used, as a replacement for qtmir. Not really the case any more. ** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided => High ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Michał Sawicz (saviq) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Status: New => Triaged ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Assignee: (unassigned) => Michał Sawicz (saviq) ** Changed in: canonical-devices-system-image Milestone: None => u8c-z -- 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/1676996 Title: unity8-tests is installed as a depends of unity8-common, but unity8-tests does not seem like a package most users need Status in Canonical System Image: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: unity8-common depends on unity8-tests, but it seems like unity8-tests and its dependencies are not necessary on most users' systems. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1676996/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630906] Re: QML segfault on arm64 due to builder kernel change
** Changed in: ubuntu-push-qml (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Invalid Status in online-accounts-api package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in ubuntu-push-qml package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu RTM: Fix Released Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1642966] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Changed xenial status by error, should be 'Triaged'. Can't change it back, sorry :( ** Changed in: cups (Ubuntu Xenial) Status: Triaged => Confirmed -- 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/1642966 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Fix Released Status in cups source package in Xenial: Confirmed Status in cups source package in Yakkety: Fix Released Status in cups source package in Zesty: Fix Released Bug description: This is in xenial-proposed, please block release to -updates accordingly :) [Impact] * fail to upgrade [testcase] Root cause is believed to be reproducible with: #!/bin/bash systemctl stop cups.path cups.service rm /var/cache/cups/org.cups.cupsd systemctl start cups.path touch /var/cache/cups/org.cups.cupsd sleep 1 rm /var/cache/cups/org.cups.cupsd sleep 1 systemctl stop cups.service echo $? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-46.67-generic 4.4.24 Uname: Linux 4.4.0-46-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CupsErrorLog: Date: Fri Nov 18 11:13:15 2016 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-05-02 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lpstat: device for mallards-officejet-pro-8600: dnssd://Officejet%20Pro%208600%20%5BD63461%5D._ipp._tcp.local/?uuid=1c852a4d-b800-1f08-abcd-d89d67d63461 MachineType: Dell Inc. XPS 15 9550 Papersize: a4 PpdFiles: mallards-officejet-pro-8600: HP Officejet Pro 8600, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-46-generic.efi.signed root=UUID=3643ef37-7cee-41b3-9387-2faa819c44db ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1642966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1677042] [NEW] Grub recovery boot root prompt is unstable
Public bug reported: I've seen this on two systems: Xubuntu on dual Xeons, and Ubuntu on an I-7. When I choose "advanced options" -> "recovery mode" in Grub, and then "root shell prompt" in the resulting booted system, I cannot expect it to be functional for long. I can do a few things, but even if I do nothing, it can break in a way that takes it back to the place where I selected "root shell prompt" but it is completely unresponsive to the keyboard or mouse. Or nearly so. I can get a reboot with the three-finger-salute. Usually. Even without that, I've been interrupted by status messages garbling the screen and other stuff I'd love to suppress. At least usually, I would. I'd like some control. When I'm already fighting system problems, this is even more annoying than usual, but it happens on healthy systems too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu16 ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 28 14:05:22 2017 ExecutablePath: /lib/systemd/systemd InstallationDate: Installed on 2016-11-24 (124 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System76, Inc. Silverback WS ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-70-generic root=UUID=c4f3d485-bc7a-4456-8d8c-44ce35b619dc ro quiet splash clocksource=tsc vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf 3 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z10PE-D16 WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: Desktop dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3204:bd04/28/2016:svnSystem76,Inc.:pnSilverbackWS:pvrsilw2:rvnASUSTeKCOMPUTERINC.:rnZ10PE-D16WS:rvrRev1.xx:cvnSystem76,Inc.:ct17:cvrDesktop: dmi.product.name: Silverback WS dmi.product.version: silw2 dmi.sys.vendor: System76, Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1677042 Title: Grub recovery boot root prompt is unstable Status in systemd package in Ubuntu: New Bug description: I've seen this on two systems: Xubuntu on dual Xeons, and Ubuntu on an I-7. When I choose "advanced options" -> "recovery mode" in Grub, and then "root shell prompt" in the resulting booted system, I cannot expect it to be functional for long. I can do a few things, but even if I do nothing, it can break in a way that takes it back to the place where I selected "root shell prompt" but it is completely unresponsive to the keyboard or mouse. Or nearly so. I can get a reboot with the three-finger-salute. Usually. Even without that, I've been interrupted by status messages garbling the screen and other stuff I'd love to suppress. At least usually, I would. I'd like some control. When I'm already fighting system problems, this is even more annoying than usual, but it happens on healthy systems too. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: systemd 229-4ubuntu16 ProcVersionSignature: Ubuntu 4.4.0-70.91-generic 4.4.49 Uname: Linux 4.4.0-70-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Tue Mar 28 14:05:22 2017 ExecutablePath: /lib/systemd/systemd InstallationDate: Installed on 2016-11-24 (124 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System76, Inc. Silverback WS ProcEnviron: TERM=linux PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-70-generic root=UUID=c4f3d485-bc7a-4456-8d8c-44ce35b619dc ro quiet splash clocksource=tsc vt.handoff=7 SourcePackage: systemd SystemdDelta: [EXTENDED] /etc/systemd/system/display-manager.service → /lib/systemd/system/display-manager.service.d/xdiagnose.conf [EXTENDED] /lib/systemd/system/systemd-timesyncd.service → /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/syst
[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
Same issue with OpenVPN. As a workaround, once the VPN is connected, I edit /etc/resolv.conf and add my DNS (nameserver 8.8.8.8). It makes DNS resolution work again. But if I disconnect and reconnect the VPN resolv.conf is indeed reseted. I tried to force my DNS in the VPN settings in the network manager but no improvement. -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: New Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib
** Changed in: canonical-devices-system-image Status: Fix Released => Fix Committed ** Changed in: canonical-devices-system-image Milestone: u8c-1 => u8c-z -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Committed Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Triaged Status in unity-system-compositor package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676993] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Can confirm. Saw this failure on dozens of machines today when 2.1.3-4 failed to upgrade to 2.1.3-4ubuntu0.2. -- 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/1676993 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 21:45:47 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-18 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: device for HP-Officejet-Pro-6830: usb://HP/Officejet%20Pro%206830?serial=TH58M8112P&interface=1 Lsusb: Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 003: ID 1058:10b8 Western Digital Technologies, Inc. Elements Portable (WDBU6Y, WDBUZG) Bus 001 Device 002: ID 0c45:6300 Microdia PC Microscope camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Compaq-Presario KQ368AA-ABD SR5421DE Papersize: a4 PpdFiles: HP-Officejet-Pro-6830: HP Officejet Pro 6830, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.10 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.10:bd02/21/2008:svnCompaq-Presario:pnKQ368AA-ABDSR5421DE:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KQ368AA-ABD SR5421DE dmi.sys.vendor: Compaq-Presario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676993] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New => Confirmed -- 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/1676993 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Mon Mar 27 21:45:47 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-03-18 (9 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lpstat: device for HP-Officejet-Pro-6830: usb://HP/Officejet%20Pro%206830?serial=TH58M8112P&interface=1 Lsusb: Bus 001 Device 004: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader Bus 001 Device 003: ID 1058:10b8 Western Digital Technologies, Inc. Elements Portable (WDBU6Y, WDBUZG) Bus 001 Device 002: ID 0c45:6300 Microdia PC Microscope camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Compaq-Presario KQ368AA-ABD SR5421DE Papersize: a4 PpdFiles: HP-Officejet-Pro-6830: HP Officejet Pro 6830, hpcups 3.16.3 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=682d55bf-0f21-4986-8551-32e6eb4e50b1 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2008 dmi.bios.vendor: Phoenix Technologies, LTD dmi.bios.version: 5.10 dmi.board.name: NARRA3 dmi.board.vendor: ASUSTek Computer INC. dmi.board.version: 3.02 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr5.10:bd02/21/2008:svnCompaq-Presario:pnKQ368AA-ABDSR5421DE:pvr:rvnASUSTekComputerINC.:rnNARRA3:rvr3.02:cvnHewlett-Packard:ct3:cvrChassisVersion: dmi.product.name: KQ368AA-ABD SR5421DE dmi.sys.vendor: Compaq-Presario To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676993/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1668409] Re: Firefox fails to launch in unity8 zesty
It's going to be an issue until Firefox gets fixed upstream to not try to use X11 when it's using Mir. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1668409 Title: Firefox fails to launch in unity8 zesty Status in Canonical System Image: Incomplete Status in firefox package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: daily iso of zesty exploring clean u8 to repro 1) open app drawer 2) find ff icon, click to launch journal shows the following http://pastebin.ubuntu.com/24080554/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1668409/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1569719] Re: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python3-defaults (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1569719 Title: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3 Status in python3-defaults package in Ubuntu: Confirmed Bug description: Upgraded to Ubuntu 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3 3.5.1-3 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Tue Apr 12 12:33:05 2016 ErrorMessage: pre-dependency problem - not installing python3 InstallationDate: Installed on 2015-01-16 (453 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: python3-defaults Title: package python3 3.5.1-3 failed to install/upgrade: pre-dependency problem - not installing python3 UpgradeStatus: Upgraded to xenial on 2016-04-12 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1569719/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673563] Re: Cannot start mediaplayer-app to play videos on Unity8 session
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1673563 Title: Cannot start mediaplayer-app to play videos on Unity8 session Status in Canonical System Image: Fix Released Status in mediaplayer-app package in Ubuntu: Fix Released Bug description: In zesty and xenial+overlay, the mediaplayer-app won't start when attempting to play videos, because the .desktop file is marked as hidden. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672955] Re: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::Lib
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1672955 Title: unity-system-compositor crashed with SIGSEGV in libinput_device_config_accel_is_available() from libinput_device_config_accel_set_speed() from mir::input::evdev::LibInputDevice::apply_settings() Status in Canonical System Image: Fix Released Status in Mir: Fix Committed Status in Mir 0.26 series: Fix Committed Status in Unity System Compositor: Invalid Status in mir package in Ubuntu: Triaged Status in unity-system-compositor package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-system-compositor. This problem was most recently seen with package version 0.9.1+17.04.20170216-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/fcf5550475fb0478d6eb2a307f03705ef1ed398a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. It seems that the configuration change is requested just a moment before the device gets removed. The change actions are serialized, depending on where there memory of mir::input::DefaultDevice is allocated the segfault either occurs inside the lambda or inside underlying mir::input::LibInputDevice in the platform. The activities on input dispatch device removal and reconfiguration are serialized inside the input thread, so we just need to clean the action queue (or have multiple queues) before removing the devices. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1630906] Re: QML segfault on arm64 due to builder kernel change
** Changed in: qtdeclarative-opensource-src (Ubuntu RTM) Status: In Progress => Fix Released ** Changed in: unity8 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: online-accounts-api (Ubuntu) Status: New => Invalid ** Changed in: qmenumodel (Ubuntu) Status: New => Invalid ** Changed in: webbrowser-app (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1630906 Title: QML segfault on arm64 due to builder kernel change Status in linux package in Ubuntu: Invalid Status in online-accounts-api package in Ubuntu: Invalid Status in qmenumodel package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: Fix Released Status in ubuntu-push-qml package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: Invalid Status in qtdeclarative-opensource-src package in Ubuntu RTM: Fix Released Bug description: Builders were changed from wily to xenial (4.4) kernel for arm64, and likely due to this the following kind of errors started happening: https://launchpadlibrarian.net/288487533/buildlog_ubuntu-yakkety-arm64 .ubuntu-push-qml_0.1+15.10.20150826.1-0ubuntu2_BUILDING.txt.gz They happen when executing QML code. I've ruled out that reverting to previous qtbase and qtdeclarative versions don't affect this, so it's not coming from a Qt change. I've also verified there's no problem eg on our Bq tablet running the same tests on xenial+overlay. There are currently no found changes at least in Qt upstream to backport arm64 related fixes. Cause is unknown. But the same problem is there on vivid, xenial and yakkety builds: https://launchpadlibrarian.net/288516465/buildlog_ubuntu-yakkety-arm64.online-accounts-api_0.1+16.10.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515705/buildlog_ubuntu-xenial-arm64.online-accounts-api_0.1+16.04.20161006.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288515510/buildlog_ubuntu-vivid-arm64.online-accounts-api_0.1+15.04.20161006.1-0ubuntu1_BUILDING.txt.gz This means it does not matter if it's Qt 5.4 or 5.6, GCC 4.9, 5 or 6, or glibc 2.21, 2.23 or 2.24. More logs from affected packages: https://launchpadlibrarian.net/288493058/buildlog_ubuntu-yakkety-arm64.qtdeclarative-opensource-src_5.6.1-7ubuntu3~1_BUILDING.txt.gz https://launchpadlibrarian.net/288347391/buildlog_ubuntu-xenial-arm64.webbrowser-app_0.23+16.04.20161005.1-0ubuntu1_BUILDING.txt.gz https://launchpadlibrarian.net/288385063/buildlog_ubuntu-vivid-arm64.qmenumodel_0.2.10+15.04.20161005.1-0ubuntu1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673550] Re: system-settings not remembering previous size on unity8
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- 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/1673550 Title: system-settings not remembering previous size on unity8 Status in Canonical System Image: Fix Released Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Invalid Bug description: running u8 desktop session Steps to reproduce: - open u-s-s - resize the window to 2 column mode - close the app with X from window control - restart the app Expected results: - u-s-s should open at the size it was last closed at Actutual results: - u-s-s window is smaller only showing one column This may be related to limiting the max size which we used to have? I think we should remove all max sizing restrictions on the app, and bring back the maximize button which is not displayed either. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1673550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672804] Re: can't login to dropbox.com on desktop
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1672804 Title: can't login to dropbox.com on desktop Status in Canonical System Image: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: when I try to access dropbox.com on webbrowser-app on desktop I get an banner saying our browser is not supported, and it's displayed on top of the login button so there is no way to login. Guessing we need an override for this site To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566172] Re: [SUGGESTION] Use the space bar for moving the text cursor
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1566172 Title: [SUGGESTION] Use the space bar for moving the text cursor Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Committed Status in ubuntu-keyboard package in Ubuntu: Fix Committed Bug description: I have an idea which maybe considered to be implemented. What if we use the space bar for moving the text cursor horizontally or even vertically. Currently, moving the cursor is quite hard and inaccurate. Space bar is quite big and makes it a good place to swipe to move the cursor. With this approach, we're not using more space and instead use a big part of the keyboard that is only there mostly for inserting spaces. The sensitivity is critical though because you don't want unintended movement of the cursor but I think it's very much doable. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639776] Re: dnsmasq fails to send queries out after suspend disconnects the interface
I uploaded the fix today to 16.04 and 16.10, will need to go through the SRU process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1639776 Title: dnsmasq fails to send queries out after suspend disconnects the interface Status in dnsmasq package in Ubuntu: Fix Released Status in dnsmasq source package in Xenial: In Progress Status in dnsmasq source package in Yakkety: In Progress Status in dnsmasq package in Debian: Fix Released Bug description: [Impact] * suspend/resume (which involves disconnection of network devices) leads to dnsmasq failures. [Test Case] * suspend/resume on 16.04 or 16.10 when using dnsmasq, and see failures upon resume. [Regression Potential] * The fix was NMU'd in Debian in the version immediately after 16.10's. I believe the regression potential is very low as this is a clear bug-fix from upstream. --- Failure is caused by ENODEV return for all dns queries like: sendto(11, "\232\325\1\0\0\1\0\0\0\0\0\0\4mail\6google\3com\0\0\1\0"..., 33, 0, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("62.241.198.245")}, 16) = -1 ENODEV (No such device) Problem is reported and fixed: https://bugzilla.redhat.com/show_bug.cgi?id=1367772 http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=2675f2061525bc954be14988d64384b74aa7bf8b I didn't yet test if applying that patch to ubuntu package works. I will try the patch in a few hours. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: dnsmasq-base 2.76-4 ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0 Uname: Linux 4.8.0-26-generic x86_64 ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 7 14:11:51 2016 InstallationDate: Installed on 2037-12-25 (-7718 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: dnsmasq UpgradeStatus: Upgraded to yakkety on 2016-10-21 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1639776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661283] Re: Qt.ImhUrlCharactersOnly should not disable predictive text
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1661283 Title: Qt.ImhUrlCharactersOnly should not disable predictive text Status in Canonical System Image: Fix Released Status in ubuntu-keyboard package in Ubuntu: Fix Committed Bug description: When in a TextInput the flag Qt.ImhUrlCharactersOnly is set on inputMethodHints [1], predictive text is implicitly disabled. This should not be the case. Additionnally, a space should not be added after predicted words. http://doc.qt.io/qt-5/qml-qtquick-textinput.html#inputMethodHints-prop To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1661283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1676307] Re: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
*** This bug is a duplicate of bug 1676380 *** https://bugs.launchpad.net/bugs/1676380 Hello, I have a similar problem... I hope you will quickly release a patch, my printer is unusable. Tks. -- 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/1676307 Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in cups package in Ubuntu: Confirmed Bug description: Preparing to unpack .../cups-daemon_2.1.3-4ubuntu0.2_amd64.deb ... Job for cups.service canceled. invoke-rc.d: initscript cups, action "stop" failed. dpkg: warning: subprocess old pre-removal script returned error exit status 1 dpkg: trying script from the new package instead ... Job for cups.service canceled. invoke-rc.d: initscript cups, action "stop" failed. dpkg: error processing archive /var/cache/apt/archives/cups-daemon_2.1.3-4ubuntu0.2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 1 insserv: warning: script 'lprng' missing LSB tags and overrides insserv: warning: script 'lpd' missing LSB tags and overrides insserv: warning: script 'cupsys' missing LSB tags and overrides ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CupsErrorLog: Date: Mon Mar 27 09:29:40 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-04-25 (336 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lpstat: device for MFCJ6920DW: dnssd://Brother%20MFC-J6720DW._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-30055cc07adf device for PDF: cups-pdf:/ device for RICOH-Aficio-SP-3410SF: dnssd://RICOH%20Aficio%20SP%203410SF%20(201634)._printer._tcp.local/ MachineType: NOVATECH LTD MBB-61004 Papersize: a4 PpdFiles: PDF: Generic CUPS-PDF Printer MFCJ6920DW: Brother MFC-J6920DW CUPS RICOH-Aficio-SP-3410SF: RICOH Aficio SP 3410SF PS ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=a541ced6-881c-42f4-a434-f2f2975fb723 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=a541ced6-881c-42f4-a434-f2f2975fb723 ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.19 SourcePackage: cups Title: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2016-06-26 (274 days ago) dmi.bios.date: 01/13/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4b dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H110M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: 7411698-004 dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4b:bd01/13/2016:svnNOVATECHLTD:pnMBB-61004:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH110M-S2H-CF:rvrx.x:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.name: MBB-61004 dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD modified.conffile..etc.default.cups: [modified] mtime.conffile..etc.default.cups: 2015-08-05T06:20:06 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1676307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1671449] Re: Unity8 window shadows have gone missing
** Changed in: canonical-devices-system-image Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1671449 Title: Unity8 window shadows have gone missing Status in Canonical System Image: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Status in unity8 package in Ubuntu: Confirmed Bug description: [unity8] windows don't have shadow i see this on both 16.04 and 17.04 unity8 after the last update i think? i've also seen this before by installing silo 2540 see attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1671449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1672673] Re: Application menus should hide when triggering the spread
** Changed in: canonical-devices-system-image Importance: Undecided => Medium -- 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/1672673 Title: Application menus should hide when triggering the spread Status in Canonical System Image: In Progress Status in unity8 package in Ubuntu: In Progress Bug description: Having the menu open makes using the spread hard. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1675572] Re: GUI of desktop apps are too big on high-dpi screens
** Changed in: canonical-devices-system-image Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1675572 Title: GUI of desktop apps are too big on high-dpi screens Status in Canonical System Image: In Progress Status in qtubuntu package in Ubuntu: In Progress Bug description: On a 13" 1080p display, fonts and UI in general is too big when running desktop Qt-based apps like konsole, QtCreator and Kate. Strangely, hardcoding logical dpi to 96 in qtubuntu fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1675572/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp