[Touch-packages] [Bug 1781125] Re: Display drivers are not Avaialble
It appears the problem is that you have partially/unsuccessfully/manually installed the Nvidia graphics driver but it's no longer installed and it has left the 'nomodeset' flag in your kernel command line: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID =47ee8f4e-ddca-4b1f-beeb-159611ec343b ro nomodeset which will prevent the default 'nouveau' graphics driver from working properly. To fix this you should edit your /etc/default/grub and remove 'nomodeset'. Then run 'sudo update-initramfs' and reboot. That will allow the nouveau driver to work properly. If that doesn't fully solve the problem then you can later also try the official nvidia driver by running: sudo apt install nvidia-driver-390 ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1781125 Title: Display drivers are not Avaialble Status in xorg-server package in Ubuntu: Invalid Bug description: I cannot see the displays listed in my display settings. Can't plugin an extra monitor. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Jul 11 10:53:54 2018 DistUpgraded: 2018-07-10 12:43:41,594 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07d1] Subsystem: Dell Device [1028:07d1] InstallationDate: Installed on 2017-09-12 (301 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 5580 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=47ee8f4e-ddca-4b1f-beeb-159611ec343b ro nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-07-10 (0 days ago) dmi.bios.date: 03/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.3 dmi.board.name: 0FH6CJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.3:bd03/08/2018:svnDellInc.:pnLatitude5580:pvr:rvnDellInc.:rn0FH6CJ:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5580 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 11 10:49:48 2018 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1781125/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780807] Re: Please provide ED25519 support in 18.04 OpenSSL
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssl (Ubuntu) Status: New => Confirmed -- 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/1780807 Title: Please provide ED25519 support in 18.04 OpenSSL Status in openssl package in Ubuntu: Confirmed Bug description: Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking support for the ED25519 signature algorithm. As ED25519 is quickly gaining traction as most demanded and preferred elliptic curve algorithm, it would be a substantial issue not to have any support for it in the remaining lifetime of Ubuntu LTS released most recently. OpenSSL is introducing ED25519 with their 1.1.1 release, which is currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1780807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781160] [NEW] current issue tab keeps on crashing - plus error message pops up on login
Public bug reported: see summary for details ProblemType: Package DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2.4 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jul 11 08:48:20 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-08-27 (682 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: procps Title: package procps 2:3.3.10-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1781160 Title: current issue tab keeps on crashing - plus error message pops up on login Status in procps package in Ubuntu: New Bug description: see summary for details ProblemType: Package DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2.4 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jul 11 08:48:20 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-08-27 (682 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: procps Title: package procps 2:3.3.10-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1781160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1778366] Re: apt.package.Version.raw_description doesn’t work
For more detail: The question is whether raw_description is intended to get the Description field in the packages file, which it does; or whether it's intended to get the unformatted translated description. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1778366 Title: apt.package.Version.raw_description doesn’t work Status in python-apt package in Ubuntu: New Bug description: The raw_description property of apt.package.Version returns the summary rather than the long description. This is because it accesses self._records instead of self._translated_records, and the long description is located only in the translated records. Ubuntu 18.04 LTS python3-apt 1.6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1778366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737441] Re: python-apt crashes if objects of one cache are passed to depcache belonging to another cache
Hello errors.ubuntu.com, or anyone else affected, Accepted python-apt into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python- apt/1.1.0~beta1ubuntu0.16.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: python-apt (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial ** Changed in: python-apt (Ubuntu Trusty) Status: New => Fix Committed ** Tags added: verification-needed-trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: python-apt crashes if objects of one cache are passed to depcache belonging to another cache Status in python-apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in python-apt source package in Trusty: Fix Committed Status in unattended-upgrades source package in Trusty: Won't Fix Status in python-apt source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: Won't Fix Status in python-apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache, performing operations on the old package would perform it on the new package. If the old package's ID is out of bounds in the new cache, the behavior is undefined - it's an out of bounds array access. [Test case] The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. More test cases like this are in the autopkgtest. [Regression potential] The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. [Other info] The xenial SRU also includes the change "python/tag.cc: Fix invalid read in TagFileNext". We don't have any specific verification for it, as we just saw weird crashes on the error tracker, and this seemed like the culprit. We released bionic with it, and it seems fine. The fix is fairly obvious: We were copying the char array "Start" which was not nul terminated in an odd way, without using the lenght. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737441] Please test proposed package
Hello errors.ubuntu.com, or anyone else affected, Accepted python-apt into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python- apt/0.9.3.5ubuntu3 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-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: python-apt crashes if objects of one cache are passed to depcache belonging to another cache Status in python-apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in python-apt source package in Trusty: Fix Committed Status in unattended-upgrades source package in Trusty: Won't Fix Status in python-apt source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: Won't Fix Status in python-apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache, performing operations on the old package would perform it on the new package. If the old package's ID is out of bounds in the new cache, the behavior is undefined - it's an out of bounds array access. [Test case] The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. More test cases like this are in the autopkgtest. [Regression potential] The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. [Other info] The xenial SRU also includes the change "python/tag.cc: Fix invalid read in TagFileNext". We don't have any specific verification for it, as we just saw weird crashes on the error tracker, and this seemed like the culprit. We released bionic with it, and it seems fine. The fix is fairly obvious: We were copying the char array "Start" which was not nul terminated in an odd way, without using the lenght. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1737441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781091] Re: notify-send only works the first time
OK, thanks. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid ** Changed in: libnotify (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1781091 Title: notify-send only works the first time Status in gnome-shell package in Ubuntu: Invalid Status in libnotify package in Ubuntu: Invalid Bug description: (I think this started happening after upgrading gnome-shell to 3.28.2-0ubuntu0.18.04.1 today.) Reproduce: * Run `notify-send ok ok`. Expected result: * A notification pops up for every execution of the command above. Actual result: * A notification might pop up every once in a while (it always appears the first time, I think). The journal gets a message like this for every notify-send call: Jul 11 02:29:20 tensin-pc1 gnome-shell[3723]: JS ERROR: Call to GetConnectionUnixProcessID failed: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name ':1.68': no such name _proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:71:26 I use notify-send in quite a few of my scripts, and it broke precisely today. > lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779942] Re: package python3-apt 1.6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
PackageKit should not have attempted to do stuff in that situation I think ** Package changed: python-apt (Ubuntu) => packagekit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1779942 Title: package python3-apt 1.6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in packagekit package in Ubuntu: New Bug description: I was trying to install virtualbox then I received a message that I needed to run dpkg manually and then it reported the the python3-apt was in error ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3-apt 1.6.1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Tue Jul 3 18:01:23 2018 DuplicateSignature: package:python3-apt:1.6.1 Setting up make (4.1-9.1ubuntu1) ... dpkg: error processing package python3-apt (--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 2018-07-03 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: python-apt Title: package python3-apt 1.6.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1779942/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781183] Re: Skip updates on metered connections
Fixed in 1.4ubuntu1 ** Changed in: unattended-upgrades (Ubuntu) Status: New => Fix Released -- 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/1781183 Title: Skip updates on metered connections Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades package in Debian: Unknown Bug description: [Impact] * Systems running unattended-upgrades may download updates over metered connections causing excessive data usage possibly making users being charged for the downloads. * Avoiding users being unexpectedly charged due to unattended- upgrades' activity warrants an SRU, IMO. * The fix uses NetworkMonitor.get_network_metered(NetworkMonitor.get_default()) for deciding if the connection is metered and skips or gracefully stops updates. [Test Case] * Run "unattended-upgrades --dry-run --verbose" on metered connection - The unfixed versions should provide the following output with default configuration: $ sudo unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic No packages found that can be upgraded unattended and no pending auto-removals - The fixed versions should provide the following output with default configuration: Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic System is on metered connection, stopping - You can check if the default route is on metered connection by running: nmcli -t -f GENERAL.DEVICE,GENERAL.METERED dev show `ip route list 0/0 | sed -r 's/.*dev (\S*).*/\1/g'` - Also run fixed u-u on not metered connection to check if it still works. U-u in lxc for example does not detect the connection to be metered. - Check if the following configuration can enable updates even on metered connections: $ cat /etc/apt/apt.conf.d/51unattended-upgrades-metered Unattended-Upgrade::Skip-Updates-On-Metered-Connections "false"; [Regression Potential] * Unattended-upgrades may skip updates even on not metered connections or crash, but those are not likely. * U-u also adds two new dependencies with the fix which can be seen as a regression, but those packages exist on most Ubuntu installations already. (The packages are: gir1.2-glib-2.0 and python3-gi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781180] [NEW] The graphic driver for Intel graphic card is not working properly.
Public bug reported: The graphic driver for Intel graphic card is not working properly. I see annoying white stripes across my screen since an actualization 2 months ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 11 12:06:42 2018 DistUpgraded: 2018-06-03 20:24:19,873 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d] InstallationDate: Installed on 2018-06-03 (37 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 20354 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=ad4f5447-3aaa-4725-8db4-de122486343b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-06-03 (37 days ago) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 11 11:58:33 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5579 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1781180 Title: The graphic driver for Intel graphic card is not working properly. Status in xorg package in Ubuntu: New Bug description: The graphic driver for Intel graphic card is not working properly. I see annoying white stripes across my screen since an actualization 2 months ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 11 12:06:42 2018 DistUpgraded: 2018-06-03 20:24:19,873 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d] InstallationDate: Installed on 2018-06-03 (37 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 20354 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=ad4f5447-3aaa-4725-8db4-de122486343b ro quiet splash
[Touch-packages] [Bug 1756755] Re: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2
Just ran into the same with xenial → bionic upgrade. -- 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/1756755 Title: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 Status in systemd package in Ubuntu: Confirmed Bug description: Upgrading from xenial to bionic failed the removal of systemd-shim. I think the messages were the same as the following, that I can reproduce by running "apt upgrade" from the upgraded system: Removing systemd-shim (9-1bzr4ubuntu1) ... Removing 'diversion of /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by systemd-shim' dpkg-divert: error: rename involves overwriting '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with different file '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', not allowed dpkg: error processing package systemd-shim (--remove): installed systemd-shim package post-removal script subprocess returned error exit status 2 Errors were encountered while processing: systemd-shim E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd-sysv 237-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sun Mar 18 22:52:00 2018 ErrorMessage: installed systemd-shim package post-removal script subprocess returned error exit status 2 InstallationDate: Installed on 2013-01-11 (1892 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1 PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4 RelatedPackageVersions: dpkg 1.19.0.5ubuntu1 apt 1.6~beta1 SourcePackage: systemd Title: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2 UpgradeStatus: Upgraded to bionic on 2018-03-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected
Launchpad has imported 3 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=199873.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2018-05-29T08:05:07+00:00 leon.liao wrote:
The BT 3.0 mouse is disconnected automatically after connected with the
notebook.
The fail rate is around 9/10.
1. The bug only occurs on the machine with intel 8265 module.
I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
This bug can not be reproduced on the machine with Killer 1435.
2. This bug can be reproduced since bluez 5.46.
I verified the bluez 5.49, this bug still can be reproduced.
This bug can not be reproduced in bluez 5.45.
Notebook: Dell XPS 13
Wi-Fi/BT module: intel 8265, 8087:0a2b
bluez: 5.48
BT mouse: logitech M337
Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/comments/24
On 2018-05-29T08:12:50+00:00 leon.liao wrote:
In bluez git, since "6b34bdd96 ("shared/gatt-client: Fix not removing services
that had disappeared", 2017-05-24)", this bug can be reproduced with low fail
rate (around 1/10 or lower).
This commit is between 5.45 and 5.46.
Before this commit, I don't reproduce this bug (maybe the reproduce rate is
very low.).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/comments/26
On 2018-07-10T16:03:30+00:00 phil+kernbugz wrote:
I can also reproduce the bug.
Notebook: HP Spectre x360 Convertible W2Q33AV
Wi-Fi/BT module: 8087:0a2a Intel
BlueZ: 5.50 (bluez-5.50-1.fc28.x86_64)
BT Mouse: Logitech M535
Log:
[bluetooth]# scan on
Discovery started
[CHG] Controller C8:21:58:16:95:58 Discovering: yes
[NEW] Device 34:88:5D:89:64:81 Bluetooth Mouse M336/M337/M535
[bluetooth]# trust 34:88:5D:89:64:81
[CHG] Device 34:88:5D:89:64:81 Trusted: yes
Changing 34:88:5D:89:64:81 trust succeeded
[bluetooth]# connect 34:88:5D:89:64:81
Attempting to connect to 34:88:5D:89:64:81
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Modalias: usb:v046DpB016d1203
[CHG] Device 34:88:5D:89:64:81 UUIDs: 1000--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:89:64:81 UUIDs: 1124--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:89:64:81 UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 34:88:5D:89:64:81 ServicesResolved: yes
[CHG] Device 34:88:5D:89:64:81 Paired: yes
Connection successful
# Mouse is powered off and then back on
[CHG] Device 34:88:5D:89:64:81 ServicesResolved: no
[CHG] Device 34:88:5D:89:64:81 Paired: no
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Class: 0x0580
[CHG] Device 34:88:5D:89:64:81 Icon: input-mouse
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
[CHG] Device 34:88:5D:89:64:81 Connected: yes
[CHG] Device 34:88:5D:89:64:81 Connected: no
Reply at:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1773897/comments/28
** Changed in: bluez
Status: Unknown => Confirmed
** Changed in: bluez
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1773897
Title:
[regression] Logitech M337 mice are automatically disconnected after
connected
Status in Bluez Utilities:
Confirmed
Status in OEM Priority Project:
New
Status in bluez package in Ubuntu:
Confirmed
Bug description:
The BT 3.0 mouse is disconnected automatically after connected with the
notebook.
The fail rate is around 9/10.
1. The bug only occurs on the machine with intel 8265 module.
I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
This bug can not be reproduced on the machine with Killer 1435.
2. This bug can be reproduced since bluez 5.46.
Using bluez 5.45, this bug can not be reproduced.
Notebook: Dell XPS 13
Wi-Fi/BT module: intel 8265, 8087:0a2b
bluez: 5.48
BT mouse: logitech M337
---
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-05-29 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InterestingModules: rfcomm bnep btusb bluetooth
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux
[Touch-packages] [Bug 1781176] Re: Blacklisted packages are included in the "upgradable origin", while they should not
** Changed in: unattended-upgrades Status: Unknown => Fix Released -- 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/1781176 Title: Blacklisted packages are included in the "upgradable origin", while they should not Status in unattended-upgrades: Fix Released Status in unattended-upgrades package in Ubuntu: New Bug description: [Impact] * Reports from u-u incorrectly list packages from non-upgradable origins as "Packages with upgradable origin but kept back" * The incorrectly the packages incorrectly is a result of is_pkgname_in_blacklist() having a side effect and removing the side effect is part of fixing LP: #1396787 which fix is also being SRU-d. * The fix is removing the side effect of is_pkgname_in_blacklist() [Test Case] * There is a build-time test in test/test_blacklisted_wrong_origin.py * TODO copy test case here from GitHub report [Regression Potential] * Regressions may make packages incorrectly missing from u-u's report, but the autopkgtests also cover that to some extent. [Other Info] * Original report: https://github.com/mvo5/unattended-upgrades/issues/116 To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1781049 Title: WiFI hard blocked after resuming laptop (RTL 8723BE) Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781049] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1781049 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1781049 Title: WiFI hard blocked after resuming laptop (RTL 8723BE) Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: I installed a fresh copy of Ubuntu 18.04 and everything seems to work fine, till I suspended and resumed the laptop. After resume, the wifi is hard blocked is rfkill. Reinstalling drivers, different drivers, nothing helped. All this was done under Secure Boot disabled under Ubuntu and BIOS (UEFI). The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If any further info is required, I'll add it on notification. I am familiar with Linux, any help will be really appreciated. P.S: If this wifi card is the issue, please suggest some PCI-mini card that will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 5.0) Thank you all! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1777415] Re: Local authorization bypass by using suspend mode
Markus Laire, Yes, the bug is exploitable even with full disk encryption. Among other things, if there's an open instant messaging app, an attacker can send a message which would appear as if it was sent by the authenticated user. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pam in Ubuntu. https://bugs.launchpad.net/bugs/1777415 Title: Local authorization bypass by using suspend mode Status in Unity: New Status in pam package in Ubuntu: New Status in unity package in Ubuntu: Confirmed Bug description: Version: Ubuntu 16.04.04 LTS Desktop, all packets are updated at 15.06.2018 Affects: access to latest user opened applications, that can contain sensitive information (documents, private information, passwords, etc.) How to reproduce: 1. open some applications (LibreOffice, browsers, editors, ...) 2. go to suspend mode 3. extract hard drive 4. wake up 5. after that can be several behaviors: * Ubuntu show lock screen. Enter ANY password -> access granted. * Ubuntu show lock screen. Enter ANY password, access denied. Fast press the hardware shutdown button -> access granted. * Ubuntu does not show lock screen, only black screen. We can repeat actions like in previous paragraphs To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1777415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781154] [NEW] Xorg session reset on suspend / wake-up
Public bug reported: My preconditions: - running Chromium + Thunderbird on workspace 1 - running 2x Eclipse + Notepad on workspace 2 - active workspace - using internal laptop screen - using Gnome desktop with dynamic workspaces How I reproduce (with almost 100% success): - Suspend (using suspend button from system menu) - connect external monitors to Display-Port (primary) and SVGA (secondary); internal laptop screen is disabled in this configuration (saved) - wake-up Current result: - Xorg session is re-started and *no* applications from previous session are running. Expected result: - System resumes where it was before with all applications continuing from where they were on suspend. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24.02 Thu May 24 03:48:07 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1~16.04) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Jul 11 09:56:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f6] MachineType: LENOVO 244759G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=cf56f770-2527-47cc-bf3b-a1815c6c2a09 ro quiet splash acpi_osi=Linux acpi_backlight=none vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 244759G dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA6WW(2.66):bd08/24/2016:svnLENOVO:pn244759G:pvrThinkPadW530:rvnLENOVO:rn244759G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 244759G dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jul 11 09:54:47 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4~16.04.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug 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/1781154 Title: Xorg session reset on suspend / wake-up Status in xorg package in Ubuntu: New Bug description: My preconditions: - running Chromium + Thunderbird on workspace 1 - running 2x Eclipse + Notepad on workspace 2 - active workspace - using internal laptop screen - using Gnome desktop with dynamic workspaces How I reproduce (with almost 100% success): - Suspend (using suspend button from system menu) - connect external monitors to Display-Port (primary) and SVGA (secondary); internal laptop screen is disabled in this configuration (saved) - wake-up Current result: - Xorg session is re-started and *no* applications from previous session are running. Expected result: - System resumes where it was before with all applications continuing from where they were on suspend. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset
[Touch-packages] [Bug 1781169] Re: frontend locking
** Changed in: dpkg (Ubuntu) Status: New => In Progress ** Changed in: apt (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1781169 Title: frontend locking Status in apt package in Ubuntu: In Progress Status in dpkg package in Ubuntu: In Progress Bug description: frontend locking fixes locking for dpkg frontends. Implementation is in dpkg git and apt support is coming soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1439771] Re: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend'
I can confirm this is happening also in my recently installed 18.04 on Bell Latitude E6430 Using the logs tool I can see this 11:16:20 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed 11:16:16 gdm-x-session: dbus-update-activation-environment: setting WINDOWPATH=2 11:16:02 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed 11:16:02 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed 11:15:58 wpa_supplicant: wlp3s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0 11:15:58 wpa_supplicant: wlp3s0: CTRL-EVENT-CONNECTED - Connection to 00:26:f2:29:d4:ac completed [id=0 id_str=] 11:15:58 wpa_supplicant: wlp3s0: Associated with 00:26:f2:29:d4:ac 11:15:58 wpa_supplicant: wlp3s0: Trying to associate with 00:26:f2:29:d4:ac (SSID='NETGEAR' freq=2447 MHz) 11:15:58 wpa_supplicant: wlp3s0: SME: Trying to authenticate with 00:26:f2:29:d4:ac (SSID='NETGEAR' freq=2447 MHz) 11:15:55 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed 11:15:55 wpa_supplicant: dbus: Failed to construct signal 11:15:55 wpa_supplicant: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none 11:15:55 wpa_supplicant: dbus: fill_dict_with_properties dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter failed 11:15:55 NetworkManager: [1531304155.3344] supplicant: wpa_supplicant running 11:15:53 systemd: Started WPA supplicant. 11:15:52 wpa_supplicant: Successfully initialized wpa_supplicant I am assuming that wifi is failing at boot but succeding after login. Is this a security feature or a bug? -- 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/1439771 Title: wpa_supplicant[874]: dbus: Failed to construct signal after 'suspend' Status in network-manager package in Ubuntu: Confirmed Bug description: The Wifi network can't connect after the wake up from suspend. Xubuntu 15.04 I'll post more useful details (journalctl log) as a comment to this bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dbus 1.8.12-1ubuntu5 Uname: Linux 4.0.0-04rc5-generic x86_64 ApportVersion: 2.17-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Apr 2 18:18:56 2015 InstallationDate: Installed on 2015-03-27 (5 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Beta amd64 (20150326) SourcePackage: dbus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1439771/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781160] Re: current issue tab keeps on crashing - plus error message pops up on login
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1781160 Title: current issue tab keeps on crashing - plus error message pops up on login Status in procps package in Ubuntu: New Bug description: see summary for details ProblemType: Package DistroRelease: Ubuntu 16.04 Package: procps 2:3.3.10-4ubuntu2.4 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Jul 11 08:48:20 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2016-08-27 (682 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: procps Title: package procps 2:3.3.10-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1781160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781176] [NEW] Blacklisted packages are included in the "upgradable origin", while they should not
Public bug reported: [Impact] * Reports from u-u incorrectly list packages from non-upgradable origins as "Packages with upgradable origin but kept back" * The incorrectly the packages incorrectly is a result of is_pkgname_in_blacklist() having a side effect and removing the side effect is part of fixing LP: #1396787 which fix is also being SRU-d. * The fix is removing the side effect of is_pkgname_in_blacklist() [Test Case] * There is a build-time test in test/test_blacklisted_wrong_origin.py * TODO copy test case here from GitHub report [Regression Potential] * Regressions may make packages incorrectly missing from u-u's report, but the autopkgtests also cover that to some extent. [Other Info] * Original report: https://github.com/mvo5/unattended-upgrades/issues/116 ** Affects: unattended-upgrades Importance: Unknown Status: Unknown ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/mvo5/unattended-upgrades/issues #116 https://github.com/mvo5/unattended-upgrades/issues/116 ** Also affects: unattended-upgrades via https://github.com/mvo5/unattended-upgrades/issues/116 Importance: Unknown Status: Unknown -- 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/1781176 Title: Blacklisted packages are included in the "upgradable origin", while they should not Status in unattended-upgrades: Unknown Status in unattended-upgrades package in Ubuntu: New Bug description: [Impact] * Reports from u-u incorrectly list packages from non-upgradable origins as "Packages with upgradable origin but kept back" * The incorrectly the packages incorrectly is a result of is_pkgname_in_blacklist() having a side effect and removing the side effect is part of fixing LP: #1396787 which fix is also being SRU-d. * The fix is removing the side effect of is_pkgname_in_blacklist() [Test Case] * There is a build-time test in test/test_blacklisted_wrong_origin.py * TODO copy test case here from GitHub report [Regression Potential] * Regressions may make packages incorrectly missing from u-u's report, but the autopkgtests also cover that to some extent. [Other Info] * Original report: https://github.com/mvo5/unattended-upgrades/issues/116 To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1781176/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781154] Re: Xorg session reset on suspend / wake-up
It sounds like some part of the system has crashed. Please: 1. Apply the workaround from bug 994921. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash and tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1781154 Title: Xorg session reset on suspend / wake-up Status in xorg-server package in Ubuntu: Incomplete Bug description: My preconditions: - running Chromium + Thunderbird on workspace 1 - running 2x Eclipse + Notepad on workspace 2 - active workspace - using internal laptop screen - using Gnome desktop with dynamic workspaces How I reproduce (with almost 100% success): - Suspend (using suspend button from system menu) - connect external monitors to Display-Port (primary) and SVGA (secondary); internal laptop screen is disabled in this configuration (saved) - wake-up Current result: - Xorg session is re-started and *no* applications from previous session are running. Expected result: - System resumes where it was before with all applications continuing from where they were on suspend. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 396.24.02 Thu May 24 03:48:07 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-21ubuntu1~16.04) .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME Date: Wed Jul 11 09:56:12 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f6] MachineType: LENOVO 244759G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=cf56f770-2527-47cc-bf3b-a1815c6c2a09 ro quiet splash acpi_osi=Linux acpi_backlight=none vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: G5ETA6WW (2.66 ) dmi.board.asset.tag: Not Available dmi.board.name: 244759G dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG5ETA6WW(2.66):bd08/24/2016:svnLENOVO:pn244759G:pvrThinkPadW530:rvnLENOVO:rn244759G:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W530 dmi.product.name: 244759G dmi.product.version: ThinkPad W530 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Wed Jul 11 09:54:47 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1781154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781091] Re: notify-send only works the first time
I installed a fresh Ubuntu on a VM, and the problem did go away. I'm sorry for misleading you. I found out that the problem goes away if I disable the third-party GSConnect extension (due to be included in the next Ubuntu, https://github.com/andyholmes/gnome-shell-extension- gsconnect) that talks to KDE Connect on my phone. Disable the extension, reboot, and the problem is gone (Alt+F2 & r doesn't work). Enable it again, or even open the preferences, and the problem appears again. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1781091 Title: notify-send only works the first time Status in gnome-shell package in Ubuntu: Incomplete Status in libnotify package in Ubuntu: Incomplete Bug description: (I think this started happening after upgrading gnome-shell to 3.28.2-0ubuntu0.18.04.1 today.) Reproduce: * Run `notify-send ok ok`. Expected result: * A notification pops up for every execution of the command above. Actual result: * A notification might pop up every once in a while (it always appears the first time, I think). The journal gets a message like this for every notify-send call: Jul 11 02:29:20 tensin-pc1 gnome-shell[3723]: JS ERROR: Call to GetConnectionUnixProcessID failed: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Could not get PID of name ':1.68': no such name _proxyInvoker/asyncCallback@resource:///org/gnome/gjs/modules/overrides/Gio.js:71:26 I use notify-send in quite a few of my scripts, and it broke precisely today. > lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781091/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1737441] Re: python-apt crashes if objects of one cache are passed to depcache belonging to another cache
** Description changed: [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache, performing operations on the old package would perform it on the new package. If the old package's ID is out of bounds in the new cache, the behavior is undefined - it's an out of bounds array access. [Test case] The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. More test cases like this are in the autopkgtest. [Regression potential] The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. + [Other info] + The xenial SRU also includes the change "python/tag.cc: Fix invalid read in TagFileNext". We don't have any specific verification for it, as we just saw weird crashes on the error tracker, and this seemed like the culprit. We released bionic with it, and it seems fine. The fix is fairly obvious: We were copying the char array "Start" which was not nul terminated in an odd way, without using the lenght. + [Original bug report] The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 0.98ubuntu1, the problem page at https://errors.ubuntu.com/problem/727153285ba3335a07f801a298a3d94cbe6ba05d contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1737441 Title: python-apt crashes if objects of one cache are passed to depcache belonging to another cache Status in python-apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in python-apt source package in Trusty: Fix Committed Status in unattended-upgrades source package in Trusty: Won't Fix Status in python-apt source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: Won't Fix Status in python-apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] Some applications, like unattended-upgrades or update-manager, reopen the apt cache. They also keep around old apt.Package objects however, and operate on them after reopening. Under the hood, this means that apt_pkg.Package objects belonging to an old cache are passed to a new cache. APT relies on the ID of the package (it's position in the cache) for it's operation. So if a package has ID 0 in the old cache, and a different package has ID 0 in the new cache, performing operations on the old package would perform it on the new package. If the old package's ID is out of bounds in the new cache, the behavior is undefined - it's an out of bounds array access. [Test case] The attached test case has a list of packages 0-9, a-z; stores the package "z" into a variable, then reopens the cache. It then marks z for deletion. This either segfaults or does nothing; when it should mark z for deletion. More test cases like this are in the autopkgtest. [Regression potential] The initial fix introduced bug 1780099, there might be similar bugs lurking. However, these bugs would have been undefined behavior before and might have caused segmentation faults or did the wrong thing. It seems likely that any regression cannot possibly be worse than the current state. [Other info] The xenial SRU also includes the change "python/tag.cc: Fix invalid read in TagFileNext". We don't have any specific verification for it, as we just saw weird crashes on the error tracker, and this seemed like the culprit. We released bionic with it, and it seems fine. The fix is fairly obvious: We were copying the char array "Start" which was not nul terminated in an odd way, without using the lenght. [Original bug report] The Ubuntu Error Tracker has been receiving reports about a
[Touch-packages] [Bug 1781169] [NEW] frontend locking
Public bug reported: frontend locking fixes locking for dpkg frontends. Implementation is in dpkg git and apt support is coming soon. ** Affects: apt (Ubuntu) Importance: Undecided Status: In Progress ** Affects: dpkg (Ubuntu) Importance: Undecided Status: In Progress ** Also affects: dpkg (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1781169 Title: frontend locking Status in apt package in Ubuntu: In Progress Status in dpkg package in Ubuntu: In Progress Bug description: frontend locking fixes locking for dpkg frontends. Implementation is in dpkg git and apt support is coming soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon
Thank you @gedakc for pointing out that old package versions are
available to download from Launchpad. I did not know that.
The intersection of the set of packages which @gedakc downgraded and the set of
packages I downgraded is:
libegl1-mesa:amd64
libwayland-egl1-mesa:amd64
libgl1-mesa-dri:amd64
libgl1-mesa-dri:i386
mesa-vdpau-drivers:amd64
However, it is not possible to downgrade just the packages in this
intersection, due to unsatisfied dependencies.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780664
Title:
Recent libgl-mesa graphics update prevents drop down list menu
appearing in apps like firefox three line/bar menu icon
Status in mesa package in Ubuntu:
Confirmed
Bug description:
PROBLEM
Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
drop down list menu appearing in apps like firefox three line/bar menu
icon.
After recently applying updates, left clicking on some application
menus and icons no longer displays a drop-down menu list.
For example in Firefox when I left-click on the **three line/bar**
icon in the upper right-hand corner, the normal drop down list menu
does not display. Also the menu drop down doesn't display in
keypassx. Further xchat-gnome doesn't even display a window.
Another anomaly is that my KDE bottom menu bar changed to a dark
theme.
BACKGROUND
I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
Graphics. I have KDE **System Settings -> Compositor** enabled with:
Scale method :Accurate
Rendering backend: OpenGL 3.1
OpenGL interface: GLX
Tearing prevention ("vsync"): Full screen repaints
Keep window thumbnails:Only for Shown Windows
INVESTIGATION
After several hours of searching the Internet I found one other case
of a similar problem.
Firefox's Menu Bar won't open
https://support.mozilla.org/en-US/questions/1194760
The reported solution was to rollback the graphics drivers.
Because the issues cropped up after applying updates on July 6, 2018,
I tracked down the list of recent updates with:
grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
-1 >packages.txt
After some editing to place packages on separate lines, and
identifying the grahics libraries, I arrived at the following list:
--
libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
--
To revert to the prior graphic drivers I tracked down the '.deb'
packages for each of the above packages and downloaded the
'17.2.8-0ubuntu0~16.04.1' version.
For example:
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1
I also discovered that some of these depended on
libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:
libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb
WORKAROUND (ROLLBACK TO PRIOR VERSION)
Install older versions with:
sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb
After
[Touch-packages] [Bug 1780767] Re: Some tests are flaky due to timeout
** Tags added: rls-cc-incoming -- 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/1780767 Title: Some tests are flaky due to timeout Status in apport package in Ubuntu: New Bug description: The autopkgtests are sometimes passing, sometimes stuck for more than 2h: http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64. It's blocking randomly on different tests. All tests that are stucked, implements closing a request via a timeout (and then, executing "run"). The bet is that the timeout is short enough (1s) so that, when autopkgtests infra is busy, time to execute the bash subcommand is taking more than a second, and so "dismissing" is ran before execution happens and the whole testsuite hangs. There are few instances of setting this timeout function: $ grep eout_add_sec test/* test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c) Short term solution could be to increase the timeout. Long term would be to eliminate this potential race implementing cancelling differently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1780767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781231] Re: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1781231 Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: Get it when trying to start terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jul 11 08:32:16 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-08-11 (333 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1781231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781231] [NEW] package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Public bug reported: Get it when trying to start terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jul 11 08:32:16 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-08-11 (333 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1781231 Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in apport package in Ubuntu: New Bug description: Get it when trying to start terminal. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.15 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Jul 11 08:32:16 2018 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2017-08-11 (333 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: apport Title: package apport 2.20.1-0ubuntu2.15 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1781231/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: postgresql-common (Ubuntu Xenial) Status: New => Triaged ** Changed in: postgresql-common (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: postgresql-common (Ubuntu Bionic) Status: New => Fix Released ** Changed in: postgresql-common (Ubuntu) Status: New => Fix Released ** Changed in: postgresql-common (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Triaged Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Triaged Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured.
[Touch-packages] [Bug 1744536] Re: Zeitgeist homepage doesn't exist
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zeitgeist (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zeitgeist in Ubuntu. https://bugs.launchpad.net/bugs/1744536 Title: Zeitgeist homepage doesn't exist Status in zeitgeist package in Ubuntu: Confirmed Bug description: Zeitgeist package has a homepage address http://zeitgeist- project.com/. When I visit it, I get redirected to various shady advertising pages. As it looks like from the archive.org database, the true site ceased to exist between July 2016 and June 2017. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1744536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: clutter-imcontext (Ubuntu) Status: New => Triaged ** Changed in: clutter-imcontext (Ubuntu Bionic) Status: New => Triaged ** Changed in: clutter-imcontext (Ubuntu Xenial) Status: New => Triaged ** Changed in: clutter-imcontext (Ubuntu) Assignee: (unassigned) => Julian Andres Klode (juliank) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: gosa (Ubuntu) Assignee: (unassigned) => Łukasz Zemczak (sil2100) ** Changed in: gosa (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this
[Touch-packages] [Bug 1462441] Re: apport hangs, wrong menu entries
*** This bug is a duplicate of bug 879825 *** https://bugs.launchpad.net/bugs/879825 This looks like a duplicate of #879825 ** This bug has been marked a duplicate of bug 879825 Severe logic errors in questionaire GUI -- 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/1462441 Title: apport hangs, wrong menu entries Status in apport package in Ubuntu: Confirmed Bug description: Well, two problems. First: if you start ubuntu-bug without parameter, it shows a dialog containing: Other Problem (a lot of options) Display (X.org) first and last item are swapped. If you click other (the first), you will get a list of display problems. If you click Display (the last one), you will get "You need to specify a package or a PID. See --help for more information." Second problem: if you click cancel on the display page, apport hangs forever. Maybe duplicate of #660024 ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: reportbug (not installed) 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: KDE Date: Fri Jun 5 18:13:55 2015 InstallationDate: Installed on 2013-10-25 (588 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: reportbug UpgradeStatus: Upgraded to vivid on 2015-05-19 (17 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1462441/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781180] Re: The graphic driver for Intel graphic card is not working properly.
Can you please take a photo of the problem and attach it here? ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1781180 Title: The graphic driver for Intel graphic card is not working properly. Status in mesa package in Ubuntu: Incomplete Status in xorg-server package in Ubuntu: Incomplete Bug description: The graphic driver for Intel graphic card is not working properly. I see annoying white stripes across my screen since an actualization 2 months ago. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Jul 11 12:06:42 2018 DistUpgraded: 2018-06-03 20:24:19,873 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: nvidia-304, 304.135, 4.4.0-130-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d] InstallationDate: Installed on 2018-06-03 (37 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) MachineType: LENOVO 20354 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-130-generic.efi.signed root=UUID=ad4f5447-3aaa-4725-8db4-de122486343b ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to xenial on 2018-06-03 (37 days ago) dmi.bios.date: 10/20/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9BCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A5 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Z50-70 dmi.modalias: dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70: dmi.product.name: 20354 dmi.product.version: Lenovo Z50-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Jul 11 11:58:33 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5579 vendor CMN xserver.version: 2:1.18.4-0ubuntu0.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1781180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781183] Re: Skip updates on metered connections
** Changed in: unattended-upgrades (Debian) Status: Unknown => Fix Released -- 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/1781183 Title: Skip updates on metered connections Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [Impact] * Systems running unattended-upgrades may download updates over metered connections causing excessive data usage possibly making users being charged for the downloads. * Avoiding users being unexpectedly charged due to unattended- upgrades' activity warrants an SRU, IMO. * The fix uses NetworkMonitor.get_network_metered(NetworkMonitor.get_default()) for deciding if the connection is metered and skips or gracefully stops updates. [Test Case] * Run "unattended-upgrades --dry-run --verbose" on metered connection - The unfixed versions should provide the following output with default configuration: $ sudo unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic No packages found that can be upgraded unattended and no pending auto-removals - The fixed versions should provide the following output with default configuration: Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic System is on metered connection, stopping - You can check if the default route is on metered connection by running: nmcli -t -f GENERAL.DEVICE,GENERAL.METERED dev show `ip route list 0/0 | sed -r 's/.*dev (\S*).*/\1/g'` - Also run fixed u-u on not metered connection to check if it still works. U-u in lxc for example does not detect the connection to be metered. - Check if the following configuration can enable updates even on metered connections: $ cat /etc/apt/apt.conf.d/51unattended-upgrades-metered Unattended-Upgrade::Skip-Updates-On-Metered-Connections "false"; [Regression Potential] * Unattended-upgrades may skip updates even on not metered connections or crash, but those are not likely. * U-u also adds two new dependencies with the fix which can be seen as a regression, but those packages exist on most Ubuntu installations already. (The packages are: gir1.2-glib-2.0 and python3-gi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1781183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Tags added: id-5b1169fb7c4ba277874d3879 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: New Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: New Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: New Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: New Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: New Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: New Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them. What this means is that packages with await triggers either need to have all triggering packages depend on them (e.g. B Depends A), or they need to be moved to noawait. This bug is about moving
[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
@yoosofan: Several options, including CapsLock, are available to switch layout. If you want to suggest that to be the default option in Ubuntu, you'd better approach the GNOME developers: https://gitlab.gnome.org/GNOME/gnome-control-center/issues (The discussion seems unrelated to this bug.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal
It's not clear to me what is going on in the ubuntu-make autopkgtest for artful/s390x but the failure isn't related to my SRU. From the log: Investigating (0) autopkgtest-satdep:s390x < 0 @iU mK Nb Ib > Broken autopkgtest-satdep:s390x Depends on ubuntu-desktop:s390x < none @un H > Removing autopkgtest-satdep:s390x because I can't find ubuntu-desktop:s390x Done There is no ubuntu-desktop for s390x in artful, so the failure makes sense. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1768379 Title: python3-minimal should predepend on versioned version of python3-minimal Status in python3-defaults package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Invalid Status in python3-defaults source package in Artful: Fix Committed Status in ubuntu-release-upgrader source package in Artful: Invalid Status in python3-defaults source package in Bionic: Fix Committed Status in ubuntu-release-upgrader source package in Bionic: Invalid Status in python3-defaults package in Debian: Fix Released Bug description: [Impact] Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 LTS can fail if python3-minimial is unpacked before python3.x-minimal so a system won't have a usable python3 symlink. Then upgrades will fail because py3clean, used in prerm scripts of python3 packages, will fail with "not found". [Test Case] 1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt 2) dpkg --unpack python3-minimal... 3) dpkg --unpack python3-apt... Observe the following Traceback: Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ... /var/lib/dpkg/info/python3-apt.prerm: 6: /var/lib/dpkg/info/python3-apt.prerm: py3clean: not found dpkg: warning: subprocess old pre-removal script returned error exit status 127 dpkg: trying script from the new package instead ... /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found dpkg: error processing archive /home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack): subprocess new pre-removal script returned error exit status 127 /var/lib/dpkg/info/python3-apt.postinst: 6: /var/lib/dpkg/info/python3-apt.postinst: py3compile: not found dpkg: error while cleaning up: subprocess installed post-installation script returned error exit status 127 With the deb python3-minimal from -proposed you won't be able to unpack python3-minimal without first installing python3.6-minimal. While that may qualify as verification it'd still be good to test unpacking python3-apt. To do that you'll need to install python3.6-minimal from the target release by editing you /etc/apt/sources.list to the new release, running 'apt-get update', and then 'apt-get install python3.6-minimal'. After that's all done you can try steps 2 and 3 from the test case again and you should not receive a Traceback. [Regression Potential] Its possible this could cause or reveal different upgrade failures so some extensive (desktop, cloud, server) upgrade testing should be done. [A Portion of the Original Description (it was a huge blob of failure)] do-release-upgrade -d on my 16.04 LTS unity laptop lead to an install failure: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: octave (Ubuntu Xenial) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: octave (Ubuntu) Status: New => Fix Released ** Changed in: octave (Ubuntu Bionic) Status: New => Fix Released ** Changed in: octave (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: New Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: New Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: New Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: Triaged Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: New Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: New Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B
[Touch-packages] [Bug 879825] Re: Severe logic errors in questionaire GUI
See also bug under Apport project https://bugs.launchpad.net/apport/+bug/1163740 -- 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/879825 Title: Severe logic errors in questionaire GUI Status in apport package in Ubuntu: Confirmed Bug description: The following misbehaviour are just examples I found during my first few clicks within this tool. Run "apport-bug" without any arguments. * A dialog appears asking "Which kind of problem do you want to report?" => Just clicking "ok" without selecting anything will crash the bug report application. => Selecting "Other Problem" brings up the "Display Problem" dialog, but "Display-Problem" is a completely different selection in the first dialog... * Clicking "Ok" without selection any option will also crash the bug report application at this point. * Clicking "Cancel" instead in this "Display Problem" dialog will completely freeze the bug report application, the windows will stay there but will not react to any interaction any more. I did not try anything further... ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: apport-kde 1.23-0ubuntu3 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 ApportLog: ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Sat Oct 22 11:09:28 2011 PackageArchitecture: all ProcEnviron: LANGUAGE= LANG=de_DE@euro SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to oneiric on 2011-10-17 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/879825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Thanks @Patrick for the link between the bug reports. Bug #1780664 contains instructions on how to revert to earlier libgl-mesa package versions while we wait for a fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in libdrm package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: bumblebee (Ubuntu) Importance: Undecided Status: New ** Changed in: bumblebee (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: New Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: In Progress Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: bumblebee (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: In Progress Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in Packages files, so we don't see them.
[Touch-packages] [Bug 1781271] [NEW] Gnome shell crashing after login
Public bug reported: Gnome shell usually (not everytime) crashes after login. When I log in everything looks fine. Then I try to start firefox, gnome-shell crashes first time, but recovers in this first case. Second crash occurs after I try to click with mouse or press some key. This time it crashes whole X and returns to login screen. In log I can see gnome-shell segfaults in libgobject. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 20:07:36 2018 DistUpgraded: 2018-05-05 10:06:30,687 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-22-generic, x86_64: installed nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidiabl, 0.88, 4.15.0-22-generic, x86_64: installed nvidiabl, 0.88, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GP104M [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1080 Mobile] [1558:7708] InstallationDate: Installed on 2017-12-04 (218 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Eurocom Sky X7E2G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=2042381a-928b-4dcb-aabe-3d1cc338cc1a ro quiet splash nvidia.NVreg_EnableBacklightHandler=1 video.only_lcd=0 noresume vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-05 (67 days ago) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.06.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: Sky X7E2G dmi.board.vendor: Eurocom dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Eurocom dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.06.11:bd07/27/2017:svnEurocom:pnSkyX7E2G:pvrNotApplicable:rvnEurocom:rnSkyX7E2G:rvrNotApplicable:cvnEurocom:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Sky X7E2G dmi.product.version: Not Applicable dmi.sys.vendor: Eurocom version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic crash 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/1781271 Title: Gnome shell crashing after login Status in xorg package in Ubuntu: New Bug description: Gnome shell usually (not everytime) crashes after login. When I log in everything looks fine. Then I try to start firefox, gnome-shell crashes first time, but recovers in this first case. Second crash occurs after I try to click with mouse or press some key. This time it crashes whole X and returns to login screen. In log I can see gnome-shell segfaults in libgobject. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: maxima (Ubuntu) Importance: Undecided Status: New ** Changed in: maxima (Ubuntu) Status: New => In Progress ** Changed in: maxima (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: In Progress Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: neurodebian (Ubuntu) Importance: Undecided Status: New ** Changed in: neurodebian (Ubuntu) Status: New => In Progress ** Changed in: neurodebian (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Also affects: nevow (Ubuntu) Importance: Undecided Status: New ** Changed in: nevow (Ubuntu) Status: New => In Progress ** Changed in: nevow (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: In Progress Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
David, if the workaround in Bug #1780664 works in our case (i.e. for this bug) we should change the affected component from "libdrm" to "mesa": I was searching for something related to graphics drivers to be responsible for this bug, thought it was libdrm, but it can be mesa, too. Have you tried the workaround? I did not for now, I have a lot of work to do till weekend: and in my case Firefox, Mplayer, Dosbox and Vim work fine, which are the programs I use most, so I am not very pressured to do the fix, maybe I will wait until the official fix is out. I was also thinking that another thing that may fix this could be upgrading the kernel from GA to HWE according to this article: https://wiki.ubuntu.com/Kernel/LTSEnablementStack (the command when they say "DESKTOP") - but this can be dangerous and can break other things so I was not brave enough to do this upgrade: also the bug can maybe stay even when the kernel is updated this way which would be sad ** Package changed: libdrm (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
changing package to "mesa" according to comment #17 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
dovecot for cosmic and bionic already changed to noawait triggers by Debian maintainer. ** Changed in: dovecot (Ubuntu) Status: In Progress => Fix Released ** Changed in: dovecot (Ubuntu Bionic) Status: New => Fix Released ** Changed in: dovecot (Ubuntu Xenial) Status: New => In Progress ** Changed in: dovecot (Ubuntu Xenial) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
I was able to work-around this issue by rolling back only the *libgl- mesa* packages from version 18.0.5-0ubuntu0~16.04.1 to version 17.2.8-0ubuntu0~16.04.1. I did not need to revert the *libdrm* packages in order to work-around this issue. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in libdrm package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
** Changed in: ufrs-apt Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: New Status in unbuntu-fr Scripts - apt: Fix Committed Status in hud package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from
[Touch-packages] [Bug 1781183] [NEW] Skip updates on metered connections
Public bug reported: [Impact] * Systems running unattended-upgrades may download updates over metered connections causing excessive data usage possibly making users being charged for the downloads. * Avoiding users being unexpectedly charged due to unattended-upgrades' activity warrants an SRU, IMO. * The fix uses NetworkMonitor.get_network_metered(NetworkMonitor.get_default()) for deciding if the connection is metered and skips or gracefully stops updates. [Test Case] * Run "unattended-upgrades --dry-run --verbose" on metered connection - The unfixed versions should provide the following output with default configuration: $ sudo unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic No packages found that can be upgraded unattended and no pending auto-removals - The fixed versions should provide the following output with default configuration: Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic System is on metered connection, stopping - You can check if the default route is on metered connection by running: nmcli -t -f GENERAL.DEVICE,GENERAL.METERED dev show `ip route list 0/0 | sed -r 's/.*dev (\S*).*/\1/g'` - Also run fixed u-u on not metered connection to check if it still works. U-u in lxc for example does not detect the connection to be metered. - Check if the following configuration can enable updates even on metered connections: $ cat /etc/apt/apt.conf.d/51unattended-upgrades-metered Unattended-Upgrade::Skip-Updates-On-Metered-Connections "false"; [Regression Potential] * Unattended-upgrades may skip updates even on not metered connections or crash, but those are not likely. * U-u also adds two new dependencies with the fix which can be seen as a regression, but those packages exist on most Ubuntu installations already. (The packages are: gir1.2-glib-2.0 and python3-gi) ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: unattended-upgrades (Debian) Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #855570 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855570 ** Also affects: unattended-upgrades (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855570 Importance: Unknown Status: Unknown -- 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/1781183 Title: Skip updates on metered connections Status in unattended-upgrades package in Ubuntu: Fix Released Status in unattended-upgrades package in Debian: Unknown Bug description: [Impact] * Systems running unattended-upgrades may download updates over metered connections causing excessive data usage possibly making users being charged for the downloads. * Avoiding users being unexpectedly charged due to unattended- upgrades' activity warrants an SRU, IMO. * The fix uses NetworkMonitor.get_network_metered(NetworkMonitor.get_default()) for deciding if the connection is metered and skips or gracefully stops updates. [Test Case] * Run "unattended-upgrades --dry-run --verbose" on metered connection - The unfixed versions should provide the following output with default configuration: $ sudo unattended-upgrade --dry-run --verbose Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic No packages found that can be upgraded unattended and no pending auto-removals - The fixed versions should provide the following output with default configuration: Initial blacklisted packages: Initial whitelisted packages: Starting unattended upgrades script Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic System is on metered connection, stopping - You can check if the default route is on metered connection by running: nmcli -t -f GENERAL.DEVICE,GENERAL.METERED dev show `ip route list 0/0 | sed -r 's/.*dev (\S*).*/\1/g'` - Also run fixed u-u on not metered connection to check if it still works. U-u in lxc for example does not detect the connection to be metered. - Check if the following configuration can enable updates even on metered connections: $ cat /etc/apt/apt.conf.d/51unattended-upgrades-metered Unattended-Upgrade::Skip-Updates-On-Metered-Connections "false"; [Regression Potential] * Unattended-upgrades may skip updates even on not metered connections or crash, but those are not likely.
[Touch-packages] [Bug 1781190] [NEW] package linux-image-4.4.0-130-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: After update from 14.04 to 16.04 I have these unresolved problems. now I'm stuck (can't install, can't remove) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-132.181-generic 3.13.11-ckt39 Uname: Linux 3.13.0-132-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: federico 2300 F pulseaudio Date: Wed Jul 11 12:27:07 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=8c867cd3-0494-4dd0-9e20-8c9f6157e50e InstallationDate: Installed on 2014-04-19 (1544 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: tun0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-132-generic root=UUID=6ddc2dc2-d8c8-4939-8564-b760952c2067 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-130-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2018-05-18 (53 days ago) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H67M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: initramfs-tools (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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1781190 Title: package linux-image-4.4.0-130-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: After update from 14.04 to 16.04 I have these unresolved problems. now I'm stuck (can't install, can't remove) ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-130-generic (not installed) ProcVersionSignature: Ubuntu 3.13.0-132.181-generic 3.13.11-ckt39 Uname: Linux 3.13.0-132-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: federico 2300 F pulseaudio Date: Wed Jul 11 12:27:07 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=8c867cd3-0494-4dd0-9e20-8c9f6157e50e InstallationDate: Installed on 2014-04-19 (1544 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: tun0 no wireless extensions. eth0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-132-generic root=UUID=6ddc2dc2-d8c8-4939-8564-b760952c2067 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: SourcePackage: initramfs-tools Title: package linux-image-4.4.0-130-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to xenial on 2018-05-18 (53 days ago) dmi.bios.date: 07/08/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.60 dmi.board.name: H67M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.60:bd07/08/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Is there a reason why we cannot use CapsLock for changing layout? CapsLock is the most simplest key for changing layout when you want to work with both hand while writing a mixed text of two language. Actually CapsLock does not use to its main function because people barely write with a lot of bold words and using shift for occasionally one letter is very common, -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743553] Re: [Typo] Missing word in Zesty Man Page for e4defrag
Indeed, I can verify it is fixed in e4fsprogs 1.44.3-1 which just landed in Ubuntu Cosmic. :) ** Changed in: e2fsprogs (Ubuntu) Status: New => Fix Released ** Tags removed: typo ** Tags added: artful bionic manpage string-fix zesty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to e2fsprogs in Ubuntu. https://bugs.launchpad.net/bugs/1743553 Title: [Typo] Missing word in Zesty Man Page for e4defrag Status in e2fsprogs package in Ubuntu: Fix Released Bug description: Location: First sentence, second paragraph, Notes section. http://manpages.ubuntu.com/manpages/zesty/man8/e4defrag.8.html Original: "It safe to run e4defrag on a file while it is actively in use by another application." Text should state "It is safe to run..." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1743553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Possible related or duplicate bug #1780664 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in libdrm package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon
This appears to be the same bug I am experiencing. Graphical regression Kubuntu xenial/16.04.4 Intel HD Graphics 530 Symptoms: * Under KDE Plasma 5, the blur effect for most widgets with a transparent background is not rendered. Instead, an opaque background is rendered. * The on-screen display provided by KMix when adjusting the volume using keyboard hotkeys is not rendered. Instead, only its background blur effect is rendered. * In some applications, some pop-up menu widgets do not render (they are invisible). For example, in Clementine, the drop down menu on the Stop button does not appear visibly when summoned, the main menus do not appear visibly when summoned, and the right-click menu does not appear visibly when summoned. In Firefox, the all-in-one "hamburger" menu, as well as other pop-ups from the main toolbar, do not appear visibly when summoned. However, the main menus (accessed by pressing Alt, if hidden) do appear. In the print dialogs in Okular, the drop-downs for "Page set" and for printer-specific settings do not drop down. (Selection has to be made by blindly scrolling through options using the arrow keys.) As remarked by others, menu and volume OSD visibility is restored by using XRender instead of OpenGL 3.1, but there is no background blur effect and the background of Plasma widgets remains opaque. For completeness, here are the results of my investigation into which packages were causing the problem. This seems very similar to what has already been said. The symptoms appeared after upgrading some packages using the package manager (aptitude). The following subset of the package upgrades that took place appear to have caused the symptoms, since downgrading only these packages eliminates the symptoms: package / old version / new version libwayland-egl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1 libdrm-common:all 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-dev:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm2:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm2:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-intel1:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-intel1:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-radeon1:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-radeon1:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-nouveau2:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-nouveau2:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-amdgpu1:amd64 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libdrm-amdgpu1:i386 2.4.83-1~16.04.1 2.4.91-2~16.04.1 libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1 libgl1-mesa-dri:i386 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1 libgl1-mesa-dri:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1 mesa-vdpau-drivers:amd64 17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1 libsensors4:i386 [not previously installed] 1:3.4.0-2 There were other package upgrades at the same time, but downgrading only these packages eliminated the symptoms. There are no symptoms with the following versions: package / version downgraded to libwayland-egl1-mesa:amd64 11.2.0-1ubuntu libdrm-common:all 2.4.83-1 libdrm-dev:amd64 2.4.83-1 libdrm2:amd64 2.4.83-1 libdrm2:i386 2.4.83-1 libdrm-intel1:amd64 2.4.83-1 libdrm-intel1:i386 2.4.83-1 libdrm-radeon1:amd64 2.4.83-1 libdrm-radeon1:i386 2.4.83-1 libdrm-nouveau2:amd64 2.4.83-1 libdrm-nouveau2:i386 2.4.83-1 libdrm-amdgpu1:amd64 2.4.83-1 libdrm-amdgpu1:i386 2.4.83-1 libegl1-mesa:amd64 11.2.0-1ubuntu libgl1-mesa-dri:i386 11.2.0-1ubuntu libgl1-mesa-dri:amd64 11.2.0-1ubuntu mesa-vdpau-drivers:amd64 11.2.0-1ubuntu libsensors4:i386 [removed] (N.B. I downloaded the 2.4.83-1 versions of the libdrm packages manually from archive.ubuntu.com since the older version 2.4.67-1 in the xenial repository created many dependency problems. These are therefore not precisely the same package version as they were before the upgrade that caused the symptoms.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780664 Title: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon Status in mesa package in Ubuntu: Confirmed Bug description: PROBLEM Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon. After recently applying updates, left clicking on some application menus and icons no longer displays a drop-down menu list. For example in Firefox when I left-click on the **three line/bar** icon in the upper right-hand corner, the normal drop down list menu does not display. Also the menu drop down doesn't display in keypassx. Further xchat-gnome doesn't even display a window. Another anomaly is that my KDE bottom menu bar changed to a dark theme. BACKGROUND I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon
Possible related or duplicate bug #1780846
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780664
Title:
Recent libgl-mesa graphics update prevents drop down list menu
appearing in apps like firefox three line/bar menu icon
Status in mesa package in Ubuntu:
Confirmed
Bug description:
PROBLEM
Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
drop down list menu appearing in apps like firefox three line/bar menu
icon.
After recently applying updates, left clicking on some application
menus and icons no longer displays a drop-down menu list.
For example in Firefox when I left-click on the **three line/bar**
icon in the upper right-hand corner, the normal drop down list menu
does not display. Also the menu drop down doesn't display in
keypassx. Further xchat-gnome doesn't even display a window.
Another anomaly is that my KDE bottom menu bar changed to a dark
theme.
BACKGROUND
I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
Graphics. I have KDE **System Settings -> Compositor** enabled with:
Scale method :Accurate
Rendering backend: OpenGL 3.1
OpenGL interface: GLX
Tearing prevention ("vsync"): Full screen repaints
Keep window thumbnails:Only for Shown Windows
INVESTIGATION
After several hours of searching the Internet I found one other case
of a similar problem.
Firefox's Menu Bar won't open
https://support.mozilla.org/en-US/questions/1194760
The reported solution was to rollback the graphics drivers.
Because the issues cropped up after applying updates on July 6, 2018,
I tracked down the list of recent updates with:
grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
-1 >packages.txt
After some editing to place packages on separate lines, and
identifying the grahics libraries, I arrived at the following list:
--
libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
--
To revert to the prior graphic drivers I tracked down the '.deb'
packages for each of the above packages and downloaded the
'17.2.8-0ubuntu0~16.04.1' version.
For example:
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1
I also discovered that some of these depended on
libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:
libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb
WORKAROUND (ROLLBACK TO PRIOR VERSION)
Install older versions with:
sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb
After rebooting, all the issues disappeared.
For example I was once again able to left-click on the Firefox **three
line/bar** menu and view the drop down list menu. Also the KDE bottom
menu bar retured to the normal "breeze" light grey colour.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780664/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
[Touch-packages] [Bug 1762952] Re: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1762952 Title: Alternative shortcut for layout switching Alt+Shift unexpectedly set by default Status in console-setup package in Ubuntu: Fix Released Status in gnome-control-center package in Ubuntu: Invalid Status in console-setup source package in Bionic: Confirmed Status in gnome-control-center source package in Bionic: Invalid Bug description: Version: Ubuntu 18.04 Final Beta with default Gnome Shell included in 18.04 Steps to reproduce: 1. Define two keyboard input methods in Settings -> Region & Language -> Input Sources 2. Open several applications 3. Observe that application windows can be iterated with Alt + Tab 4. Once application window iteration was begun with Alt + Tab, try to iterate backwards with Alt + Shift + Tab. 5. Try to change keyboard input method switching hotkeys in Settings -> Region & Language -> Input Sources -> Options. 6. Observe that Keyboard shortcut for "Alternative switch to next source" is set to "Alt + Shift" and that keyboard shortcuts can only be changed in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. 7. Observe that the shortcut for "Alternative switch to next source" is not available for configuration in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Actual state: * Performing step 4 does not select the previous app in application switcher but instead changes keyboard input method. Expected state: * The shortcut for "Alternative switch to next source" can be changed and / or deactivated in Settings -> Devices -> Keyboard -> Keyboard Shortcuts. Notes: * The above was working fine in Ubuntu 17.10. I assume "Alternative switch to next source" did not exist in that version of Gnome Shell. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1762952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon
I'm sorry, my previous comment seems to be untrue.
I have just found that aptitude will happily upgrade everything else the latest
version, if I hold just these five packages at the versions listed:
libwayland-egl1-mesa:amd64 11.2.0-1ubuntu2
libegl1-mesa:amd64 11.2.0-1ubuntu2
libgl1-mesa-dri:i386 11.2.0-1ubuntu2
libgl1-mesa-dri:amd64 11.2.0-1ubuntu2
mesa-vdpau-drivers:amd64 11.2.0-1ubuntu2
So it is in fact possible to have just these five packages downgraded
while waiting for a fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1780664
Title:
Recent libgl-mesa graphics update prevents drop down list menu
appearing in apps like firefox three line/bar menu icon
Status in mesa package in Ubuntu:
Confirmed
Bug description:
PROBLEM
Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
drop down list menu appearing in apps like firefox three line/bar menu
icon.
After recently applying updates, left clicking on some application
menus and icons no longer displays a drop-down menu list.
For example in Firefox when I left-click on the **three line/bar**
icon in the upper right-hand corner, the normal drop down list menu
does not display. Also the menu drop down doesn't display in
keypassx. Further xchat-gnome doesn't even display a window.
Another anomaly is that my KDE bottom menu bar changed to a dark
theme.
BACKGROUND
I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
Graphics. I have KDE **System Settings -> Compositor** enabled with:
Scale method :Accurate
Rendering backend: OpenGL 3.1
OpenGL interface: GLX
Tearing prevention ("vsync"): Full screen repaints
Keep window thumbnails:Only for Shown Windows
INVESTIGATION
After several hours of searching the Internet I found one other case
of a similar problem.
Firefox's Menu Bar won't open
https://support.mozilla.org/en-US/questions/1194760
The reported solution was to rollback the graphics drivers.
Because the issues cropped up after applying updates on July 6, 2018,
I tracked down the list of recent updates with:
grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
-1 >packages.txt
After some editing to place packages on separate lines, and
identifying the grahics libraries, I arrived at the following list:
--
libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
--
To revert to the prior graphic drivers I tracked down the '.deb'
packages for each of the above packages and downloaded the
'17.2.8-0ubuntu0~16.04.1' version.
For example:
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1
I also discovered that some of these depended on
libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:
libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb
WORKAROUND (ROLLBACK TO PRIOR VERSION)
Install older versions with:
sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: dovecot (Ubuntu) Status: New => In Progress ** Changed in: dovecot (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: In Progress Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured. Triggers do not specify a ordering dependency however, so apt can very well have A in a state where it is not configurable, and installing B then fails. This is a limitation of triggers: They are not exposed in
[Touch-packages] [Bug 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot
237-3ubuntu10.2 fixed the issue for me in Bionic. With this version installed I was able to successfully log into the wifi on the train in the Netherlands. Previously I could not load the accept page. -- 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/1766969 Title: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot Status in systemd package in Ubuntu: Fix Committed Status in systemd source package in Artful: Confirmed Status in systemd source package in Bionic: Fix Committed Status in systemd source package in Cosmic: Fix Committed Bug description: [Impact] * More captive portals have been discovered that do not handle DNS requests with D0 set. * Thus extend previous aruba-networks fix from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all NXDOMAIN results with lower feature levels just in case. [Test Case] * systemd-resolved something-nonexistant.ubuntu.com * monitor the logs, and check that the transaction has been downgraded multiple times and tried at least once at a feature level below D0. There should be a downgrade message in the log. * Note, it will be cached, thus one may need to call $ systemd-resolved --flush-caches [Regression Potential] * Legitimate NXDOMAIN queries will now take longer, as they will be retried multiple times with different features sets until an answer is found. At that point the query will be cached and will return quickly. This is needed to work-around bad captive portals that do not support dns queries with D0. Post-captive portal, the feature level can usually be cranked back up and it does after a grace period. [Other Info] * Original bug report I was asked to create a new bug for this in https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it seems to be a different issue. I have installed the nightly image of Kubuntu Bionic from 25th of April. There systemd is in version 237-3ubuntu10. When connecting to the wifi hotspot in my hotel (Quality Hotel Augsburg) I cannot open the hotspot landing page that should give me access to the WIFI. With Windows and on an Iphone it's working. For the following distributions I can confirm it not working: Kubuntu 17.10 Kubuntu 18.04 (nightly image 25th of April 2018) The logs were taken on 18.04. Workaround: sudo systemctl disable systemd-resolved.service sudo service systemd-resolved stop sudo rm /etc/resolv.conf sudo nano /etc/NetworkManager/NetworkManager.conf >> add "dns=default" under [main] sudo service network-manager restart Then I can connect to the WIFI and I see the login page in Firefox. To capture some data I did the following: - connect to Hotspot - enter golem.de Case 1: Fresh default Kubuntu install With a default Kubuntu install it does not work. I can connect to the WIFI and get IP and DNS from DHCP but I cannot resolve any hostname. When trying to open the router ip directly in the browser it forwards to hotsplots.de which cannot be resolved. Case 2: With aforementioned Workaround I connect to the wifi, I open firefox and the login page shows up (if I havent been connected yet. In the capture I already was able to connect to the hotspot which allows immediately to connect to the webpage) PS: I'll be in this hotel till Friday 27th if more information are required. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1766969/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
clutter-imcontext declares an interest on /usr/lib/clutter- imcontext/immodules, but no package ships files in there, so not fixing that in a stable release. Not sure about devel. ** Changed in: clutter-imcontext (Ubuntu Xenial) Status: Triaged => Won't Fix ** Changed in: clutter-imcontext (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: yorick (Ubuntu Bionic) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: New Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: New Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: New Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: dochelp (Ubuntu Xenial) Status: New => Triaged ** Changed in: dochelp (Ubuntu Xenial) Assignee: (unassigned) => Julian Andres Klode (juliank) ** Changed in: dochelp (Ubuntu) Status: New => Fix Released ** Changed in: dochelp (Ubuntu Bionic) Status: New => Fix Released ** Changed in: dochelp (Ubuntu Xenial) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: New Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: New Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: New Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be configured.
[Touch-packages] [Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
For anyone that's interested --- I added the following to root's crontab: @reboot sleep 120 && /bin/systemctl restart sshd That works for me to get sshd up AND listening -- 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/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. Status in portable OpenSSH: New Status in openssh package in Ubuntu: Confirmed Status in openssh package in Debian: New Bug description: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/openssh/+bug/1549473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1779157] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@1927:main:do_install
** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback Traceback (most recent call last): - File "/usr/bin/unattended-upgrade", line 1927, in - sys.exit(main(options)) - File "/usr/bin/unattended-upgrade", line 1782, in main - logfile_dpkg) - File "/usr/bin/unattended-upgrade", line 1057, in do_install - "removal:%s" % "".join([pkg.name for pkg in marked_delete])) + File "/usr/bin/unattended-upgrade", line 1927, in + sys.exit(main(options)) + File "/usr/bin/unattended-upgrade", line 1782, in main + logfile_dpkg) + File "/usr/bin/unattended-upgrade", line 1057, in do_install + "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic + + Also seen as: + https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5 -- 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/1779157 Title: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended- upgrade@1927:main:do_install Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1.18.04.1, the problem page at https://errors.ubuntu.com/problem/9b1b98279fa2b503abb1b1b69bec0cabf647be0c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Traceback Traceback (most recent call last): File "/usr/bin/unattended-upgrade", line 1927, in sys.exit(main(options)) File "/usr/bin/unattended-upgrade", line 1782, in main logfile_dpkg) File "/usr/bin/unattended-upgrade", line 1057, in do_install "removal:%s" % "".join([pkg.name for pkg in marked_delete])) AssertionError: Internal error. The following packages are marked for removal:linux-headers-4.15.0-20-generic Also seen as: https://errors.ubuntu.com/problem/733d2e7865692e215f406231edd3692a6a1810c5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1779157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396787] Re: checking trust of archives eats a lot of cpu
** Description changed: + [Impact] + + * Unattended-upgrades consumes tens of seconds or even minutes of CPU + time to verify the origin of the packages + + * Using excessive amount of CPU is unpleasant for desktop/laptop users + and also wastes computation time on servers/cloud instances. + + * Unattended-upgrades' algorithm for checking and adjusting package + origins is redesigned to visit and adjust less packages. + + [Test Case] + + * The added upgrade-all-security autopkgtest measure the time u-u needs for upgrading security updates on the tested release starting with no security updates applied to the point where all security updates are applied but all packages are left upgradable from -updates. The test also measures the time needed for --dry-run to find no updates to be installed unattended. + * Please run autopkgtests and look for the to time results: + ... + All upgrades installed + 44.41user 3.06system 0:48.35elapsed 98%CPU (0avgtext+0avgdata 164872maxresident)k + 208inputs+192376outputs (0major+642657minor)pagefaults 0swaps + ... + No packages found that can be upgraded unattended and no pending auto-removals + 2.83user 0.11system 0:02.98elapsed 98%CPU (0avgtext+0avgdata 79308maxresident)k + + + [Regression Potential] + + * Due to algorithm redesign there is a risk that packages from allowed + origins are not upgraded. There were unit tests for testing the + selection of the right packages to upgrade already, but a new + autopkgtest is also introduce to verify u-u's behavior on current real- + life security-updates. + + + [Original bug text] + (System: Ubuntu 14.04, up to date packages) I noticed that unattended-upgrades spends a significant amount of time in phases where it runs at 100% cpu. On a slower machine (core 2 t7200 2GHz) this goes on for minutes rather than seconds. This interferes with using the machine for other tasks. Using the --debug option to unattended-upgrades shows that the program outputs a lot of lines like the following during these 100% cpu phases: matching 'a'='trusty-updates' against ' From this output I guess the operation executed is not so complicated that it should require so much cpu power. ?? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Nov 26 21:53:57 2014 InstallationDate: Installed on 2014-08-28 (90 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) PackageArchitecture: all ProcEnviron: - TERM=xterm - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1396787 Title: checking trust of archives eats a lot of cpu Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: [Impact] * Unattended-upgrades consumes tens of seconds or even minutes of CPU time to verify the origin of the packages * Using excessive amount of CPU is unpleasant for desktop/laptop users and also wastes computation time on servers/cloud instances. * Unattended-upgrades' algorithm for checking and adjusting package origins is redesigned to visit and adjust less packages. [Test Case] * The added upgrade-all-security autopkgtest measure the time u-u needs for upgrading security updates on the tested release starting with no security updates applied to the point where all security updates are applied but all packages are left upgradable from -updates. The test also measures the time needed for --dry-run to find no updates to be installed unattended. * Please run autopkgtests and look for the to time results: ... All upgrades installed 44.41user 3.06system 0:48.35elapsed 98%CPU (0avgtext+0avgdata 164872maxresident)k 208inputs+192376outputs (0major+642657minor)pagefaults 0swaps ... No packages found that can be upgraded unattended and no pending auto-removals 2.83user 0.11system 0:02.98elapsed 98%CPU (0avgtext+0avgdata 79308maxresident)k [Regression Potential] * Due to algorithm redesign there is a risk that packages from allowed origins are not upgraded. There were unit tests for testing the selection of the right packages to upgrade already, but a new autopkgtest is also introduce to verify u-u's behavior on current real-life security-updates. [Original bug text] (System: Ubuntu 14.04, up to date packages) I noticed that unattended-upgrades spends a
[Touch-packages] [Bug 1780846] Re: After update 2018-07-08 menus and buttons are behaving badly
Thanks to Patrick Wigmore and Curtis Gedak for diagnosing the problem and coming up with a way to revert the problem. I downloaded the .deb files linked to from Bug #1780664. Then sudo dpkg -i \ libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \ libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \ libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \ libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \ libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \ mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb Then restarted the machine, tho restarting X might have done the job. Now I am back to menus and buttons looking like they should. Really good, thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1780846 Title: After update 2018-07-08 menus and buttons are behaving badly Status in mesa package in Ubuntu: Confirmed Bug description: After an update to Description: Ubuntu 16.04.4 LTS Release: 16.04 Menus and buttons are behaving badly. This is a general issue, affecting most programs. Text in buttons is not always being displayed. When you mouse over an entry in a menu list the previous entry disappears e.g. the logout menu (power button icon at top right of panel) Menu items are getting red backgrounds where they were not before. Introduced by update done by update-manager on Last update Start-Date: 2018-07-08 21:25:10 Modified packages: libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-nouveau2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-nouveau2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libapt-inst2.0:amd64 (1.2.26, 1.2.27) libegl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt:amd64 (1.2.26, 1.2.27) libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) mesa-common-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libapt-pkg5.0:amd64 (1.2.26, 1.2.27) apache2-data:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-amdgpu1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-amdgpu1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) firefox-locale-en:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm2:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm2:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libgl1-mesa-dev:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apt-utils:amd64 (1.2.26, 1.2.27) libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) libdrm-intel1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-intel1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) apache2-bin:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) firefox:amd64 (60.0.2+build1-0ubuntu0.16.04.1, 61.0+build3-0ubuntu0.16.04.2) apt-transport-https:amd64 (1.2.26, 1.2.27) libdrm-radeon1:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-radeon1:i386 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1, 18.0.5-0ubuntu0~16.04.1) apache2:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) apache2-utils:amd64 (2.4.18-2ubuntu3.8, 2.4.18-2ubuntu3.9) libdrm-dev:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) libdrm-common:amd64 (2.4.83-1~16.04.1, 2.4.91-2~16.04.1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1780846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781271] Re: Gnome shell crashing after login
It sounds like some part of the system has crashed. Please: 1. Apply the workaround from bug 994921. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash and tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the contents of the /var/lib/whoopsie/whoopsie-id file on the machine. Do you find any links to recent problems on the machine? If so then please send them to us. ** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1781271 Title: Gnome shell crashing after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: Gnome shell usually (not everytime) crashes after login. When I log in everything looks fine. Then I try to start firefox, gnome-shell crashes first time, but recovers in this first case. Second crash occurs after I try to click with mouse or press some key. This time it crashes whole X and returns to login screen. In log I can see gnome-shell segfaults in libgobject. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.48 Thu Mar 22 00:42:57 PDT 2018 GCC version: gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3) ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 20:07:36 2018 DistUpgraded: 2018-05-05 10:06:30,687 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-22-generic, x86_64: installed nvidia, 390.48, 4.15.0-23-generic, x86_64: installed nvidiabl, 0.88, 4.15.0-22-generic, x86_64: installed nvidiabl, 0.88, 4.15.0-23-generic, x86_64: installed virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation GP104M [GeForce GTX 1080 Mobile] [10de:1be0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CLEVO/KAPOK Computer GP104M [GeForce GTX 1080 Mobile] [1558:7708] InstallationDate: Installed on 2017-12-04 (218 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) MachineType: Eurocom Sky X7E2G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic root=UUID=2042381a-928b-4dcb-aabe-3d1cc338cc1a ro quiet splash nvidia.NVreg_EnableBacklightHandler=1 video.only_lcd=0 noresume vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to bionic on 2018-05-05 (67 days ago) dmi.bios.date: 07/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.06.11 dmi.board.asset.tag: Tag 12345 dmi.board.name: Sky X7E2G dmi.board.vendor: Eurocom dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Eurocom dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.06.11:bd07/27/2017:svnEurocom:pnSkyX7E2G:pvrNotApplicable:rvnEurocom:rnSkyX7E2G:rvrNotApplicable:cvnEurocom:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Sky X7E2G dmi.product.version: Not Applicable dmi.sys.vendor: Eurocom version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1781271/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781294] Re: no sound but system recognizes integrated sound card on laptop [Dell XPS 13 9360]
** Summary changed: - no sound but system recognizes integrated sound card on laptop + no sound but system recognizes integrated sound card on laptop [Dell XPS 13 9360] ** Summary changed: - no sound but system recognizes integrated sound card on laptop [Dell XPS 13 9360] + No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => High -- 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/1781294 Title: No sound card detected by PulseAudio and ALSA, but is visible in lspci [Dell XPS 13 9360] Status in pulseaudio package in Ubuntu: New Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780196] Re: Timed out Availability of block devices service
I think it can be fixed in 2 ways: * blkdeactivate handles properly the syncing software-raid arrays * re-order this service, to be after the "standard" software-raid deinit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1780196 Title: Timed out Availability of block devices service Status in lvm2 package in Ubuntu: New Bug description: On a fresh Ubuntu 18.04 (64 bit) Server install, the blk- availability.service always killed by timeout at shutdown. I think the dependency of this service is bad, but I don't know what would be the good shutdown order for this. An almost same config has been worked on Xenial... The disk sub-system is * NVMe SSD * EFI partition * boot partition * LVM phisical volume * root logical volume * swap logical volume * data logical volume * 2 pcs. HDDs in RAID1 (but the md0 is not used yet) ## # Versions # # Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 # Kernel Linux server 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # LVM lvm2 2.02.176-4.1ubuntu3 ## # Journal # systemd[1]: Stopped Load/Save Random Seed. systemd[1]: Stopped Update UTMP about System Boot/Shutdown. systemd[1]: Stopped Network Time Synchronization. kernel: usb 1-13: USB disconnect, device number 2 systemd[1]: blk-availability.service: Stopping timed out. Terminating. systemd[1]: blk-availability.service: Control process exited, code=killed status=15 blkdeactivate[2447]: [MD]: deactivating raid1 device md0... resync action in progress... systemd[1]: blk-availability.service: Failed with result 'timeout'. systemd[1]: Stopped Availability of block devices. systemd[1]: Stopping iSCSI initiator daemon (iscsid)... iscsid[951]: iscsid shutting down. systemd[1]: Stopped iSCSI initiator daemon (iscsid). systemd[1]: Stopped target Network is Online. systemd[1]: Stopped Wait for Network to be Configured. systemd[1]: Stopped target Network. systemd[1]: Stopping Network Name Resolution... systemd[1]: Stopped Network Name Resolution. systemd[1]: Stopping Network Service... systemd[1]: Stopped Create Volatile Files and Directories. systemd[1]: Stopped target Local File Systems. systemd[1]: Unmounting /boot/efi... systemd[1]: Unmounting /run/user/1000... systemd[1]: Unmounted /run/user/1000. systemd[1]: Stopped target Swap. systemd[1]: Deactivating swap /dev/disk/by-uuid/8a3d99d0-683e---9765162cc070... systemd[1]: Unmounted /boot/efi. systemd[1]: Unmounting /boot... systemd[1]: Stopped File System Check on /dev/disk/by-uuid/AB9E-5A2C. systemd[1]: Deactivated swap /dev/xxx_server_ssd/swap. systemd[1]: Deactivated swap /dev/disk/by-uuid/8a3d99d0-683e---9765162cc070. systemd[1]: Deactivated swap /dev/disk/by-id/dm-uuid-LVM-eatHKVdbDuw5L5RXXX2yJn7QosUWvV2IIApCOG73Bc2CbrUabBC6L3dh0N2D. systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-xxx_server_ssd-swap. systemd[1]: Deactivated swap /dev/dm-1. systemd[1]: Stopped Network Service. systemd[1]: Deactivated swap /dev/mapper/xxx_server_ssd-swap. systemd[1]: Unmounted /boot. systemd[1]: Stopped File System Check on /dev/disk/by-uuid/d7cc70cc-0f33---cc21d3ed1232. systemd[1]: Removed slice system-systemd\x2dfsck.slice. systemd[1]: Stopped target Local File Systems (Pre). systemd[1]: Stopped Remount Root and Kernel File Systems. systemd[1]: Stopped Create Static Device Nodes in /dev. systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... systemd[1]: Stopped target Network (Pre). systemd[1]: Stopped Apply Kernel Variables. systemd[1]: Stopped Load Kernel Modules. systemd[1]: Reached target Shutdown. systemd[1]: Reached target Unmount All Filesystems. systemd[1]: Reached target Final Step. systemd[1]: Starting Power-Off... ## # systemctl cat blk-availability.service # # /lib/systemd/system/blk-availability.service [Unit] Description=Availability of block devices After=lvm2-activation.service lvm2-lvmetad.service iscsi-shutdown.service iscsi.service iscsid.service fcoe.service DefaultDependencies=no Conflicts=shutdown.target [Service] Type=oneshot ExecStart=/bin/true ExecStop=/sbin/blkdeactivate -u -l wholevg -m disablequeueing -r wait RemainAfterExit=yes [Install] WantedBy=sysinit.target ## # Other # I tried to ask help on https://askubuntu.com/questions/1051856/timed-out-availability-of-block-devices, but I haven't got any response. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lvm2 2.02.176-4.1ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 ApportVersion:
[Touch-packages] [Bug 1781327] Re: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other in
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1781327 Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 Status in perl package in Ubuntu: New Bug description: Package failed to install while updating ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libperl5.26 5.26.2-6 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Thu Jul 12 06:55:08 2018 DuplicateSignature: package:libperl5.26:5.26.2-6 Unpacking libperl5.26:i386 (5.26.2-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-dzor1c/10-libperl5.26_5.26.2-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-06-12 (29 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180602) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: perl Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1781327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781242] Re: as segfault with invalid -march= option
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => binutils (Ubuntu) ** Changed in: ubuntu-z-systems Status: New => Triaged ** Changed in: ubuntu-z-systems Importance: Undecided => Low ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Canonical Foundations Team (canonical-foundations) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1781242 Title: as segfault with invalid -march= option Status in Ubuntu on IBM z Systems: Triaged Status in binutils package in Ubuntu: New Bug description: The GNU assembler segfaults with an invalid -march= option Contact Information = n/a ---uname output--- n/a Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ as -march=foo Segmentation fault Userspace tool common name: as The userspace tool has the following bit modes: 64 Userspace rpm: binutils-2.26.1-1ubuntu1~16.04.6 Userspace tool obtained from project website: na *Additional Instructions for n/a: -Attach ltrace and strace of userspace application. The problem is not critical since usually 'as' is invoked through the gcc driver which itself errors out for wrong -march= options. It will only be a problem if somebody builds a more recent GCC from source and uses an -march= option for a machine not supported by the default binutils. Please consider integrating the attached patch into 16.04 binutils. The problem has been fixed in later binutils already. Ubuntu 18.04 does not appear to be affected. --> Package has to set corectly by Canonical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1781242/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /
** Patch added: "mkinitramfs.patch" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1661629/+attachment/5162606/+files/mkinitramfs.patch -- 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/1661629 Title: upgrade of kernel fails with mkinitramfs: failed to determine device for / Status in initramfs-tools package in Ubuntu: Confirmed Bug description: When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with root on ZFS I get this error: Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /etc/initramfs-tools/ Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-59-generic (--configure): subprocess installed post-installation script returned error exit status 2 version of initramfs-tools is 0.122ubuntu8.8 Output of mount is: sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755) rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) debugfs on /sys/kernel/debug type debugfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl) rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl) rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl) rpool/srv on /srv type zfs (rw,noatime,xattr,noacl) rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl) rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl) rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl) rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1623576k,mode=700,uid=1000,gid=1000) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,relatime) tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime) cat
[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /
The attachment "mkinitramfs.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.] ** Tags added: patch -- 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/1661629 Title: upgrade of kernel fails with mkinitramfs: failed to determine device for / Status in initramfs-tools package in Ubuntu: Confirmed Bug description: When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with root on ZFS I get this error: Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic /boot/vmlinuz-4.4.0-59-generic kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic mkinitramfs: failed to determine device for / mkinitramfs: workaround is MODULES=most, check: grep -r MODULES /etc/initramfs-tools/ Error please report bug on initramfs-tools Include the output of 'mount' and 'cat /proc/mounts' update-initramfs: failed for with 1. run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052. dpkg: error processing package linux-image-4.4.0-59-generic (--configure): subprocess installed post-installation script returned error exit status 2 version of initramfs-tools is 0.122ubuntu8.8 Output of mount is: sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755) rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) mqueue on /dev/mqueue type mqueue (rw,relatime) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=31,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) debugfs on /sys/kernel/debug type debugfs (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) rpool/home on /home type zfs (rw,nosuid,noatime,xattr,noacl) rpool/home/fredrik on /home/fredrik type zfs (rw,nosuid,noatime,xattr,noacl) rpool/home/root on /root type zfs (rw,nosuid,noatime,xattr,noacl) rpool/srv on /srv type zfs (rw,noatime,xattr,noacl) rpool/var/cache on /var/cache type zfs (rw,nosuid,noexec,noatime,xattr,noacl) rpool/var/log on /var/log type zfs (rw,nosuid,noexec,noatime,xattr,noacl) rpool/var/spool on /var/spool type zfs (rw,nosuid,noexec,noatime,xattr,noacl) rpool/var/tmp on /var/tmp type zfs (rw,nosuid,noatime,xattr,noacl) tmpfs on /run/user/1000 type tmpfs
[Touch-packages] [Bug 1781327] [NEW] package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other
Public bug reported: Package failed to install while updating ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libperl5.26 5.26.2-6 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Thu Jul 12 06:55:08 2018 DuplicateSignature: package:libperl5.26:5.26.2-6 Unpacking libperl5.26:i386 (5.26.2-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-dzor1c/10-libperl5.26_5.26.2-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-06-12 (29 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180602) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: perl Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: perl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic package-conflict -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to perl in Ubuntu. https://bugs.launchpad.net/bugs/1781327 Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 Status in perl package in Ubuntu: New Bug description: Package failed to install while updating ProblemType: Package DistroRelease: Ubuntu 18.10 Package: libperl5.26 5.26.2-6 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.10-0ubuntu3 Architecture: amd64 Date: Thu Jul 12 06:55:08 2018 DuplicateSignature: package:libperl5.26:5.26.2-6 Unpacking libperl5.26:i386 (5.26.2-6) ... dpkg: error processing archive /tmp/apt-dpkg-install-dzor1c/10-libperl5.26_5.26.2-6_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 InstallationDate: Installed on 2018-06-12 (29 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180602) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3 RelatedPackageVersions: dpkg 1.19.0.5ubuntu3 apt 1.7.0~alpha2 SourcePackage: perl Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other instances of package libperl5.26:i386 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1781327/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780196] Re: Timed out Availability of block devices service
I found the commit where introduced this blkdeactivate: https://sourceware.org/git/?p=lvm2.git;a=commit;h=c698ee14bbb1310cf2383c8977d14a8e29139f8c > Traverses the tree of block devices and tries to deactivate them. > Currently, it supports device-mapper-based devices together with LVM. > See man/blkdeactivate.8 for more info. > > It is targeted for use during shutdown to properly deactivate the > whole block device stack - systemd and init scripts are provided as > well. However, it might be used directly on command line too. In this case, this stuff runs too early, as I think. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1780196 Title: Timed out Availability of block devices service Status in lvm2 package in Ubuntu: New Bug description: On a fresh Ubuntu 18.04 (64 bit) Server install, the blk- availability.service always killed by timeout at shutdown. I think the dependency of this service is bad, but I don't know what would be the good shutdown order for this. An almost same config has been worked on Xenial... The disk sub-system is * NVMe SSD * EFI partition * boot partition * LVM phisical volume * root logical volume * swap logical volume * data logical volume * 2 pcs. HDDs in RAID1 (but the md0 is not used yet) ## # Versions # # Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 # Kernel Linux server 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # LVM lvm2 2.02.176-4.1ubuntu3 ## # Journal # systemd[1]: Stopped Load/Save Random Seed. systemd[1]: Stopped Update UTMP about System Boot/Shutdown. systemd[1]: Stopped Network Time Synchronization. kernel: usb 1-13: USB disconnect, device number 2 systemd[1]: blk-availability.service: Stopping timed out. Terminating. systemd[1]: blk-availability.service: Control process exited, code=killed status=15 blkdeactivate[2447]: [MD]: deactivating raid1 device md0... resync action in progress... systemd[1]: blk-availability.service: Failed with result 'timeout'. systemd[1]: Stopped Availability of block devices. systemd[1]: Stopping iSCSI initiator daemon (iscsid)... iscsid[951]: iscsid shutting down. systemd[1]: Stopped iSCSI initiator daemon (iscsid). systemd[1]: Stopped target Network is Online. systemd[1]: Stopped Wait for Network to be Configured. systemd[1]: Stopped target Network. systemd[1]: Stopping Network Name Resolution... systemd[1]: Stopped Network Name Resolution. systemd[1]: Stopping Network Service... systemd[1]: Stopped Create Volatile Files and Directories. systemd[1]: Stopped target Local File Systems. systemd[1]: Unmounting /boot/efi... systemd[1]: Unmounting /run/user/1000... systemd[1]: Unmounted /run/user/1000. systemd[1]: Stopped target Swap. systemd[1]: Deactivating swap /dev/disk/by-uuid/8a3d99d0-683e---9765162cc070... systemd[1]: Unmounted /boot/efi. systemd[1]: Unmounting /boot... systemd[1]: Stopped File System Check on /dev/disk/by-uuid/AB9E-5A2C. systemd[1]: Deactivated swap /dev/xxx_server_ssd/swap. systemd[1]: Deactivated swap /dev/disk/by-uuid/8a3d99d0-683e---9765162cc070. systemd[1]: Deactivated swap /dev/disk/by-id/dm-uuid-LVM-eatHKVdbDuw5L5RXXX2yJn7QosUWvV2IIApCOG73Bc2CbrUabBC6L3dh0N2D. systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-xxx_server_ssd-swap. systemd[1]: Deactivated swap /dev/dm-1. systemd[1]: Stopped Network Service. systemd[1]: Deactivated swap /dev/mapper/xxx_server_ssd-swap. systemd[1]: Unmounted /boot. systemd[1]: Stopped File System Check on /dev/disk/by-uuid/d7cc70cc-0f33---cc21d3ed1232. systemd[1]: Removed slice system-systemd\x2dfsck.slice. systemd[1]: Stopped target Local File Systems (Pre). systemd[1]: Stopped Remount Root and Kernel File Systems. systemd[1]: Stopped Create Static Device Nodes in /dev. systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... systemd[1]: Stopped target Network (Pre). systemd[1]: Stopped Apply Kernel Variables. systemd[1]: Stopped Load Kernel Modules. systemd[1]: Reached target Shutdown. systemd[1]: Reached target Unmount All Filesystems. systemd[1]: Reached target Final Step. systemd[1]: Starting Power-Off... ## # systemctl cat blk-availability.service # # /lib/systemd/system/blk-availability.service [Unit] Description=Availability of block devices After=lvm2-activation.service lvm2-lvmetad.service iscsi-shutdown.service iscsi.service iscsid.service fcoe.service DefaultDependencies=no Conflicts=shutdown.target [Service] Type=oneshot ExecStart=/bin/true ExecStop=/sbin/blkdeactivate -u -l wholevg -m disablequeueing -r wait RemainAfterExit=yes [Install]
[Touch-packages] [Bug 1780196] Re: Timed out Availability of block devices service
FYI: This problem can happen when the md0 device still synchronizing. Now, when the md0 is in sync, the service stopped as well: # journalctl -b -1 -u blk-availability.service systemd[1]: Starting Availability of block devices... systemd[1]: Started Availability of block devices. systemd[1]: Stopping Availability of block devices... blkdeactivate[1440]: Deactivating block devices: blkdeactivate[1440]: [UMOUNT]: unmounting paint_server_ssd-system (dm-2) mounted on /var/datastore/system... done blkdeactivate[1440]: [SKIP]: unmount of paint_server_ssd-swap (dm-1) mounted on [SWAP] blkdeactivate[1440]: [SKIP]: unmount of paint_server_ssd-root (dm-0) mounted on / blkdeactivate[1440]: [MD]: deactivating raid1 device md0... done systemd[1]: Stopped Availability of block devices. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1780196 Title: Timed out Availability of block devices service Status in lvm2 package in Ubuntu: New Bug description: On a fresh Ubuntu 18.04 (64 bit) Server install, the blk- availability.service always killed by timeout at shutdown. I think the dependency of this service is bad, but I don't know what would be the good shutdown order for this. An almost same config has been worked on Xenial... The disk sub-system is * NVMe SSD * EFI partition * boot partition * LVM phisical volume * root logical volume * swap logical volume * data logical volume * 2 pcs. HDDs in RAID1 (but the md0 is not used yet) ## # Versions # # Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 # Kernel Linux server 4.15.0-24-generic #26-Ubuntu SMP Wed Jun 13 08:44:47 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux # LVM lvm2 2.02.176-4.1ubuntu3 ## # Journal # systemd[1]: Stopped Load/Save Random Seed. systemd[1]: Stopped Update UTMP about System Boot/Shutdown. systemd[1]: Stopped Network Time Synchronization. kernel: usb 1-13: USB disconnect, device number 2 systemd[1]: blk-availability.service: Stopping timed out. Terminating. systemd[1]: blk-availability.service: Control process exited, code=killed status=15 blkdeactivate[2447]: [MD]: deactivating raid1 device md0... resync action in progress... systemd[1]: blk-availability.service: Failed with result 'timeout'. systemd[1]: Stopped Availability of block devices. systemd[1]: Stopping iSCSI initiator daemon (iscsid)... iscsid[951]: iscsid shutting down. systemd[1]: Stopped iSCSI initiator daemon (iscsid). systemd[1]: Stopped target Network is Online. systemd[1]: Stopped Wait for Network to be Configured. systemd[1]: Stopped target Network. systemd[1]: Stopping Network Name Resolution... systemd[1]: Stopped Network Name Resolution. systemd[1]: Stopping Network Service... systemd[1]: Stopped Create Volatile Files and Directories. systemd[1]: Stopped target Local File Systems. systemd[1]: Unmounting /boot/efi... systemd[1]: Unmounting /run/user/1000... systemd[1]: Unmounted /run/user/1000. systemd[1]: Stopped target Swap. systemd[1]: Deactivating swap /dev/disk/by-uuid/8a3d99d0-683e---9765162cc070... systemd[1]: Unmounted /boot/efi. systemd[1]: Unmounting /boot... systemd[1]: Stopped File System Check on /dev/disk/by-uuid/AB9E-5A2C. systemd[1]: Deactivated swap /dev/xxx_server_ssd/swap. systemd[1]: Deactivated swap /dev/disk/by-uuid/8a3d99d0-683e---9765162cc070. systemd[1]: Deactivated swap /dev/disk/by-id/dm-uuid-LVM-eatHKVdbDuw5L5RXXX2yJn7QosUWvV2IIApCOG73Bc2CbrUabBC6L3dh0N2D. systemd[1]: Deactivated swap /dev/disk/by-id/dm-name-xxx_server_ssd-swap. systemd[1]: Deactivated swap /dev/dm-1. systemd[1]: Stopped Network Service. systemd[1]: Deactivated swap /dev/mapper/xxx_server_ssd-swap. systemd[1]: Unmounted /boot. systemd[1]: Stopped File System Check on /dev/disk/by-uuid/d7cc70cc-0f33---cc21d3ed1232. systemd[1]: Removed slice system-systemd\x2dfsck.slice. systemd[1]: Stopped target Local File Systems (Pre). systemd[1]: Stopped Remount Root and Kernel File Systems. systemd[1]: Stopped Create Static Device Nodes in /dev. systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling... systemd[1]: Stopped target Network (Pre). systemd[1]: Stopped Apply Kernel Variables. systemd[1]: Stopped Load Kernel Modules. systemd[1]: Reached target Shutdown. systemd[1]: Reached target Unmount All Filesystems. systemd[1]: Reached target Final Step. systemd[1]: Starting Power-Off... ## # systemctl cat blk-availability.service # # /lib/systemd/system/blk-availability.service [Unit] Description=Availability of block devices After=lvm2-activation.service lvm2-lvmetad.service iscsi-shutdown.service iscsi.service iscsid.service fcoe.service
[Touch-packages] [Bug 1781242] [NEW] as segfault with invalid -march= option
You have been subscribed to a public bug: The GNU assembler segfaults with an invalid -march= option Contact Information = n/a ---uname output--- n/a Machine Type = n/a ---Debugger--- A debugger is not configured ---Steps to Reproduce--- $ as -march=foo Segmentation fault Userspace tool common name: as The userspace tool has the following bit modes: 64 Userspace rpm: binutils-2.26.1-1ubuntu1~16.04.6 Userspace tool obtained from project website: na *Additional Instructions for n/a: -Attach ltrace and strace of userspace application. The problem is not critical since usually 'as' is invoked through the gcc driver which itself errors out for wrong -march= options. It will only be a problem if somebody builds a more recent GCC from source and uses an -march= option for a machine not supported by the default binutils. Please consider integrating the attached patch into 16.04 binutils. The problem has been fixed in later binutils already. Ubuntu 18.04 does not appear to be affected. --> Package has to set corectly by Canonical ** Affects: ubuntu-z-systems Importance: Undecided Status: New ** Affects: binutils (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-169493 severity-low targetmilestone-inin16044 -- as segfault with invalid -march= option https://bugs.launchpad.net/bugs/1781242 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554803] Re: apparmor: missing stub hardware directories
Ubuntu 16.04 Same issue happened to me after updates. Apparmor failure with code 123 prevents system from booting. These directories were created manually in recovery single mode: mkdir -p /usr/share/apparmor/hardware/graphics.d mkdir -p /usr/share/apparmor/hardware/audio.d mkdir -p /usr/share/apparmor/hardware/video.d but it made no effect. After that: apt-get install apparmor-easyprof-ubuntu System booted up successfully. -- 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/1554803 Title: apparmor: missing stub hardware directories Status in apparmor package in Ubuntu: Confirmed Bug description: ● apparmor.service - LSB: AppArmor initialization Loaded: loaded (/etc/init.d/apparmor; bad; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2016-03-08 14:34:04 EST; 4h 23min ago Docs: man:systemd-sysv-generator(8) Process: 2909 ExecStart=/etc/init.d/apparmor start (code=exited, status=123) Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardware/graphics.d' Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in /etc/apparmor.d/disable: usr.bin.firefox Mar 08 14:34:04 ogre apparmor[2909]: AppArmor parser error for /etc/apparmor.d/usr.bin.webbrowser-app in /etc/apparmor.d/usr.bin.webbrowser-app at line 26: Could not open '/usr/share/apparmor/hardware/graphics.d' Mar 08 14:34:04 ogre apparmor[2909]: Skipping profile in /etc/apparmor.d/disable: usr.sbin.rsyslogd Mar 08 14:34:04 ogre apparmor[2909]:...fail! Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Control process exited, code=exited status=123 Mar 08 14:34:04 ogre systemd[1]: Failed to start LSB: AppArmor initialization. Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Unit entered failed state. Mar 08 14:34:04 ogre systemd[1]: apparmor.service: Failed with result 'exit-code'. /usr/share/apparmor/hardware/graphics.d doesn't in fact exist on my system. I'm not sure what package would provide it, but it seems curious to me that the package doesn't supply its relevant apparmor bits. I'd have expected the apparmor package to not complain about bits belonging to packages that aren't installed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apparmor 2.10-3ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-11.26-generic 4.4.4 Uname: Linux 4.4.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 8 18:53:31 2016 InstallationDate: Installed on 2016-02-24 (13 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160219) ProcEnviron: TERM=xterm-color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-11-generic.efi.signed root=/dev/mapper/hostname-root ro net.ifnames=0 biosdevname=0 SourcePackage: apparmor Syslog: Mar 8 14:34:05 ogre dbus[3062]: [system] AppArmor D-Bus mediation is enabled UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1554803/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: qgis (Ubuntu) Importance: Undecided Status: New ** Changed in: qgis (Ubuntu) Status: New => In Progress ** Changed in: qgis (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: In Progress Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a
[Touch-packages] [Bug 1773033] Re: unattended upgrade no longer actions on shutdown
** Description changed:
+ [Impact]
+
+ * Unattended-upgrades does not install upgrades when it is configured
+ to install updates on shutdown and when it the system is started on
+ battery, but installs updates on battery in other cases.
+
+ * This behaviour is unintended and confuses users, moreover installing
+ updates on battery risks the system to be shut down in the middle of an
+ upgrade due to depleting the battery.
+
+ * This upload changes u-u to skip updates or gracefully stop when the
+ system is switching to batter-powered state by default minimizing the
+ risk of breaking the system.
+
+ [Test Case]
+
+ * Run "unattended-upgrade --dry-run --verbose" on battery and on AC
+ power
+
+ * With default configuration u-u should stop with the following message on
battery:
+ Initial blacklisted packages:
+ Initial whitelisted packages:
+ Starting unattended upgrades script
+ Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
+ System is on battery power, stopping
+
+ * On AC power it should continue:
+ $ sudo ./unattended-upgrade --dry-run --verbose
+ Initial blacklisted packages:
+ Initial whitelisted packages:
+ Starting unattended upgrades script
+ Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
+ No packages found that can be upgraded unattended and no pending auto-removals
+
+ * Add the following configuration file and check u-u continuing even on
battery:
+ $ cat /etc/apt/apt.conf.d/51unattended-upgrades-on-battery
+ Unattended-Upgrade::OnlyOnACPower "false";
+ rbalint@yogi:~/projects/deb/unattended-upgrades$ sudo ./unattended-upgrade
--dry-run --verbose
+ Initial blacklisted packages:
+ Initial whitelisted packages:
+ Starting unattended upgrades script
+ Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security,
o=UbuntuESM,a=bionic
+ No packages found that can be upgraded unattended and no pending auto-removals
+
+
+ [Regression Potential]
+
+ * Unattended-upgrades may fail to install updates even on AC power, but
+ this is unlikely to happen due to the code changed being fairly simple.
+ on_ac_power may return 255 (false) Power status could not be determined,
+ but this is mapped to being on AC power and installing the updates, only
+ subprocess.call("on_ac_power") == 1 makes u-u skip updates.
+
+ [Original Bug Text]
+
Ubuntu 17.10 and 18.04 do not install updates with InstallOnShutdown
flag set.
post-install script on 14.04 and 16.04 would set options in
/etc/apt/apt.conf.d/50unattended-upgrades and
/etc/apt/apt.conf.d/10periodic to install updates on shutdown of ubuntu
desktop. This worked on 17.10 also, until an update before the release
of 18.04. After a fresh install of 18.04, ran the post install script.
Below is the contents of the two files, updates do not run, even if
performing an apt update and leaving the machine up for a few hours to
download packages in the back ground. Both the unattended-upgrades and
unattended-upgrades-shutdown log files are empty.
Description: Ubuntu 18.04 LTS
Release: 18.04
ii unattended-upgrades1.1ubuntu1
all automatic installation of security upgrades
-
--/etc/apt/apt.conf.d/50unattended-upgrades
Unattended-Upgrade::Allowed-Origins {
- "${distro_id}:${distro_codename}";
- "${distro_id}:${distro_codename}-security";
- // Extended Security Maintenance; doesn't necessarily exist for
- // every release and this system may not have it installed, but if
- // available, the policy for updates is such that unattended-upgrades
- // should also install from here by default.
- "${distro_id}ESM:${distro_codename}";
- "${distro_id}:${distro_codename}-updates";
+ "${distro_id}:${distro_codename}";
+ "${distro_id}:${distro_codename}-security";
+ // Extended Security Maintenance; doesn't necessarily exist for
+ // every release and this system may not have it installed, but if
+ // available, the policy for updates is such that unattended-upgrades
+ // should also install from here by default.
+ "${distro_id}ESM:${distro_codename}";
+ "${distro_id}:${distro_codename}-updates";
// "${distro_id}:${distro_codename}-proposed";
// "${distro_id}:${distro_codename}-backports";
- "LP-PPA-libreoffice:${distro_codename}";
- "Canonical:${distro_codename}";
+ "LP-PPA-libreoffice:${distro_codename}";
+ "Canonical:${distro_codename}";
};
Unattended-Upgrade::Package-Blacklist {
// "vim";
// "libc6";
// "libc6-dev";
// "libc6-i686";
};
Unattended-Upgrade::DevRelease "false";
Unattended-Upgrade::InstallOnShutdown "true";
Unattended-Upgrade::Remove-Unused-Dependencies "true";
-
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
wokkel needed fixing in both Ubuntu 16.04 and Ubuntu 18.04 although I can't add tasks for those releases. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: In Progress Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: In Progress Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: In Progress Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is
[Touch-packages] [Bug 1163740] [NEW] Options on screen are mixed up
You have been subscribed to a public bug: To reproduce: 1. start "ubuntu-bug" from the console (without any options) 2. A new window "Apport" will open (I'm on KDE if that matters) 3. Select "Security related problems" and click "OK" 4. Select "Other problem" and click "OK" I now get the message: "This is expected as there is no "tty" allocated when running commands directly via ssh. ..." It seems like options on the screen don't match the code executed. It's as if someone reordered the options on screen without updating the code that processes the selections. To add insult to injury, the app crashes when I click on "OK": Application: Apport KDE (python3.2mu), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 QWidget::~QWidget (this=0xb6dae0, __in_chrg=) at kernel/qwidget.cpp:1630 #7 0x7fc3cfba1759 in ?? () from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so #8 0x7fc3cfb95976 in ?? () from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so #9 0x7fc3d0011cd4 in ?? () from /usr/lib/python3/dist-packages/sip.cpython-32mu.so #10 0x7fc3d00135b9 in ?? () from /usr/lib/python3/dist-packages/sip.cpython-32mu.so #11 0x0046e617 in ?? () #12 0x004d6ff9 in ?? () #13 0x0046e6af in ?? () #14 0x004cb403 in ?? () #15 0x004cb4b7 in PyDict_SetItem () #16 0x0049a924 in _PyModule_Clear () #17 0x0050a864 in PyImport_Cleanup () #18 0x0041b95c in Py_Finalize () #19 0x0041ba32 in Py_Exit () #20 0x0042c35f in ?? () #21 0x0087e9e0 in ?? () #22 0x00b00fb0 in ?? () #23 0x008bb960 in ?? () #24 0x in ?? () ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- Options on screen are mixed up https://bugs.launchpad.net/bugs/1163740 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1661629] Re: upgrade of kernel fails with mkinitramfs: failed to determine device for /
> It might be easier to resolve this by considering this as "mkinitramfs
fails on ZFS root without /etc/fstab lines for the ZFS filesystems when
MODULES=dep is used".
Yes, that sounds like an accurate summary. I'm not sure I follow how
/etc/fstab is related, though. Looking briefly through mkinitramfs, I
don't see where that is being used.
> Could you perhaps see if you can remove kdump-tools from the equation
like this?
Good idea. Here is a more minimal way to reproduce the issue: with ZFS on root
- set 'MODULES=dep' in '/etc/initramfs-tools/initramfs.conf'
- run 'sudo update-initramfs -u'
Below is an updated patch, which finds and adds the module for each
device in the zfs pool containing the root filesystem. I've tested the
patch on Bionic and Cosmic with both zfs and ext4 root filesystems. Note
that I wasn't entirely sure if we need to handle the case where
'dev_node' is /dev/root. I'm not familiar with that setup, so I'm not
sure whether that could even apply when using zfs on root.
--- hook-functions 2018-07-10 22:19:18.489142772 +
+++ /usr/share/initramfs-tools/hook-functions 2018-07-10 22:06:43.969661842
+
@@ -357,6 +357,21 @@
return
fi
+ if [ "${FSTYPE}" = "zfs" ]; then
+ manual_add_modules "${FSTYPE}"
+
+ # ZFS uses the name of a filesystem instead of a device. Find
+ # the devices that make up the pool containing the specified
+ # filesystem, and add the appropriate driver for each device.
+ local poolname="${dev_node%%/*}"
+ zpool list -vPL "$poolname" | while read dev ignored; do
+ # Ignore non-leaf vdevs by skipping anything that
doesn't
+ # look like an absolute path
+ echo "$dev" | grep -q '^/' && block_dev_mod_add "$dev"
+ done
+ return
+ fi
+
if [ "$dir" = / ] && [ "${dev_node}" = "/dev/root" ] ; then
if [ -b "${dev_node}" ]; then
# Match it to the canonical device name by UUID
--
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/1661629
Title:
upgrade of kernel fails with mkinitramfs: failed to determine device
for /
Status in initramfs-tools package in Ubuntu:
Confirmed
Bug description:
When upgrading packages with "apt upgrade" on Ubuntu 16.04.1 LTS with
root on ZFS I get this error:
Setting up linux-image-4.4.0-59-generic (4.4.0-59.80) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-59-generic
/boot/vmlinuz-4.4.0-59-generic
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-59-generic
/boot/vmlinuz-4.4.0-59-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-59-generic
run-parts: executing /etc/kernel/postinst.d/kdump-tools 4.4.0-59-generic
/boot/vmlinuz-4.4.0-59-generic
kdump-tools: Generating /var/lib/kdump/initrd.img-4.4.0-59-generic
mkinitramfs: failed to determine device for /
mkinitramfs: workaround is MODULES=most, check:
grep -r MODULES /etc/initramfs-tools/
Error please report bug on initramfs-tools
Include the output of 'mount' and 'cat /proc/mounts'
update-initramfs: failed for with 1.
run-parts: /etc/kernel/postinst.d/kdump-tools exited with return code 1
Failed to process /etc/kernel/postinst.d at
/var/lib/dpkg/info/linux-image-4.4.0-59-generic.postinst line 1052.
dpkg: error processing package linux-image-4.4.0-59-generic (--configure):
subprocess installed post-installation script returned error exit status 2
version of initramfs-tools is 0.122ubuntu8.8
Output of mount is:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs
(rw,nosuid,relatime,size=8066020k,nr_inodes=2016505,mode=755)
devpts on /dev/pts type devpts
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1623576k,mode=755)
rpool/ROOT/ubuntu on / type zfs (rw,relatime,xattr,noacl)
securityfs on /sys/kernel/security type securityfs
(rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup
(rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/freezer type cgroup
(rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/blkio type cgroup
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Changed in: wokkel (Ubuntu) Status: New => In Progress ** Changed in: wokkel (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Also affects: syslog-ng-incubator (Ubuntu) Importance: Undecided Status: New ** Changed in: syslog-ng-incubator (Ubuntu) Status: New => In Progress ** Changed in: syslog-ng-incubator (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: In Progress Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: In Progress Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: In Progress Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in
[Touch-packages] [Bug 1163740] Re: Options on screen are mixed up
** Project changed: apport => apport (Ubuntu) -- 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/1163740 Title: Options on screen are mixed up Status in apport package in Ubuntu: New Bug description: To reproduce: 1. start "ubuntu-bug" from the console (without any options) 2. A new window "Apport" will open (I'm on KDE if that matters) 3. Select "Security related problems" and click "OK" 4. Select "Other problem" and click "OK" I now get the message: "This is expected as there is no "tty" allocated when running commands directly via ssh. ..." It seems like options on the screen don't match the code executed. It's as if someone reordered the options on screen without updating the code that processes the selections. To add insult to injury, the app crashes when I click on "OK": Application: Apport KDE (python3.2mu), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [KCrash Handler] #6 QWidget::~QWidget (this=0xb6dae0, __in_chrg=) at kernel/qwidget.cpp:1630 #7 0x7fc3cfba1759 in ?? () from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so #8 0x7fc3cfb95976 in ?? () from /usr/lib/python3/dist-packages/PyQt4/QtGui.cpython-32mu.so #9 0x7fc3d0011cd4 in ?? () from /usr/lib/python3/dist-packages/sip.cpython-32mu.so #10 0x7fc3d00135b9 in ?? () from /usr/lib/python3/dist-packages/sip.cpython-32mu.so #11 0x0046e617 in ?? () #12 0x004d6ff9 in ?? () #13 0x0046e6af in ?? () #14 0x004cb403 in ?? () #15 0x004cb4b7 in PyDict_SetItem () #16 0x0049a924 in _PyModule_Clear () #17 0x0050a864 in PyImport_Cleanup () #18 0x0041b95c in Py_Finalize () #19 0x0041ba32 in Py_Exit () #20 0x0042c35f in ?? () #21 0x0087e9e0 in ?? () #22 0x00b00fb0 in ?? () #23 0x008bb960 in ?? () #24 0x in ?? () To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1163740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: django-countries (Ubuntu) Importance: Undecided Status: New ** Changed in: django-countries (Ubuntu) Status: New => In Progress ** Changed in: django-countries (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: In Progress Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: In Progress Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: In Progress Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: In Progress Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: In Progress Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in
[Touch-packages] [Bug 1781294] [NEW] no sound but system recognizes integrated sound card on laptop
Public bug reported: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32, IRQ 131 Memory at dc228000 (64-bit, non-prefetchable) [size=16K] Memory at dc20 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel, snd_soc_skl Sound settings still only list dummy output. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME Date: Wed Jul 11 18:44:06 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 InstallationDate: Installed on 2017-05-11 (426 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to bionic on 2018-07-11 (0 days ago) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.name: 01KT0M dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn01KT0M:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9360 dmi.sys.vendor: Dell Inc. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1781294 Title: no sound but system recognizes integrated sound card on laptop Status in pulseaudio package in Ubuntu: New Bug description: This is 18.04 LTS but also occurred in 16.04 LTS. I have gone through the troubleshooting steps here: https://help.ubuntu.com/community/SoundTroubleshooting and have included some output of those diagnostic steps below: $ sudo aplay -l aplay: device_list:270: no soundcards found... $ find /lib/modules/`uname -r` | grep snd /lib/modules/4.15.0-23-generic/kernel/sound/synth/emux/snd-emux-synth.ko /lib/modules/4.15.0-23-generic/kernel/sound/synth/snd-util-mem.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/pcsp/snd-pcsp.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/mpu401/snd-mpu401-uart.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mtpav.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-mts64.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/vx/snd-vx-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/snd-aloop.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-lib.ko /lib/modules/4.15.0-23-generic/kernel/sound/drivers/opl3/snd-opl3-synth.ko ...and lots more $ lspci -v | grep -A7 -i "audio" 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) (prog-if 80) Subsystem: Dell Sunrise Point-LP HD Audio Flags: bus master, fast devsel, latency 32,
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: wokkel (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: In Progress Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: In Progress Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick source package in Bionic: Fix Released Bug description: This is a bug collecting all remaining packages that need to be converted to noawait in xenial or bionic. [Impact] "await" triggers are run before a package is configured. If B activates A, then A's trigger code in the postinst must be run before A can be
[Touch-packages] [Bug 1780996] Re: Convert triggers to noawait
** Also affects: ltsp (Ubuntu) Importance: Undecided Status: New ** Changed in: ltsp (Ubuntu) Status: New => In Progress ** Changed in: ltsp (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1780996 Title: Convert triggers to noawait Status in appstream package in Ubuntu: Fix Released Status in bumblebee package in Ubuntu: In Progress Status in clutter-imcontext package in Ubuntu: Triaged Status in django-countries package in Ubuntu: In Progress Status in dochelp package in Ubuntu: Fix Released Status in dovecot package in Ubuntu: Fix Released Status in fusiondirectory package in Ubuntu: New Status in gdk-pixbuf package in Ubuntu: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Status in gosa package in Ubuntu: In Progress Status in guile-2.0 package in Ubuntu: New Status in hicolor-icon-theme package in Ubuntu: Fix Released Status in libomxil-bellagio package in Ubuntu: New Status in libreoffice package in Ubuntu: Fix Released Status in ltsp package in Ubuntu: In Progress Status in mate-icon-theme package in Ubuntu: Fix Released Status in maxima package in Ubuntu: In Progress Status in neurodebian package in Ubuntu: In Progress Status in nevow package in Ubuntu: In Progress Status in octave package in Ubuntu: Fix Released Status in packagekit package in Ubuntu: Fix Released Status in pike7.8 package in Ubuntu: New Status in pike8.0 package in Ubuntu: New Status in postgresql-common package in Ubuntu: Fix Released Status in qgis package in Ubuntu: In Progress Status in reconf-inetd package in Ubuntu: New Status in shared-mime-info package in Ubuntu: Fix Released Status in sphinx package in Ubuntu: Fix Released Status in syslog-ng-incubator package in Ubuntu: In Progress Status in tex-common package in Ubuntu: Fix Released Status in wokkel package in Ubuntu: In Progress Status in xpdf package in Ubuntu: Fix Released Status in yorick package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in clutter-imcontext source package in Xenial: Won't Fix Status in dochelp source package in Xenial: In Progress Status in dovecot source package in Xenial: In Progress Status in fusiondirectory source package in Xenial: New Status in gdk-pixbuf source package in Xenial: In Progress Status in glib2.0 source package in Xenial: In Progress Status in gosa source package in Xenial: New Status in guile-2.0 source package in Xenial: New Status in hicolor-icon-theme source package in Xenial: In Progress Status in libomxil-bellagio source package in Xenial: New Status in libreoffice source package in Xenial: Triaged Status in mate-icon-theme source package in Xenial: In Progress Status in octave source package in Xenial: In Progress Status in packagekit source package in Xenial: In Progress Status in pike7.8 source package in Xenial: New Status in pike8.0 source package in Xenial: New Status in postgresql-common source package in Xenial: In Progress Status in reconf-inetd source package in Xenial: New Status in shared-mime-info source package in Xenial: In Progress Status in sphinx source package in Xenial: In Progress Status in tex-common source package in Xenial: In Progress Status in xpdf source package in Xenial: In Progress Status in yorick source package in Xenial: In Progress Status in appstream source package in Bionic: Fix Released Status in clutter-imcontext source package in Bionic: Won't Fix Status in dochelp source package in Bionic: Fix Released Status in dovecot source package in Bionic: Fix Released Status in fusiondirectory source package in Bionic: New Status in gdk-pixbuf source package in Bionic: Fix Released Status in glib2.0 source package in Bionic: Fix Released Status in gosa source package in Bionic: New Status in guile-2.0 source package in Bionic: New Status in hicolor-icon-theme source package in Bionic: Fix Released Status in libomxil-bellagio source package in Bionic: New Status in libreoffice source package in Bionic: Fix Released Status in mate-icon-theme source package in Bionic: Fix Released Status in octave source package in Bionic: Fix Released Status in packagekit source package in Bionic: Fix Released Status in pike7.8 source package in Bionic: New Status in pike8.0 source package in Bionic: New Status in postgresql-common source package in Bionic: Fix Released Status in reconf-inetd source package in Bionic: New Status in shared-mime-info source package in Bionic: Fix Released Status in sphinx source package in Bionic: Fix Released Status in tex-common source package in Bionic: Fix Released Status in xpdf source package in Bionic: Fix Released Status in yorick
