Re: [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 con
My updates are working correctly as well since the day before yesterday. Dimitri Στις Πέμ, 13 Ιουλ 2017 στις 1:55 π.μ., ο/η Alister < 1692...@bugs.launchpad.net> έγραψε: > Hi Seth > > My problem with the half installed package appears to have been resolved > with the "sudo apt-get install --reinstall" process. Updates are now > installing correctly as far as I can see. > > Alister Lee > > > On 13/07/17 04:52, Seth Arnold wrote: > > I'm curious how we can work around this bug. If you're affected please > > report the results of: > > > > dpkg -l | awk '/^iH/ { print $2 }' > > > > This shows which specific packages are half-installed on your systems. > > > > With the list of packages this returns, please also report success or > > failure of: > > > > sudo apt-get install --reinstall ALL PACKAGES FROM THE HALF-INSTALLED > > LIST > > > > Thanks > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1698303). > 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: > Confirmed > Status in openssl package in Ubuntu: > Confirmed > > 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 > -- 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: Confirmed Status in openssl package in Ubuntu: Confirmed 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
[Touch-packages] [Bug 1703763] Re: How to correctly transition from packaged to dh_apparmor generated local includes
Thanks Jamie, I wanted to make sure there is no easier "yeah it works that way". I tested various combinations and I'm happy with using a normal rm_conffile plus the following snippet in postinst "configure": # transition from packaged to dh_apparmor generated local aa includes # all other cases (no delta rm, abort, ...) are handled by rm_conffile # can be dropped >18.04 if [ -n "$2" ] && dpkg --compare-versions -- "$2" le-nl "3.5.0-1ubuntu1~"; then for CONFFILE in /etc/apparmor.d/local/usr.sbin.libvirtd /etc/apparmor.d/local/usr.lib.libvirt.virt-aa-helper; do if [ -e "$CONFFILE.dpkg-backup" ]; then echo "Obsolete conffile $CONFFILE has been modified by you." echo "These local includes are now generated by dh_apparmor" echo "Carrying over your changes into $CONFFILE ..." mv -f "$CONFFILE.dpkg-backup" "$CONFFILE" fi done fi This has the nice benefit that checksum comparison, abort, and much more will be done by dpkg_maintsscript_helper still. Only the one special case where it would on finish_rm_conffile have made it a backup is thereby overruled and becomes this special "move over target". dh_apparmor was so kind to not complain about that later on and keep it as-is (as it always does as it only "fills" missing local includes. The tracking in dpkg status is also correctly updated (no more listed as obsolete) I'll consider the bug done and mark it as not a bug (=invalid), this update was mostly for documentation purpose. ** Changed in: apparmor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1703763 Title: How to correctly transition from packaged to dh_apparmor generated local includes Status in apparmor package in Ubuntu: Invalid Bug description: Hi, this is more a request how to "correctly do it" instead of a bug. I asked on IRC but got no reply yet, so to not forget I better file a bug. I have a package (libvirt) which used to explicitly package the local apparmor include files. So the package had files like: /etc/apparmor.d/local/usr.sbin.libvirtd These files were carried in the package itself and considered conffiles. These days that isn't needed anymore, thanks to dh_apparmor generating such local includes. Aligning with Debian we dropped the explicit files and use the generated ones. All fine so far, but I wonder how to correctly "transition" that. A) If I do rm_conffile A1) the user had no changes, old file gets removed, new one generated all is good A2) the user had changes, old file gets retained in backup, new one generated lacks the old content B) if I not have a rm_conffile B1) the user had no changes, the old file stays (and works) but is considered obsolete by "dpkg --status" B2) the user had changes, the old file stays (and works) but is considered obsolete by "dpkg --status" So far I think I'll go with B, as dropping user changes - especially thos explicitly added to likely fix/avoid something - would be bad. But I don't like having obsolete files forever. Is there a C) which would be able to retain old changes if there were any, but in any case make sure it is dropped from the package to no more be considered an obsolete conffile? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1703763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable
debdiff with updated changelog per comment #7. ** Changed in: sound-theme-freedesktop (Ubuntu) Status: New => Confirmed ** Changed in: sound-theme-freedesktop (Ubuntu) Importance: Undecided => Medium ** Changed in: sound-theme-freedesktop (Ubuntu) Assignee: (unassigned) => Will Cooke (willcooke) ** Patch added: "sound-theme-freedesktop.debdiff" https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+attachment/4913988/+files/sound-theme-freedesktop.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1703946 Title: Dedicated mono test sound is unavailable Status in sound-theme-freedesktop package in Ubuntu: Confirmed Bug description: When testing stereo speakers you get the "Front left" and "Front right" samples, but no such sample exists for mono speakers e.g. HSP/HFP bluetooth devices. Instead you get played the "audio-test-signal" which is white noise. To begin with I thought this was a problem with Bluetooth or the speaker itself, but it's just the sample being used. There is a bug upstream to provide this sample, but in the meantime I think playing the "audio-channel-front-center.oga" is a suitable standin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just
Please do note that in addtion to all we did before we also checked one more corner case before movign to proposed. The one that ntp was meant to be active, but came up before e.g. ppp0 and due to that can't resolve peers. It turns out ntp relaized networks that get enable later and triggers its resolver - so the stop/start on ifup hook wasn't needed to keep that working. Doing SRU verifications now ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1593907 Title: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just need to apply it and release a new version Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Trusty: Fix Committed Status in ntp source package in Xenial: Fix Committed Status in ntp source package in Yakkety: Fix Committed Status in ntp source package in Zesty: Fix Committed Bug description: [Impact] * Fixes several broken cases, those are: * Case 1 - ntp configured to drift time slowly, but time jumping - ntp is running and drifts time towards a target being way off - an interface comes up - stop ntpd - warp time via ntpdate-debian (static interfaces will even set -b) - (re-)start ntpd - if users relied on non-time warp they are now in trouble * Case 2 - ntp start/stop storms - ntpd comes up normally - the admin brings interfaces up/down rather often - ntp is restarted very very often due to this for no reason => reason for bugs like debian 823533 * Case 3 - unintentional enablement of ntp - ntpd is installed but disabled (for whatever reason) - all is fine on any ifup/down - one installs ntpdate, maybe even without realizing due to a depends - now on the next ifup ntpd (or openntpd) will be started * Solution, drop the broken Delta [Test Case] * Testing Case 2/3 as it is the easiest, case 1 needs a more complex setup to cause the time drift but otherwise works the same way. - install ntp and ntpdate - stop ntp - ifup/ifdown an interface multiple times; as simplification you can also call /etc/network/if-up.d/ntpdate directly (not that this spawns the change asnchronous and locks concurrency, so do that a few times over the time of a minute or so) - the service of ntp should still be stopped and not report plenty of restarts [Regression Potential] * It improves a lot of cases (otherwise we wouldn't SRU), but there is one regression potential I can see: - users that relied on starting NTP later on after other interfaces got up due to that code in ntpdate which did that as a side effect. But that is outweigh by Case2/3 for the majority of users. And even Case1 only hits this potential regression on e.g. late network intialization, but in that case please remind that the default (systemd timedatectl) would handle that. - Since most users of ntp do not install ntpdate (which doesn't work when ntp is active) we should be rather safe to assume that almost no one should rely on that side effect. - Furthermore this is a Ubuntu Delta for very long, cause issues (see the references on the git commit) but never made it into Debian - in that sense another indicator it isn't an important delta to have. [Other Info] * The original intention "what if net is available too late" fixed correctly would not be part of ntpdate, but ntp and additionally check if it is actually meant to be enabled - but I never seen/heard of any of it since systemd is around - maybe new ordering mostly avoids the original issue. --- I've installed ntp service on the clean ubuntu 16.04 server system. Configured it. Checked that it works, but, after reboot, it doesn't start automatically. When I check: 'systemctl is-enabled ntp', it shows enabled. If I manually start it 'systemctl start ntp' it starts just fine and woks correctly, but until I manually start it, 'systemctl status ntp' shows: Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Active: inactive (deadi) Installed 1.29ubuntu2 version of init-systems-helper, but it didn't fix the problem. Found a bugreport on ntpd package: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1577596 led to solution that involves a change to be made in file: /etc/network/if-up.d/ntpdate of ntpdate package After changing from: __CODE_START__ invoke-rc.d --quiet $service stop >/dev/null 2>&1 || true # Avoid running more than one at a time flock -n /run/lock/ntpdate /usr/
[Touch-packages] [Bug 1704094] [NEW] ubuntu-bug xorg
Public bug reported: Wine is stuck on install ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.9 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: Thu Jul 13 10:59:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-07-12 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. H55M-USB3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: H55M-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd11/01/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81+git1707071830.ac2140~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1707130730.c3b5c2~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1707130730.c3b5c2~gd~x 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: Thu Jul 13 10:23:26 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 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 compiz-0.9 third-party-packages 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/1704094 Title: ubuntu-bug xorg Status in xorg package in Ubuntu: New Bug description: Wine is stuck on install ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.9 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: Thu Jul 13 10:59:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-07-12 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. H55M-USB3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: Award Software International,
[Touch-packages] [Bug 1703415] Re: Disable Bluetooth sink in GDM to allow A2DP in the user session
** Changed in: gdm Status: Unknown => Confirmed ** Changed in: gdm Importance: Unknown => Medium -- 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/1703415 Title: Disable Bluetooth sink in GDM to allow A2DP in the user session Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704094] Re: ubuntu-bug xorg
** Package changed: xorg (Ubuntu) => wine (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/1704094 Title: ubuntu-bug xorg Status in wine package in Ubuntu: New Bug description: Wine is stuck on install ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.9 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: Thu Jul 13 10:59:03 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] (rev 12) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Core Processor Integrated Graphics Controller [1458:d000] InstallationDate: Installed on 2017-07-12 (1 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Gigabyte Technology Co., Ltd. H55M-USB3 ProcEnviron: LANGUAGE=en_ZA:en PATH=(custom, no user) LANG=en_ZA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-58-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/01/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F11 dmi.board.name: H55M-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF11:bd11/01/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.81+git1707071830.ac2140~gd~x version.libgl1-mesa-dri: libgl1-mesa-dri 17.2~git1707130730.c3b5c2~gd~x version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2~git1707130730.c3b5c2~gd~x 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: Thu Jul 13 10:23:26 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech USB Receiver KEYBOARD, id 8 inputLogitech USB Receiver KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-1ubuntu6.1~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wine/+bug/1704094/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1593907] Re: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just
Verified on all four targeted releases: - the hook does no more start a disabled ntp - the hook multiple times does no more is a thundering herd of stop/start ntp - ntpdate does not stop ntp, warp time, start ntp (might warp back if configured differently) - ntpdate no clashing with a (potentially) running ntp is not fatal (there is a log entry of the ntp socket being already in use, but that is correct - one could precheck if running and avoid even trying, but much better than restarting or timewarping) No regression seen yet, so hopefully all is good. Setting verifications to done. Still if some of the affected could test in addition to that that would be great. ** Tags removed: verification-needed verification-needed-trusty verification-needed-xenial verification-needed-yakkety verification-needed-zesty ** Tags added: verification-done verification-done-trusty verification-done-xenial verification-done-yakkety verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1593907 Title: ntpdate startup routine prevents ntp service from launching up on Ubuntu 16.04 server on system boot; manually starting ntp service works: [FIX in DESCRIPTION], just need to apply it and release a new version Status in ntp package in Ubuntu: Fix Released Status in ntp source package in Trusty: Fix Committed Status in ntp source package in Xenial: Fix Committed Status in ntp source package in Yakkety: Fix Committed Status in ntp source package in Zesty: Fix Committed Bug description: [Impact] * Fixes several broken cases, those are: * Case 1 - ntp configured to drift time slowly, but time jumping - ntp is running and drifts time towards a target being way off - an interface comes up - stop ntpd - warp time via ntpdate-debian (static interfaces will even set -b) - (re-)start ntpd - if users relied on non-time warp they are now in trouble * Case 2 - ntp start/stop storms - ntpd comes up normally - the admin brings interfaces up/down rather often - ntp is restarted very very often due to this for no reason => reason for bugs like debian 823533 * Case 3 - unintentional enablement of ntp - ntpd is installed but disabled (for whatever reason) - all is fine on any ifup/down - one installs ntpdate, maybe even without realizing due to a depends - now on the next ifup ntpd (or openntpd) will be started * Solution, drop the broken Delta [Test Case] * Testing Case 2/3 as it is the easiest, case 1 needs a more complex setup to cause the time drift but otherwise works the same way. - install ntp and ntpdate - stop ntp - ifup/ifdown an interface multiple times; as simplification you can also call /etc/network/if-up.d/ntpdate directly (not that this spawns the change asnchronous and locks concurrency, so do that a few times over the time of a minute or so) - the service of ntp should still be stopped and not report plenty of restarts [Regression Potential] * It improves a lot of cases (otherwise we wouldn't SRU), but there is one regression potential I can see: - users that relied on starting NTP later on after other interfaces got up due to that code in ntpdate which did that as a side effect. But that is outweigh by Case2/3 for the majority of users. And even Case1 only hits this potential regression on e.g. late network intialization, but in that case please remind that the default (systemd timedatectl) would handle that. - Since most users of ntp do not install ntpdate (which doesn't work when ntp is active) we should be rather safe to assume that almost no one should rely on that side effect. - Furthermore this is a Ubuntu Delta for very long, cause issues (see the references on the git commit) but never made it into Debian - in that sense another indicator it isn't an important delta to have. [Other Info] * The original intention "what if net is available too late" fixed correctly would not be part of ntpdate, but ntp and additionally check if it is actually meant to be enabled - but I never seen/heard of any of it since systemd is around - maybe new ordering mostly avoids the original issue. --- I've installed ntp service on the clean ubuntu 16.04 server system. Configured it. Checked that it works, but, after reboot, it doesn't start automatically. When I check: 'systemctl is-enabled ntp', it shows enabled. If I manually start it 'systemctl start ntp' it starts just fine and woks correctly, but until I manually start it, 'systemctl status ntp' shows: Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled) Acti
[Touch-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs
This bug was fixed in the package multipath-tools - 0.5.0+git1.656f8865-5ubuntu2.5 --- multipath-tools (0.5.0+git1.656f8865-5ubuntu2.5) xenial; urgency=medium * debian/initramfs/hooks: drop dm-emc (it hasn't existed since 2.6.27) and add dm-queue-length: it's required on some hardware, such as XtremIO, where it is the default path selector. (LP: #1673350) -- Mathieu Trudel-Lapierre Tue, 28 Mar 2017 09:58:21 -0400 ** Changed in: multipath-tools (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in multipath-tools source package in Xenial: Fix Released Status in hw-detect source package in Yakkety: Fix Committed Status in initramfs-tools source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Status in multipath-tools source package in Yakkety: Fix Released Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673350] Update Released
The verification of the Stable Release Update for multipath-tools has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in multipath-tools source package in Xenial: Fix Released Status in hw-detect source package in Yakkety: Fix Committed Status in initramfs-tools source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Status in multipath-tools source package in Yakkety: Fix Released Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs
This bug was fixed in the package hw-detect - 1.117ubuntu2.2 --- hw-detect (1.117ubuntu2.2) xenial; urgency=medium * disk-detect.sh: unconditionally modprobe dm-service-time and dm-queue-length multipath path selector modules alongside dm-round-robin. (LP: #1673350) -- Mathieu Trudel-Lapierre Wed, 14 Jun 2017 16:15:14 -0400 ** Changed in: hw-detect (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: Invalid Status in linux source package in Xenial: Fix Released Status in multipath-tools source package in Xenial: Fix Released Status in hw-detect source package in Yakkety: Fix Committed Status in initramfs-tools source package in Yakkety: Invalid Status in linux source package in Yakkety: Fix Released Status in multipath-tools source package in Yakkety: Fix Released Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 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 con
the sudo apt-get install --reinstall process worked for me On 13 July 2017 at 04:05, Homatidis Dimitris wrote: > My updates are working correctly as well since the day before yesterday. > > Dimitri > > Στις Πέμ, 13 Ιουλ 2017 στις 1:55 π.μ., ο/η Alister < > 1692...@bugs.launchpad.net> έγραψε: > > > Hi Seth > > > > My problem with the half installed package appears to have been resolved > > with the "sudo apt-get install --reinstall" process. Updates are now > > installing correctly as far as I can see. > > > > Alister Lee > > > > > > On 13/07/17 04:52, Seth Arnold wrote: > > > I'm curious how we can work around this bug. If you're affected please > > > report the results of: > > > > > > dpkg -l | awk '/^iH/ { print $2 }' > > > > > > This shows which specific packages are half-installed on your systems. > > > > > > With the list of packages this returns, please also report success or > > > failure of: > > > > > > sudo apt-get install --reinstall ALL PACKAGES FROM THE HALF-INSTALLED > > > LIST > > > > > > Thanks > > > > > > > -- > > You received this bug notification because you are subscribed to a > > duplicate bug report (1698303). > > 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: > > Confirmed > > Status in openssl package in Ubuntu: > > Confirmed > > > > 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 > > > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1698324). > 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: > Confirmed > Status in openssl package in Ubuntu: > Confirmed > > 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 be
[Touch-packages] [Bug 1703838] Re: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try
I can induce a connection drop by changing the wireless channel on my router - this also produces a similar result (no auto reconnect) - it shows like it's trying for a minute or 2, and than shows the up/down arrows. Selecting the network manually connects immediately. Here's the NetworkManager log: https://pastebin.com/CB6d8NP4 Attached is the debug wpa_supplicant log starting from the disconnect ** Attachment added: "wpa_supplicant log (debug mode)" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+attachment/4914037/+files/wpa_sup%20failure%20to%20reconnect3%20debug -- 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/1703838 Title: Failure to automatically reconnect after drop - requiring manual reconnect, only successful after second try Status in network-manager package in Ubuntu: New Bug description: Using Ubuntu 17.04 (64 bit) Package version 1.4.4-1ubuntu3.1 This happened to me 3 times today: The connection drops and is not automatically restored, even though the network is visible in the nm-applet. Manually clicking on the network to connect, results in an animation of the nm-applet showing it's trying, but it gives up after a while and changes the icon to up\down arrows instead of the wifi sign. Clicking on it again, and selecting my network again, results in an almost instant reconnection, which implies that the computer should have known to do it automatically instead of requiring me to tell it to connect again (let alone twice). Here is the journal from a system startup: https://pastebin.com/hGrFEWiU And here is the journal from one such unsuccessful reconnect. I've added (*** comments ***) to mark where I've manually tried to reconnect (twice, second time successfully): https://pastebin.com/TAyt6McQ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1703838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Summary changed: - Disable Bluetooth sink in GDM to allow A2DP in the user session + Bluetooth audio devices/profiles are missing after logging in from GDM -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable
This looks good! Sponsored :) ** Changed in: sound-theme-freedesktop (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1703946 Title: Dedicated mono test sound is unavailable Status in sound-theme-freedesktop package in Ubuntu: Fix Committed Bug description: When testing stereo speakers you get the "Front left" and "Front right" samples, but no such sample exists for mono speakers e.g. HSP/HFP bluetooth devices. Instead you get played the "audio-test-signal" which is white noise. To begin with I thought this was a problem with Bluetooth or the speaker itself, but it's just the sample being used. There is a bug upstream to provide this sample, but in the meantime I think playing the "audio-channel-front-center.oga" is a suitable standin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Triaged ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Triaged -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Triaged Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703598] Re: [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your sources.list'
Brian, you're right. The manpage was not very clear about that. This bug can be closed now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1703598 Title: [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your sources.list' Status in apport package in Ubuntu: New Bug description: I get that error when I do this: apport-retrace -g -R -S system -v crash-file.crash ERROR: E:You must put some 'source' URIs in your sources.list - But I think they are already there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport-retrace 2.20.1-0ubuntu2.9 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportLog: ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: called for pid 2837, signal 11, core limit 0 ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: executable: /usr/bin/signon-ui (command line "/usr/bin/signon-ui") ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: debug: session gdbus call: (true,) ERROR: apport (pid 3064) Tue Jul 11 12:57:44 2017: wrote report /var/crash/_usr_bin_signon-ui.1000.crash ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 11 14:02:02 2017 InstallationDate: Installed on 2017-06-21 (19 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1703598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04
This is the second time a rather serious bug was introduced with an Ubuntu upgrade. And it is very sad to see again how slow this kind of bugs are treated. -- 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/1682193 Title: Mouse acceleration significantly reduced after upgrade to 17.04 Status in xorg package in Ubuntu: Confirmed Bug description: My external Logitech USB mouse was behaving nicely under 16.10 but after upgrade to 17.04 it has slowed down to a crawl. Settings slidebars are set at the maximum acceleration, but it only affects the touch pad, the mouse is extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458322] Re: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare)
Previous patch successfully hides unmanaged eth interfaces, but it leaves menu separators. This one hides separators also. ** Patch added: "hide_unmanaged_interfaces.patch" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1458322/+attachment/4914082/+files/hide_unmanaged_interfaces.patch -- 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/1458322 Title: NetworkManager doesn't hide virtual interfaces (e.g. Docker, VMWare) Status in One Hundred Papercuts: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Previously in Ubuntu 14.04 NetworkManager hid the veth interfaces that were created by Docker. Now since I've updated to 15.04 the veth interfaces are listed as Unmanaged under the gnome system tray icon which is kind of annoying. I'm using docker 1.6.2 and network-manager 0.9.10.0-4ubuntu15.1 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-18.18-generic 3.19.6 Uname: Linux 3.19.0-18-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: GNOME Date: Sun May 24 14:22:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2013-08-29 (632 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) IpRoute: default via 192.168.178.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.42.1 192.168.178.0/24 dev wlan0 proto kernel scope link src 192.168.178.40 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-24 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-08-19T11:46:06.705439 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1458322/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable
This bug was fixed in the package sound-theme-freedesktop - 0.8-1ubuntu1 --- sound-theme-freedesktop (0.8-1ubuntu1) artful; urgency=medium * debian/sound-theme-freedesktop.links - Link front-center sample to audio-channel-mono so that testing a mono bluetooth speaker plays a real sound rather than just white noise. (LP: #1703946) * debian/control - Updated maintainers as per packaging.u.c -- Will Cooke Wed, 12 Jul 2017 19:16:20 +0100 ** Changed in: sound-theme-freedesktop (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 sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1703946 Title: Dedicated mono test sound is unavailable Status in sound-theme-freedesktop package in Ubuntu: Fix Released Bug description: When testing stereo speakers you get the "Front left" and "Front right" samples, but no such sample exists for mono speakers e.g. HSP/HFP bluetooth devices. Instead you get played the "audio-test-signal" which is white noise. To begin with I thought this was a problem with Bluetooth or the speaker itself, but it's just the sample being used. There is a bug upstream to provide this sample, but in the meantime I think playing the "audio-channel-front-center.oga" is a suitable standin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703598] Re: [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your sources.list'
** Changed in: apport (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1703598 Title: [apport-retrace] 'ERROR: E:You must put some 'source' URIs in your sources.list' Status in apport package in Ubuntu: Invalid Bug description: I get that error when I do this: apport-retrace -g -R -S system -v crash-file.crash ERROR: E:You must put some 'source' URIs in your sources.list - But I think they are already there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport-retrace 2.20.1-0ubuntu2.9 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportLog: ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: called for pid 2837, signal 11, core limit 0 ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: executable: /usr/bin/signon-ui (command line "/usr/bin/signon-ui") ERROR: apport (pid 3064) Tue Jul 11 12:57:31 2017: debug: session gdbus call: (true,) ERROR: apport (pid 3064) Tue Jul 11 12:57:44 2017: wrote report /var/crash/_usr_bin_signon-ui.1000.crash ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jul 11 14:02:02 2017 InstallationDate: Installed on 2017-06-21 (19 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1703598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703987] Re: New style permitnonkernelfacility imklog option inside module() doesn't work
I have test packages built with the patch mentioned in the github issue: https://launchpad.net/~ahasenack/+archive/ubuntu/rsyslog- permitnonkernelfacility-1703987 A quick test shows it works as expected now using the new style config. ** Changed in: rsyslog (Ubuntu) Status: New => Triaged ** Changed in: rsyslog (Ubuntu) Importance: Undecided => Low ** Tags added: server-next -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1703987 Title: New style permitnonkernelfacility imklog option inside module() doesn't work Status in Rsyslog: Unknown Status in rsyslog package in Ubuntu: Triaged Bug description: artful 8.16.0-1ubuntu5 (which is way behind upstream and debian, btw) There are two ways to load the imklog module and pass it an option (PermitNonKernelFacility in this case). a) legacy $ModLoad imklog $KLogPermitNonKernelFacility on b) "new style", also referred to as "v6+": module(load="imklog" permitnonkernelfacility="on") For a while the ubuntu package was using a mix: loading the module with the new style, but setting the option via the legacy method. In bug #1531622 this was fixed for yakkety+. Problem is, upstream isn't honouring the new style option setting due to a bug of its own: https://github.com/rsyslog/rsyslog/issues/477 With the legacy config: #module(load="imklog" permitnonkernelfacility="on") $ModLoad imklog $KLogPermitNonKernelFacility on I get kernel messages in /var/log/syslog: root@nsn7:~# grep andreas-was-here /var/log/syslog root@nsn7:~# echo andreas-was-here > /dev/kmsg root@nsn7:~# grep andreas-was-here /var/log/syslog Jul 12 16:46:33 nsn7 kernel: [27774.476193] andreas-was-here root@nsn7:~# But with this new v6 config style: module(load="imklog" permitnonkernelfacility="on") # provides kernel logging support #$ModLoad imklog #$KLogPermitNonKernelFacility on The text doesn't show up in /var/log/syslog. That's the upstream bug. To manage notifications about this bug go to: https://bugs.launchpad.net/rsyslog/+bug/1703987/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Changed in: gdm3 (Ubuntu) Assignee: (unassigned) => Will Cooke (willcooke) ** Changed in: gdm3 (Ubuntu) Status: Triaged => Fix Committed -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
For me after changing network.target to network.service on /usr/lib/systemd/system/sshd.service it started at the right time. -- 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/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-server The sshd will not start at boot if the ListenAddress option in /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 . I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the openssh-server package. I would expect that sshd is started after boot but it will not and I found this in /var/log/auth.log: sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign requested address. sshd[4527]: fatal: Cannot bind any address. Once the System is started you can start/stop the sshd with the /etc/init.d/ssh script without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Hi guys, I am still unable to get the list of half-installed packages using the dpkg command, is there another way to find these? Out of curiosity, how many half-installed packages did you need to reinstall? Thanks for all the support, Jeremy -- 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: Confirmed Status in openssl package in Ubuntu: Confirmed 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 1646739] Re: "Use of uninitialized value" in debconf via update-manager
*** This bug is a duplicate of bug 1679435 *** https://bugs.launchpad.net/bugs/1679435 If this is gnome-software, then this should be fixed already in gnome- software 3.20.1+git20170427.0.3d09239-0ubuntu1~xenial1 ** This bug has been marked a duplicate of bug 1679435 GNOME Software fails to install .deb packages that trigger debconf prompts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: "Use of uninitialized value" in debconf via update-manager Status in debconf package in Ubuntu: Confirmed Status in php7.0 package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1629021] Re: package clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
*** This bug is a duplicate of bug 1679435 *** https://bugs.launchpad.net/bugs/1679435 ** This bug is no longer a duplicate of bug 1646739 "Use of uninitialized value" in debconf via update-manager ** This bug has been marked a duplicate of bug 1679435 GNOME Software fails to install .deb packages that trigger debconf prompts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1629021 Title: package clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in clamav package in Ubuntu: New Status in debconf package in Ubuntu: New Bug description: 0.98 was already installed prior to upgrade. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-96.143-generic 3.13.11-ckt39 Uname: Linux 3.13.0-96-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 Date: Thu Sep 29 10:02:15 2016 DuplicateSignature: package:clamav-freshclam:0.99.2+addedllvm-0ubuntu0.14.04.1:subprocess installed post-installation script returned error exit status 128 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2015-01-14 (623 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-96-generic root=UUID=37f17f9e-a506-4ead-8d00-47107a0179fb ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: clamav Title: package clamav-freshclam 0.99.2+addedllvm-0ubuntu0.14.04.1 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/clamav/+bug/1629021/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1575614] Re: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication
Has there been any progress on this bug? The spurious "unencrypted keys" message persists even in network-manager-gnome 1.2.6-0ubuntu0.16.04. -- 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/1575614 Title: [SRU]Can't select p12 secret key for TLS auth for 802.1X authentication Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Status in network-manager-applet source package in Xenial: Fix Released Bug description: [Impact] Users cannot select TLS certificate when connecting to a network that requires TLS type 802.1X authentication [Test case] STR: 1. Click on Connections icon in status panel 2. Click on Edit connections 3. Select Wired connection 4. Go to 802.1x tab 5. Check the Use 802.1X checkbox 6. Choose TLS 7. Click on Secret key button 8. In file chooser navigate to the folder where key is located and try to select key file - the list is empty For wifi connection: 1. Click on Connections icon in status panel 2. Click on Edit connections 3. Select Wi-Fi connection 4. Go to Wi-Fi Security tab 5. Select WPA & WPA2 Enterprise in the drop-down list 6. Choose TLS 7. Click on (None) next to Private key 8. In file chooser navigate to the folder where key is located and try to select key file - the list is empty [Regression Potential] The fix is quite straight forward and the possibility of causing regression is limited. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1575614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1188475] Re: ldap group doesn't work
Why invalid? Please get into ubuntu current code :-) https://github.com/cyrusimap/cyrus-sasl/pull/428 ** Changed in: cyrus-sasl2 (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1188475 Title: ldap group doesn't work Status in cyrus-sasl2 package in Ubuntu: Confirmed Bug description: Hello! I wrote almost the same mail to sasl mail list, but , I guess, it is good to fix in 12.04... This bug exists in 2.1.26 , and in 2.1.25 which is in 12.04 Problem is that after user is authentificated with ldap bind , ldap connection for checking user in group ( lak_group_member function ) is made with this user's bind, not bind parameters from config file. User can not ( and have not in our case- I don't know why , but this is not real problem ) have access to ldap groups. And so, authentication is always fail. I added unbind and anonymous bind ( enough in our case): /var/local/files/sasl/cyrus-sasl-2.1.26/saslauthd# diff -ur lak.c.orig lak.c --- lak.c.orig2013-06-07 09:15:20.098788278 +0400 +++ lak.c2013-06-07 09:22:31.504774185 +0400 @@ -1342,6 +1342,10 @@ if (rc != LAK_OK) goto done; +lak_unbind (lak ); +rc = lak_bind(lak, ""); + + rc = ldap_search_st(lak->ld, group_search_base, lak->conf->group_scope, group_filter, (char **) group_attrs, 0, &(lak->conf->timeout), &res); switch (rc) { case LDAP_SUCCESS: but, it is obvoius that rebind should be done with credintials from config, but this is over my head :-( Could you, please, fix this bug correctly? Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1188475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
** Also affects: pulseaudio (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: gdm3 (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu Xenial) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Xenial) Status: New => Triaged ** Changed in: gdm3 (Ubuntu Zesty) Importance: Undecided => High ** Changed in: gdm3 (Ubuntu Zesty) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Xenial) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Xenial) Status: New => Triaged ** Changed in: pulseaudio (Ubuntu Zesty) Importance: Undecided => High ** Changed in: pulseaudio (Ubuntu Zesty) Status: New => Triaged -- 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/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Fix Committed Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 source package in Xenial: Triaged Status in pulseaudio source package in Xenial: Triaged Status in gdm3 source package in Zesty: Triaged Status in pulseaudio source package in Zesty: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489651] Re: Bluetooth audio not working (with GDM(3))
*** This bug is a duplicate of bug 1703415 *** https://bugs.launchpad.net/bugs/1703415 ** This bug has been marked a duplicate of bug 1703415 Bluetooth audio devices/profiles are missing after logging in from GDM -- 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/1489651 Title: Bluetooth audio not working (with GDM(3)) Status in PulseAudio: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Status in gdm3 package in Debian: New Bug description: I'm having problems with a Marshall Stanmore bluetooth speaker in Ubuntu GNOME 15.10 Beta. It pairs fine and is listed as a bluetooth device but won't show up in the audio settings as a device nor will it show up with pactl list. I also had this problem in Ubuntu GNOME 15.04 with the gnome-staging 3.16 ppa. It works fine with stock Ubuntu GNOME 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1489651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703640] Re: nplan and libnss-resolve should be in same dependency
Release: Artful/17.10 Manually removed libnss-resolve to simulate the result of only having installed ubuntu-minimal (netplan configured with networkd as renderer). 1) Actual result is that /etc/resolv.conf is empty (except for comments). 2) systemctl status systemd-resolved * systemd-resolved.service - Network Name Resolution Loaded: loaded (/lib/systemd/system/systemd-resolved.service; disabled; vendor preset: enabled) Drop-In: /lib/systemd/system/systemd-resolved.service.d └─resolvconf.conf Active: inactive (dead) 3) systemd-resolve --status Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found. journalctl |grep resolve Jul 13 17:14:12 bar-artful6402 kernel: Key type dns_resolver registered Jul 13 17:28:58 bar-artful6402 dbus[765]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' Jul 13 17:28:58 bar-artful6402 dbus[765]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found. Jul 13 17:43:57 bar-artful6402 dbus[765]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' Jul 13 17:43:57 bar-artful6402 dbus[765]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found. networkctl status eth0 * 2: eth0 Link File: /lib/systemd/network/99-default.link Network File: /etc/systemd/network/05-eth0.network Type: ether State: routable (configured) Path: xen-vif-0 Driver: vif HW Address: 00:16:3e:46:16:e2 (Xensource, Inc.) Address: 192.168.2.196 fe80::216:3eff:fe46:16e2 Gateway: 192.168.2.1 (PC Engines GmbH) DNS: 192.168.2.1 -- 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/1703640 Title: nplan and libnss-resolve should be in same dependency Status in systemd package in Ubuntu: Triaged Bug description: I am filing this under nplan because I don't know what better anchor to use. I discovered for systems which I bring up by using debootstrap and then extend that installation to be bootable, I end up with nplan installed but not libnss-resolve. This results in broken DNS resolution when starting to use nplan. It looks like nplan is a dependency of ubuntu-minimal but libnss- resolve is only in ubuntu-standard. But it is also required when using networkd as renderer for netplan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703640] Re: nplan and libnss-resolve should be in same dependency
Network file was still the override I had from when RA was causing problems. Same results after removal and re-applying netplan. -- 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/1703640 Title: nplan and libnss-resolve should be in same dependency Status in systemd package in Ubuntu: Triaged Bug description: I am filing this under nplan because I don't know what better anchor to use. I discovered for systems which I bring up by using debootstrap and then extend that installation to be bootable, I end up with nplan installed but not libnss-resolve. This results in broken DNS resolution when starting to use nplan. It looks like nplan is a dependency of ubuntu-minimal but libnss- resolve is only in ubuntu-standard. But it is also required when using networkd as renderer for netplan. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703415] Re: Bluetooth audio devices/profiles are missing after logging in from GDM
This bug was fixed in the package gdm3 - 3.24.2-1ubuntu9 --- gdm3 (3.24.2-1ubuntu9) artful; urgency=medium * debian/default.pa - Added new file to disable Bluetooth audio devices in PulseAudio from gdm3. (LP: #1703415) (LP: #1489651) * debian/gdm3.install - Added details of the default.pa file * debian/gdm3.postinst - Added installation of default.pa and creation of dir if it doesn't exist. -- Will Cooke Thu, 13 Jul 2017 12:14:34 +0100 ** Changed in: gdm3 (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1703415 Title: Bluetooth audio devices/profiles are missing after logging in from GDM Status in gdm: Confirmed Status in PulseAudio: Confirmed Status in gdm3 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Triaged Status in gdm3 source package in Xenial: Triaged Status in pulseaudio source package in Xenial: Triaged Status in gdm3 source package in Zesty: Triaged Status in pulseaudio source package in Zesty: Triaged Status in gdm3 package in Debian: New Bug description: This is actually a PulseAudio bug, but the workaround is to disable Bluetooth audio in GDM. Further discussion (and the source of my understanding about this issue) upstream are here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805414 To summarise: GDM opens the A2DP profile for a11y purposes to allow screenreaders to output over BT audio devices. However Pulse doesn't release those devices when no audio is being played and the upshot is that once in the users session A2DP is not available for any Bluetooth audio devices, this means that you can only use the low quality profile HSP/HFP. There is a proposed workaround, but this means that a11y tools which need to output audio won't be able to use Bluetooth devices within GDM. I think that for 17.10 shipping this work-around is acceptable, and we should revisit in the 18.04 cycle to try and get a proper fix in PA. The suggested PA bug is: https://bugs.freedesktop.org/show_bug.cgi?id=57167 but that hasn't seen movement since 2012. = The work around = From the Debian wiki: https://wiki.debian.org/BluetoothUser/a2dp Disable the Bluetooth sink in the GDM PA daemon. Add this to /var/lib/gdm3/.config/pulse/default.pa #!/usr/bin/pulseaudio -nF # # load system wide configuration .include /etc/pulse/default.pa ### unload driver modules for Bluetooth hardware .ifexists module-bluetooth-policy.so unload-module module-bluetooth-policy .endif .ifexists module-bluetooth-discover.so unload-module module-bluetooth-discover .endif I have tested this, and I can confirm that it allows access to A2DP again in the user session. To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1703415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489651] Re: Bluetooth audio not working (with GDM(3))
*** This bug is a duplicate of bug 1703415 *** https://bugs.launchpad.net/bugs/1703415 This bug was fixed in the package gdm3 - 3.24.2-1ubuntu9 --- gdm3 (3.24.2-1ubuntu9) artful; urgency=medium * debian/default.pa - Added new file to disable Bluetooth audio devices in PulseAudio from gdm3. (LP: #1703415) (LP: #1489651) * debian/gdm3.install - Added details of the default.pa file * debian/gdm3.postinst - Added installation of default.pa and creation of dir if it doesn't exist. -- Will Cooke Thu, 13 Jul 2017 12:14:34 +0100 ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Fix Released -- 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/1489651 Title: Bluetooth audio not working (with GDM(3)) Status in PulseAudio: Confirmed Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Status in gdm3 package in Debian: New Bug description: I'm having problems with a Marshall Stanmore bluetooth speaker in Ubuntu GNOME 15.10 Beta. It pairs fine and is listed as a bluetooth device but won't show up in the audio settings as a device nor will it show up with pactl list. I also had this problem in Ubuntu GNOME 15.04 with the gnome-staging 3.16 ppa. It works fine with stock Ubuntu GNOME 15.04. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1489651/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704171] [NEW] WiFi connections unstable
Public bug reported: I have 3 WiFi signals here, and use them all without issue most of the time. Since upgrading to 17.04 I have issues where my wifi will not connect to one of the other 2 signals, then also won't re-connect to the signal that was just in use. When this happens, I can do a 'restart' and it will connect just fine to any of the 3 signals. While it was failing a bit ago, I captured the syslog of whats going on and will include it below. Distributor ID: Ubuntu Description:Ubuntu 17.04 Release:17.04 Codename: zesty Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' (58396782-9fe4-4ce3-b0e6-f72df56c72d5) Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2720] audit: op="connection-activate" uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 result="success" Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2723] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2725] manager: NetworkManager state is now CONNECTING Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to C4:D9:87:6E:9B:0F (permanent) Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.891148] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898132] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898220] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.183332] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190314] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190403] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.274573] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> disabled Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has security, but secrets are required. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has security, and secrets exist. No new secrets needed. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6739] Config: added 'ssid' value 'LisaN' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'scan_ssid' value '1' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'psk' value '' Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.7127] sup-iface[0x55b98e0536e0,wlp2s0]: config: set interface ap_scan to 1 Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.7128] device (wlp2s0): supplicant interface state: disabled -> inactive Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.7242] device (wlp2s0): supplicant interface state: inactive -> scanning Jul 13 09:52:42 lisa-Inspiron-7720 wpa_supplicant[1259]:
[Touch-packages] [Bug 1704171] Re: WiFi connections unstable
Adding text file of syslog for readability ** Attachment added: "UbuntuWiFiFailure.txt" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704171/+attachment/4914176/+files/UbuntuWiFiFailure.txt -- 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/1704171 Title: WiFi connections unstable Status in network-manager package in Ubuntu: New Bug description: I have 3 WiFi signals here, and use them all without issue most of the time. Since upgrading to 17.04 I have issues where my wifi will not connect to one of the other 2 signals, then also won't re-connect to the signal that was just in use. When this happens, I can do a 'restart' and it will connect just fine to any of the 3 signals. While it was failing a bit ago, I captured the syslog of whats going on and will include it below. Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty Linux lisa-Inspiron-7720 4.10.0-28-generic #32-Ubuntu SMP Fri Jun 30 05:32:18 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2717] device (wlp2s0): Activation: starting connection 'LisaN' (58396782-9fe4-4ce3-b0e6-f72df56c72d5) Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2720] audit: op="connection-activate" uuid="58396782-9fe4-4ce3-b0e6-f72df56c72d5" name="LisaN" pid=1962 uid=1000 result="success" Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2723] device (wlp2s0): state change: disconnected -> prepare (reason 'none') [30 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2725] manager: NetworkManager state is now CONNECTING Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.2779] device (wlp2s0): set-hw-addr: set-cloned MAC address to C4:D9:87:6E:9B:0F (permanent) Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.891148] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898132] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 312.898220] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.183332] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190314] iwlwifi :02:00.0: L1 Enabled - LTR Disabled Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.190403] iwlwifi :02:00.0: Radio type=0x2-0x1-0x0 Jul 13 09:52:39 lisa-Inspiron-7720 kernel: [ 313.274573] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6644] device (wlp2s0): supplicant interface state: inactive -> disabled Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6649] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): Activation: (wifi) access point 'LisaN' has security, but secrets are required. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6654] device (wlp2s0): state change: config -> need-auth (reason 'none') [50 60 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6728] device (wlp2s0): state change: need-auth -> prepare (reason 'none') [60 40 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6735] device (wlp2s0): state change: prepare -> config (reason 'none') [40 50 0] Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6738] device (wlp2s0): Activation: (wifi) connection 'LisaN' has security, and secrets exist. No new secrets needed. Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6739] Config: added 'ssid' value 'LisaN' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'scan_ssid' value '1' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'key_mgmt' value 'WPA-PSK' Jul 13 09:52:39 lisa-Inspiron-7720 NetworkManager[1047]: [1499961159.6740] Config: added 'psk' value '' Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: Can't set a parent on widget which has a parent Jul 13 09:52:39 lisa-Inspiron-7720 nm-applet[1962]: gtk_widget_destroy: assertion 'GTK_IS_WIDGET (widget)' failed Jul 13 09:52:39 lisa-Inspiron-7720 nm-app
[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
** Tags added: indeed -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Status in unattended-upgrades source package in Artful: Confirmed Status in update-notifier source package in Artful: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704174] [NEW] update apparmor rules to include wicd's dhclient.conf file
Public bug reported: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. ** Affects: isc-dhcp (Ubuntu) Importance: Undecided Status: New ** Tags: patch ** Patch added: "sbin.dhclient-wicd.patch" https://bugs.launchpad.net/bugs/1704174/+attachment/4914177/+files/sbin.dhclient-wicd.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1704174 Title: update apparmor rules to include wicd's dhclient.conf file Status in isc-dhcp package in Ubuntu: New Bug description: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1704174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689299] Re: ssh-agent systemd user service failed to start, trying to set environment in Upstart way.
Colin, could you please SRU this fix to Zesty as well? -- 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/1689299 Title: ssh-agent systemd user service failed to start, trying to set environment in Upstart way. Status in openssh package in Ubuntu: Fix Committed Bug description: "systemctl --user status ssh-agent.service" give me the following info: agent-launch[11327]: initctl: Name "com.ubuntu.Upstart" does not exist As I'm running Systemd session instead of Upstart one, it shouldn't try to run initctl. So, I take a look at /usr/lib/openssh/agent- launcher. And this is what's in the file: if type initctl >/dev/null 2>&1; then initctl set-env --global SSH_AUTH_SOCK=$S fi So, the script checks if Upstart is installed, but doesn't actually check if the current session is Upstart session or not. It has to check if $UPSTART_SESSION is defined or not. $ lsb_release -a LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:printing-9.20160110ubuntu5-amd64:printing-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch Distributor ID: Ubuntu Description: Ubuntu 17.04 Release: 17.04 Codename: zesty $ LANG=C apt policy openssh-client openssh-client: Installed: 1:7.4p1-10 Candidate: 1:7.4p1-10 Version table: *** 1:7.4p1-10 500 500 http://th.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: openssh-client 1:7.4p1-10 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 Uname: Linux 4.10.0-20-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Mon May 8 17:51:09 2017 InstallationDate: Installed on 2013-04-23 (1475 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:7.4p1-10 SSHClientVersion: OpenSSH_7.4p1 Ubuntu-10, OpenSSL 1.0.2g 1 Mar 2016 SourcePackage: openssh UpgradeStatus: Upgraded to zesty on 2017-04-29 (9 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1689299/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997200] Re: Add NetworkManager connectivity config package
I split the gnome-control-center part of this feature to LP: #1704162 -- 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/997200 Title: Add NetworkManager connectivity config package Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Status in network-manager source package in Precise: Won't Fix Status in update-manager source package in Precise: Won't Fix Status in network-manager source package in Quantal: Won't Fix Status in update-manager source package in Quantal: Won't Fix Status in network-manager source package in Raring: Won't Fix Status in update-manager source package in Raring: Won't Fix Status in network-manager package in Debian: Fix Released Bug description: Feature === A separate network-manager-config-connectivity package that contains the 3-line config snippet to enable NetworkManager's connectivity check. This is the same approach taken by Fedora since 2014 (their package is named config-connectivity-fedora). jbicha would like to have ubuntu-gnome-desktop recommend this package for zesty. With this config, GNOME Shell will popup a browser page when a captive portal is detected. The browser page is powered by webkit2gtk. https://help.gnome.org/misc/release-notes/3.14/#captive-portals By making it a separate package, it is very easy for Ubuntu flavors to opt in to installing it by default if they choose. And it's very easy for users to opt in or out without needing to mess around with system configuration files. This new feature (and how to opt out) will be mentioned in Ubuntu GNOME's Release Notes. Enabling the connectivity check by default for all of Ubuntu was discussed almost 5 years ago: https://lists.ubuntu.com/archives/ubuntu-devel/2012-July/035490.html Link to new discussion: https://lists.ubuntu.com/archives/ubuntu-devel/2017-February/039696.html Git merge proposal attached. Original Bug Report == When in a hotel there is a often a T&Cs page that is delivered when connecting to the network. Some combination of network manager and update manager (or something else entirely) doesn't seem to be able to handle this, and update are left in a non-working state after not being able to read package headers file. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: network-manager 0.9.4.0-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 17:27:02 2012 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) IpRoute: default via 10.155.32.1 dev wlan0 proto static 10.155.32.0/19 dev wlan0 proto kernel scope link src 10.155.38.82 metric 2 169.254.0.0/16 dev wlan0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to precise on 2012-03-07 (63 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.4.0connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/997200/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693850] Re: libzen wasn't compiled with large file support
Tested and verified on xenial, yakkety and zesty. ** Tags removed: verification-needed verification-needed-xenial verification-needed-yakkety verification-needed-zesty ** Tags added: verification-done verification-done-xenial verification-done-yakkety verification-done-zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libzen in Ubuntu. https://bugs.launchpad.net/bugs/1693850 Title: libzen wasn't compiled with large file support Status in libzen package in Ubuntu: Fix Released Status in libzen source package in Xenial: Fix Committed Status in libzen source package in Yakkety: Fix Committed Status in libzen source package in Zesty: Fix Committed Status in libzen source package in Artful: Fix Released Bug description: [Impact] The switch to cmake caused two compilation flags to be accidentally dropped: -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 This causes all file-handling operations in zenlib to fail to work with large files on 32-bit machines. This affects the following reverse-dependencies: - libmediainfo - mediainfo - mediaconch This has been fixed in https://github.com/MediaArea/ZenLib/commit/dc105b3ed035413577d21c979d1998d889350855. [Test Case] Run `mediainfo $filename` where $filename is a file that is larger than 4.2GB. Output will be missing if this bug is present. [Regression Potential] Quite low, since the only thing that's changed here are some -D compilation flags that aren't even directly referenced in the codebase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libzen/+bug/1693850/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1702741] Re: QtCreator crashes when opening a filechooser under wayland
Hello Andrew, or anyone else affected, Accepted qtbase-opensource-src into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /qtbase-opensource-src/5.7.1+dfsg-2ubuntu4~1.17.04.1 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: qtbase-opensource-src (Ubuntu Zesty) Status: In Progress => 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 qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1702741 Title: QtCreator crashes when opening a filechooser under wayland Status in qtbase-opensource-src package in Ubuntu: Fix Committed Status in qtbase-opensource-src source package in Zesty: Fix Committed Status in qtbase-opensource-src package in Debian: Fix Released Bug description: Impact == The file chooser dialog app for Qt apps will crash the app when trying to use the file chooser from a Wayland session such as GNOME on Wayland. GNOME on Wayland is included by default in Ubuntu GNOME. Test Case = 1) Install Ubuntu 17.04 GNOME 2) On the login screen, click the gear button and choose GNOME on Wayland and log in. 3) Install qtcreator 4) Launch qtcreator 5) Try to do File -> Open File or Project The file chooser should open without crashing the app Regression Potential This fix was included in Qt 5.8. This patch was applied in Debian stretch in January as part of qtbase-opensource-src 5.7.1+dfsg-3 == Upstream == There is a qt bug here "GTK+ dialogs crash on Wayland" - https://bugreports.qt.io/browse/QTBUG-55583 With what looks like a simple code change that Ubuntu could carry as a patch? https://codereview.qt-project.org/#/c/179124/ Fedora appear to have fixed the bug in Fedora 25 - https://bugzilla.redhat.com/show_bug.cgi?id=1403500 == Debug output == When this occurs in the console you see the following: (qtcreator:16534): Gdk-WARNING **: /build/gtk+3.0-qPyWJl/gtk+3.0-3.22.11/./gdk/x11/gdkwindow-x11.c:5573 drawable is not a native X11 window Segmentation fault (core dumped) When running under GDB: http://pastebin.ubuntu.com/25033921/ $ apt-cache policy qtcreator qtcreator: Installed: 4.1.0-3ubuntu1 Candidate: 4.1.0-3ubuntu1 Version table: *** 4.1.0-3ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu zesty/universe amd64 Packages 100 /var/lib/dpkg/status $ lsb_release -rd Description: Ubuntu 17.04 Release: 17.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1702741/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 474646] Re: house renovation
Hello! I'm planning some house renovation in the near future, so I wanted to show you some pictures of walls I really like, what do you think? Here is the link http://amontanaview.com/wine.php?c7c6 Darren Barney From: Bug 474646 [mailto:474...@bugs.launchpad.net] Sent: Thursday, July 13, 2017 1:38 PM To: sha...@computersystemconsulting.ca Subject: He's role-playing, dude. Sorry for such a late reply. Thanks for the advice and yeah I was worried about the shrimp being eaten but I also thought I could put alot of plants for them to hide. By the way I didn't know the substrate didn't make any difference! That's good to know and also very informative I would of never found out without asking. But either way what do you personally recommend for a nood :( Sent from Mail for Windows 10 ** Attachment added: "953D93BB9E5D2E7E67D8E00F8A82CB04.jpg" https://bugs.launchpad.net/bugs/474646/+attachment/4914226/+files/953D93BB9E5D2E7E67D8E00F8A82CB04.jpg -- 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/474646 Title: sound dos not work crackaling noise only Status in alsa-driver package in Ubuntu: Invalid Bug description: This as not worked for some time I have added utills but they don't help. New upgrade to the latest version did not help If run a game call railroad tycoon the sound dose work. so the card in the laptap is ok I am running a msi mega book s430x AMD Athlon-x2 64 ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: NVidia [HDA NVidia], device 0: ALC883 Analog [ALC883 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shanta 2558 F pulseaudio Card0.Amixer.info: Card hw:0 'NVidia'/'HDA NVidia at 0xfebd8000 irq 23' Mixer name : 'Realtek ALC883' Components : 'HDA:10ec0883,1462373d,0012 HDA:11c11040,11c10001,00100200' Controls : 23 Simple ctrls : 14 CheckboxCommand: alsa_record_playback CheckboxDescription: Connect a microphone to your microphone port. Click the Test button, then speak into the microphone. After a few seconds, your speech will be played back to you. Did you hear your speech played back? CheckboxTest: alsa_record_playback_external Date: Wed Nov 4 11:46:10 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: alsa-base 1.0.20+dfsg-1ubuntu5 PackageArchitecture: all ProcEnviron: SHELL=/bin/bash LANG=en_CA.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: alsa-driver Tags: checkbox-bug Uname: Linux 2.6.31-14-generic x86_64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/474646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703631] Re: Rebuilt with new libgdal20 needed
This is a normal part of the development cycle especially before Debian Import Freeze. These are tracked through these pages: https://people.canonical.com/~ubuntu-archive/proposed-migration/artful/update_excuses.html https://people.canonical.com/~ubuntu-archive/proposed-migration/artful/update_output.txt and sometimes through https://people.canonical.com/~ubuntu-archive/transitions/ Debian uses https://release.debian.org/transitions/ I am closing this bug because we don't generally need transition bugs in Ubuntu for syncs from Debian unstable. ** Changed in: vtk6 (Ubuntu) Status: New => Invalid ** Changed in: opencv (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opencv in Ubuntu. https://bugs.launchpad.net/bugs/1703631 Title: Rebuilt with new libgdal20 needed Status in opencv package in Ubuntu: Invalid Status in vtk6 package in Ubuntu: Invalid Bug description: Artful got a new libgdal20 version (2.2.1+dfsg-1) but some packages need to support that new version: these packages are removed if libgdal20 is upgraded: libopencv-imgcodecs3.1 : Depends: gdal-abi-2-1-2 (all libopencv* suppositly concerned ) libvtk6.3 : Depends: gdal-abi-2-1-2 gstreamer1.0-plugins-bad ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libvtk6.3 6.3.0+dfsg1-9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Tue Jul 11 17:32:06 2017 EcryptfsInUse: Yes SourcePackage: vtk6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/1703631/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Proposed package upload rejected
An upload of gnome-session to zesty-proposed has been rejected from the upload queue for the following reason: "Rejecting because of LP: #1700485 - this sounds like a serious regression.". ** Changed in: gnome-session (Ubuntu Yakkety) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged 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 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)
Resetting to "Triaged" with Brian's approval. ** Changed in: gnome-session (Ubuntu Zesty) Status: Won't Fix => Triaged ** Changed in: gnome-online-accounts (Ubuntu Yakkety) Status: Triaged => Won't Fix -- 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: Won't Fix Status in gnome-session source package in Yakkety: Won't Fix Status in gnome-online-accounts source package in Zesty: Triaged Status in gnome-session source package in Zesty: Triaged 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 1703520] Re: DNS resolving doesn't work in complain mode with dnsmasq and apparmor
For the records: revno: 3437 fixes bug: https://launchpad.net/bugs/1569316 committer: Tyler Hicks branch nick: apparmor timestamp: Tue 2016-04-12 16:36:43 -0500 message: profiles: Add attach_disconnected flag to dnsmasq profile https://launchpad.net/bugs/1569316 When Ubuntu made the jump from network-manager 1.0.4 to 1.1.93, the dnsmasq process spawned from network-manager started hitting a disconnected path denial: ;-) Note: I don't know if Ubuntu ships this profile from upstream bzr or has its own one. Or maybe 16.04 is just a bit too old for this change. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1703520 Title: DNS resolving doesn't work in complain mode with dnsmasq and apparmor Status in apparmor package in Ubuntu: New Bug description: After i have firefox, chromium-browser and dnsmasq profiled with sudo aa-autodep (complain-mode was used), i can not resolving websites. (Log is at the attachement) I have copied the profiles of the three programms from the top in /etc/apparmor.d/disable and after a reboot i can resolving websites. The network manager can connect with my router the whole time. I'm have Ubuntu 16.04.02 LTS with all updates. (11.07.2017 CEST) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1703520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704202] [NEW] package bsdutils 1:2.27.1-6ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: I was trying to install as normal the suggested installations, but the software installation couldn't run / had a problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bsdutils 1:2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jul 13 22:23:14 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-02 (71 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: util-linux Title: package bsdutils 1:2.27.1-6ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: 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/1704202 Title: package bsdutils 1:2.27.1-6ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in util-linux package in Ubuntu: New Bug description: I was trying to install as normal the suggested installations, but the software installation couldn't run / had a problem. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: bsdutils 1:2.27.1-6ubuntu3 ProcVersionSignature: Ubuntu 4.8.0-58.63~16.04.1-generic 4.8.17 Uname: Linux 4.8.0-58-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jul 13 22:23:14 2017 DpkgTerminalLog: dpkg: error processing package bsdutils (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-05-02 (71 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: util-linux Title: package bsdutils 1:2.27.1-6ubuntu3 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/util-linux/+bug/1704202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704210] [NEW] NetworkManager does not disable accept_ra when a managed device is set to ipv6 method=ignore
Public bug reported: As per the title; it looks (at first glance anyway, running TestNetworkManager.test_eth_dhcp6_off integration test from nplan) like NM does not set accept_ra to false, or provide a method for specifying whether you want to accept IPv6 RAs on that device. When IPv6 is disabled, we might also not want the kernel to heed RAs and create SLAAC addresses. NM already is able to disable accept_ra, since it does so when a device transitions to UNAVAILABLE or DISCONNECTED in some cases (see src/devices/nm-device.c). ** 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/1704210 Title: NetworkManager does not disable accept_ra when a managed device is set to ipv6 method=ignore Status in network-manager package in Ubuntu: New Bug description: As per the title; it looks (at first glance anyway, running TestNetworkManager.test_eth_dhcp6_off integration test from nplan) like NM does not set accept_ra to false, or provide a method for specifying whether you want to accept IPv6 RAs on that device. When IPv6 is disabled, we might also not want the kernel to heed RAs and create SLAAC addresses. NM already is able to disable accept_ra, since it does so when a device transitions to UNAVAILABLE or DISCONNECTED in some cases (see src/devices/nm-device.c). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1704210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704174] Re: update apparmor rules to include wicd's dhclient.conf file
The attachment "sbin.dhclient-wicd.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] -- 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/1704174 Title: update apparmor rules to include wicd's dhclient.conf file Status in isc-dhcp package in Ubuntu: New Bug description: Package: isc-dhcp-client Version: 4.3.5-3ubuntu Arch: amd64 Release: artful Report == The apparmor rules for /sbin/dhclient are missing an entry for wicd's dhclient.conf file, see the log bellow: audit: type=1400 audit(1499962030.711:50): apparmor="DENIED" operation="open" profile="/sbin/dhclient" name="/var/lib/wicd/dhclient.conf" pid=16339 comm="dhclient" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Expected result === /sbin/dhclient should be allowed to read from /var/lib/wicd/dhclient.conf Other = Patch has been attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1704174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1673817] Re: update-secure-boot-policy behaving badly with unattended-upgrades
An upload of shim-signed to trusty-proposed has been rejected from the upload queue for the following reason: "needs adjusted versioned dep on grub2-common; drop ref to LP: #1624096 from changelog". ** Changed in: unattended-upgrades (Ubuntu Trusty) Status: New => Invalid ** Changed in: unattended-upgrades (Ubuntu Xenial) Status: New => Invalid ** Changed in: unattended-upgrades (Ubuntu Yakkety) Status: New => Invalid -- 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/1673817 Title: update-secure-boot-policy behaving badly with unattended-upgrades Status in shim-signed package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in shim-signed source package in Trusty: New Status in unattended-upgrades source package in Trusty: Invalid Status in shim-signed source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Invalid Status in shim-signed source package in Yakkety: Fix Released Status in unattended-upgrades source package in Yakkety: Invalid Bug description: [Impact] Any user with unattended upgrades enabled and DKMS packages in a Secure Boot environment might be prompted to change Secure Boot policy, which will fail and crash in unattended-upgrades. [Test case] = unattended upgrade = 1) Create /var/lib/dkms/TEST-DKMS 2) Install new package 3) Trigger unattended-upgrades: unattended-upgrades -d Upgrade should run smoothly for all the processing but fail to complete; shim-signed should end the unattended upgrade with a error as unattended change of the Secure Boot policy can not be done. Upgrade should not hang in high CPU usage. = standard upgrade = 1) Create /var/lib/dkms/TEST-DKMS 2) install new package. 3) Verify that the upgrade completes normally. [Regression Potential] Any failure to prompt for or change Secure Boot policy in mokutil while in an *attended* upgrade scenario would constitute a regression of this SRU. Any other issues related to booting in Secure Boot mode should instead be directed to bug 1637290 (shim update). --- Currently, unattended-upgrades will automatically install all updates for those running development releases of Ubuntu (LP: #1649709) Today, my computer was acting very sluggish. Looking at my process list, I saw/ usr/sbin/update-secureboot-policy was using a log of CPU. I killed the process. I have a /var/crash/shim-signed.0.crash but since it's 750 MB, I didn't bother submitting it or looking at it more. Maybe it crashed because I killed the process. Also, I see that unattended-upgrades-dpkg.log is 722 MB. Today's update included both VirtualBox and the linux kernel. I am attaching an excerpt of /var/log/unattended-upgrades/unattended- upgrades-dpkg.log This message was repeated a very large number of times (but I only included it once in the attachment: "Invalid password The Secure Boot key you've entered is not valid. The password used must be between 8 and 16 characters." ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: shim-signed 1.23+0.9+1474479173.6c180c6-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-11.13-generic 4.10.1 Uname: Linux 4.10.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 17 11:15:04 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-02-23 (21 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Alpha amd64 (20170219) SourcePackage: shim-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1673817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1703350] Re: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac
Done 2017-07-11 16:10 GMT-03:00 Andreas Hasenack : > Thanks for filing this bug in Ubuntu. > > Could you please try the following commands: > > sudo apt update > > sudo apt install --reinstall liburcu4 > > And report back here please? > > Thanks > > > ** Changed in: liburcu (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1703350 > > Title: > package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete > está en un estado grave de inconsistencia - debe reinstalarlo antes > de intentar su configuración. > > Status in liburcu package in Ubuntu: > Incomplete > > Bug description: > it crashes on sudo apt update > > ProblemType: Package > DistroRelease: Ubuntu 16.04 > Package: liburcu4:i386 0.9.1-3 > ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 > Uname: Linux 4.4.0-83-generic i686 > ApportVersion: 2.20.1-0ubuntu2.9 > Architecture: i386 > Date: Mon Jul 10 07:44:55 2017 > Dependencies: >gcc-6-base 6.0.1-0ubuntu1 >libc6 2.23-0ubuntu9 >libgcc1 1:6.0.1-0ubuntu1 > ErrorMessage: El paquete está en un estado grave de inconsistencia - > debe reinstalarlo antes de intentar su configuración. > InstallationDate: Installed on 2017-05-20 (51 days ago) > InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 > (20160719) > RelatedPackageVersions: >dpkg 1.18.4ubuntu1.2 >apt 1.2.20 > SourcePackage: liburcu > Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El > paquete está en un estado grave de inconsistencia - debe reinstalarlo > antes de intentar su configuración. > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/ > 1703350/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to liburcu in Ubuntu. https://bugs.launchpad.net/bugs/1703350 Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. Status in liburcu package in Ubuntu: Incomplete Bug description: it crashes on sudo apt update ProblemType: Package DistroRelease: Ubuntu 16.04 Package: liburcu4:i386 0.9.1-3 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 Date: Mon Jul 10 07:44:55 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu9 libgcc1 1:6.0.1-0ubuntu1 ErrorMessage: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. InstallationDate: Installed on 2017-05-20 (51 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: liburcu Title: package liburcu4:i386 0.9.1-3 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configuración. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/liburcu/+bug/1703350/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704238] [NEW] ftbfs on non-amd64
Public bug reported: The build of the test package fails with: make[6]: Leaving directory '/tmp/tmp9tnlt7ag/melticecream' dpkg-genbuildinfo --build=binary dpkg-genbuildinfo: error: binary build with no binary artifacts found; .buildinfo is meaningless dpkg-buildpackage: error: dpkg-genbuildinfo --build=binary gave error exit status 2 Changing the test packages to be arch: all rather than arch: any still leaves test_subsequent_runs_with_new_script failing, with self.assertTrue(re.match("Using '{}' directory\nFile '{files}_test.sh already migrated, skipping\nFile '{files}_test.sh already migrated, skipping\n" "File '{files}_test.sh already migrated, skipping\nExecuting: {}\nExecuting: {}\n".format(self.script_path, os.path.join(self.script_path, '08_test.sh'), os.path.join(self.script_path, '08_testexecute.sh'), files='(01|02|10)'), stdout)) failing to match this output: Using '/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts' directory File '02_test.sh already migrated, skipping File '01_test.sh already migrated, skipping File '10_test.sh already migrated, skipping Executing: /<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_test.sh Executing: /<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_testexecute.sh (as an aside, these tests are not written in such a way as to make failures easy to diagnose!) ** Affects: session-migration (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to session-migration in Ubuntu. https://bugs.launchpad.net/bugs/1704238 Title: ftbfs on non-amd64 Status in session-migration package in Ubuntu: New Bug description: The build of the test package fails with: make[6]: Leaving directory '/tmp/tmp9tnlt7ag/melticecream' dpkg-genbuildinfo --build=binary dpkg-genbuildinfo: error: binary build with no binary artifacts found; .buildinfo is meaningless dpkg-buildpackage: error: dpkg-genbuildinfo --build=binary gave error exit status 2 Changing the test packages to be arch: all rather than arch: any still leaves test_subsequent_runs_with_new_script failing, with self.assertTrue(re.match("Using '{}' directory\nFile '{files}_test.sh already migrated, skipping\nFile '{files}_test.sh already migrated, skipping\n" "File '{files}_test.sh already migrated, skipping\nExecuting: {}\nExecuting: {}\n".format(self.script_path, os.path.join(self.script_path, '08_test.sh'), os.path.join(self.script_path, '08_testexecute.sh'), files='(01|02|10)'), stdout)) failing to match this output: Using '/<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts' directory File '02_test.sh already migrated, skipping File '01_test.sh already migrated, skipping File '10_test.sh already migrated, skipping Executing: /<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_test.sh Executing: /<>/session-migration-0.3.1+ppa4/obj-x86_64-linux-gnu/tests/data/main/session-migration/scripts/08_testexecute.sh (as an aside, these tests are not written in such a way as to make failures easy to diagnose!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/session-migration/+bug/1704238/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704244] [NEW] package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-
Public bug reported: when I start the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jul 12 21:53:47 2017 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2016-06-06 (402 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 xenial -- 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/1704244 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in openssl package in Ubuntu: New Bug description: when I start the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jul 12 21:53:47 2017 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2016-06-06 (402 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1704244/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704244] Bug is not a security issue
*** This bug is a duplicate of bug 1692981 *** https://bugs.launchpad.net/bugs/1692981 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. ** This bug has been marked a duplicate of bug 1692981 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 -- 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/1704244 Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. Status in openssl package in Ubuntu: New Bug description: when I start the system. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libssl1.0.0:i386 1.0.2g-1ubuntu4.8 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Wed Jul 12 21:53:47 2017 ErrorMessage: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. InstallationDate: Installed on 2016-06-06 (402 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.20 SourcePackage: openssl Title: package libssl1.0.0:i386 1.0.2g-1ubuntu4.8 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1704244/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Jeremy, if you get the prompt back immediately after the dpkg -l | awk '/^iH/ { print $2 }' command, that means dpkg thinks nothing is half- installed. This is good news; if you still have problems with: sudo apt-get update sudo apt-get -u dist-upgrade then please paste the results you're getting. Thanks -- 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: Confirmed Status in openssl package in Ubuntu: Confirmed 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
Re: [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 con
Thanks, Seth. I ended up using sudo apt-get install --reinstall libssl1.0.0:i386 (which I found in the term.log listed as a bad package).now everything seems to be working fine. On Thu, Jul 13, 2017 at 5:33 PM, Seth Arnold <1692...@bugs.launchpad.net> wrote: > Jeremy, if you get the prompt back immediately after the dpkg -l | awk > '/^iH/ { print $2 }' command, that means dpkg thinks nothing is half- > installed. This is good news; if you still have problems with: > > sudo apt-get update > sudo apt-get -u dist-upgrade > > then please paste the results you're getting. > > Thanks > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1696799). > 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: > Confirmed > Status in openssl package in Ubuntu: > Confirmed > > 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 > -- 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: Confirmed Status in openssl package in Ubuntu: Confirmed 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 1704250] Re: ERROR
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 xorg in Ubuntu. https://bugs.launchpad.net/bugs/1704250 Title: ERROR Status in xorg package in Ubuntu: New Bug description: The system has a breakdown problem since the new update from ubuntu 15.04, I would like to know how to repair it. From already thank you very much. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.9 Architecture: i386 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Thu Jul 13 22:20:10 2017 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-62-generic, i686: installed bbswitch, 0.8, 4.4.0-66-generic, i686: installed bbswitch, 0.8, 4.4.0-75-generic, i686: installed bbswitch, 0.8, 4.4.0-83-generic, i686: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: NVIDIA Corporation G84 [GeForce 8600 GT] [10de:0402] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] NX8600GT-T2D256EZ [1462:0910] InstallationDate: Installed on 2017-02-09 (154 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) Lsusb: Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0b38:0010 Gear Head 107-Key Keyboard Bus 002 Device 002: ID 04f3:0230 Elan Microelectronics Corp. 3D Optical Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Gigabyte Technology Co., Ltd. GA-73VM-S2 ProcEnviron: LANGUAGE=es_ES PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic root=UUID=73161ce2-6cf4-4d9d-8c08-a11a9e14405b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/07/2008 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4c dmi.board.name: GA-73VM-S2 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4c:bd10/07/2008:svnGigabyteTechnologyCo.,Ltd.:pnGA-73VM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-73VM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-73VM-S2 dmi.sys.vendor: Gigabyte Technology Co., Ltd. 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.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: Thu Jul 13 22:17:49 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputUSB+PS/2 Optical Mouse MOUSE, id 8 inputHID 0b38:0010KEYBOARD, id 9 inputHID 0b38:0010KEYBOARD, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.2 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1704250/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-
[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU
"if dnsmasq's option "--dns-loop-detect" via DNSMASQ_OPTS in /etc/default/dnsmasq." this does not help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1670959 Title: systemd-resolved using 100% CPU Status in dnsmasq package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Sometimes systemd-resolved process is using 100% CPU. After a while it changes back to normal. It happens usually after connecting to the (wifi) network, like starting the OS. strace output: sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0", 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], msg_flags=0}, 0) = 81 sendmsg(3, {msg_name(0)=NULL, msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n", 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188 epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1 clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0 recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53 recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), sin_addr=inet_addr("127.0.0.1")}, msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0", 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, {cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) = 53 stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 getrandom("\365I", 2, GRND_NONBLOCK)= 2 stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 getrandom("\203;", 2, GRND_NONBLOCK)= 2 clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0 open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0 socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18 connect(18, {sa_family=AF_INET, sin_port=htons(53), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, u64=94565471566608}}) = 0 write(18, "\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0", 53) = 53 clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0 clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0 epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL) = 0 close(18) = 0 journalctl output: Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query... Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS queries reached (max: 150) As you can see, I would use it together with dnsmasq. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: systemd 232-18ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0 Uname: Linux 4.10.0-9-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 Date: Wed Mar 8 08:20:18 2017 MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1 ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@ SourcePackage: systemd UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago) dmi.bios.date: 03/09/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M77 Ver. 01.05 dmi.board.name: 2271 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.4C dmi.chassis.asset.tag: CNU51199KV dmi.chassis.type: 10 dmi.chas
[Touch-packages] [Bug 1704262] [NEW] package base-files 9.6ubuntu13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: while doing multiple installs at a same time this error occurred. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 Date: Fri Jul 14 08:09:04 2017 DpkgTerminalLog: dpkg: error processing package base-files (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-01-24 (170 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: base-files Title: package base-files 9.6ubuntu13 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-17 (87 days ago) ** Affects: base-files (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 base-files in Ubuntu. https://bugs.launchpad.net/bugs/1704262 Title: package base-files 9.6ubuntu13 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in base-files package in Ubuntu: New Bug description: while doing multiple installs at a same time this error occurred. ProblemType: Package DistroRelease: Ubuntu 17.04 Package: base-files 9.6ubuntu13 ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17 Uname: Linux 4.10.0-26-generic i686 ApportVersion: 2.20.4-0ubuntu4 Architecture: i386 Date: Fri Jul 14 08:09:04 2017 DpkgTerminalLog: dpkg: error processing package base-files (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-01-24 (170 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2) RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4 SourcePackage: base-files Title: package base-files 9.6ubuntu13 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-17 (87 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1704262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable
I have sound-theme-freedesktop (0.8-1ubuntu1) installed and still get white noise. Is something still missing? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1703946 Title: Dedicated mono test sound is unavailable Status in sound-theme-freedesktop package in Ubuntu: Fix Released Bug description: When testing stereo speakers you get the "Front left" and "Front right" samples, but no such sample exists for mono speakers e.g. HSP/HFP bluetooth devices. Instead you get played the "audio-test-signal" which is white noise. To begin with I thought this was a problem with Bluetooth or the speaker itself, but it's just the sample being used. There is a bug upstream to provide this sample, but in the meantime I think playing the "audio-channel-front-center.oga" is a suitable standin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1703946] Re: Dedicated mono test sound is unavailable
$ ls -l /usr/share/sounds/freedesktop/stereo/audio-channel-* -rw-r--r-- 1 root root 17015 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-front-center.oga -rw-r--r-- 1 root root 15675 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-front-left.oga -rw-r--r-- 1 root root 19019 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-front-right.oga lrwxrwxrwx 1 root root30 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-mono.oga -> audio-channel-front-center.oga -rw-r--r-- 1 root root 17099 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-rear-center.oga -rw-r--r-- 1 root root 14129 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-rear-left.oga -rw-r--r-- 1 root root 18791 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-rear-right.oga -rw-r--r-- 1 root root 17089 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-side-left.oga -rw-r--r-- 1 root root 17198 Jul 13 02:16 /usr/share/sounds/freedesktop/stereo/audio-channel-side-right.oga -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sound-theme-freedesktop in Ubuntu. https://bugs.launchpad.net/bugs/1703946 Title: Dedicated mono test sound is unavailable Status in sound-theme-freedesktop package in Ubuntu: Fix Released Bug description: When testing stereo speakers you get the "Front left" and "Front right" samples, but no such sample exists for mono speakers e.g. HSP/HFP bluetooth devices. Instead you get played the "audio-test-signal" which is white noise. To begin with I thought this was a problem with Bluetooth or the speaker itself, but it's just the sample being used. There is a bug upstream to provide this sample, but in the meantime I think playing the "audio-channel-front-center.oga" is a suitable standin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sound-theme-freedesktop/+bug/1703946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 216847] Re: sshd will not start at boot if ListenAddress is set, because network interface is not yet up
As Seth mentioned in comment #13 likely network-online.target should be the solution. @Owlbsidian - could you test and confirm with that as a fix as well? A related fun quote from the systemd page about it: "... please just fix your program to be friendly to dynamically changing network configuration. That way you will make your users happy because things just start to work, and you will get fewer bug reports ..." Without that support you can still run into issues if e.g. you have a manually added interface you depend on (no service target will help you there). But that in turn would be an upstream feature request more than anything else. Anyway, as long as ssh doesn't support that we might want to finally tackle that issue to at least improve it. Now that systemd has more means to express "online". Maybe even by directly fixing it in Debian. Subscribing server to track and cjwatson for his opinion (actually I see he is auto-subscribed to the pkg so he will see). -- 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/216847 Title: sshd will not start at boot if ListenAddress is set, because network interface is not yet up Status in openssh package in Ubuntu: Confirmed Bug description: Binary package hint: openssh-server The sshd will not start at boot if the ListenAddress option in /etc/ssh/sshd_config is set to an IPv4 address other then 0.0.0.0 . I am using Ubuntu 7.10 and the version 1:4.6p1-5ubuntu0.2 of the openssh-server package. I would expect that sshd is started after boot but it will not and I found this in /var/log/auth.log: sshd[4527]: error: Bind to port 22 on 10.1.1.22 failed: Cannot assign requested address. sshd[4527]: fatal: Cannot bind any address. Once the System is started you can start/stop the sshd with the /etc/init.d/ssh script without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/216847/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704297] [NEW] Parrot Zik headphones stuck in A2DP profile
Public bug reported: I've got a pair of Parot Zik bluetooth headphones, with inbuilt microphones and such. The Sound control panel offers a “Profile” dropdown, with choice of A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add an input source to the “Inputs” tab, and (b) doesn't stop the headphones playing stereo sound, indicating that it hasn't actually been switched to HSP profile (which is, AFAIK, mono). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chris 7755 F pulseaudio /dev/snd/controlC1: chris 7755 F pulseaudio /dev/snd/pcmC0D0c: chris 7755 F...m pulseaudio /dev/snd/controlC0: chris 7755 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 16:27:09 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful third-party-packages wayland-session -- 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/1704297 Title: Parrot Zik headphones stuck in A2DP profile Status in pulseaudio package in Ubuntu: New Bug description: I've got a pair of Parot Zik bluetooth headphones, with inbuilt microphones and such. The Sound control panel offers a “Profile” dropdown, with choice of A2DP and HSP profiles, but selecting the HSP profile (a) doesn't add an input source to the “Inputs” tab, and (b) doesn't stop the headphones playing stereo sound, indicating that it hasn't actually been switched to HSP profile (which is, AFAIK, mono). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chris 7755 F pulseaudio /dev/snd/controlC1: chris 7755 F pulseaudio /dev/snd/pcmC0D0c: chris 7755 F...m pulseaudio /dev/snd/controlC0: chris 7755 F pulseaudio CurrentDesktop: GNOME Date: Fri Jul 14 16:27:09 2017 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA1 02/20/2017 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA102/20/2017:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.name: Oryx Pro dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1704297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704295] [NEW] Gnome Software titlebar is too thin during startup under Ambiance
Public bug reported: Gnome Software titlebar is too thin during startup under Ambiance ** Affects: gnome-software (Ubuntu) Importance: Medium Status: New ** Affects: ubuntu-themes (Ubuntu) Importance: Medium Status: New ** Tags: gnome-17.10 visual-quality ** Also affects: ubuntu-themes (Ubuntu) Importance: Undecided Status: New ** Tags added: gnome-17.10 ** Tags added: visual-quality -- 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/1704295 Title: Gnome Software titlebar is too thin during startup under Ambiance Status in gnome-software package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Gnome Software titlebar is too thin during startup under Ambiance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1704295] Re: Gnome Software titlebar is too thin during startup under Ambiance
Although closing the app and reopening it often skips the thin titlebars phase so it's not easy to reproduce on demand... ** Changed in: gnome-software (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Medium -- 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/1704295 Title: Gnome Software titlebar is too thin during startup under Ambiance Status in gnome-software package in Ubuntu: New Status in ubuntu-themes package in Ubuntu: New Bug description: Gnome Software titlebar is too thin during startup under Ambiance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1704295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1699759] Comment bridged from LTC Bugzilla
--- Comment From urjaw...@in.ibm.com 2017-07-14 02:27 EDT--- Any Updates ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1699759 Title: LXC Alpine template broken on ppc64le Status in The Ubuntu-power-systems project: Fix Committed Status in lxc package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Breno Leitao - 2017-06-14 07:36:33 == LXC Alpine template is broken on Ubuntu 17.10, since it does not support ppc64le. It shows the following message: # Unknown architecture. == Comment: #1 - Breno Leitao - 2017-06-14 07:37:50 == Patch sent to upstream and accepted already: https://github.com/lxc/lxc/pull/1621#issuecomment-307887344 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1699759/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1696945] Re: Ubuntu's red close button is too far left in Gnome Shell (Ambiance and Radiance)
** Changed in: ubuntu-themes Importance: Undecided => Low ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low -- 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/1696945 Title: Ubuntu's red close button is too far left in Gnome Shell (Ambiance and Radiance) Status in Ubuntu theme: Incomplete Status in Ubuntu UX: New Status in ubuntu-themes package in Ubuntu: Incomplete Bug description: Ubuntu's red close button is too far left in Gnome Shell (Ambiance and Radiance) Although this is only a problem in client-side decorated titlebars (the thick ones like in Nautilus and Settings) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-themes/+bug/1696945/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1693724] Re: Context menus have no animation/fade-in under Gnome Shell
** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low -- 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/1693724 Title: Context menus have no animation/fade-in under Gnome Shell Status in gnome-shell package in Ubuntu: Confirmed Status in ubuntu-themes package in Ubuntu: Confirmed Status in gnome-shell package in Arch Linux: New Bug description: Context menus have no animation/fade-in under Gnome Shell. The transitions under Unity7 for context menus look nicer, less abrupt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1693724/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp