[Touch-packages] [Bug 1693361] Please test proposed package
Hello Jim, or anyone else affected, Accepted cloud-init into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.9-153-g16a7302f-0ubuntu1~16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial.If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Committed Status in cloud-init source package in Yakkety: Fix Committed Status in cloud-init source package in Zesty: Fix Committed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
Hello Jim, or anyone else affected, Accepted cloud-init into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.9-153-g16a7302f-0ubuntu1~16.10.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-yakkety to verification-done-yakkety.If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-yakkety. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Yakkety) Status: Confirmed => Fix Committed ** Tags added: verification-needed-yakkety ** Changed in: cloud-init (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags added: verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Fix Committed Status in cloud-init source package in Yakkety: Fix Committed Status in cloud-init source package in Zesty: Fix Committed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1699283] Re: package click 0.4.43+16.04.20160203-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Does this happen because Ubuntu created its own `click` package that is not the same as the one installed by `pip3 install click`? Maybe this bug affects users who have installed that other package? Before I realized that, I uninstalled click with pip. Now I'm having additional problems. Ubuntu's click is trying to import `click`, but `click` is something else on my system (http://click.pocoo.org/5/). sudo apt-get install -f 100 ↵ Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: linux-headers-4.4.0-79 linux-headers-4.4.0-79-generic linux-image-4.4.0-79-generic linux-image-extra-4.4.0-79-generic linux-signed-image-4.4.0-79-generic Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: click Suggested packages: ubuntu-app-launch-tools | upstart-app-launch-tools The following packages will be upgraded: click 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/14.5 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y (Legado de datumbazo ... 629350 dosieroj kaj dosierujoj aktuale instalitaj.) Preparado por anstataŭigi .../click_0.4.43+16.04.20170613-0ubuntu1_amd64.deb ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: averto: subprocezo malnova skripto pre-removal liveris eraran elir-staton 1 dpkg: ni provas skripton el la nova pako anstataŭe ... Traceback (most recent call last): File "/usr/bin/click", line 37, in import click ImportError: No module named 'click' dpkg: eraro dum procezado de la arĥivo /var/cache/apt/archives/click_0.4.43+16.04.20170613-0ubuntu1_amd64.deb (--unpack): subprocezo nova skripto pre-removal liveris eraran elir-staton 1 Job for click-system-hooks.service failed because the control process exited with error code. See "systemctl status click-system-hooks.service" and "journalctl -xe" for details. click-system-hooks.service couldn't start. Eraroj aperis dum procezado de: /var/cache/apt/archives/click_0.4.43+16.04.20170613-0ubuntu1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1699283 Title: package click 0.4.43+16.04.20160203-0ubuntu3 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in click package in Ubuntu: Incomplete Bug description: An update that failed. Many thanks for your great contributions and efforts to improve a great product. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: click 0.4.43+16.04.20160203-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Tue Jun 20 12:17:04 2017 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2016-04-01 (445 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: click Title: package click 0.4.43+16.04.20160203-0ubuntu3 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/click/+bug/1699283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701163] [NEW] package console-setup-linux 1.165 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-con
Public bug reported: its corrupt many times so give us ubuntu which does not have graphics issues in the pc ProblemType: Package DistroRelease: Debian 9 Package: console-setup-linux 1.165 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sat Jun 24 10:52:56 2017 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2017-06-23 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24 apt 1.2.20 SourcePackage: console-setup Title: package console-setup-linux 1.165 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: console-setup (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 console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1701163 Title: package console-setup-linux 1.165 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 Status in console-setup package in Ubuntu: New Bug description: its corrupt many times so give us ubuntu which does not have graphics issues in the pc ProblemType: Package DistroRelease: Debian 9 Package: console-setup-linux 1.165 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Sat Jun 24 10:52:56 2017 ErrorMessage: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 InstallationDate: Installed on 2017-06-23 (5 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.24 apt 1.2.20 SourcePackage: console-setup Title: package console-setup-linux 1.165 failed to install/upgrade: trying to overwrite '/lib/systemd/system/console-setup.service', which is also in package keyboard-configuration 1.108ubuntu15.3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1701163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
Hello Jim, or anyone else affected, Accepted cloud-init into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cloud- init/0.7.9-153-g16a7302f-0ubuntu1~17.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty.If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cloud-init (Ubuntu Zesty) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Fix Committed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep -i order [Regression Potential] Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1701161] [NEW] black terminal
Public bug reported: my terminal becoms black all ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jun 29 12:32:32 2017 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fdd0] InstallationDate: Installed on 2016-10-16 (255 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) MachineType: TOSHIBA Satellite L740 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=5c492036-60d3-4079-8608-60181e27aac2 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2012 dmi.bios.vendor: INSYDE dmi.bios.version: 2.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis Version dmi.modalias: dmi:bvnINSYDE:bvr2.50:bd04/12/2012:svnTOSHIBA:pnSatelliteL740:pvrPSK6XL-00C002:rvnIntelCorp.:rnBaseBoardProductName:rvrBaseBoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion: dmi.product.name: Satellite L740 dmi.product.version: PSK6XL-00C002 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1 version.libdrm2: libdrm2 2.4.65-3 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.4-1intel1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Jun 29 11:43:33 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 760 vendor LGD xserver.version: 2:1.17.2-1ubuntu9.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 third-party-packages ubuntu wily -- 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/1701161 Title: black terminal Status in xorg package in Ubuntu: New Bug description: my terminal becoms black all ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jun 29 12:32:32 2017 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:fdd0] InstallationDate: Installed on 2016-10-16 (255 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021) MachineType: TOSHIBA Satellite L740 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=5c492036-60d3-4079-8608-60181e27aac2 ro quiet splash vt.handoff=7 SourcePackage: xorg UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/12/2012 dmi.bios.vendor: INSYDE dmi.bios.version: 2.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Base Board Product Name dmi.board.vendor: Intel Corp. dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: OEM Chassis Manufacturer dmi.chassis.version: OEM Chassis
[Touch-packages] [Bug 1701162] [NEW] package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed')
Public bug reported: sudo apt upgrade fails. Output is as follows... Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/130 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: mount E: Sub-process /usr/bin/dpkg returned an error code (1) I've combed the web for a solution and tried all of the following. None of which have resolved the issue... sudo apt-get install -f sudo apt-get install --fix-broken --fix-missing sudo apt-get -f install sudo apt-get update –fix-missing sudo apt-get autoremove sudo apt-get -u dist-upgrade sudo apt --reinstall mount sudo dpkg –configure -a sudo dpkg -r -a ProblemType: Package DistroRelease: Ubuntu 17.04 Package: mount 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: mount:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 29 00:16:17 2017 DpkgTerminalLog: dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package mount is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-09-02 (300 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to zesty on 2017-05-20 (39 days ago) ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701162 Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') Status in util-linux package in Ubuntu: New Bug description: sudo apt upgrade fails. Output is as follows... Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/130 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') Errors were encountered while processing: mount E: Sub-process /usr/bin/dpkg returned an error code (1) I've combed the web for a solution and tried all of the following. None of which have resolved the issue... sudo apt-get install -f sudo apt-get install --fix-broken --fix-missing sudo apt-get -f install sudo apt-get update –fix-missing sudo apt-get autoremove sudo apt-get -u dist-upgrade sudo apt --reinstall mount sudo dpkg –configure -a sudo dpkg -r -a ProblemType: Package DistroRelease: Ubuntu 17.04 Package: mount 2.29-1ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: mount:amd64: Configure NULL: ConfigurePending Architecture: amd64 Date: Thu Jun 29 00:16:17 2017 DpkgTerminalLog: dpkg: error processing package mount (--configure): package mount is not ready for configuration cannot configure (current status 'half-installed') ErrorMessage: package mount is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2016-09-02 (300 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: util-linux Title: package mount 2.29-1ubuntu2.1 failed to install/upgrade: package mount is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: Upgraded to zesty on 2017-05-20 (39 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701162/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to :
[Touch-packages] [Bug 1701157] Re: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701157 Title: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: unknown the system want to send the bug report ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libpam-systemd:amd64 231-9ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Wed Jun 28 15:23:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-05-02 (422 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: systemd Title: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701157] [NEW] package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: unknown the system want to send the bug report ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libpam-systemd:amd64 231-9ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Wed Jun 28 15:23:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-05-02 (422 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: systemd Title: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701157 Title: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: unknown the system want to send the bug report ProblemType: Package DistroRelease: Ubuntu 16.10 Package: libpam-systemd:amd64 231-9ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.3 Architecture: amd64 Date: Wed Jun 28 15:23:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-05-02 (422 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1.1 apt 1.3.5 SourcePackage: systemd Title: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu
I'm using 17.04 and I can't access the pictures I get folder contains pictures then a message folder is empty, I have a IPhone 7 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name
** Changed in: oem-priority/xenial Status: Fix Released => New ** Changed in: oem-priority Status: Fix Released => Confirmed ** Changed in: oem-priority/xenial Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1647283 Title: WiFi being detected as ethernet when race condition on renaming for persistent name Status in HWE Next: Fix Released Status in NetworkManager: Fix Released Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in network-manager package in Ubuntu: Fix Released Bug description: Forwarded https://bugzilla.gnome.org/show_bug.cgi?id=775613 Version: NetworkManager 1.4.2 This bug happens after power-on with probability about 1/50. That means we need to reboot about 50 times to get into the buggy situation. "nmcli d" shows the device type is ethernet: DEVICE TYPE STATECONNECTION wlp1s0 ethernet unavailable -- lo loopback unmanaged-- The bug starts from a race condition. But it is not the root cause. I've also attach 2 logs. One is in good situation. Another is in bad situation. This log is generated by applying a "log patch" to network-manager 1.4.2 so we can see more stuff. In the bad situation. The bug starts with race condition. But the race condition is not the root cause. The race condition is: * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared. * Inside the NM, it is still using "wlan0" in "_linktype_get_type()". * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching failed in _linktype_get_type(). * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 disappeared. * And finally, devtype and kind are both NULL, so it returns NM_LINK_TYPE_ETHERNET for wlan0. Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit the type so it is still type ethernet. But from the log, I saw _linktype_get_type() is called several times later and return the correct type (wifi). But just, "nmcli d" still shows type ethernet. I'm wondering if we are missing to update the type in the Object created after renaming and re-detecting the type. fix need landing LP: #1645698 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1647283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700898] Re: I can't open my Ubuntu in lightDM mode all of the sudden
Maybe related to the crashes in bug 1700485?? -- 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/1700898 Title: I can't open my Ubuntu in lightDM mode all of the sudden Status in lightdm package in Ubuntu: New Bug description: It happened suddenly and I can't open my Ubuntu on LightDM mode. It kept saying "The system is running in low-graphics mode" and only terminal mode was available whenever I tried to open with lightDM mode. Now I have to work with GDM and it's pretty uncomfortable to work with. (ex) I can't type my native language) I've tried everything on google and still can't fix it. When I typed ubuntu-bug lightdm on terminal this appeared: Gtk-Message: GtkDialog mapped without a transient parent. This is discouraged. cat: /etc/lightdm/lightdm.conf: No such file or directory cat: /var/log/lightdm/seat0-greeter.log.old: No such file or directory Using PPAPI flash. --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so --ppapi-flash-version= ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: lightdm 1.18.3-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 28 15:00:19 2017 InstallationDate: Installed on 2016-12-19 (190 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1700898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701143] [NEW] package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1701003 *** https://bugs.launchpad.net/bugs/1701003 Public bug reported: error during boot ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 15:49:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (55 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701143 Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: error during boot ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 15:49:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (55 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701143] Re: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1701003 *** https://bugs.launchpad.net/bugs/1701003 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 #1701003, 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 1701003 package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- 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/1701143 Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: error during boot ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 15:49:07 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-05-04 (55 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701003] Re: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (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/1701003 Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: Confirmed Bug description: unable to run android emulator when we run the application, android emulator is not lunching due to some lib issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 17:21:53 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-06-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
The problem really is isolated to gnome-keyring (as OP and others stated). Here's my workaround for Chrome... it might help others (like Photon). But in the end it is only a workaround. It does demonstrate that if you bypass the display manager (lightdm, gdm) triggering the gnome-keyring for you, everything works great. By having a session not orchestrated by a display manager, apps work correctly: $ ssh -X localhost $ google-chrome & -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
** Description changed: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: - $ cat my.yaml - #cloud-config - packages: ['hello'] - + $ cat my.yaml + #cloud-config + packages: ['hello'] + [Test Case] - lxc-proposed-snapshot is - https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot + lxc-proposed-snapshot is + https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. -This is platform independent. The test case demonstrates lxd. -$ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ -"package_upgrade: true" > config.yaml -$ release=xenial -$ ref=proposed-$release + This is platform independent. The test case demonstrates lxd. + $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ + "package_upgrade: true" > config.yaml + $ release=xenial + $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance -$ name=$release-1693361 -$ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) + $ name=$release-1693361 + $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 -$ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log -# watch this boot. - - c.) Look for evidence of systemd failure -journalctl -o short-precise | grep -i break -journalctl -o short-precise | grep -i order + $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log + # watch this boot. + + c.) Look for evidence of systemd failure + journalctl -o short-precise | grep -i break + journalctl -o short-precise | grep -i order [Regression Potential] - Regression chance here is low. Its possible that ordering dependencies + Regression chance here is low. Its possible that ordering loops could occur. When that does happen, journalctl will mention it. Unfortunately in such cases systemd somewhat randomly picks a service to kil so behavior is somewhat undefined. [Other Info] Upstream commit at - https://git.launchpad.net/cloud-init/commit/?id=11121fe4 + https://git.launchpad.net/cloud-init/commit/?id=11121fe4 === End SRU Template === apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is
[Touch-packages] [Bug 1701133] Re: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701133 Title: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: Not sure what caused the error ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:i386 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic i686 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: i386 Date: Wed Jun 28 19:00:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-24 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701133] [NEW] package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: Not sure what caused the error ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:i386 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic i686 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: i386 Date: Wed Jun 28 19:00:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-24 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701133 Title: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: Not sure what caused the error ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:i386 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic i686 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: i386 Date: Wed Jun 28 19:00:57 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-24 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:i386 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701068] Re: motd is advertising HBO's Silicon Valley
I have to say, I was very disappointed to see this when I logged onto one of my servers today. I can understand the desire to be able to communicate directly to users and present timely, relevant information, but linking out to content marketing in what seems to be one of its first uses is self-sabotage. This type of behavior will lead to it being disabled and the "important security messages" to not be seen. Note, you can disable this behavior in /etc/default/motd-news -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd is advertising HBO's Silicon Valley Status in base-files package in Ubuntu: Triaged Bug description: The MOTD is advertising HBO's Silicon Valley. The MOTD should not be advertising anything. Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 185692] Re: pinning negative preferences not preventing installation
*** This bug is a duplicate of bug 565364 *** https://bugs.launchpad.net/bugs/565364 It is a duplicate, just maybe with a different effect. Anyway fixed over a year ago in 16.04, no need to bring that up again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/185692 Title: pinning negative preferences not preventing installation Status in apt package in Ubuntu: Confirmed Bug description: Binary package hint: apt I'm not sure if this is a problem with the documentation, or a problem with the application, however apt is not behaving as expected when pinning negative values. According to man 5 apt_preferences, a Pin-Priority "P < 0 prevents the version from being installed." Now I'll take a package at random and pin it in /etc/apt/preferences: Package: python-tcm Pin: version 0.5.1-0ubuntu4 Pin-Priority: -100 And yet, the package attempts to install: root@prizm:/tmp# apt-get -Vs install python-tcm Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: pessulus (2.16.3-0ubuntu1) python-tcm (0.5.1-0ubuntu4) 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Inst python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy) Conf python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy) The same occurs with a generalized version (Pin: version *). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/185692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 185692] Re: pinning negative preferences not preventing installation
*** This bug is a duplicate of bug 565364 *** https://bugs.launchpad.net/bugs/565364 this does not look like a duplicate of bug #565364 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/185692 Title: pinning negative preferences not preventing installation Status in apt package in Ubuntu: Confirmed Bug description: Binary package hint: apt I'm not sure if this is a problem with the documentation, or a problem with the application, however apt is not behaving as expected when pinning negative values. According to man 5 apt_preferences, a Pin-Priority "P < 0 prevents the version from being installed." Now I'll take a package at random and pin it in /etc/apt/preferences: Package: python-tcm Pin: version 0.5.1-0ubuntu4 Pin-Priority: -100 And yet, the package attempts to install: root@prizm:/tmp# apt-get -Vs install python-tcm Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: pessulus (2.16.3-0ubuntu1) python-tcm (0.5.1-0ubuntu4) 0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded. Inst python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy) Conf python-tcm (0.5.1-0ubuntu4 Ubuntu:7.10/gutsy) The same occurs with a generalized version (Pin: version *). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/185692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1637800] Re: add a motd script for news
> So, you promise it's not just going to return the output of GNU fortune over and over? https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068 is confirmed proof what this ticket is for is now being used inappropriately (unprofessionally). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1637800 Title: add a motd script for news Status in base-files package in Ubuntu: Fix Released Status in base-files source package in Xenial: In Progress Bug description: Add a new update-motd script for printing news and/or important notices. == SRU == [IMPACT] We should add important security messages or other news to the MOTD. [TEST CASE] Login to the system and ensure that the "news" section of the motd is displayed. Note that you might need to force trigger an update by running 'sudo update-motd'. [REGRESSION POTENTIAL] No reasonable regression potential. The script simply prints 2 lines of text to the MOTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701119] Re: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1699360 *** https://bugs.launchpad.net/bugs/1699360 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 #1699360, 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 1699360 package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 -- 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/1701119 Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: Installing some Update Packages ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun Jun 25 14:47:19 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-09 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701119] [NEW] package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1699360 *** https://bugs.launchpad.net/bugs/1699360 Public bug reported: Installing some Update Packages ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun Jun 25 14:47:19 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-09 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701119 Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: Installing some Update Packages ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu4 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun Jun 25 14:47:19 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-09 (19 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
** Changed in: dpkg (Ubuntu) Status: Fix Committed => New ** Changed in: openssl (Ubuntu) Status: Fix Committed => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1692981 Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: New Status in openssl package in Ubuntu: New Bug description: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libssl1.0.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 23 21:47:55 2017 DuplicateSignature: package:libssl-dev:amd64:1.0.2g-1ubuntu11.2 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ... dpkg: error processing package libssl-dev:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-15 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: openssl Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1692981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700955] Re: [GE620/GE620DX/FX620DX, Realtek ALC892, Speaker, Internal] Playback problem
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1700955 Title: [GE620/GE620DX/FX620DX, Realtek ALC892, Speaker, Internal] Playback problem Status in alsa-driver package in Ubuntu: New Bug description: when I play a music my speaker does not work well so that I can hear from one of my speakers. this just happened when I installed ubuntu. I have ubuntu for 6 month. I just endure this problem and now I have decided to report it. I have tried it with other music players as well but nothing changed. can you tell me how to fix this problem? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-81.104~14.04.1-generic 4.4.67 Uname: Linux 4.4.0-81-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nima 20707 F pulseaudio CurrentDesktop: Unity Date: Wed Jun 28 15:10:39 2017 InstallationDate: Installed on 2016-12-06 (203 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_Type: Only some of outputs are working Title: [GE620/GE620DX/FX620DX, Realtek ALC892, Speaker, Internal] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16G5IMS V1.0F dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16G5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.: dmi.product.name: GE620/GE620DX/FX620DX dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1700955/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
** Description changed: + === Begin SRU Template === + [Impact] + A cloud-config that contains packages to install (see below) or + 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a + result of contention with the apt-daily.service that updates that information. + + Cloud-config showing the problem is just like: + + $ cat my.yaml + #cloud-config + packages: ['hello'] + + [Test Case] + lxc-proposed-snapshot is + https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot + It publishes an image to lxd with proposed enabled and cloud-init upgraded. + + a.) launch an instance with proposed version of cloud-init and some user-data. +This is platform independent. The test case demonstrates lxd. +$ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ +"package_upgrade: true" > config.yaml +$ release=xenial +$ ref=proposed-$release + $ ./lxc-proposed-snapshot --proposed --publish $release $ref; + + b.) start the instance +$ name=$release-1693361 +$ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) + $ sleep 1 +$ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log +# watch this boot. + + c.) Look for evidence of systemd failure +journalctl -o short-precise | grep -i break +journalctl -o short-precise | grep -i order + + [Regression Potential] + Regression chance here is low. Its possible that ordering dependencies + could occur. When that does happen, journalctl will mention it. Unfortunately + in such cases systemd somewhat randomly picks a service to kil so behavior + is somewhat undefined. + + [Other Info] + Upstream commit at + https://git.launchpad.net/cloud-init/commit/?id=11121fe4 + + === End SRU Template === + apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: === Begin SRU Template === [Impact] A cloud-config that contains packages to install (see below) or 'package_upgrade' will run 'apt-get update'. That can sometimes fail as a result of contention with the apt-daily.service that updates that information. Cloud-config showing the problem is just like: $ cat my.yaml #cloud-config packages: ['hello'] [Test Case] lxc-proposed-snapshot is https://git.launchpad.net/~smoser/cloud-init/+git/sru-info/tree/bin/lxc-proposed-snapshot It publishes an image to lxd with proposed enabled and cloud-init upgraded. a.) launch an instance with proposed version of cloud-init and some user-data. This is platform independent. The test case demonstrates lxd. $ printf "%s\n%s\n%s\n" "#cloud-config" "packages: ['hello']" \ "package_upgrade: true" > config.yaml $ release=xenial $ ref=proposed-$release $ ./lxc-proposed-snapshot --proposed --publish $release $ref; b.) start the instance $ name=$release-1693361 $ lxc launch my-xenial "--config=user.user-data=$(cat config.yaml) $ sleep 1 $ lxc exec $name -- tail -f /var/log/cloud-init.log /var/log/cloud-init-output.log # watch this boot. c.) Look for evidence of systemd failure journalctl -o short-precise | grep -i break journalctl -o short-precise | grep
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Uploaded update-notifier 3.181 to fix this https://launchpad.net/ubuntu/+source/update-notifier/3.181 ** Changed in: update-notifier (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Committed Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: Unknown Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
I think we should fix this, but an SRU for this seems a bit too much. There's more important stuff pending since months. ** Changed in: update-notifier (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: aptitude (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Committed Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: Unknown Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701068] Re: motd is advertising HBO's Silicon Valley
** Changed in: base-files (Ubuntu) Assignee: (unassigned) => Dustin Kirkland (kirkland) ** Changed in: base-files (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd is advertising HBO's Silicon Valley Status in base-files package in Ubuntu: Triaged Bug description: The MOTD is advertising HBO's Silicon Valley. The MOTD should not be advertising anything. Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1604617] Re: dhclient does not send fqdn.fqdn for DHCPv6
I am also facing this issue. Your settings seems to fix it thank you. Just and a note the issue also exist in debain 9 -- 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/1604617 Title: dhclient does not send fqdn.fqdn for DHCPv6 Status in isc-dhcp package in Ubuntu: Confirmed Bug description: ISC DHCP's dynamic DNS updates rely on the fqdn.fqdn option being sent in order to work for DHCPv6. This used to be done in Ubuntu, as shown in bugs #991360 and #108862, and all my Windows hosts send it. However this was removed in Ubuntu due to a regression in IPv4 functionality. As IPv6 is more widely deployed these days, this regression in IPv6 should be fixed. This bug is current as of Ubuntu 16.04 LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1604617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
** Changed in: aptitude (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: New Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: Unknown Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701068] [NEW] motd is advertising HBO's Silicon Valley
Public bug reported: The MOTD is advertising HBO's Silicon Valley. The MOTD should not be advertising anything. Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: base-files (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug zesty ** Attachment added: "je8OSJU.png" https://bugs.launchpad.net/bugs/1701068/+attachment/4904878/+files/je8OSJU.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1701068 Title: motd is advertising HBO's Silicon Valley Status in base-files package in Ubuntu: New Bug description: The MOTD is advertising HBO's Silicon Valley. The MOTD should not be advertising anything. Welcome to Ubuntu 17.04 (GNU/Linux 4.10.0-21-generic x86_64) * Documentation: https://help.ubuntu.com * Management: https://landscape.canonical.com * Support:https://ubuntu.com/advantage * How HBO's Silicon Valley built "Not Hotdog" with mobile TensorFlow, Keras & React Native on Ubuntu - https://ubu.one/HBOubu ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 Date: Wed Jun 28 12:31:24 2017 InstallationDate: Installed on 2017-05-02 (56 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: base-files UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1701068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- 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/1623003 Title: udev-generated /dev/disk/by-path names broken for virtio disks Status in systemd: Unknown Status in Ubuntu on IBM z Systems: Fix Released Status in systemd package in Ubuntu: Fix Released Bug description: The udev-generated /dev/disk/by-path names for virtio disks are broken on z Systems as they have the format virtio-pci-h.h.[-partn], where h.h. is the CCW devno of the virtio device representing the whole disk. Historically, the standard CCW naming was applied, which was ccw-h.h.[-partn] ---uname output--- Linux ubuntu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = 2964-703 running KVM for IBM z Systems ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu LTS 16.04.1 on KVM for IBM z Systems 1.1.1 2. Issue ls -l /dev/disk/by-path Userspace tool common name: udev The userspace tool has the following bit modes: 64-bit Userspace rpm: udev Userspace tool obtained from project website: na There are basically two problems with this: 1. The naming is technically incorrect, since the virtio devices on z are no PCI devices but CCW devices 2. Then naming based on virtio- is backwards incompatible. This may seem not to be an issue for Xenial but customers may be confused if they have been running Linux on KVM for IBM z before. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1623003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
@nc-duenkekl3
>Watch out, most of the time, it is a security hole, to run something as root.
>Privilege escalation is not something funny.
APT was executed as root for years, is not it?
Moreover root user is used as fallback or something (see
https://git.launchpad.net/~usd-import-team/ubuntu/+source/apt/tree/apt-
pkg/acquire.cc?h=ubuntu/xenial-updates#n593 ). I'm not an author of this code.
Can you or maintainers suggest better solution?
Without sandboxing I get the following process tree (in htop):
USER COMMAND
root apt-get install ...
rootdpkg ...
root sh ... postinst
rootpython3 .../package-data-downloader
root apt-helper download-file ...
roothttp
So 6 processes are run by root user.
With sandboxing I get the following process tree:
USER COMMAND
root apt-get install ...
rootdpkg ...
root sh ... postinst
rootpython3 .../package-data-downloader
root apt-helper download-file ...
_apt (*)http
So only http (1/6) is called by _apt user. Is it really safer?
apt-get, dpkg, sh, python3, apt-helper may be vulnerable too (5/6 likelihood).
Http process download file, not execute it.
Downloadable file
(/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20170616.1.orig.tar.gz
for example) has executable bit disabled for all users ("-rw-r--r-- 1 root
root" or "-rw-r--r-- 1 _apt nogroup").
As far I can understand its contents will be checked by hash before installing.
Aptitude is affected too. And bug
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806595 was fixed in it.
Bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813786 in apt was fixed
too.
So I think that we need SRU for apt and aptitude.
** Also affects: synaptic (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808802
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1522675
Title:
Warning messages about unsandboxed downloads
Status in apt package in Ubuntu:
Fix Released
Status in aptitude package in Ubuntu:
New
Status in synaptic package in Ubuntu:
Triaged
Status in update-notifier package in Ubuntu:
Triaged
Status in apt package in Debian:
Fix Released
Status in aptitude package in Debian:
Unknown
Status in synaptic package in Debian:
Unknown
Bug description:
Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but
now get that error when installing/upgrading some packages:
Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ...
Processing triggers for libc-bin (2.21-0ubuntu5) ...
W: Can't drop privileges for downloading as file
'/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. -
pkgAcquire::Run (13: Permission denied)
From nautilus, i'm seeing a /root/ folder locked (x on its icon) and
the folder is empty (no /.synaptic/ sub-folder or file), so the above
error.
oem@u64:~$ ls -l .synaptic
total 4
-rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options
-rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf
oem@u64:~$ ls -l /var/lib/apt/lists/
-rw-r- 1 root root0 Sep 20 06:36 lock
drwx-- 2 _apt root16384 Sep 24 15:25 partial
..
oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/
.
drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: synaptic 0.82+build1
ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0
Uname: Linux 4.3.0-1-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.2-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Dec 4 05:23:25 2015
SourcePackage: synaptic
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701053] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1701053/+attachment/4904876/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Also affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Changed in: alsa-driver (Ubuntu) Status: New => Opinion ** No longer affects: alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1701053 Title: Sound Interrupts with Gigabyte H97-D3H on Linux in General Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 16.04.2 LTS Release: 16.04 apt-cache policy pkgname Not Working Hello Community i have a big Problem with Linux in General. atm im Running Ubuntu 16.04 My Problem is at every Kernel i get Sound interrupts with my Onboard Chip ALC 1150 The Sound Stutterst or Loop for a sec is thre a Way how to fix it ? --- ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4de378c1-3c56-4b69-8070-23a6055d504f InstallationDate: Installed on 2017-06-27 (0 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. H97-D3H NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic.efi.signed root=UUID=b705a630-f436-4c7c-a6ee-8fc2d022497b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-56-generic N/A linux-backports-modules-4.8.0-56-generic N/A linux-firmware1.157.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: xenial Uname: Linux 4.8.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: H97-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1701053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318834] Re: Applications can no longer access your @gmail.com Online Account
"Applications can no longer access your [gmail address]. Choose Online Accounts from the user menu to reinstate access to this account." This bug is still present in 17.04 with Gnome. I don't think it was an issue until I entered the information for my Google account in Online Accounts. Now, the error pops up at every login and is quite annoying. I have tried to remove it, add it again, remove it and remove authorization via Google as well as adding it and turning off all applications. Nothing works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-control-center- signon in Ubuntu. https://bugs.launchpad.net/bugs/1318834 Title: Applications can no longer access your @gmail.com Online Account Status in gnome-control-center-signon package in Ubuntu: Confirmed Bug description: IN start UBUNTU Application can no longer access your dumetz1...@gmail.com Online Account. Choose online Accounts from the user menu to reinstale access to this account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1318834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
** Also affects: aptitude (Ubuntu) Importance: Undecided Status: New ** Bug watch added: Debian Bug tracker #806595 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806595 ** Also affects: aptitude (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806595 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: New Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Unknown Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692981] Re: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
** Changed in: dpkg (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: openssl (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1692981 Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in dpkg package in Ubuntu: Fix Committed Status in openssl package in Ubuntu: Fix Committed Bug description: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libssl-dev:amd64 1.0.2g-1ubuntu11.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 AptOrdering: libssl1.0.0:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 23 21:47:55 2017 DuplicateSignature: package:libssl-dev:amd64:1.0.2g-1ubuntu11.2 Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu11.2) ... dpkg: error processing package libssl-dev:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-15 (7 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: openssl Title: package libssl-dev:amd64 1.0.2g-1ubuntu11.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1692981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
I don't think it's hard to fix at all, the directory just needs to be owned by _apt instead of root. But if everyone just complains and does not put any work into it, nothing gets done. There's more important stuff going on. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1173926] Re: unable to search for google drive documents in raring 13.04
** Changed in: libgdata (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgdata in Ubuntu. https://bugs.launchpad.net/bugs/1173926 Title: unable to search for google drive documents in raring 13.04 Status in libgdata: Fix Released Status in Online Accounts: Sign-on UI: Fix Released Status in Online Accounts setup for Ubuntu Touch: Fix Released Status in Google Documents Lens: Fix Released Status in webapps-sprint: Fix Released Status in libgdata package in Ubuntu: Fix Released Bug description: After setting up the online account, and verified by logging into google, I try to search my file in google drive, but it is not working. It works on Ubuntu 12.10, even without search, the dash would show the latest documents from google drive. from system monitor, I can see unity-scope-gdrive in the acting list. To manage notifications about this bug go to: https://bugs.launchpad.net/libgdata/+bug/1173926/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution
** Merge proposal linked: https://code.launchpad.net/~smoser/cloud-init/+git/cloud-init/+merge/326452 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1693361 Title: cloud-init sometimes fails on dpkg lock due to concurrent apt- daily.service execution Status in APT: Confirmed Status in cloud-init: Confirmed Status in apt package in Ubuntu: New Status in cloud-init package in Ubuntu: Fix Released Status in cloud-init source package in Xenial: Confirmed Status in cloud-init source package in Yakkety: Confirmed Status in cloud-init source package in Zesty: Confirmed Status in cloud-init source package in Artful: Fix Released Bug description: apt-daily is now a systemd service rather than being invoked by cron.daily. If one builds a custom AMI it is possible that the apt- daily.timer will fire during boot. This can fire at the same time cloud-init is running and if cloud-init loses the race the invocation of apt (e.g. use of "packages:" in the config) will fail. There is a lot of discussion online about this change to apt-daily (e.g. unattended upgrades happening during business hours, delaying boot, etc.) and discussion of potential systemd changes regarding timers firing during boot (c.f. https://github.com/systemd/systemd/issues/5659). While it would be better to solve this in apt itself, I suggest that cloud-init be defensive when calling apt and implement some retry mechanism. Various instances of people running into this issue: https://github.com/chef/bento/issues/609 https://clusterhq.atlassian.net/browse/FLOC-4486 https://github.com/boxcutter/ubuntu/issues/73 https://unix.stackexchange.com/questions/315502/how-to-disable-apt-daily-service-on-ubuntu-cloud-vm-image To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1693361/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
"It's not like you get hundreds of them each day." True. But even one such message puzzles and worries users. 360 users have marked this bug, but imagine how many thousands don't even know to look on Launchpad? This report was filed 18 months ago. I don't doubt it's hard to fix it for systems that have been upgraded. But this affects a fresh install of 16.04.2. Is it hard to make _apt the owner of .../package-data- downloads/partial/ when Ubuntu is freshly installed? I'm sure some of us reporting this bug come across as whiners, part of the problem, not part of the solution. Chippendale didn't send out furniture with splinters, he was passionate about quality. We're passionate about Linux. That's why we go to the trouble of reporting bugs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)
I also have this problem running Ubuntu 17.04 with a TrendNet TEW-644UB USB WiFi stick (ID 148f:2770 Ralink Technology, Corp. RT2770 Wireless Adapter). The symptoms are that it sees the networks but won't connect, even if unencrypted. The workaround in #1 also works for me. Many thanks, Jesse. This bug shouldn't be in a final release and it is inexcusable that it still hasn't been corrected two months later. I expect that, like me, many people have wasted a lot of time before finding this workaround. (I even ordered a new USB WiFi stick.) -- 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/1681513 Title: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue) Status in network-manager package in Ubuntu: Confirmed Bug description: According to https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/ there is a new privacy feature in the new version of NetworkManager. This privacy feature can cause some USB WiFi adapters to stop working while they used to work with older versions of NetworkManager (Ubuntu 16.10 or older). The purpose of this privacy feature is to get your computer to report a new random MAC address whenever you connect to a WiFi network. This privacy feature is especially useful when you connect to public WiFi networks, so that the operators cannot identify you when you connect multiple times. The downside of this privacy feature is that some USB WiFi adapters misbehave when NetworkManager tries to change their MAC address repeatedly. The result is that those USB WiFi adapters cannot connect anymore to the WiFi network. Original report follows: My Panda USB wi-fi adapter works just fine on 16.10, but when I try to connect to my wi-fi router in 17.04, GNOME network manager reports "Connection failed." I did some tinkering, and noticed that my MAC address for my wifi adapter, according to GNOME, is DIFFERENT every time I make it forget my wifi settings and try to reconnect. Weird, right? Any leads on a possible fix or work-around? I'm running the latest beta of Ubuntu GNOME 17.04, kernel 4.10.0-19-generic, GNOME 3.24.0. https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in- networkmanager-1-4-0/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1681513/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701039] [NEW] e
Public bug reported: w ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 19:25:44 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504] NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 540M] [1025:0505] InstallationDate: Installed on 2017-06-27 (0 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: Acer Aspire 5755G ProcEnviron: LANGUAGE=it PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-24-generic root=UUID=20d8cc6f-f587-4814-ab9d-bdcac4687018 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/09/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.21 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV51_HR dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.21 dmi.modalias: dmi:bvnAcer:bvrV1.21:bd08/09/2012:svnAcer:pnAspire5755G:pvrV1.21:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.21: dmi.product.name: Aspire 5755G dmi.product.version: V1.21 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.14-0ubuntu1 xserver.bootTime: Wed Jun 28 18:35:35 2017 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu zesty -- 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/1701039 Title: e Status in xorg package in Ubuntu: New Bug description: w ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 375.66 Mon May 1 15:29:16 PDT 2017 GCC version: gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2) .tmp.unity_support_test.0: ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 19:25:44 2017 DistUpgraded: Fresh install DistroCodename: zesty DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family Integrated Graphics Controller [1025:0504]
[Touch-packages] [Bug 1623003] Re: udev-generated /dev/disk/by-path names broken for virtio disks
Was not mentioned in debian/changelog but this is part of v233 release and thus is fix released in artful, and is present in the below mentioned uploads: ubuntu/233-5ubuntu1 ubuntu/233-6ubuntu1 ubuntu/233-6ubuntu2 ubuntu/233-6ubuntu3 ubuntu/233-8ubuntu1 ubuntu/233-8ubuntu2 ** Changed in: systemd (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1623003 Title: udev-generated /dev/disk/by-path names broken for virtio disks Status in systemd: Unknown Status in Ubuntu on IBM z Systems: Fix Committed Status in systemd package in Ubuntu: Fix Released Bug description: The udev-generated /dev/disk/by-path names for virtio disks are broken on z Systems as they have the format virtio-pci-h.h.[-partn], where h.h. is the CCW devno of the virtio device representing the whole disk. Historically, the standard CCW naming was applied, which was ccw-h.h.[-partn] ---uname output--- Linux ubuntu 4.4.0-36-generic #55-Ubuntu SMP Thu Aug 11 18:05:09 UTC 2016 s390x s390x s390x GNU/Linux Machine Type = 2964-703 running KVM for IBM z Systems ---Debugger--- A debugger is not configured ---Steps to Reproduce--- 1. Install Ubuntu LTS 16.04.1 on KVM for IBM z Systems 1.1.1 2. Issue ls -l /dev/disk/by-path Userspace tool common name: udev The userspace tool has the following bit modes: 64-bit Userspace rpm: udev Userspace tool obtained from project website: na There are basically two problems with this: 1. The naming is technically incorrect, since the virtio devices on z are no PCI devices but CCW devices 2. Then naming based on virtio- is backwards incompatible. This may seem not to be an issue for Xenial but customers may be confused if they have been running Linux on KVM for IBM z before. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1623003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701033] [NEW] no tengo sonido
Public bug reported: al instalar elementari OS ME ENCUENTRO SIN SONIDO EN EL ORDENADOR , que puede pasar? ProblemType: Bug DistroRelease: elementary 0.4.1 Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: /dev/sda1: clean, 283988/2138112 files, 2119562/8544768 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 28 18:40:33 2017 DistUpgraded: Fresh install DistroCodename: loki DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.8.0-54-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.8.0-56-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0412] InstallationDate: Installed on 2017-06-04 (24 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=b6eadee4-6ca4-4c76-8037-cbb775c7f6e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00 dmi.board.name: H97M Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.00:bd07/27/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH97MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jun 28 18:39:24 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug loki third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1701033 Title: no tengo sonido Status in xorg package in Ubuntu: New Bug description: al instalar elementari OS ME ENCUENTRO SIN SONIDO EN EL ORDENADOR , que puede pasar? ProblemType: Bug DistroRelease: elementary 0.4.1 Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu] ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 BootLog: /dev/sda1: clean, 283988/2138112 files, 2119562/8544768 blocks CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jun 28 18:40:33 2017 DistUpgraded: Fresh install DistroCodename: loki DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.8.0-54-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.8.0-56-generic, x86_64: installed GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASRock Incorporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1849:0412] InstallationDate: Installed on 2017-06-04 (24 days ago) InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20170517) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-56-generic root=UUID=b6eadee4-6ca4-4c76-8037-cbb775c7f6e8 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.00
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Just live with the warnings until somebody fixes them. Or give _apt rwx access to /var/lib/update-notifier/package-data-downloads/partial, that's safe. It's not like you get hundreds of them each day. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
I need to correct my previous statement. It looks like skypeforlinux is actually starting the gnome-keyring-daemon --start --foreground --components=secrets command line, it is not there at boot. The gnome-keyring-daemon --daemonize --login command line seems to sometimes be there and sometimes not, on all machines. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1689825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1276796] Re: Long hostname placeholder for PS1 (\H) fails in Bash
This problem doesn't occur in Ubuntu 16.04 LTS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1276796 Title: Long hostname placeholder for PS1 (\H) fails in Bash Status in bash package in Ubuntu: Confirmed Bug description: When using "\H" in the PS1 prompt value bash is not displaying the FQDN but instead only the short form hostname. This is the same as "\h". Issue has also been noted at http://serverfault.com/questions/296970/bash-prompt-on-ubuntu-fqdn-h-same-as-hostname-h https://answers.launchpad.net/ubuntu/+source/bash/+question/200900 This appears related to /etc/hostname only having the host and not the FQDN. Bash should obtain the \H value from somewhere other than /etc/hostname. --- ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 DistroRelease: Ubuntu 13.10 InstallationDate: Installed on 2014-01-16 (20 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016) MarkForUpload: True Package: bash 4.2-5ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10 Tags: saucy Uname: Linux 3.11.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1276796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456670] Re: insserv: Service mountdevsubfs has to be enabled to start service hwclock
** Summary changed: - debootstrap failure: insserv: Service mountdevsubfs has to be enabled to start service hwclock + insserv: Service mountdevsubfs has to be enabled to start service hwclock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1456670 Title: insserv: Service mountdevsubfs has to be enabled to start service hwclock Status in sysvinit package in Ubuntu: Fix Released Status in sysvinit source package in Wily: Fix Released Bug description: Since today, debootstrap'ing wily is broken: W: Failure while configuring required packages. W: See /tmp/wily/debootstrap/debootstrap.log for details (possibly the package util-linux is at fault) Setting up util-linux (2.26.2-3ubuntu1) ... update-alternatives: using /bin/more to provide /usr/bin/pager (pager) in auto mode insserv: Service mountdevsubfs has to be enabled to start service hwclock insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package util-linux (--configure): subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1456670/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Watch out, most of the time, it is a security hole, to run something as root. Privilege escalation is not something funny. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689825] Re: gnome-keyring not unlocked on boot
I experience the same problem on Manjaro Linux with gnome-keyring 3.20.0+57+g9db67ef6 and skypeforlinux. So it seems to be a bug in gnome- keyring, not in Ubuntu's package. Some observations (citing my post on the Manjaro forums https://forum.manjaro.org/t/skypeforlinux-weird-and-inconsistent- authentification-behaviour/26076): I read that the old Skype client will stop working on Juli 1st, that is in less than two weeks, so I switched to the new client on several machines. However, the new client behaves in a weird way on starting up: 1. On some machines the user gets logged in without being asked for his password 2. On some machines the user gets a gnome-keyring password dialogue 3. On some machines the user has to enter the complete Skype user name and password into the Skype client itself In the ideal world I would like to have all machines behave as in 1. But how to do so? Does anybody else experience the same problem? I have digged deeper into this issue. It turned out that the gnome- keyring-daemon is running with different command lines in the three cases. Case 1: gnome-keyring-daemon --start --foreground --components=secrets (on my Manjaro laptop) gnome-keyring-daemon --start (on my old Arch install) Case2: gnome-keyring-daemon is not running at all. It is then launched when skypeforlinux is started and needs a password to unlock the keyring. Case3: gnome-keyring-daemon --daemonize --login So there seem to be two problems: First, the problem that gnome-keyring- daemon is not launched at login at all, second, if it is launched, it is launched with a bad command line. I looked in the Xfce session settings and there is an entry for gnome- keyring-daemon with the correct (Case 1) command line, but it is not activated. I activated it, but it seems to have changed nothing, gnome- keyring is still launched with the wrong command line. It looks like it is started by some system wide service and then the Xfce session settings entry collides with the already running instance. But what is this system wide service and why does it use the wrong command line on some machines but the right command line on others? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1689825 Title: gnome-keyring not unlocked on boot Status in chromium-browser package in Ubuntu: Invalid Status in gnome-keyring package in Ubuntu: Confirmed Status in libgnome-keyring package in Ubuntu: Confirmed Bug description: 1) Release: 16.04.2 2) gnome-keyring: 3.18.3-0ubuntu2 3) Login. gnome-keyring unlocks "login" features including for google chrome 4) gnome-keyring is not unlocked, chrome takes 2 minutes to open and with no secure password features(sync) functioning. For the past couple days, chrome on Ubuntu 16.04 takes a REALLY long time (maybe 2 minutes) to start. Once chrome is started, I am not able to sync and any secure password features are broken. I found out this is due to gnome-keyring not being unlocked at login. There's also no way to unlock the "login" portion of the keyring from the running daemon by default. I have to kill the gnome-keyring process and start without "--login" as a parameter. Then the "login" section shows up which I'm able to unlock. From there chrome starts up instantly but asks the following: Enter password to unlock your login keyring The login keyring did not get unlocked when you logged into your computer After that, all of it's sync and secure features are functional. Starting google-chrome-stable from a command line at boot without running the above workaround shows the following error messages: Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Gkr-Message: secret service operation failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4364:4393:0510/100407.740292:ERROR:token_service_table.cc(130)] Failed to decrypt token for service AccountId-108842767310111573264 [4364:4445:0510/100407.740292:ERROR:gcm_store_impl.cc(929)] Failed to restore security token. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-keyring 3.18.3-0ubuntu2 ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Wed May 10 09:43:37 2017 SourcePackage: gnome-keyring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Touch-packages] [Bug 1701004] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1456670 *** https://bugs.launchpad.net/bugs/1456670 ** This bug has been marked a duplicate of bug 1456670 insserv: Service mountdevsubfs has to be enabled to start service hwclock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701004 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: Got this bug on xenial during installing of upgrades $ sudo apt-get upgrade -f Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: gir1.2-nautilus-3.0 libblkid1 libfdisk1 libmount1 libnautilus-extension-dev libnautilus-extension1a libsmartcols1 libuuid1 libuuid1:i386 mount nautilus nautilus-data uuid-dev uuid-runtime 14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/1 272 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up util-linux (2.27.1-6ubuntu3.3) ... insserv: Service mountdevsubfs has to be enabled to start service hwclock insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package util-linux (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 28 18:00:45 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2010-12-05 (2396 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-06-24 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701003] Re: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701003 Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: unable to run android emulator when we run the application, android emulator is not lunching due to some lib issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 17:21:53 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-06-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701004] [NEW] package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1456670 *** https://bugs.launchpad.net/bugs/1456670 Public bug reported: Got this bug on xenial during installing of upgrades $ sudo apt-get upgrade -f Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: gir1.2-nautilus-3.0 libblkid1 libfdisk1 libmount1 libnautilus-extension-dev libnautilus-extension1a libsmartcols1 libuuid1 libuuid1:i386 mount nautilus nautilus-data uuid-dev uuid-runtime 14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/1 272 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up util-linux (2.27.1-6ubuntu3.3) ... insserv: Service mountdevsubfs has to be enabled to start service hwclock insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package util-linux (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 28 18:00:45 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2010-12-05 (2396 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-06-24 (3 days ago) ** Affects: util-linux (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 util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701004 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: Got this bug on xenial during installing of upgrades $ sudo apt-get upgrade -f Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: gir1.2-nautilus-3.0 libblkid1 libfdisk1 libmount1 libnautilus-extension-dev libnautilus-extension1a libsmartcols1 libuuid1 libuuid1:i386 mount nautilus nautilus-data uuid-dev uuid-runtime 14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/1 272 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up util-linux (2.27.1-6ubuntu3.3) ... insserv: Service mountdevsubfs has to be enabled to start service hwclock insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package util-linux (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 28 18:00:45 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2010-12-05 (2396 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-06-24 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701004] Re: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1456670 *** https://bugs.launchpad.net/bugs/1456670 ** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1701004 Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in util-linux package in Ubuntu: New Bug description: Got this bug on xenial during installing of upgrades $ sudo apt-get upgrade -f Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: gir1.2-nautilus-3.0 libblkid1 libfdisk1 libmount1 libnautilus-extension-dev libnautilus-extension1a libsmartcols1 libuuid1 libuuid1:i386 mount nautilus nautilus-data uuid-dev uuid-runtime 14 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. Need to get 0 B/1 272 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up util-linux (2.27.1-6ubuntu3.3) ... insserv: Service mountdevsubfs has to be enabled to start service hwclock insserv: exiting now! update-rc.d: error: insserv rejected the script header dpkg: error processing package util-linux (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: util-linux E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3.3 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 28 18:00:45 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2010-12-05 (2396 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: util-linux Title: package util-linux 2.27.1-6ubuntu3.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2017-06-24 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1701004/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701005] [NEW] sporadic defunct of network-manager after standby
Public bug reported: ubuntu version: Ubuntu 16.04.2 LTS network-manager version: 1.2.6-0ubuntu0.16.04.1 After the dist-upgrade to Ubuntu 16.04 the network-manager seems to be dead sometimes after returning from the standby. I am not completely sure that it is really the network-manager but sudo /etc/init.d/network-manager restart helps. After that, the WLAN is available again. The bug occurs only in 1 of 10 cases. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1701005 Title: sporadic defunct of network-manager after standby Status in network-manager package in Ubuntu: New Bug description: ubuntu version: Ubuntu 16.04.2 LTS network-manager version: 1.2.6-0ubuntu0.16.04.1 After the dist-upgrade to Ubuntu 16.04 the network-manager seems to be dead sometimes after returning from the standby. I am not completely sure that it is really the network-manager but sudo /etc/init.d/network-manager restart helps. After that, the WLAN is available again. The bug occurs only in 1 of 10 cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1701005/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1654448] Re: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss
Kai: Confirmed my assumption, your patch SIGNIFICANTLY lowers the output volume! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1654448 Title: XPS 13 9360 and 9350, Realtek ALC3246, Headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1701003] [NEW] package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Public bug reported: unable to run android emulator when we run the application, android emulator is not lunching due to some lib issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 17:21:53 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-06-26 (1 days ago) ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1701003 Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in systemd package in Ubuntu: New Bug description: unable to run android emulator when we run the application, android emulator is not lunching due to some lib issue ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libpam-systemd:amd64 232-21ubuntu5 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 17:21:53 2017 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2017-06-02 (26 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: systemd Title: package libpam-systemd:amd64 232-21ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to zesty on 2017-06-26 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701003/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
I removed warning messages by setting APT::Sandbox::User to "root" with cat
[Touch-packages] [Bug 1569925] Re: Shutdown hang on 16.04 with iscsi targets
I can confirm that the daily 17.10 build does not exhibit the problem. Interestingly, the first time we tried we forgot to stop running IO to our iSCSI volumes and it _looked_ like we reproduced the problem, then the IOs timed out and our application stopped and we were able to complete the reboot. The next time we retried and correctly stopped our application before shutting down and had no issue. Whatever it is, is fixed in 17.10. -- 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/1569925 Title: Shutdown hang on 16.04 with iscsi targets Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Confirmed Bug description: I have 4 servers running the latest 16.04 updates from the development branch (as of right now). Each server is connected to NetApp storage using iscsi software initiator. There are a total of 56 volumes spread across two NetApp arrays. Each volume has 4 paths available to it which are being managed by device mapper. While logged into the iscsi sessions all I have to do is reboot the server and I get a hang. I see a message that says: "Reached target Shutdown" followed by "systemd-shutdown[1]: Failed to finalize DM devices, ignoring" and then I see 8 lines that say: "connection1:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection2:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection3:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection4:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection5:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection6:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection7:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" "connection8:0: ping timeout of 5 secs expired, recv timeout 5, last rx 4311815***, last ping 43118164**, now 4311817***" NOTE: the actual values of the *'s differ for each line above. This seems like a bug somewhere but I am unaware of any additional logging that I could turn on to pinpoint the problem. Note I also have similar setups that are not doing iscsi and they don't have this problem. Here is a screenshot of what I see on the shell when I try to reboot: (https://launchpadlibrarian.net/291303059/Screenshot.jpg) This is being tracked in NetApp bug tracker CQ number 860251. If I log out of all iscsi sessions before rebooting then I do not experience the hang: iscsiadm -m node -U all We are wondering if this could be some kind of shutdown ordering problem. Like the network devices have already disappeared and then iscsi tries to perform some operation (hence the ping timeouts). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1569925/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700949] Re: manpage is incomplete
The only mention is within the "Packetfilter HOWTO" at the chapter "7.3 Filtering specification". See http://iptables.netfilter.org/documentation/HOWTO/packet-filtering-HOWTO-7.html Quote: > iptables is extensible, meaning that both the kernel and the iptables tool can be extended to provide new features. and > The TCP extensions are automatically loaded if `-p tcp' is specified. Those are "standard extensions" that get loaded automatically. Maybe I am wrong, but those options should be into the man page! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1700949 Title: manpage is incomplete Status in iptables package in Ubuntu: Confirmed Bug description: At least the "--dport" option is missing from both the man page and the --help command option. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iptables 1.6.0-2ubuntu3 Uname: Linux 4.11.6-041106-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 28 11:45:45 2017 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1700949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
** Branch linked: lp:~ubuntu-desktop/gnome-session/ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1610944 Title: GNOME Online Accounts breaks if you log out (until you reboot) Status in gnome-online-accounts: Confirmed Status in Ubuntu GNOME: Triaged Status in gnome-online-accounts package in Ubuntu: Triaged Status in gnome-session package in Ubuntu: Fix Released Status in gnome-online-accounts source package in Yakkety: Triaged Status in gnome-session source package in Yakkety: In Progress Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Won't Fix Bug description: Impact == After logging out, GNOME Online Accounts doesn't work the next time you log in. This bug was a Release Blocker for Fedora 26. (Fedora 26 will be released in July). gnome-session is the only package updated in this update (not gnome- online-accounts). Test Case = From Ubuntu GNOME, click Settings>Online Accounts and add your Google account. Install Evolution if it's not installed. Verified that your Google account has synced. Log out. Log in. It may help to reproduce the bug log in to a different session (GNOME on Wayland instead of GNOME, or the other way around). Open Evolution. Verify that no errors are reported and that your Google account is still syncing. After installing the gnome-session update, I recommend rebooting once to clear any old lingering GNOME Online Accounts processes from previous sessions. Regression Potential This fix is the same as was accepted into Fedora 26. It is a workaround by killing all the user's D-Bus sessions when the user logs out. This fix has been backported from gnome-session 3.25.3. It has not been applied to the 3.24 git branch upstream. Since 16.10 has almost reached its end of life (July), I am not proposing this fix there. I believe 16.10 is the first release affected since Ubuntu moved many more services to systemd user sessions in that release. The patch tries to only kill the D-Bus sessions if the session being logged out is the final remaining session for the user. The workaround makes sense to me. It seems similar to the KillUserProcesses option that was pushed into systemd to fix this kind of problem but it's more limited than the systemd method so hopefully it won't be as controversial. Original Bug Report === Can't add any online accounts in after opened Online accounts + mark is faded, can't click. After reinstalled gnome-online-accounts still has same problem. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: gnome-online-accounts 3.20.3-1 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu5 Architecture: amd64 CurrentDesktop: Budgie:GNOME Date: Mon Aug 8 15:33:45 2016 SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700944] Re: less display is broken when using option to show line numbers
Thank you for taking the time to report this bug and helping to make Ubuntu better. I tried with a some files, but I couldn't reproduce this issue. Could you attach one of the files that are affected by this problem? Of course, be sure to provide a file with no sensible information in it. This will help us to find and resolve the problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1700944 Title: less display is broken when using option to show line numbers Status in less package in Ubuntu: New Bug description: hi, in my .bashrc I have recently added: alias less='less -r -N' Now, msot of the time, when I open a file, less displays the file starting at line 2 (sometimes even at line 38 or more), with no possibility to go up in the file. Using "-n " in less started with -N does not solve the problem. As soon as I remove the options (particularly -N) the behaviour is OK again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1700944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700949] Re: manpage is incomplete
Oddly enough, the official man page at http://ipset.netfilter.org/iptables.man.html is also lacking such information! :-( -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1700949 Title: manpage is incomplete Status in iptables package in Ubuntu: Confirmed Bug description: At least the "--dport" option is missing from both the man page and the --help command option. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iptables 1.6.0-2ubuntu3 Uname: Linux 4.11.6-041106-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 28 11:45:45 2017 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1700949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700590] Re: libmount-dev reports version "2.29."
Found relevant information in util-linux sources: libmount/src/libmount.h: #define LIBMOUNT_VERSION "2.29." #define LIBMOUNT_MAJOR_VERSION 2 #define LIBMOUNT_MINOR_VERSION 29 #define LIBMOUNT_PATCH_VERSION -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1700590 Title: libmount-dev reports version "2.29." Status in util-linux package in Ubuntu: New Bug description: "pkg-config --modversion mount" reports version "2.29." which breaks meson build: Meson encountered an error in file meson.build, line 636, column 0: Invalid version to compare against: '2.29.'; only numeric digits separated by "." are allowed: invalid literal for int() with base 10: '' Actual version of libmount-dev is 2.29-1ubuntu2 It's ubuntu 17.04 (Sorry for posting into util-linux, launchpad thinks that "libmount- dev" does not exist in Ubuntu) ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: libmount-dev 2.29-1ubuntu2 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Mon Jun 26 18:32:50 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-20 (5 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1700590/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700949] Re: manpage is incomplete
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: iptables (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1700949 Title: manpage is incomplete Status in iptables package in Ubuntu: Confirmed Bug description: At least the "--dport" option is missing from both the man page and the --help command option. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iptables 1.6.0-2ubuntu3 Uname: Linux 4.11.6-041106-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 28 11:45:45 2017 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1700949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while
I am also on Ubuntu 170.04 (Kernel 4.10.0-24-generic) and this headphone issue is driving me crazy. I would like to know if there is a workaround to move the sound to headphones forever? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1575078 Title: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: I'm experiencing a strange behavior with a headphone jack on my laptop. I have an external audio speaker connected to it. When I disconnect the speaker and reconnect it again it stops working. Even more, laptop audio stops working too. And after the reboot, I don't even see any of the audio devices. I've googled a lot and tried different fixes from forums with no luck. After a while, I've accidentally discovered that putting the laptop to the sleep mode and rebooting system after brings audio back to live. Even more, if speakers were attached during this sleep-reboot procedure, they are starting to work as well. However, after the next reboot speakers are not working again. And if I will plug them out and in - problem with completely missing audio returns. P.S. I'm using laptop-mode-tools package on my laptop. Recovery after hibernation made me believe that it's somehow related. But after uninstalling this package nothing really changed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: kop3224 F...m pulseaudio /dev/snd/controlC0: kop3224 F pulseaudio CurrentDesktop: Unity Date: Tue Apr 26 12:17:03 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2016-04-22 (3 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Встроенное аудио - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Sound works for a while, then breaks Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698437] Re: Please upload libgdata 0.17.8
** Also affects: libgdata (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: libgdata (Ubuntu Zesty) Importance: Undecided => Low ** Changed in: libgdata (Ubuntu) Importance: Undecided => Low ** Changed in: libgdata (Ubuntu) Status: Confirmed => Fix Committed ** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgdata in Ubuntu. https://bugs.launchpad.net/bugs/1698437 Title: Please upload libgdata 0.17.8 Status in libgdata package in Ubuntu: Fix Committed Status in libgdata source package in Zesty: New Bug description: libgdata 0.17.8 was released on April 20. Please upload the new version for Ubuntu. Once it gets into Artful, it can be uploaded into zesty as well as SRU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgdata/+bug/1698437/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5
By the time BLKRRPART returns the partition device nodes should have been created in devtmpfs, so there shouldn't be any need to wait for things to settle. I'm not sure where a race could exist. Yet it's odd that this failed only for ppc since all the code which deals with this is generic, not platform-specific. It would be nice if we had dmesg, unfortunately we do not. I'm re-running the test just to see if it happens consistently. We have a ppc test machine, however it's currently occupied running tests. Once it's free I can do some testing there. -- 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/1700806 Title: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5 Status in systemd package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Norbert and David, those sort of messages just clutter up people's inboxes and annoy the people who get the messages, if you want to help get this bug fixed faster you should probably work out what the issue is by reading the rest of comments on this bug ticket and then contacting people direct with your preferred solution or implement it yourselves. Saying 'it's so bad this bug hasn't been fixed, ugh, someone really should fix this!' does not help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1667407] Re: improve 2x-3x sha256sum performance on ppc64le due to current gcc optimization bug
@doko I already added the verification-done-xenial tag so I guess that's all that's needed to do, right? ** Tags removed: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1667407 Title: improve 2x-3x sha256sum performance on ppc64le due to current gcc optimization bug Status in coreutils package in Ubuntu: Fix Released Status in coreutils source package in Xenial: Fix Committed Status in coreutils source package in Yakkety: Fix Released Status in coreutils package in Debian: Fix Released Bug description: [Impact] * Performance drop of 2x-3x on ppc64le when using sha256sum * Please backport this bug to last LTS as this application is widely used. * This fix is due to a optimization issue found on gcc v4.9 to gcc v7.0. [Test Case] * Run sha256sum with a big file and measure the time it takes. The patch improves this timing up to 3 times faster. [Regression Potential] * This patch is specifically for the sha256.o object, affecting only this binary. [Other Info] Michael Stone's improved patch: Index: coreutils-8.26/Makefile.in === --- coreutils-8.26.orig/Makefile.in 2016-11-30 13:34:55.0 -0500 +++ coreutils-8.26/Makefile.in 2017-02-22 07:18:55.352394058 -0500 @@ -14661,6 +14661,10 @@ $(TEST_LOGS): $(PROGRAMS) +ifeq ($(DEB_TARGET_ARCH), ppc64el) +lib/sha256.o: CFLAGS+=-fno-schedule-insns +endif + # Tell versions [3.59,3.63) of GNU make to not export all variables. # Otherwise a system limit (for SysV at least) may be exceeded. .NOEXPORT: Original bug description: The sha256sum provided by coreutils (without openssl) is performing poorly with gcc versions >= 4.9 until 7.0 (currently under development). The reason for that is the -fschedule-insns optimization that is used with -O2. By simply deactivating it, there is a performance improvement of 2 to 3 times. I'm using Ubuntu 16.10 and the coreutils package version 8.25-2ubuntu2. Please check the following closed debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854053 Be aware of the following conditions that are required: * If ppc64le * If gcc being used is >= 4.9 and < 7.0 Notes: 1) gcc-7 is not affected by this bug (verified on 20170129 snapshot). 2) clang is not affected by this bug (verified on v3.8 and v3.9). 3) strangely the sha512 is not affected by this. Below a demonstration of how it performs on my POWER8 machine: === $ (./configure && make -j9) > /dev/null && time src/sha256sum ~/ubuntu-16.10-server-ppc64el.iso configure: WARNING: libacl development library was not found or not usable. configure: WARNING: GNU coreutils will be built without ACL support. configure: WARNING: libattr development library was not found or not usable. configure: WARNING: GNU coreutils will be built without xattr support. configure: WARNING: libcap library was not found or not usable. configure: WARNING: GNU coreutils will be built without capability support. configure: WARNING: libgmp development library was not found or not usable. configure: WARNING: GNU coreutils will be built without GMP support. src/who.c: In function 'print_user': src/who.c:454:20: warning: initialization discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers] int *a = utmp_ent->ut_addr_v6; ^~~~ d14bdb413ea6cdc8d9354fcbc37a834b7de0c23f992deb0c6764d0fd5d65408e /home/gut/ubuntu-16.10-server-ppc64el.iso real0m18.670s user0m16.566s sys 0m0.745s $ # now with the following patch: ## Check Michael Stone's patch for an improved version. $ diff Makefile.in ../Makefile.in 8989c8989 < @am__fastdepCC_TRUE@ $(COMPILE) -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\ --- > @am__fastdepCC_TRUE@ $(COMPILE) $$([ "$@" == "lib/sha256.o" ] && echo "-fno-schedule-insns") -MT $@ -MD -MP -MF $$depbase.Tpo -c -o $@ $< &&\ $ cp ../Makefile.in Makefile.in $ (./configure && make -j9) > /dev/null && time src/sha256sum ~/ubuntu-16.10-server-ppc64el.iso configure: WARNING: libacl development library was not found or not usable. configure: WARNING: GNU coreutils will be built without ACL support. configure: WARNING: libattr development library was not found or not usable. configure: WARNING: GNU coreutils will be built without xattr support. configure: WARNING: libcap library was not found or not usable. configure: WARNING: GNU coreutils will be built without capability support. configure: WARNING: libgmp development library was not found or not usable. configure: WARNING: GNU coreutils will be built without GMP support. src/who.c: In function 'print_user':
[Touch-packages] [Bug 1700971] [NEW] ubunto
Public bug reported: Does not restart normally - have to go thru recovery mode- and shuts down suddenly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70 Uname: Linux 4.4.0-82-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 07:55:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8370D] [1002:9998] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Richland [Radeon HD 8370D] [1462:7721] InstallationDate: Installed on 2014-09-19 (1012 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MSI MS-7721 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-82-generic root=UUID=c79315a4-8e4a-4807-a210-4df3df6b1d9b ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V32.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A55M-E33 (MS-7721) dmi.board.vendor: MSI dmi.board.version: 7.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV32.5:bd03/20/2014:svnMSI:pnMS-7721:pvr7.0:rvnMSI:rnA55M-E33(MS-7721):rvr7.0:cvnMSI:ct3:cvr7.0: dmi.product.name: MS-7721 dmi.product.version: 7.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jun 28 07:09:29 2017 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- 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/1700971 Title: ubunto Status in xorg package in Ubuntu: New Bug description: Does not restart normally - have to go thru recovery mode- and shuts down suddenly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-82.105-generic 4.4.70 Uname: Linux 4.4.0-82-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 07:55:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8370D] [1002:9998] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Richland [Radeon HD 8370D] [1462:7721] InstallationDate: Installed on 2014-09-19 (1012 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: MSI MS-7721 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-82-generic root=UUID=c79315a4-8e4a-4807-a210-4df3df6b1d9b ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date:
[Touch-packages] [Bug 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5
The test doesn't even get past the setup function. The setup function is quite basic. Create an image, partition the image, create filesystem on the image. https://git.launchpad.net/~ubuntu-core-dev/+git/systemd/tree/test/test- functions?h=ubuntu-artful#n333 It appears that the kernel has failed to re-read the partition table, as /dev/loop4p1 is expected to exist. Is sfdisk not sufficient to re-read the parition table?! i wonder if between calling sfdisk and mkfs, and udevadm wait for idle state is needed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1700806 Title: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5 Status in systemd package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5
(As in, there is a race that mkfs was attempted before /dev/loop4p1 device was created, however i thought return from ioctl to re-read parition table returns only after the p* devices have been created by the kernel) dmesg from this machine would be interesting. -- 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/1700806 Title: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5 Status in systemd package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5
== TEST-05-RLIMITS == make: Entering directory '/tmp/autopkgtest.ipRf3i/build.uhX/systemd-233/test/TEST-05-RLIMITS' TEST CLEANUP: Resource limits-related tests TEST SETUP: Resource limits-related tests 0+0 records in 0+0 records out 0 bytes copied, 0.000211387 s, 0.0 kB/s Checking that no-one is using this disk right now ... OK Disk /dev/loop4: 400 MiB, 419430400 bytes, 819200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes >>> Created a new DOS disklabel with disk identifier 0xa1dd3fbe. /dev/loop4p1: Created a new partition 1 of type 'Linux' and of size 390 MiB. /dev/loop4p2: Created a new partition 2 of type 'Linux' and of size 9 MiB. /dev/loop4p3: Done. New situation: Device Boot StartEnd Sectors Size Id Type /dev/loop4p12048 800767 798720 390M 83 Linux /dev/loop4p2 800768 819199 184329M 83 Linux The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. The file /dev/loop4p1 does not exist and no size was specified. F: Failed to mkfs -t ext3 Makefile:4: recipe for target 'setup' failed -- 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/1700806 Title: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5 Status in systemd package in Ubuntu: New Bug description: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[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
** This bug is no longer a duplicate of bug 1639776 name resolution (dnsmasq) fails to send queries out after suspend/resume reconnects the interface -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/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: Invalid 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 1522675] Re: Warning messages about unsandboxed downloads
Since upgrade to xenial I have these 24 error messages in logs $ sudo grep -r _apt /var/log/* | sort | uniq | grep drop /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20170411.1.orig.tar.gz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/arial32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/arialb32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/comic32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/courie32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/georgi32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/impact32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/times32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/trebuc32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/verdan32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/apt-term.log:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/webdin32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20170411.1.orig.tar.gz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/andale32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/arial32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/arialb32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/comic32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/courie32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/georgi32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/impact32.exe' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) /var/log/dist-upgrade/screenlog.0:W: Can't drop privileges for downloading as file
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
Got "W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)" on Xenial. Do you plan to fix this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Triaged Status in apt package in Debian: Fix Released Bug description: Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700954] [NEW] Critical about Intel Graphics Driver Update
Public bug reported: I receive problems when I'm install that program that it not display the login screen but it's black screen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.11.7-041107-generic i686 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..05.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:05:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 375.66 Mon May 1 14:31:26 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 18:32:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-04-28 (61 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.7-041107-generic root=UUID=9b111cda-c784-49a8-a97d-03d4ec26ea04 ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jun 28 17:01:45 2017 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1700954 Title: Critical about Intel Graphics Driver Update Status in xorg package in Ubuntu: New Bug description: I receive problems when I'm install that program that it not display the login screen but it's black screen ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 Uname: Linux 4.11.7-041107-generic i686 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..05.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:05:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 375.66 Mon May 1 14:31:26 PDT 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.6 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jun 28 18:32:46 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 430] [10de:0de1] (rev a1) (prog-if 00 [VGA controller]) InstallationDate: Installed on 2017-04-28 (61 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" -
[Touch-packages] [Bug 1700949] [NEW] manpage is incomplete
Public bug reported: At least the "--dport" option is missing from both the man page and the --help command option. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iptables 1.6.0-2ubuntu3 Uname: Linux 4.11.6-041106-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 28 11:45:45 2017 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to iptables in Ubuntu. https://bugs.launchpad.net/bugs/1700949 Title: manpage is incomplete Status in iptables package in Ubuntu: New Bug description: At least the "--dport" option is missing from both the man page and the --help command option. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: iptables 1.6.0-2ubuntu3 Uname: Linux 4.11.6-041106-lowlatency x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: KDE Date: Wed Jun 28 11:45:45 2017 SourcePackage: iptables UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1700949/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1589289] Re: fstrim: cannot open /dev/.lxd-mounts: Permission denied
Fails also on Proxmox LXC https://forum.proxmox.com/threads/deleting- data-in-lxc-lvm-thin-doesnt-release-space.32179/#post-173302 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1589289 Title: fstrim: cannot open /dev/.lxd-mounts: Permission denied Status in util-linux package in Ubuntu: Confirmed Bug description: fstrim weekly cronjob output in an unprivileged LXD container: /etc/cron.weekly/fstrim: fstrim: cannot open /dev/.lxd-mounts: Permission denied fstrim: /dev/fuse: not a directory fstrim: /dev/lxd: FITRIM ioctl failed: Operation not permitted There is a github issue: https://github.com/lxc/lxd/issues/2030 The outcome is that it's purely an fstrim misbehaviour, it could be smarter. Stephane Graber comment: As all of this is handled by the kernel, there isn't anything we can do about it in LXD. I think fstrim should be made slightly more clever: * Don't run on bind-mounts (you can detect bind-mounts by parsing /proc/self/mountinfo instead of /proc/mounts) * Maybe not be as noisy on expected errors like EACCES, EPERM and ENOENT, only log actual failures which would likely be EINVAL or memory related errors. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: util-linux 2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sun Jun 5 19:49:04 2016 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: util-linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1589289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700944] [NEW] less display is broken when using option to show line numbers
Public bug reported: hi, in my .bashrc I have recently added: alias less='less -r -N' Now, msot of the time, when I open a file, less displays the file starting at line 2 (sometimes even at line 38 or more), with no possibility to go up in the file. Using "-n " in less started with -N does not solve the problem. As soon as I remove the options (particularly -N) the behaviour is OK again ** Affects: less (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to less in Ubuntu. https://bugs.launchpad.net/bugs/1700944 Title: less display is broken when using option to show line numbers Status in less package in Ubuntu: New Bug description: hi, in my .bashrc I have recently added: alias less='less -r -N' Now, msot of the time, when I open a file, less displays the file starting at line 2 (sometimes even at line 38 or more), with no possibility to go up in the file. Using "-n " in less started with -N does not solve the problem. As soon as I remove the options (particularly -N) the behaviour is OK again To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/less/+bug/1700944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520615] Re: Use of Ubuntu logo as default app icon dilutes the brand
Visual reference attached. Thanks. ** Attachment added: "visual-reference.png" https://bugs.launchpad.net/software-center-agent/+bug/1520615/+attachment/4904494/+files/visual-reference.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1520615 Title: Use of Ubuntu logo as default app icon dilutes the brand Status in Canonical System Image: Confirmed Status in Click Package Index: Invalid Status in Snap Store: Triaged Status in Software Center Agent: Invalid Status in ubuntu-sdk-ide package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: New Bug description: Currently, MyApps and CPI are using the "placeholder-app-icon.png" from the Suru theme, which is a basic greyscale image, including a version of the Ubuntu logo. Showing this logo as the app icon for apps which have no icon, implies they are officially supported apps by Ubuntu, and dilutes the brand and trademark, when they are not actually such apps, particularly when they have no function directly linked to any part of Ubuntu. Instead, a better representation would be a generic representation of an app window or similar. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1520615] Re: Use of Ubuntu logo as default app icon dilutes the brand
Hi Bret, Please find new placeholder icon attached in SVG format along with a visual reference so you can see it in situ. I ran it past head of brand yesterday and he is happy to use this 'app store' icon as the replacement placeholder icon. Thanks. ** Attachment added: "default-app-icon.svg" https://bugs.launchpad.net/software-center-agent/+bug/1520615/+attachment/4904488/+files/default-app-icon.svg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1520615 Title: Use of Ubuntu logo as default app icon dilutes the brand Status in Canonical System Image: Confirmed Status in Click Package Index: Invalid Status in Snap Store: Triaged Status in Software Center Agent: Invalid Status in ubuntu-sdk-ide package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: Confirmed Status in ubuntu-touch-meta package in Ubuntu: New Bug description: Currently, MyApps and CPI are using the "placeholder-app-icon.png" from the Suru theme, which is a basic greyscale image, including a version of the Ubuntu logo. Showing this logo as the app icon for apps which have no icon, implies they are officially supported apps by Ubuntu, and dilutes the brand and trademark, when they are not actually such apps, particularly when they have no function directly linked to any part of Ubuntu. Instead, a better representation would be a generic representation of an app window or similar. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1520615/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700934] Re: package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1700934 Title: package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 Status in kmod package in Ubuntu: New Bug description: System crashed while updating ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 11:03:40 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 DuplicateSignature: package:libkmod2:22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (22-1.1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-tSc5y2/12-libkmod2_22-1.1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2015-05-17 (772 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: kmod Title: package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to zesty on 2017-05-15 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1700934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700931] [NEW] package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1
Public bug reported: update-rc.d: error: insserv rejected the script header dpkg: 处理软件包 openssh-server (--configure)时出错： 子进程 已安装 post-installation 脚本 返回错误状态 1 在处理时有错误发生： openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 28 16:49:30 2017 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-06-27 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (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 openssh in Ubuntu. https://bugs.launchpad.net/bugs/1700931 Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 Status in openssh package in Ubuntu: New Bug description: update-rc.d: error: insserv rejected the script header dpkg: 处理软件包 openssh-server (--configure)时出错： 子进程 已安装 post-installation 脚本 返回错误状态 1 在处理时有错误发生： openssh-server E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.2 ProcVersionSignature: Ubuntu 4.8.0-56.61~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-56-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jun 28 16:49:30 2017 ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1 InstallationDate: Installed on 2017-06-27 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.2 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1700931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700934] [NEW] package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod
Public bug reported: System crashed while updating ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 11:03:40 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 DuplicateSignature: package:libkmod2:22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (22-1.1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-tSc5y2/12-libkmod2_22-1.1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2015-05-17 (772 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: kmod Title: package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to zesty on 2017-05-15 (43 days ago) ** Affects: kmod (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package package-conflict zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1700934 Title: package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 Status in kmod package in Ubuntu: New Bug description: System crashed while updating ProblemType: Package DistroRelease: Ubuntu 17.04 Package: libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 28 11:03:40 2017 Dependencies: gcc-6-base 6.3.0-12ubuntu2 libc6 2.24-9ubuntu2.2 libgcc1 1:6.3.0-12ubuntu2 DuplicateSignature: package:libkmod2:22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (22-1.1ubuntu1) ... dpkg: error processing archive /tmp/apt-dpkg-install-tSc5y2/12-libkmod2_22-1.1ubuntu1_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2015-05-17 (772 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: kmod Title: package libkmod2 22-1.1ubuntu1 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to zesty on 2017-05-15 (43 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1700934/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700930] [NEW] Default action policy for "Security Updates" changed between 14.04 and 16.04
Public bug reported: In Ubuntu 14.04.5, the default policy under the "Updates" tab for "Security Updates" is set to "Display Immediately". In Ubuntu 16.04+, the default policy is now "Download and Install Immediately". I think this occurred due to the fix rolled out for bug #1554099. This has the following consequences: - Users may be denied apt lock when trying to install software because unattended-upgrades is running in the background. - If a shutdown is forced when the background update is running, users may be left with an unstable system - In case the update server is compromised and made to deliver malware, the blow to the userbase will be massive - From a PR standpoint, this moves away from the previous "your system won't ever do stuff without your permission" default policy. I'm of the opinion that the "Display Immediately" default should be rolled back. Failing that at least an official policy change announcement should be published so that users are made aware of this new default. ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: xenial yakkety zesty ** Description changed: In Ubuntu 14.04.5, the default policy under the "Updates" tab for "Security Updates" is set to "Display Immediately". In Ubuntu 16.04+, the default policy is now "Download and Install Immediately". I think this occurred due to the fix rolled out for bug #1554099. This has the following consequences: - Users may be denied apt lock when trying to install software because unattended-upgrades is running in the background. - If a shutdown is forced when the background update is running, users may be left with an unstable system - In case the update server is compromised and made to deliver malware, the blow to the userbase will be massive - From a PR standpoint, this moves away from the previous "your system won't ever do stuff without your permission" default policy. - I'm in the opinion that the "Display Immediately" default should be + I'm of the opinion that the "Display Immediately" default should be rolled back. Failing that at least an official policy change announcement should be published so that users are made aware of this new default. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1700930 Title: Default action policy for "Security Updates" changed between 14.04 and 16.04 Status in software-properties package in Ubuntu: New Bug description: In Ubuntu 14.04.5, the default policy under the "Updates" tab for "Security Updates" is set to "Display Immediately". In Ubuntu 16.04+, the default policy is now "Download and Install Immediately". I think this occurred due to the fix rolled out for bug #1554099. This has the following consequences: - Users may be denied apt lock when trying to install software because unattended-upgrades is running in the background. - If a shutdown is forced when the background update is running, users may be left with an unstable system - In case the update server is compromised and made to deliver malware, the blow to the userbase will be massive - From a PR standpoint, this moves away from the previous "your system won't ever do stuff without your permission" default policy. I'm of the opinion that the "Display Immediately" default should be rolled back. Failing that at least an official policy change announcement should be published so that users are made aware of this new default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1700930/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1211110] Re: network manager openvpn dns push data not updating system DNS addresses
@Silas Linux users are patient indeed and they are certainly not waiting for useless comments like yours. If you want to contribute, educate yourself and try to help out. Ranting does contribute NOTHING. So if you really love Linux, think about that. Try to follow the rules regarding the bug report and contribute where you can and people will like it. Nobody asked you to use Ubuntu, if you're happy with windows 10 (which probably nobody else here is) then use it and be happy, why post here? Don't forget Linux is a community effort and the ways to fix certain problems is difficult. However, making an effort to get it to work will teach you and will get you appreciation from others. As bagl0312 commented already, your point is not even viable, because the issue was fixed in 17.04 by a patch. If you google the issue for older versions, you will probably land on a page that describes how to fix that too: https://askubuntu.com/questions/838948/16-10-fail-to-resolve-dns and see work arounds in this thread, so your comment is really just bad timing. Please think twice before you post something and read the rules. Thanks to the relentless efforts of the community, this is fixed and work is going on to get this in the main version(s). -- 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/120 Title: network manager openvpn dns push data not updating system DNS addresses Status in network-manager package in Ubuntu: Confirmed Status in openvpn package in Ubuntu: Confirmed Bug description: [Triage Notes] This bug can no longer make progress. Please see comment 50 for details and further instructions. [Original Description] When IPv4 Method is set to Automatic VPN, DNS address recieved from OpenVPN server do not update resolv.conf. This can be achieved when using a standard openvpn config file by adding the lines: script-security 2 up /etc/openvpn/update-resolv-conf down /etc/openvpn/update-resolv-conf In Network-manager there seems to be no option to run connection specific scripts and the DNS data from the server is ignored. Ubuntu 13.04 Network-manager 0.9.8.0-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
Me too ASUS X555UQ, ALC255. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1596381 Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256 speakers work, it's just the mic not working. sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200 sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200 sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0 sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0 8 lines make mic working until reboot. thx a lot for ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio CasperVersion: 1.376 CurrentDesktop: Unity Date: Sun Jun 26 23:56:46 2016 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 2 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: ubuntu 1983 F...m pulseaudio /dev/snd/controlC0: ubuntu 1983 F pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/23/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X555UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so much other solution I could find :(
--
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/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
Ok, I've found a workaround, to specify this kernel parameter in GRUB:
video=VGA-1:1920x1080@60
--
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/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/25/2013:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz
[Touch-packages] [Bug 1688253] Re: Wrong resolution, and "unknown monitor" since upgraded to 17.04
With wayland, the problem is even worse, with X11 I could at least use
xrandr to set the correct resolution. This is not an option with wayland
though, so I cannot even use my desktop normally, I guess I should
downgrade ubuntu, since no way to use the machine in a sane way anymore,
and not so much other solution I could find :(
--
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/1688253
Title:
Wrong resolution, and "unknown monitor" since upgraded to 17.04
Status in xorg package in Ubuntu:
New
Bug description:
I've never had a problem like this before. Now, after upgraded to
Ubuntu 17.04 it was already strange to see the boot logo in a kind of
low and fuzzy resolution. And it remained for the LightDM login
screen, also for the desktop after logged on. System setting ->
Display reports "Unknown Display". System settings -> Software &
updates -> Additional drivers shows title "Unknown: Unknown" though
after that "Using Processor microcode firmware for Intel CPUs from
intel-microcode" is active. I could "work the problem around" (see the
end of this writing) but it's really ugly that I need to run a script
every time, when it always worked well on the same machine before this
Ubuntu release.
According to xrandr:
lgb@vega:~$ xrandr
Screen 0: minimum 320 x 200, current 1024 x 768, maximum 8192 x 8192
VGA-1 connected primary 1024x768+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00*
800x600 60.3256.25
848x480 60.00
640x480 59.94
My GPU:
lgb@vega:~$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen
Core processor Graphics Controller (rev 09)
Monitor is Samsung SyncMaster E2220, standard VGA-cable connection
(this monitor hasn't got any other connector like HDMI or DVI).
My workaround was to create this script and run:
DEV=`xrandr | awk '$2 == "connected" { print $1 }'`
xrandr --newmode "1920x1080" 173.00 1920 2048 2248 2576 1080 1083 1088
1120 -hsync +vsync
xrandr --addmode $DEV 1920x1080
xrandr --output $DEV --mode 1920x1080
After this, the resolution is fine, but still everything reports
"Unknown display" and such. The output of xrandr after running my
script (I played with adding some modes, that is the _60.00 stuff):
root@vega:~# xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
VGA-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y
axis) 0mm x 0mm
1024x768 60.00
800x600 60.3256.25
848x480 60.00
640x480 59.94
1920x1080 59.96*
1920x1080_60.00 (0xda) 173.000MHz -HSync +VSync
h: width 1920 start 2048 end 2248 total 2576 skew0 clock
67.16KHz
v: height 1080 start 1083 end 1088 total 1120 clock 59.96Hz
ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
Uname: Linux 4.10.0-21-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7
Date: Thu May 4 15:03:53 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
[8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v2/3rd Gen Core
processor Graphics Controller [1458:d000]
InstallationDate: Installed on 2016-06-10 (328 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic
root=UUID=c6e12cf5-267b-49d3-83eb-87a1464a2633 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/25/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61M-S1
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
[Touch-packages] [Bug 1640784] Re: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configur
** Tags added: zesty -- 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/1640784 Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: fresh install ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Thu Nov 10 14:57:54 2016 DuplicateSignature: package:unattended-upgrades:0.90ubuntu0.1 Processing triggers for man-db (2.7.5-1) ... dpkg: error processing package unattended-upgrades (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2016-11-10 (0 days ago) InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1640784/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1700379] Re: package unattended-upgrades 0.93.1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
*** This bug is a duplicate of bug 1640784 *** https://bugs.launchpad.net/bugs/1640784 ** This bug has been marked a duplicate of bug 1640784 package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- 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/1700379 Title: package unattended-upgrades 0.93.1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in unattended-upgrades package in Ubuntu: New Bug description: It does not automatically delete prior packages. Old packages not removed. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.2 ProcVersionSignature: Ubuntu 4.10.0-24.28-generic 4.10.15 Uname: Linux 4.10.0-24-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Sun Jun 25 09:48:53 2017 DuplicateSignature: package:unattended-upgrades:0.93.1ubuntu2.2 Setting up systemd (232-21ubuntu4) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. dpkg: error processing package unattended-upgrades (--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 2014-10-09 (990 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to zesty on 2017-04-18 (67 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-10-13T16:05:09.919104 mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2017-04-18T12:21:19.502089 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1700379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696583] Re: package unattended-upgrades 0.93.1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config
*** This bug is a duplicate of bug 1640784 *** https://bugs.launchpad.net/bugs/1640784 ** This bug has been marked a duplicate of bug 1640784 package unattended-upgrades 0.90ubuntu0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- 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/1696583 Title: package unattended-upgrades 0.93.1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in unattended-upgrades package in Ubuntu: New Bug description: failed updates bug report ProblemType: Package DistroRelease: Ubuntu 17.04 Package: unattended-upgrades 0.93.1ubuntu2.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 Date: Wed Jun 7 15:25:38 2017 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2014-10-09 (972 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: unattended-upgrades Title: package unattended-upgrades 0.93.1ubuntu2.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: Upgraded to zesty on 2017-04-18 (50 days ago) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "0"; APT::Periodic::AutocleanInterval "0"; APT::Periodic::Unattended-Upgrade "0"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-10-13T16:05:09.919104 mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2017-04-18T12:21:19.502089 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1696583/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1670269] Re: Add com.ubuntu.usbcreator.format for usb creator action
Any news on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-desktop- privileges in Ubuntu. https://bugs.launchpad.net/bugs/1670269 Title: Add com.ubuntu.usbcreator.format for usb creator action Status in policykit-desktop-privileges package in Ubuntu: New Bug description: Usb creator still asks for password when formatting or trying to install boot-loader. If user doesn't respond within a sepecific time, it fails and user has to start the process all over again. Adding "com.ubuntu.usbcreator.format" to Action solves the issue. ### PATCH - --- a/com.ubuntu.desktop.pkla +++ b/com.ubuntu.desktop.pkla @@ -25,7 +25,7 @@ [usb-creator] Identity=unix-group:admin;unix-group:sudo -Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image +Action=com.ubuntu.usbcreator.mount;com.ubuntu.usbcreator.image;com.ubuntu.usbcreator.format ResultActive=yes [Printer administration] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug/1670269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
