[Touch-packages] [Bug 1798579] Re: GUI Graphics are not working and touchpad is also not working
your machine is an intel/radeon hybrid, yet you have the nvidia drivers installed... DkmsStatus: nvidia, 390.87, 4.15.0-36-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3964] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] ** Changed in: xorg (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1798579 Title: GUI Graphics are not working and touchpad is also not working Status in xorg package in Ubuntu: Invalid Bug description: It has Intel Graphics Driver but still display is not fine. Touchpad drivers are also available but it is also not working. Although external mouse is working fine. Version- Ubuntu 18.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 16:46:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3964] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [17aa:3964] InstallationDate: Installed on 2018-10-16 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:58ea Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 062a:413e Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=773e1eb0-580f-49a5-ab82-20f86c99e160 ro i8042.reset quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 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/xorg/+bug/1798579/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798725] [NEW] Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=
*** This bug is a security vulnerability *** Public security bug reported: Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases ** Affects: pcre3 (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "PoC from upstream bug report" https://bugs.launchpad.net/bugs/1798725/+attachment/5202814/+files/PoC_pcre_gnome.zip -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcre3 in Ubuntu. https://bugs.launchpad.net/bugs/1798725 Title: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*= Status in pcre3 package in Ubuntu: Confirmed Bug description: Reported upstream at https://bugs.exim.org/show_bug.cgi?id=2330 - libpcre3 can be made to crash when matching the pattern \s*= when the context is n\xff= Able to reproduce on current Bionic using the PoC attached (which is copied directly from the upstream bug report) - in a fresh Bionic VM: $ sudo apt install build-essential libgtk2.0-dev $ cd PCRE_PoC $ ./compilePoC.sh $ ./PoC Content: --- n�= --- Pattern: --- \s*= - Segmentation fault (core dumped) Haven't yet tested the second PoC via an external disk autorun.inf and gvfs-udisks2-volume-monitor. Also haven't tested in Cosmic / older releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1798725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798687] Re: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal
Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your log files attached to this bug report it seems that a package failed to install due to a segmentation fault in the application being used for the package installation process. Unfortunately, this bug report isn't very useful in its current state and a crash report would be much more useful. Could you try recreating this issue by enabling apport to catch the crash report 'sudo service apport start force_start=1' and then trying to install the same package again? This process will create a new bug report so I am marking this one as Invalid. Thanks again for helping out! [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: package-install-segfault ** Changed in: fonts-arphic-ukai (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-arphic-ukai in Ubuntu. https://bugs.launchpad.net/bugs/1798687 Title: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped Status in fonts-arphic-ukai package in Ubuntu: Invalid Bug description: fonts-arphic-ukai ProblemType: Package DistroRelease: Ubuntu 18.10 Package: fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 01:30:30 2018 Dependencies: DuplicateSignature: package:fonts-arphic-ukai:0.2.20080216.2-4ubuntu2 Removing fonts-arphic-ukai (0.2.20080216.2-4ubuntu2) ... double free or corruption (!prev) dpkg: error processing package fonts-arphic-ukai (--remove): installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped ErrorMessage: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: fonts-arphic-ukai Title: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1798687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798712] Re: No sound (18.10 Cosmic)
Also, here's the output of `alsa-info.sh`: http://www.alsa- project.org/db/?f=a328206d40f67c3777f6366514f1a991335d47fc -- 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/1798712 Title: No sound (18.10 Cosmic) Status in pulseaudio package in Ubuntu: New Bug description: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798712] [NEW] No sound (18.10 Cosmic)
Public bug reported: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1798712 Title: No sound (18.10 Cosmic) Status in pulseaudio package in Ubuntu: New Bug description: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798712] Re: No sound (18.10 Cosmic)
** Description changed: - Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. -- 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/1798712 Title: No sound (18.10 Cosmic) Status in pulseaudio package in Ubuntu: New Bug description: Installed: 1:12.2-0ubuntu4 I'm getting no sound on boot after upgrade. I tried killing the currently running pulseaudio daemon, then starting it with `-`, here's what happens: `~$ pulseaudio - I: [pulseaudio] main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operation not permitted I: [pulseaudio] main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operation not permitted D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.` Although this appears in the terminal, there's still no sound in the settings menu, or in pavucontrol. alsamixer runs just fine, showing that alsa is working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1798712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1738153] Re: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial
Verified fixed on DP/N BRM5-DVT1-C2H with xenial-proposed Image: dell-bto-xenial-breckenridge-mlk-cfl-X46-20180705-128.iso There's also one thing to mention; it has to reboot twice before the fix to take effect. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1738153 Title: need backport the new scancode of dell-wmi for Microphone mute hotkey to xenial Status in OEM Priority Project: Confirmed Status in OEM Priority Project xenial series: Confirmed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in systemd source package in Artful: Won't Fix Bug description: [Impact] dell-wmi expend the scan code of Microphone mute hotkey from 0x150 to 0x100150, so need to add a new mapping for it. related commit: https://github.com/systemd/systemd/pull/5012 [Test Case] 1. install the udev package which applied patch. 2. check if Microphone mute hotkey works. 3. if it not works, please provide the log of evtest. [Regression Potential] low regression potential, because it just add one more mapping. also affect: LP: #1736352 LP: #1740080 LP: #1734609 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1738153/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
for an Explanation of the problem, and a work around see: https://github.com/GitTools/GitVersion/issues/1508 the problem started with libcurl3 having an incorrect symlink named: 'libcurl.so.4' ** Bug watch added: github.com/GitTools/GitVersion/issues #1508 https://github.com/GitTools/GitVersion/issues/1508 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to curl in Ubuntu. https://bugs.launchpad.net/bugs/1754294 Title: After last updated libcurl3 on libcurl4, some apps are removed. Status in curl package in Ubuntu: Confirmed Bug description: Hi! After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) deleted such applications as: virtualbox-5.2 opera-stable slack-desktop mongodb I really need these applications, I installed them with broken dependencies, but they are deleted after each update. Is it possible to make the dependence of the libcurl3 in libcurl4, and not remove it altogether from system? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798700] Re: ftbfs on arm64
** Also affects: elfutils (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1798700 Title: ftbfs on arm64 Status in elfutils package in Ubuntu: New Status in elfutils source package in Cosmic: New Bug description: [impact] elfutils ftbfs on sid on arm64 currently: FAIL: run-backtrace-dwarf.sh 0xb3c5373craise 0xb3c418e8abort /<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null) dwarf: no main FAIL run-backtrace-dwarf.sh (exit status: 1) FAIL: run-deleted.sh PID 19405 - process TID 19405: #0 0x81e7f3e0 __nanosleep #1 0x81e7f2c0 sleep /<>/src/stack: dwfl_thread_getframes tid 19405 at 0x81e7f2bf in /lib/aarch64-linux-gnu/libc-2.28.so: (null) FAIL run-deleted.sh (exit status: 1) Current git passes, and git bisect and logic point to the following upstream commit as fixing it: commit f881459ffc95b6fad51aa055a158ee14814073aa Author: Mark Wielaard Date: Wed Apr 11 10:37:45 2018 +0200 aarch64: Add default cfi rule to restore SP from CFA address. The CFA is set by default to the stack pointer of the previous frame. So that is also how we can always restore the SP. This default aarch64 CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh and run-backtrace-dwarf.sh testcases work. Signed-off-by: Mark Wielaard Debugging the test failure made it clear that the libdw1 in the archive will not be able to successfully walk the stack of processes built by gcc-8, i.e. this is a regression in runtime functionality. I don't know if any of the revdeps of libdw1 depend on this but it seems at least possible and the patch to fix all this is pretty simple so my inclination is that this meets the threshold for an SRU. [test case] Build the package on arm64. [regression potential] The patch is small, fairly (given the general level of hairiness around here) simple and only affects the functionality that is currently broken. There's always the chance that building with a new toolchain will introduce new problems, but there's not much we can do about that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1798700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798700] [NEW] ftbfs on arm64
Public bug reported: [impact] elfutils ftbfs on sid on arm64 currently: FAIL: run-backtrace-dwarf.sh 0xb3c5373c raise 0xb3c418e8 abort /<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null) dwarf: no main FAIL run-backtrace-dwarf.sh (exit status: 1) FAIL: run-deleted.sh PID 19405 - process TID 19405: #0 0x81e7f3e0 __nanosleep #1 0x81e7f2c0 sleep /<>/src/stack: dwfl_thread_getframes tid 19405 at 0x81e7f2bf in /lib/aarch64-linux-gnu/libc-2.28.so: (null) FAIL run-deleted.sh (exit status: 1) Current git passes, and git bisect and logic point to the following upstream commit as fixing it: commit f881459ffc95b6fad51aa055a158ee14814073aa Author: Mark Wielaard Date: Wed Apr 11 10:37:45 2018 +0200 aarch64: Add default cfi rule to restore SP from CFA address. The CFA is set by default to the stack pointer of the previous frame. So that is also how we can always restore the SP. This default aarch64 CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh and run-backtrace-dwarf.sh testcases work. Signed-off-by: Mark Wielaard Debugging the test failure made it clear that the libdw1 in the archive will not be able to successfully walk the stack of processes built by gcc-8, i.e. this is a regression in runtime functionality. I don't know if any of the revdeps of libdw1 depend on this but it seems at least possible and the patch to fix all this is pretty simple so my inclination is that this meets the threshold for an SRU. [test case] Build the package on arm64. [regression potential] The patch is small, fairly (given the general level of hairiness around here) simple and only affects the functionality that is currently broken. There's always the chance that building with a new toolchain will introduce new problems, but there's not much we can do about that. ** Affects: elfutils (Ubuntu) Importance: Undecided Status: New ** Affects: elfutils (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to elfutils in Ubuntu. https://bugs.launchpad.net/bugs/1798700 Title: ftbfs on arm64 Status in elfutils package in Ubuntu: New Status in elfutils source package in Cosmic: New Bug description: [impact] elfutils ftbfs on sid on arm64 currently: FAIL: run-backtrace-dwarf.sh 0xb3c5373craise 0xb3c418e8abort /<>/tests/backtrace-dwarf: dwfl_thread_getframes: (null) dwarf: no main FAIL run-backtrace-dwarf.sh (exit status: 1) FAIL: run-deleted.sh PID 19405 - process TID 19405: #0 0x81e7f3e0 __nanosleep #1 0x81e7f2c0 sleep /<>/src/stack: dwfl_thread_getframes tid 19405 at 0x81e7f2bf in /lib/aarch64-linux-gnu/libc-2.28.so: (null) FAIL run-deleted.sh (exit status: 1) Current git passes, and git bisect and logic point to the following upstream commit as fixing it: commit f881459ffc95b6fad51aa055a158ee14814073aa Author: Mark Wielaard Date: Wed Apr 11 10:37:45 2018 +0200 aarch64: Add default cfi rule to restore SP from CFA address. The CFA is set by default to the stack pointer of the previous frame. So that is also how we can always restore the SP. This default aarch64 CFI rule is necessary on Fedora 28 with GCC8 to make the run-deleted.sh and run-backtrace-dwarf.sh testcases work. Signed-off-by: Mark Wielaard Debugging the test failure made it clear that the libdw1 in the archive will not be able to successfully walk the stack of processes built by gcc-8, i.e. this is a regression in runtime functionality. I don't know if any of the revdeps of libdw1 depend on this but it seems at least possible and the patch to fix all this is pretty simple so my inclination is that this meets the threshold for an SRU. [test case] Build the package on arm64. [regression potential] The patch is small, fairly (given the general level of hairiness around here) simple and only affects the functionality that is currently broken. There's always the chance that building with a new toolchain will introduce new problems, but there's not much we can do about that. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1798700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798687] [NEW] package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signa
Public bug reported: fonts-arphic-ukai ProblemType: Package DistroRelease: Ubuntu 18.10 Package: fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 01:30:30 2018 Dependencies: DuplicateSignature: package:fonts-arphic-ukai:0.2.20080216.2-4ubuntu2 Removing fonts-arphic-ukai (0.2.20080216.2-4ubuntu2) ... double free or corruption (!prev) dpkg: error processing package fonts-arphic-ukai (--remove): installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped ErrorMessage: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: fonts-arphic-ukai Title: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: fonts-arphic-ukai (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package cosmic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-arphic-ukai in Ubuntu. https://bugs.launchpad.net/bugs/1798687 Title: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped Status in fonts-arphic-ukai package in Ubuntu: New Bug description: fonts-arphic-ukai ProblemType: Package DistroRelease: Ubuntu 18.10 Package: fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 01:30:30 2018 Dependencies: DuplicateSignature: package:fonts-arphic-ukai:0.2.20080216.2-4ubuntu2 Removing fonts-arphic-ukai (0.2.20080216.2-4ubuntu2) ... double free or corruption (!prev) dpkg: error processing package fonts-arphic-ukai (--remove): installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped ErrorMessage: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: fonts-arphic-ukai Title: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1798687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798687] Re: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to fonts-arphic-ukai in Ubuntu. https://bugs.launchpad.net/bugs/1798687 Title: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped Status in fonts-arphic-ukai package in Ubuntu: New Bug description: fonts-arphic-ukai ProblemType: Package DistroRelease: Ubuntu 18.10 Package: fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Fri Oct 19 01:30:30 2018 Dependencies: DuplicateSignature: package:fonts-arphic-ukai:0.2.20080216.2-4ubuntu2 Removing fonts-arphic-ukai (0.2.20080216.2-4ubuntu2) ... double free or corruption (!prev) dpkg: error processing package fonts-arphic-ukai (--remove): installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped ErrorMessage: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 3.6.6-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.0.5ubuntu5 apt 1.7.0 SourcePackage: fonts-arphic-ukai Title: package fonts-arphic-ukai 0.2.20080216.2-4ubuntu2 failed to install/upgrade: installed fonts-arphic-ukai package post-removal script subprocess was killed by signal (Aborted), core dumped UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-arphic-ukai/+bug/1798687/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798656] Re: gtk3 frontend gives no widget for answering a boolean prompt
Test package noisy-fake-driver from https://launchpad.net/~vorlon/+archive/ubuntu/debconf-tests/+packages does not reproduce the problem in an upgraded cosmic environment. dpkg-reconfigure docker.io also does not reproduce the original problem. Either the problem was present in bionic and fixed in cosmic; or it is a consequence of the debconf frontend being started up in the middle of the release upgrade and having a somehow incoherent filesystem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1798656 Title: gtk3 frontend gives no widget for answering a boolean prompt Status in debconf package in Ubuntu: New Bug description: On upgrade from bionic to cosmic with update-manager, I was shown a debconf prompt about docker.io that asked: Automatically restart Docker daemon? There was no widget in the window that allowed me to select either yes or no. This is a grave deficiency in the default debconf frontend on the Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"
The issue described in this bug, failure to shut down due to a 'Wait for Network' job, is believed to be resolved in the Ubuntu 18.04 final release and in later releases. I am therefore closing this bug. If someone can reproduce this failure with a currently-supported release image, please reopen the bug report. If you are having difficulty shutting down after a live session with a different symptom, please open a separate bug report for that bug. ** Changed in: systemd (Ubuntu) Status: Confirmed => Invalid ** Changed in: casper (Ubuntu) Status: New => Invalid ** Changed in: casper (Ubuntu Bionic) Status: New => Invalid -- 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/1706939 Title: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)" Status in Release Notes for Ubuntu: Fix Released Status in casper package in Ubuntu: Invalid Status in gdm3 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in casper source package in Bionic: Invalid Status in gdm3 source package in Bionic: Invalid Bug description: Test case: Boot to live session using current or recent image Attempt to restart, shutdown or even log out. Hangs basically forever with: [ *** ] (2 of 2) A start job is running for Hold until boot process finishes up (21s / no limit) or [ *** ] (2 of 2) A start job is running for Wait for Network to be Configured (21s / no limit) --- ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gdm3 3.24.2-1ubuntu9 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 CasperVersion: 1.384 CurrentDesktop: GNOME Date: Thu Jul 27 10:15:57 2017 LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1551623] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
gconf2 broke my 18.04 -> 18.10 upgrade with dpkg: dependency problems prevent processing triggers for gconf2: gconf2 priklauso nuo psmisc; tačiau: Paketas psmisc dar nekonfigūruotas. dpkg: klaida, apdorojant paketą gconf2 (--configure): dependency problems - leaving triggers unprocessed in a loop until dpkg gave up. Perhaps this is another instance of bug 1780996? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1551623 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: When upgrading from 15.10 to 16.04Beta (2016-03-01), this error occured, alongside many others related to systemd and gnome. Notice that despite all warnings and errors, finally, the system remained functional. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2 Uname: Linux 4.4.0-8-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 Date: Tue Mar 1 09:21:15 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2015-10-04 (148 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151002) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.3 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-03-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1551623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
Found this lkml thread for other issues related to this change. It seems the effort to run it down fizzled. What would be the best way to tie this to that to hopefully raise visibility / priority? https://lkml.org/lkml/2018/4/6/221 -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU
and here is the commit that adds these events that are causing us such issues on the Dell hardware: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=1455cf8dbfd06aa7651dcfccbadb7a093944ca65 -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta: [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf 2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797714] Re: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta
I just 'resolved' that issue myself by removing the package timidity - it seems this program exclusively used the audio hardware. If there is a issue, it is with this package. -- 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/1797714 Title: [Dell Studio 1557] No sound after upgrade to Kubuntu 18.10 beta Status in pulseaudio package in Ubuntu: New Bug description: I upgraded from Kubuntu 18.04 to 18.10 beta today, and I noticed I don't have sounds. The UI only shows a 'Dummy Device'. After doing a 'sudo alsa force-reload', KDE shows the audio device. When I execute alsamixer in a shell before executing the force-reload, the audio card is shown. My hardware: (from lspci) 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: pulseaudio 1:12.2-0ubuntu4 Uname: Linux 4.19.0-041900rc6-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: juergen8924 F pulseaudio /dev/snd/controlC1: juergen8924 F pulseaudio CurrentDesktop: KDE Date: Sat Oct 13 21:07:53 2018 InstallationDate: Installed on 2015-02-16 (1334 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) SourcePackage: pulseaudio UpgradeStatus: Upgraded to cosmic on 2018-10-13 (0 days ago) dmi.bios.date: 10/06/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 0KM426 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd10/06/2009:svnDellInc.:pnStudio1557:pvrA02:rvnDellInc.:rn0KM426:rvrA02:cvnDellInc.:ct8:cvrA02: dmi.product.name: Studio 1557 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743216] Re: perl crashed with SIGABRT in _dbus_abort()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: perl (Ubuntu Bionic) Status: New => Confirmed -- 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/1743216 Title: perl crashed with SIGABRT in _dbus_abort() Status in perl package in Ubuntu: Invalid Status in xdg-utils package in Ubuntu: Fix Released Status in perl source package in Bionic: Confirmed Status in xdg-utils source package in Bionic: Fix Committed Status in perl source package in Cosmic: Invalid Status in xdg-utils source package in Cosmic: Fix Released Status in xdg-utils package in Debian: Unknown Bug description: [ Description ] When xdg-screensaver suspend refers to a window with invalid UTF-8 in its title, it will spawn a perl process that crashes with an assertion: dbus[19455]: arguments to dbus_message_iter_append_basic() were incorrect, assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file ../../../dbus/dbus-message.c line 2754. This is normally a bug in some application using the D-Bus library. [ Fix ] Use decode() from the Encode module to replace invalid character sequences with U+FFFD, the replacement symbol. This is not a new dependency as Encode has been a perl core module since 5.8. [ QA ] I don't know how to get a window with such a title, so we can do two things. 1) 1. $ sudo -e $(which xdg-screensaver) # hack the script 2. Find the line "# Inhibit idle detection (flags = 8) with window name and ID." 3. Find the } on its own above that. Insert a new line afterwards and set the window name to be the same as the one in this bug, by pasting the code $window_name = "\253\062\065 Meter fehlten bis zur Katastrophe\273 - News Panorama: Vermischtes - tagesanzeiger.ch - Mozilla Firefox"; 4. Save and exit 5. $ xwininfo 6. click some window, and copy the "Window id", which will be 0x 7. $ xdg-screensaver suspend In the bad case (before this bug is fixed) it should crash, and in the good case it should work. 8. Undo what you just did by running $ xdg-screensaver resume 2) Observe that the error bucket https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 has a reduction in report rate with the new versions. [ Regression potential ] If the code is bad then the window name passed to Inhibit() could be wrong. That shouldn't matter too much. If it is really bad then the program might crash for everybody and we'll see an increase in errors. [ Original description ] Errors Bucket - https://errors.ubuntu.com/problem/b386f287972198daca290969b0ea5182ce8e5d52 crashed after launching the software updater ProblemType: CrashDistroRelease: Ubuntu 18.04 Package: perl-base 5.26.1-4 ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12 Uname: Linux 4.14.0-16-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jan 14 13:30:52 2018 ExecutablePath: /usr/bin/perl InstallationDate: Installed on 2017-12-28 (17 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171201) Signal: 6SourcePackage: perl StacktraceTop: _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3 _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_message_iter_append_basic () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () from /usr/lib/x86_64-linux-gnu/perl5/5.26/auto/Net/DBus/DBus.so Perl_pp_entersub () Title: perl crashed with SIGABRT in _dbus_abort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/perl/+bug/1743216/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798656] [NEW] gtk3 frontend gives no widget for answering a boolean prompt
Public bug reported: On upgrade from bionic to cosmic with update-manager, I was shown a debconf prompt about docker.io that asked: Automatically restart Docker daemon? There was no widget in the window that allowed me to select either yes or no. This is a grave deficiency in the default debconf frontend on the Ubuntu desktop. ** Affects: debconf (Ubuntu) Importance: Critical Status: New ** Changed in: debconf (Ubuntu) Importance: Undecided => Critical ** Summary changed: - gnome frontend gives no widget for answering a boolean prompt + gtk3 frontend gives no widget for answering a boolean prompt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1798656 Title: gtk3 frontend gives no widget for answering a boolean prompt Status in debconf package in Ubuntu: New Bug description: On upgrade from bionic to cosmic with update-manager, I was shown a debconf prompt about docker.io that asked: Automatically restart Docker daemon? There was no widget in the window that allowed me to select either yes or no. This is a grave deficiency in the default debconf frontend on the Ubuntu desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798657] [NEW] gtk3 frontend 'help' window is huge and not resizeable
Public bug reported: If I click on 'help' on a debconf question when using the gtk3 frontend, I get a huge window with a 'close' button in the bottom right corner and a small amount of text in the middle of the screen. The window can be resized horizontally, but not vertically. ** Affects: debconf (Ubuntu) Importance: Medium Status: New ** Changed in: debconf (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1798657 Title: gtk3 frontend 'help' window is huge and not resizeable Status in debconf package in Ubuntu: New Bug description: If I click on 'help' on a debconf question when using the gtk3 frontend, I get a huge window with a 'close' button in the bottom right corner and a small amount of text in the middle of the screen. The window can be resized horizontally, but not vertically. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules
** Bug watch added: Debian Bug tracker #909163 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909163 ** Also affects: ufw (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909163 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ufw in Ubuntu. https://bugs.launchpad.net/bugs/1368411 Title: Cannot insert IPV6 rule before IPV4 rules Status in ufw: New Status in ufw package in Ubuntu: Confirmed Status in ufw package in Debian: Unknown Bug description: I am unable to insert any rules concerning IPV6 before IPV4 rules. Thus, when IPV4 rules are numbered 1 to 5 and IPV6 rules are numbered 6 to 10, the following command: [code] ufw insert 1 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] errors with "ERROR: Invalid position '1'". However, the command [code] ufw insert 6 deny from 2a02:2210:12:a:b820:fff:fea2:25d1 [/code] succeeds. In my case, this poses a problem, since I am trying to insert rules from a script against brute force attacks. The script needs to insert blocking rules before a number of other rules that open up some ports (since the order of rules is important in ufw). However since the number of IPV4 rules will be changing all the time, the position of the first available number for an IPV6 address is hard to determine. Proposed solution: either allow IPV6 rules to precede IPV4 rules, or implement a keyword defining the first available position; e.g. "ufw insert first deny from 2a02:2210:12:a:b820:fff:fea2:25d1". BTW: this was all figured out with ufw version 0.31.1-1, Ubuntu 12.04.5 LTS, To manage notifications about this bug go to: https://bugs.launchpad.net/ufw/+bug/1368411/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1573720] Re: Unencrypted private keys are insecure error reported even when key is encrypted
I found another workaround. I used "nm-connection-editor" in order to configure the connection $ sudo nm-connection-editor -- 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/1573720 Title: Unencrypted private keys are insecure error reported even when key is encrypted Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Triaged Bug description: When I enter an EAP-TLS wifi config, I get the error: "Unencrypted private keys are insecure The selected private key does not appear to be protected by a password. This could allow your security credentials to be compromised. Please select a password-protected private key. (You can password-protect your private key with openssl)" I have verified that my key is, in fact, encrypted, and I have tried using both des3 and aes256. I have also verified the password used to encrypt the key. For a while, it wouldn't even let me save the config. I managed to save it eventually, but now when I try to connect to the saved connection, I get the same error. I am on Ubuntu mate 16.04 network-manager 1.1.93 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Apr 22 13:25:16 2016 InstallationDate: Installed on 2015-08-19 (246 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) IpRoute: default via 192.168.151.254 dev eth1 proto static metric 100 169.254.0.0/16 dev eth1 scope link metric 1000 192.168.151.0/24 dev eth1 proto kernel scope link src 192.168.151.95 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 ed50d4f9-c810-4be0-b06c-8acd58015c50 /org/freedesktop/NetworkManager/ActiveConnection/0 wlan0 wifi disconnected /org/freedesktop/NetworkManager/Devices/1 -- ---- eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- ---- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1573720/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781794] Re: package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4
using external ppa ** Changed in: libdrm (Ubuntu) Status: New => Invalid -- 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/1781794 Title: package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.89+git1801130630.fd9bcb~oibaf~x Status in libdrm package in Ubuntu: Invalid Bug description: Nil ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common (not installed) ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic i686 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sun Jul 15 18:38:39 2018 DuplicateSignature: package:libdrm-common:(not installed) Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.89+git1801130630.fd9bcb~oibaf~x ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.89+git1801130630.fd9bcb~oibaf~x InstallationDate: Installed on 2017-10-13 (275 days ago) InstallationMedia: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: libdrm Title: package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.89+git1801130630.fd9bcb~oibaf~x UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1781794/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781111] Re: libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~
using external ppa ** Changed in: libdrm (Ubuntu) Status: New => Invalid -- 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/178 Title: libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 Status in libdrm package in Ubuntu: Invalid Bug description: DRM package needed this lib, I installed it and DRM install proceeded successfuly ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common 2.4.91-2~16.04.1 Uname: Linux 4.14.0-041400-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 Date: Fri Jul 6 19:18:35 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgTerminalLog: Preparing to unpack .../libdrm-common_2.4.91-2~16.04.1_all.deb ... Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 DuplicateSignature: package:libdrm-common:2.4.91-2~16.04.1 Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 GraphicsCard: NVIDIA Corporation G94GLM [Quadro FX 2700M] [10de:063a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company G94GLM [Quadro FX 2700M] [103c:30ec] InstallationDate: Installed on 2017-08-06 (338 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Hewlett-Packard HP EliteBook 8730w PackageArchitecture: all PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-041400-generic root=/dev/mapper/ubuntu--vg-root ro acpi_osi=Linux pcie_aspm=force acpi_enforce_resources=lax intel_iommu=igfx_off quiet splash resume=/dev/ubuntu-vg/swap_1 vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: libdrm Title: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PAD Ver. F.20 dmi.board.name: 30EC dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 91.25 dmi.chassis.asset.tag: CNU90728P0 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PADVer.F.20:bd12/07/2011:svnHewlett-Packard:pnHPEliteBook8730w:pvrF.20:rvnHewlett-Packard:rn30EC:rvrKBCVersion91.25:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8730w dmi.product.version: F.20 dmi.sys.vendor: Hewlett-Packard 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 1:17.2.1-0~x~padoka0 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.1-0~x~padoka0 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: Tue Jul 10 19:14:55 2018 xserver.configfile: default xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1798597] [NEW] Backport packages for 18.04.2 HWE stack
Public bug reported: [Impact] [Test case] [Regression potential] libdrm: llvm-7: libclc: mesa: xserver: drivers: [Other info] ** Affects: libclc (Ubuntu) Importance: Undecided Status: Invalid ** Affects: libdrm (Ubuntu) Importance: Undecided Status: Invalid ** Affects: llvm-toolchain-7 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: mesa (Ubuntu) Importance: Undecided Status: Invalid ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: Invalid ** Affects: libclc (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: llvm-toolchain-7 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: llvm-toolchain-7 (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: libclc (Ubuntu) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libdrm (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: xorg-server (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: libclc (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: llvm-toolchain-7 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Invalid ** Changed in: llvm-toolchain-7 (Ubuntu) Status: New => Invalid ** Changed in: libdrm (Ubuntu) Status: New => Invalid ** Changed in: libclc (Ubuntu) Status: New => Invalid -- 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/1798597 Title: Backport packages for 18.04.2 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-7 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Invalid Status in libclc source package in Bionic: New Status in libdrm source package in Bionic: New Status in llvm-toolchain-7 source package in Bionic: New Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: New Bug description: [Impact] [Test case] [Regression potential] libdrm: llvm-7: libclc: mesa: xserver: drivers: [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1798597/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798601] [NEW] posix_memalign corrupts heap
Public bug reported: The attached program exposes a bug in posix_memalign that causes it to either silently corrupt heap or cause the memory allocation checker to report spurious failures. I believe that the former is the case here because on more complex software (minetest or Irrlight tutorial examples) I had seen "pointer passed to free() which was never returned by an allocation function" errors. The posix_memalign is used by the OpenGL driver (package: mesa) and can be avoided by compiling mesa from source after telling the package we don't have posix_memalign. The "pointer passed to free()..." error was seen coming from inside the OpenGL as the irrlight example did not do much malloc calls itself. Unfortunately I could not figure out how this "real corruption" could be exposed by a simple program like this as it seems it requires a complicated mixture of malloc() and posix_memalign to trigger. To compile the program run "sh compile.sh" and to run it run "sh run.sh". You will then get two files, "memalign.out" (the output of the program until the failure) and "memalign.log" (a mtrace log). The program shall run for a several seconds but in fact it only runs for about 0.2 seconds before aborting with "invalid pointer" complaint. The program appears to finish normally (with no memory leaks detected) when "-lmcheck" is omitted from the compilation command (see compile.sh). However I had seen crashes caused by the problem in more complicated software that mixes posix_memalign with malloc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libc6 2.19-0ubuntu6.14 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 18 15:49:02 2018 Dependencies: gcc-4.9-base 4.9.3-0ubuntu4 libc6 2.19-0ubuntu6.14 libgcc1 1:4.9.3-0ubuntu4 multiarch-support 2.19-0ubuntu6.14 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 InstallationDate: Installed on 2015-12-26 (1027 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 ProcEnviron: LD_LIBRARY_PATH= TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/bash SourcePackage: eglibc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: eglibc (Ubuntu) Importance: Undecided Status: New ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ** Attachment added: "Test program that exposes a mcheck() problem with posiix_memalign" https://bugs.launchpad.net/bugs/1798601/+attachment/5202600/+files/memalign.tgz ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1798601 Title: posix_memalign corrupts heap Status in eglibc package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: The attached program exposes a bug in posix_memalign that causes it to either silently corrupt heap or cause the memory allocation checker to report spurious failures. I believe that the former is the case here because on more complex software (minetest or Irrlight tutorial examples) I had seen "pointer passed to free() which was never returned by an allocation function" errors. The posix_memalign is used by the OpenGL driver (package: mesa) and can be avoided by compiling mesa from source after telling the package we don't have posix_memalign. The "pointer passed to free()..." error was seen coming from inside the OpenGL as the irrlight example did not do much malloc calls itself. Unfortunately I could not figure out how this "real corruption" could be exposed by a simple program like this as it seems it requires a complicated mixture of malloc() and posix_memalign to trigger. To compile the program run "sh compile.sh" and to run it run "sh run.sh". You will then get two files, "memalign.out" (the output of the program until the failure) and "memalign.log" (a mtrace log). The program shall run for a several seconds but in fact it only runs for about 0.2 seconds before aborting with "invalid pointer" complaint. The program appears to finish normally (with no memory leaks detected) when "-lmcheck" is omitted from the compilation command (see compile.sh). However I had seen crashes caused by the problem in more complicated software that mixes posix_memalign with malloc. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libc6 2.19-0ubuntu6.14 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion:
[Touch-packages] [Bug 1780455] Re: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.
using external ppa ** Changed in: libdrm (Ubuntu) Status: New => Invalid -- 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/1780455 Title: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.83+git1708241830.f19dbb~gd~x Status in libdrm package in Ubuntu: Invalid Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common 2.4.91-2~16.04.1 ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134 Uname: Linux 4.4.0-130-generic i686 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Fri Jul 6 20:58:59 2018 Dependencies: DuplicateSignature: package:libdrm-common:2.4.91-2~16.04.1 Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.83+git1708241830.f19dbb~gd~x ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.83+git1708241830.f19dbb~gd~x InstallationDate: Installed on 2016-11-15 (598 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: libdrm Title: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:i386 2.4.83+git1708241830.f19dbb~gd~x UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780798] Re: package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.
using external ppa ** Changed in: libdrm (Ubuntu) Status: New => Invalid -- 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/1780798 Title: package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 Status in libdrm package in Ubuntu: Invalid Bug description: I clicked on software and problem occurred when it did not load properly. can attempt to load again. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common (not installed) ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-24-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Started LSB: Speech Dispatcher. [[0;32m OK [0m] Started LSB: Set the CPU Frequency Scaling governor to "ondemand". [[0;32m OK [0m] Started LSB: Record successful boot for GRUB. CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Jul 9 09:35:45 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libdrm-common:(not installed) Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 GraphicsCard: Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01d2] Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01d2] InstallationDate: Installed on 2017-09-29 (282 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Dell Inc. Dell DM051 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic root=UUID=abe400d9-984a-4f2a-afaa-0c6aa3156fbf ro quiet splash nomodeset vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 Renderer: Software SourcePackage: libdrm Title: package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/08/2007 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0RD203 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDM051:pvr:rvnDellInc.:rn0RD203:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: Dell DM051 dmi.sys.vendor: Dell Inc. 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 1:17.2.1-0~x~padoka0 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.1-0~x~padoka0 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: Mon Jul 9 09:02:56 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputDell Dell USB Keyboard Hub KEYBOARD, id 8 inputDell Dell USB Keyboard Hub KEYBOARD, id 9 inputLogitech Optical USB Mouse MOUSE, id 10 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.5-0ubuntu2~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1780522] Re: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2
using external ppa ** Changed in: libdrm (Ubuntu) Status: New => Invalid -- 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/1780522 Title: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.89+git1712180630.831036~oibaf~x Status in libdrm package in Ubuntu: Invalid Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common 2.4.91-2~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-40-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: None Date: Sat Jul 7 09:52:24 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DuplicateSignature: package:libdrm-common:2.4.91-2~16.04.1 Unpacking libdrm-common (2.4.91-2~16.04.1) ... dpkg: error processing archive /var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack): trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.89+git1712180630.831036~oibaf~x ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.89+git1712180630.831036~oibaf~x GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:185e] Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6730M/6770M/7690M XT] [1002:6740] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Radeon HD 7690M XT [103c:185e] InstallationDate: Installed on 2017-11-26 (222 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic root=UUID=f51ee470-057f-4896-b7a2-64c436c05572 ro radeon.modeset=0 vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: libdrm Title: package libdrm-common 2.4.91-2~16.04.1 failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.4.89+git1712180630.831036~oibaf~x UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.1B dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 17FA dmi.board.vendor: Hewlett-Packard dmi.board.version: 10.5A dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1B:bd10/23/2012:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr06902120462620100:rvnHewlett-Packard:rn17FA:rvr10.5A:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 06902120462620100 dmi.sys.vendor: Hewlett-Packard 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 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: Sat Jul 7 10:05:18 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1780522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1741473] Re: package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:am
using external ppa ** Changed in: libdrm (Ubuntu) Status: Confirmed => Invalid -- 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/1741473 Title: package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1 Status in libdrm package in Ubuntu: Invalid Bug description: automatic login ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libdrm-common 2.4.83-1~16.04.1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Wed Jan 3 15:20:41 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgTerminalLog: A preparar para desempacotar .../libdrm-common_2.4.83-1~16.04.1_all.deb ... A descompactar libdrm-common (2.4.83-1~16.04.1) ... dpkg: erro ao processar o arquivo /var/cache/apt/archives/libdrm-common_2.4.83-1~16.04.1_all.deb (--unpack): a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1 ErrorMessage: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1 GraphicsCard: Subsystem: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:2042] NVIDIA Corporation GF108 [GeForce GT 440] [10de:0de0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GF108 [GeForce GT 440] [10de:0828] InstallationDate: Installed on 2017-04-10 (269 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=2ecae89c-893b-4efc-b110-7c907b246eb6 ro quiet splash nomodeset acpi_osi=Linux vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: libdrm Title: package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:amd64 2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: Intel Corp. dmi.bios.version: HOH6110H.86A.0011.2012.0530.1036 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DH61HO dmi.board.vendor: Intel Corporation dmi.board.version: AAG62445-103 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrHOH6110H.86A.0011.2012.0530.1036:bd05/30/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-103:cvn:ct3:cvr: version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 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: Fri Jan 5 10:45:50 2018 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 input USB OPTICAL
[Touch-packages] [Bug 1795614] Re: packagekit frontend locking
Same on xenial (0.8.17-4ubuntu6~gcc5.4ubuntu1.4): root@xxx:~# lslocks COMMAND PID TYPE SIZE MODE M START END PATH iscsid396 POSIX 4B WRITE 0 0 0 /run/iscsid.pid atd 390 POSIX 4B WRITE 0 0 0 /run/atd.pid cron 392 FLOCK 4B WRITE 0 0 0 /run/crond.pid dpkg 2729 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock packagekitd 2653 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock-frontend packagekitd 2653 POSIX 0B WRITE 0 0 0 /var/cache/apt/archives/lock ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1795614 Title: packagekit frontend locking Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in packagekit source package in Cosmic: Fix Released Bug description: [SRU Notes] [rbasak] Requires apt 1.2.28 (Xenial) and 1.6.5 (Bionic), both of which are currently in proposed. Do not release to updates without releasing the newer apt first. [Impact] PackageKit needs an adjustment for frontend locking, so it does not release the frontend lock during dpkg invocations, but only the normal dpkg lock. Frontend locking prevents race conditions between multiple dpkg frontends, which can cause other frontends to be interrupted while they are installing stuff - the frontend loses the dpkg lock between dpkg runs and the system ends up in a partially configured state. See bug 1781169 for more details on frontend locking. [Test case] 1. Install a package 2. Modify prerm to sleep 3. Remove package via pkcon and check that packagekitd process holds lock-frontend and dpkg holds lock (we release lock by closing the lock files, so just check if the files are open). [Regression potential] Changing the code to call UnLockInner() vs UnLock() makes it do less steps and only release "lock" as before, and not "lock-frontend". That should not be causing any regressions. The patch also adds a call to LockInner() after the dpkg execution to make it reacquire "lock", this could fail. It should not have much impact however, as it only affects a single transaction AFAICT. It does reduce the risk of some frontend not implementing frontend locking from racing while we still hold the frontend lock, though. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795614] Re: packagekit frontend locking
(that was 1.1.9-1ubuntu2.18.04.3 in bionic) ** 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 packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1795614 Title: packagekit frontend locking Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in packagekit source package in Cosmic: Fix Released Bug description: [SRU Notes] [rbasak] Requires apt 1.2.28 (Xenial) and 1.6.5 (Bionic), both of which are currently in proposed. Do not release to updates without releasing the newer apt first. [Impact] PackageKit needs an adjustment for frontend locking, so it does not release the frontend lock during dpkg invocations, but only the normal dpkg lock. Frontend locking prevents race conditions between multiple dpkg frontends, which can cause other frontends to be interrupted while they are installing stuff - the frontend loses the dpkg lock between dpkg runs and the system ends up in a partially configured state. See bug 1781169 for more details on frontend locking. [Test case] 1. Install a package 2. Modify prerm to sleep 3. Remove package via pkcon and check that packagekitd process holds lock-frontend and dpkg holds lock (we release lock by closing the lock files, so just check if the files are open). [Regression potential] Changing the code to call UnLockInner() vs UnLock() makes it do less steps and only release "lock" as before, and not "lock-frontend". That should not be causing any regressions. The patch also adds a call to LockInner() after the dpkg execution to make it reacquire "lock", this could fail. It should not have much impact however, as it only affects a single transaction AFAICT. It does reduce the risk of some frontend not implementing frontend locking from racing while we still hold the frontend lock, though. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795614] Re: packagekit frontend locking
I verified by creating a prerm script for packagekit-tools with sleep 20 in it, and then looked at the locks while that was sleeping: # lslocks COMMAND PID TYPE SIZE MODE M START END PATH cron 415 FLOCK 4B WRITE 0 0 0 /run/crond.pid packagekitd 3374 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock-frontend packagekitd 3374 POSIX 0B WRITE 0 0 0 /var/cache/apt/archives/lock atd 406 POSIX 4B WRITE 0 0 0 /run/atd.pid dpkg 3500 POSIX 0B WRITE 0 0 0 /var/lib/dpkg/lock We can see the packagekitd holds the frontend lock, and dpkg holds the lock. -- 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/1795614 Title: packagekit frontend locking Status in packagekit package in Ubuntu: Fix Released Status in packagekit source package in Xenial: Fix Committed Status in packagekit source package in Bionic: Fix Committed Status in packagekit source package in Cosmic: Fix Released Bug description: [SRU Notes] [rbasak] Requires apt 1.2.28 (Xenial) and 1.6.5 (Bionic), both of which are currently in proposed. Do not release to updates without releasing the newer apt first. [Impact] PackageKit needs an adjustment for frontend locking, so it does not release the frontend lock during dpkg invocations, but only the normal dpkg lock. Frontend locking prevents race conditions between multiple dpkg frontends, which can cause other frontends to be interrupted while they are installing stuff - the frontend loses the dpkg lock between dpkg runs and the system ends up in a partially configured state. See bug 1781169 for more details on frontend locking. [Test case] 1. Install a package 2. Modify prerm to sleep 3. Remove package via pkcon and check that packagekitd process holds lock-frontend and dpkg holds lock (we release lock by closing the lock files, so just check if the files are open). [Regression potential] Changing the code to call UnLockInner() vs UnLock() makes it do less steps and only release "lock" as before, and not "lock-frontend". That should not be causing any regressions. The patch also adds a call to LockInner() after the dpkg execution to make it reacquire "lock", this could fail. It should not have much impact however, as it only affects a single transaction AFAICT. It does reduce the risk of some frontend not implementing frontend locking from racing while we still hold the frontend lock, though. [Other info] This is part of a wider series of SRUs for frontend locking - dpkg (bug 1796081) - apt (bug 1781169) - python-apt (bug 1795407) - packagekit (bug 1795614) - unattended-upgrades (bug 1789637) - aptdaemon (no bug filed yet) Further details about frontend locking can be found in https://lists.debian.org/debian-dpkg/2017/01/msg00044.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795614/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version
>From release to updates: # pkcon install packagekit Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Installing[=] Loading cache [=] Downloading packages [=] Running [=] Installing packages [=== ] (63%) The daemon crashed mid-transaction! To proposed (-...18.04.3): # pkcon install packagekit Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: apt-1.6.6.amd64commandline package manager apt-utils-1.6.6.amd64 package management related utility programs libapt-inst2.0-1.6.6.amd64 deb package format runtime library libapt-pkg5.0-1.6.6.amd64 package management runtime library packagekit-1.1.9-1ubuntu2.18.04.3.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.3.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Installing[=] Loading cache [=] Downloading packages [=] Running [=] Installing packages [=] Finished [=] => no crash, verified ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1790613 Title: Regression: packagekit crashes updating itself to a new version Status in packagekit package in Ubuntu: Fix Released Status in plasma-discover package in Ubuntu: Confirmed Status in packagekit source package in Bionic: Fix Committed Status in plasma-discover source package in Bionic: Confirmed Bug description: [Impact] Bionic: 18.04 Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1 Updating with pkcon upgrade or plasma-discover crashes packagekit mid transaction, requiring user intervention on the command line. In plasma-discover the gui reports the crash briefly, but then stalls in apparent mid update, requiring the user to force close it and again resolve the issue on the command line. Example transactions: $ pkcon update Getting updates [=] Finished [=] Loading cache [=] Testing changes [=] Finished [ ] (0%) The following packages have to be updated: gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection data for the PackageKit GLib library libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing PackageKit using GLib packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management service packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64 Provides PackageKit command-line tools Proceed with changes? [N/y] y [=] Updating packages [=] Waiting for authentication[=] Loading cache [=] Running [=] Installing packages [ ] (80%) The daemon crashed mid-transaction! $ sudo apt-get upgrade E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. and obviously after that doing anything meaningful with packagekit like installing a package fails $pkcon install kaffeine Resolving [=] Testing changes [=] Finished [ ] (0%) The following packages have to be installed: kaffeine-2.0.14-1.amd64
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
But well, the verification of 2.18.04.2 is still valid, the change to
the postinst does not invalidate it, so let's ignore that I'm not lucky
enough to end up with a broken apt cache.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Status in packagekit package in Ubuntu:
Fix Released
Status in packagekit source package in Bionic:
Fix Committed
Bug description:
[Impact]
pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache). Also, cancalled
transactions crash as well, even if you're lucky with your apt cache, as the
"matcher" object is deleted twice.
There are two reasons: A duplicate delete statement in providesCodec
entered when cancelling the lookup, and a invalid pointer dereference
in there.
[Test case]
The daemon should not crash as below, but should print a useful message.
$ lxc launch -e ubuntu:bionic bbb
$ lxc exec bbb apt update
$ lxc exec bbb -- apt -y install packagekit
$ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)"
[...] The daemon crashed mid-transaction!
(empty lxd container seems to be able to reproduce easily)
This only tests the pointer dereference, I don't have a test for the
duplicate. But the code is obviously correct:
for ... [
if (m_cancel) {
// here used to be "delete matcher" - that's deleted
break;
}
}
delete matcher;
That is, matcher is always deleted once now, and was always deleted
twice when cancelling before.
[Regression potential]
I don't think it's possible to have a regression here, given the nature of
the fix, but if there were one, we'd see different behavior in codec lookup.
For the duplicate delete on cancelled transactions, you'd be looking
at memory leaks if there were a regression.
[Other info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.10-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2
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/packagekit/+bug/1790671/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Well, timing broke the test - it no longer fails in the unfixed version.
ugh.
** Tags removed: block-proposed
--
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/1790671
Title:
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy
Status in packagekit package in Ubuntu:
Fix Released
Status in packagekit source package in Bionic:
Fix Committed
Bug description:
[Impact]
pkcon what-provides and other tools querying codecs do not work, they crash
(unless you happen to be lucky with your apt cache). Also, cancalled
transactions crash as well, even if you're lucky with your apt cache, as the
"matcher" object is deleted twice.
There are two reasons: A duplicate delete statement in providesCodec
entered when cancelling the lookup, and a invalid pointer dereference
in there.
[Test case]
The daemon should not crash as below, but should print a useful message.
$ lxc launch -e ubuntu:bionic bbb
$ lxc exec bbb apt update
$ lxc exec bbb -- apt -y install packagekit
$ lxc exec bbb pkcon what-provides "gstreamer1.0(decoder-audio/ac3)"
[...] The daemon crashed mid-transaction!
(empty lxd container seems to be able to reproduce easily)
This only tests the pointer dereference, I don't have a test for the
duplicate. But the code is obviously correct:
for ... [
if (m_cancel) {
// here used to be "delete matcher" - that's deleted
break;
}
}
delete matcher;
That is, matcher is always deleted once now, and was always deleted
twice when cancelling before.
[Regression potential]
I don't think it's possible to have a regression here, given the nature of
the fix, but if there were one, we'd see different behavior in codec lookup.
For the duplicate delete on cancelled transactions, you'd be looking
at memory leaks if there were a regression.
[Other info]
The Ubuntu Error Tracker has been receiving reports about a problem regarding
packagekit. This problem was most recently seen with package version
1.1.10-1ubuntu2, the problem page at
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2
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/packagekit/+bug/1790671/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781169] Re: apt frontend locking
Same with 1.2.29 from xenial:
open("/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
open("/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(5, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
[...] reading files ]
close(5)= 0
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(37, F_SETFD, FD_CLOEXEC) = 0
close(5)= 0
fcntl(37, F_GETFL) = 0x1 (flags O_WRONLY)
close(37) = 0
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=3741, si_uid=0,
si_status=0, si_utime=0, si_stime=0} ---
[ reading files and writing extended_states stuff; no close(4) ]
close(4)= 0
close(5)= -1 EBADF (Bad file descriptor)
close(3)= 0
+++ exited with 0 +++
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1781169
Title:
apt frontend locking
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
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.
[Other info]
This is part of a wider series of SRUs for frontend locking
- dpkg (bug 1796081)
- apt (bug 1781169)
- python-apt (bug 1795407)
- packagekit (bug 1795614)
- unattended-upgrades (bug 1789637)
- aptdaemon (no bug filed yet)
Further details about frontend locking can be found in
https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
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 1796808] Re: frontend locking regression: dpkg::post-invoke scripts can't install packages
The specified tests passed on both: bionic (1.6.6): (187/248) Testcase test-frontend-lock: P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P xenial (1.2.29): (165/220) Testcase test-frontend-lock: P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P P ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1796808 Title: frontend locking regression: dpkg::post-invoke scripts can't install packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt source package in Cosmic: Fix Released Bug description: [Impact] The switch to frontend locking in 1.2.28/1.6.5/1.7~ caused scripts registered in DPkg::Pre-Install-Pkgs DPkg::Pre-Invoke DPkg::Post-Invoke To be run with the frontend lock held. This caused problems with some installer packages like libdvd-pkg which install a locally built package in such a hook. To reduce the impact, a fix has been applied in 1.7.0 which exports the DPKG_FRONTEND_LOCKED variable when running those scripts, allowing dpkg to be run from those scripts. [Test case] Make sure that the test-frontend-lock test run by autopkgtest succeeds. This checks that: (1) the variable is correctly exported to those scripts (2) the frontend lock is still held (3) dpkg can be run from the post-invoke script [Regression potential] Depending on the script (for example, if the script starts a daemon manually or something like that), DPKG_FRONTEND_LOCKED might leak to other processes which might survive the apt call and thus revert surviving process to not using frontend locking. [Other info] This fix is for backwards compatibility only. Starting with the dd cycle, it will be dropped for the Pre-Install-Pkgs and Pre-Invoke scripts. Potentially for post-invoke as well, if we find a better solution for it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796808/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781169] Re: apt frontend locking
apt 1.6.6 from bionic: I verified that lock-frontend was opened and
locked at the beginning, that lock was locked after it, lock released
before dpkg is called, and that lock-frontend was not released until the
end.
[...]
openat(AT_FDCWD, "/var/lib/dpkg/lock-frontend", O_RDWR|O_CREAT|O_NOFOLLOW,
0640) = 4
fcntl(4, F_SETFD, FD_CLOEXEC) = 0
fcntl(4, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
openat(AT_FDCWD, "/var/lib/dpkg/lock", O_RDWR|O_CREAT|O_NOFOLLOW, 0640) = 5
fcntl(5, F_SETFD, FD_CLOEXEC) = 0
fcntl(5, F_SETLK, {l_type=F_WRLCK, l_whence=SEEK_SET, l_start=0, l_len=0}) = 0
[ ... Reading files ... ]
close(5)= 0
[... running dpkg and rebuilding cache; no close(4) ]
close(4)= 0
close(5)= -1 EBADF (Bad file descriptor)
close(3)= 0
+++ exited with 0 +++
** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1781169
Title:
apt frontend locking
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
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.
[Other info]
This is part of a wider series of SRUs for frontend locking
- dpkg (bug 1796081)
- apt (bug 1781169)
- python-apt (bug 1795407)
- packagekit (bug 1795614)
- unattended-upgrades (bug 1789637)
- aptdaemon (no bug filed yet)
Further details about frontend locking can be found in
https://lists.debian.org/debian-dpkg/2017/01/msg00044.html
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 1798487] Re: ubuntu
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1798487 Title: ubuntu Status in xorg package in Ubuntu: New Bug description: $ ubuntu-bug xorg ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Oct 18 00:43:26 2018 DistUpgraded: 2018-10-14 08:37:38,803 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:832a] InstallationDate: Installed on 2018-10-14 (3 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 0bda:58ed Realtek Semiconductor Corp. Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 046d:c087 Logitech, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15-bs1xx ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=41511a8e-8ac5-477b-86b9-0ac1708a0280 ro nopat vesafb.invalid=1 drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-14 (3 days ago) dmi.bios.date: 08/06/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 832A dmi.board.vendor: HP dmi.board.version: 23.61 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd08/06/2018:svnHP:pnHPLaptop15-bs1xx:pvrType1ProductConfigId:rvnHP:rn832A:rvr23.61:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-bs1xx dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP 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.1 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: Sun Oct 14 08:02:35 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1798487/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
Marking verification-done-xenial again, this got reset by 1.2.29. FWIW; I also retested: after upgrading apt to 1.2.29 in the xenial container, and rerunning the kernel hook that creates the file, I also see "^linux-cloud-tools-4\.18\.0-8-generic$"; in the list. ** Tags removed: verification-needed verification-needed-xenial ** Tags added: verification-done verification-done-xenial -- 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/1698159 Title: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Trusty: Triaged Status in unattended-upgrades source package in Trusty: New Status in apt source package in Xenial: Fix Committed Status in unattended-upgrades source package in Xenial: New Status in apt source package in Bionic: Fix Released Status in unattended-upgrades source package in Bionic: Fix Released Bug description: [Impact] When running kernel version 4.4.0-78 (for example) and the unattended-upgrade packages installs a new kernel 4.4.0-79 (for example) the linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels. The linux-cloud-tools package has the hyper-v integration services daemons in it, so it's deletion leaves some of the integration not working. Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other hyper-v users aren't caught out by this? Thanks, Ian. [Test case] Make sure that linux-cloud-tools for protected kernels are listed in APT::NeverAutoRemove, for example, on cosmic: "^linux-cloud-tools-4\.17\.0-9-generic$"; "^linux-cloud-tools-4\.18\.0-7-generic$"; Those are in 01autoremove-kernels [Regression Potential] some linux-cloud-tools will linger around, so it takes more space. [Other info] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.6 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 Date: Thu Jun 15 15:27:35 2017 InstallationDate: Installed on 2016-04-25 (415 days ago) InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.3) PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: [modified] modified.conffile..etc.update-motd.d.90-updates-available: [deleted] modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted] modified.conffile..etc.update-motd.d.98-reboot-required: [deleted] mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798457] Re: Provide curtin-requirements and server-ship-live seeds
** Tags added: id-5bc47d3c1fe26c474bc9978b -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1798457 Title: Provide curtin-requirements and server-ship-live seeds Status in ubuntu-meta package in Ubuntu: New Bug description: Provide curtin-requirements and server-ship-live seeds and make cdimage use them for server live images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1798457/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794053] Re: pkgCacheFile unlocks in destructor even if it did not acquire lock
xenial
==
With 1.2.27
---
root@glowing-mastodon:~# python3 a.py
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:15 3 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:15 6 -> pipe:[27632799]
Reading package lists... Done
Building dependency tree
Reading state information... Done
total 0
[...]
l-wx-- 1 root root 64 Oct 18 12:15 6 -> pipe:[27632799]
Traceback (most recent call last):
File "a.py", line 13, in
apt_pkg.pkgsystem_unlock()
SystemError: E:Not locked
=> broken as expected
With 1.2.29
---
root@glowing-mastodon:~# python3 a.py
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:17 3 -> /var/lib/dpkg/lock-frontend
lrwx-- 1 root root 64 Oct 18 12:17 4 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:17 6 -> pipe:[27632799]
Reading package lists... Done
Building dependency tree
Reading state information... Done
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:17 3 -> /var/lib/dpkg/lock-frontend
lrwx-- 1 root root 64 Oct 18 12:17 4 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:17 6 -> pipe:[27632799]
root@glowing-mastodon:~#
=> lock is still held at second ls, and releasing it worked fine.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794053
Title:
pkgCacheFile unlocks in destructor even if it did not acquire lock
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Trusty:
Triaged
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Cosmic:
Fix Released
Bug description:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly
breaks ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens
a cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That
said, any potential regression should be easily noticable, as it would
be a case of not unlocking where we were unlocking before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1787120] Re: apt show fails to show large records
The included autopkgtest has successfully passed for both 1.6.6/bionic and 1.2.29/xenial ** Tags removed: verification-needed verification-needed-bionic verification-needed-xenial ** Tags added: verification-done verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1787120 Title: apt show fails to show large records Status in apt package in Ubuntu: Invalid Status in apt source package in Xenial: Fix Committed Status in apt source package in Bionic: Fix Committed Status in apt package in Debian: Confirmed Bug description: [Impact] apt show can't show records that are larger than 32 KB, e.g. records with long lists of provides [Test case] A test case is provided in autopkgtest, hence validates automatically. See https://salsa.debian.org/apt-team/apt/commit/409ceec9ed30cbebd8ece1ef7ce667ab5a32f9df for details. [Other info] This is a duplicate of Debian bug #905527. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794053] Re: pkgCacheFile unlocks in destructor even if it did not acquire lock
bionic (1.6.3ubuntu0.1 -> 1.6.6):
root@dashing-panda:~# python3 a.py
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:07 3 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:07 6 -> 'pipe:[27578280]'
Reading package lists... Done
Building dependency tree
Reading state information... Done
total 0
[...]
l-wx-- 1 root root 64 Oct 18 12:07 6 -> 'pipe:[27578280]'
Traceback (most recent call last):
File "a.py", line 13, in
apt_pkg.pkgsystem_unlock()
apt_pkg.Error: E:Not locked
[...]
=> We can see that the cache was already unlocked when it should not
have been
root@dashing-panda:~# apt install libapt-pkg5.0
[...]
Unpacking libapt-pkg5.0:amd64 (1.6.6) over (1.6.3ubuntu0.1) ...
[...]
root@dashing-panda:~# python3 a.py
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:08 3 -> /var/lib/dpkg/lock-frontend
lrwx-- 1 root root 64 Oct 18 12:08 4 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:08 6 -> 'pipe:[27578280]'
Reading package lists... Done
Building dependency tree
Reading state information... Done
total 0
[...]
lrwx-- 1 root root 64 Oct 18 12:08 3 -> /var/lib/dpkg/lock-frontend
lrwx-- 1 root root 64 Oct 18 12:08 4 -> /var/lib/dpkg/lock
l-wx-- 1 root root 64 Oct 18 12:08 6 -> 'pipe:[27578280]'
root@dashing-panda:~#
=> script worked fine, we see that the lock is still open in the second
ls, and there are no error messages
** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794053
Title:
pkgCacheFile unlocks in destructor even if it did not acquire lock
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Trusty:
Triaged
Status in apt source package in Xenial:
Fix Committed
Status in apt source package in Bionic:
Fix Committed
Status in apt source package in Cosmic:
Fix Released
Bug description:
[Impact]
Closing a cache file unlocks the system (loses the lock). This randomly
breaks ubuntu-make, for example.
[Test case]
The following Python code fails, but should succeed, as it locks first, opens
a cache and closes it, and then unlocks.
import apt_pkg, os, gc
apt_pkg.init()
apt_pkg.pkgsystem_lock()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.Cache()
gc.collect()
os.system("ls -l /proc/%d/fd" % os.getpid())
apt_pkg.pkgsystem_unlock()
[Regression potential]
This fixes a regression introduced in 2001 by
commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
Author: Arch Librarian
Date: Mon Sep 20 16:56:32 2004 +
Join with aliencode
Author: jgg
Date: 2001-02-20 07:03:16 GMT
Join with aliencode
The fix is to only UnLock from the cache file if the cache file locked
before. It's unclear how far code relies on that regression. That
said, any potential regression should be easily noticable, as it would
be a case of not unlocking where we were unlocking before.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798579] [NEW] GUI Graphics are not working and touchpad is also not working
Public bug reported: It has Intel Graphics Driver but still display is not fine. Touchpad drivers are also available but it is also not working. Although external mouse is working fine. Version- Ubuntu 18.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 16:46:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3964] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [17aa:3964] InstallationDate: Installed on 2018-10-16 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:58ea Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 062a:413e Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=773e1eb0-580f-49a5-ab82-20f86c99e160 ro i8042.reset quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8TCN44WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 330-15IKB dmi.modalias: dmi:bvnLENOVO:bvr8TCN44WW:bd06/13/2018:svnLENOVO:pn81DE:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB: dmi.product.family: ideapad 330-15IKB dmi.product.name: 81DE dmi.product.version: Lenovo ideapad 330-15IKB dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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 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 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/1798579 Title: GUI Graphics are not working and touchpad is also not working Status in xorg package in Ubuntu: New Bug description: It has Intel Graphics Driver but still display is not fine. Touchpad drivers are also available but it is also not working. Although external mouse is working fine. Version- Ubuntu 18.04.1 LTS ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 18 16:46:47 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.15.0-36-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3964] Subsystem: Lenovo Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [17aa:3964] InstallationDate: Installed on 2018-10-16 (1 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0bda:58ea Realtek Semiconductor Corp. Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 062a:413e Creative Labs Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81DE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=773e1eb0-580f-49a5-ab82-20f86c99e160 ro i8042.reset quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present
[Touch-packages] [Bug 1779237] Re: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4
Hola sudo apt-get install --reinstall hplip hplip-data sudo apt-get install --reinstall python3 soluciono mi problema! Gracias Dimitri!! -- 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/1779237 Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 Status in python3-defaults package in Ubuntu: Invalid Bug description: Only Ubuntu Update ProblemType: Package DistroRelease: Ubuntu 18.04 Package: python3 3.6.5-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 Date: Thu Jun 28 22:51:28 2018 ErrorMessage: installed python3 package post-installation script subprocess returned error exit status 4 InstallationDate: Installed on 2018-04-13 (76 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) Python3Details: /usr/bin/python3.6, Python 3.6.5, 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.2 SourcePackage: python3-defaults Title: package python3 3.6.5-3ubuntu1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4 UpgradeStatus: Upgraded to bionic on 2018-05-03 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1779237/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1516410] Re: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Hi Estavan, Is your reported bug still a problem, then? When you didn't reply to the previous message, the bug report is automatically expired after 60 days. If it is still an issue, please let us know and we can look at next steps. Thanks G -- 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/1516410 Title: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: Expired Bug description: This problem is strange. I keep seeing it after I have force installs of the upgrades and updates. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: cups-common 2.0.2-1ubuntu3.2 ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CupsErrorLog: E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateAccess on line 88 of /etc/cups/cupsd.conf. E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateValues on line 89 of /etc/cups/cupsd.conf. E [15/Nov/2015:07:45:08 -0800] Unknown directive SubscriptionPrivateAccess on line 90 of /etc/cups/cupsd.conf. E [15/Nov/2015:07:45:08 -0800] Unknown directive SubscriptionPrivateValues on line 91 of /etc/cups/cupsd.conf. Date: Sun Nov 15 09:07:50 2015 Dependencies: DpkgTerminalLog: dpkg: error processing package cups-common (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration DuplicateSignature: package:cups-common:2.0.2-1ubuntu3.2:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-10-10 (35 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Lpstat: device for Samsung-M288x-Series: dnssd://Samsung%20M288x%20Series%20(SEC30CDA7334F8A)._printer._tcp.local/ MachineType: MSI MS-7693 PackageArchitecture: all Papersize: letter PpdFiles: Samsung-M288x-Series: Samsung M288x Series PXL ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed root=UUID=e699cd80-60f5-41c8-9840-87a0884cec4a ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed root=UUID=e699cd80-60f5-41c8-9840-87a0884cec4a ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: cups Title: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V22.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970 GAMING (MS-7693) dmi.board.vendor: MSI dmi.board.version: 4.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 4.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV22.3:bd05/12/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: dmi.product.name: MS-7693 dmi.product.version: 4.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1516410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1713448] Re: Adobe Reader doesn't print on OKI C911
Done. I printed some simple file to the OKI-printer, waited a few minutes while the printer was "Processing ...", unteil Cancel-ed the job on the printer. The log file is attached, hoping it helps. ** Attachment added: "Log-File of job processing on OKI for eternity" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1713448/+attachment/5202484/+files/error_log -- 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/1713448 Title: Adobe Reader doesn't print on OKI C911 Status in cups package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Bug description: Out and over. I tried whatever I could think of, but whatever I send there, anything will make the printer blink, 'processing', forever, until I cancel the job. The printer, however, prints the same files from okular, and from all other applications that I have tried so far. This would clearly point to acroread. However, acroread prints to all other printers that we have standing about without any problem. Logically, from what I could state so far, we have an AND-combination: everything works, except I print a file from acroread through OKI C911. Since I have other printers and other PDF-software, it is minor. And yet, I wouldn't mind helping to debug this thing. I'm using the OKI-provided ppd with cups. adobereader-enu:i386 9.5.5 cups 2.1.3-4 --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CupsErrorLog: E [31/Aug/2018:11:08:02 +0200] Missing value on line 617 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 668 of /var/cache/cups/job.cache. E [31/Aug/2018:11:08:02 +0200] Missing value on line 4277 of /var/cache/cups/job.cache. CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-04-01 (1247 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.1) Lpstat: device for BrotherColourMFC9970: socket://134.91.100.26:9100 device for Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600: dnssd://hp%20color%20LaserJet%204600%40IC07CA93._printer._tcp.local/ device for OKI_C911: dnssd://OKIC911-BB319._pdl-datastream._tcp.local/ device for Samsung_M262x_282x_Series: dnssd://Samsung%20M262x%20282x%20Series%20(SEC001599EE3069)._printer._tcp.local/ MachineType: LENOVO 2924WEG Package: linux PackageArchitecture: amd64 Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/BrotherColourMFC9970.ppd', '/etc/cups/ppd/OKI_C911.ppd', '/etc/cups/ppd/Samsung_M262x_282x_Series.ppd', '/etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd'] failed with exit code 2: grep: /etc/cups/ppd/BrotherColourMFC9970.ppd: Permission denied grep: /etc/cups/ppd/OKI_C911.ppd: Permission denied grep: /etc/cups/ppd/Samsung_M262x_282x_Series.ppd: Permission denied grep: /etc/cups/ppd/Hewlett-Packard_Hewlett-Packard_hp_color_LaserJet_4600.ppd: Permission denied ProcCmdline: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-134-generic root=UUID=8d3acd2e-2a7f-42ba-b873-b819283b6144 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140 Tags: xenial Uname: Linux 4.4.0-134-generic x86_64 UpgradeStatus: Upgraded to xenial on 2018-08-15 (15 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 6UET70WW (1.50 ) dmi.board.name: 2924WEG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6UET70WW(1.50):bd10/11/2012:svnLENOVO:pn2924WEG:pvrThinkPadT410s:rvnLENOVO:rn2924WEG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2924WEG dmi.product.version: ThinkPad T410s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1713448/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785699] Re: Invisible text in insenstitive suggested action buttons
$ apt-cache policy light-themes light-themes: Installato: 16.10+18.04.20181004-0ubuntu1 Candidato: 16.10+18.04.20181004-0ubuntu1 I confirm this is fixed in bionic-proposed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1785699 Title: Invisible text in insenstitive suggested action buttons Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: Impact -- The suggestion action button does not have correct text styling when the action button is "insensitive" (greyed out). This makes the text basically invisible since it has the same dark grey color for both the foreground text and the background. Test Case 1 --- 1. Open the file browser. 2. Open the ☰ menu and select New Folder. What happens: 1. In the New Folder dialog, the top right button has invisible text. Screenshot attached. What should happen: It should show the word Create but greyed out. Test Case 2 --- 1. Open the gedit text editor. 2. Open the ☰ menu and select Save As. 3. In the Name field, delete all the text to make the field empty. What happens: The word Save in the top right button becomes invisible. Regression Potential Color for elements other than the label of suggested actions is wrong Other Info -- Ubuntu 18.04.1 LTS light-themes 16.10+18.04.20180421.1-0ubuntu1 Ambiance theme libgtk-3-0 3.22.30-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1785699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1781736] Re: Buttons aren't properly themed in Radiance theme under HiDPI
Borders are properly themed and with right quality textures in this
version:
$ apt-cache policy light-themes
light-themes:
Installato: 16.10+18.04.20181004-0ubuntu1
Candidato: 16.10+18.04.20181004-0ubuntu1
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
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/1781736
Title:
Buttons aren't properly themed in Radiance theme under HiDPI
Status in Ubuntu theme:
In Progress
Status in ubuntu-themes package in Ubuntu:
Fix Released
Status in ubuntu-themes source package in Bionic:
Fix Committed
Bug description:
[ Impact ]
Buttons in radiance aren't properly themed in highdpi mode
[ Test case ]
1. Run a gtk app with CSD (i.e.) gnome-disks with GDK_SCALE=2 and
GTK_THEME=Radiance
GDK_SCALE=2 GTK_THEME=Radiance gnome-disks
2. Buttons should be properly themed and with high-quality borders in both
normal and
focused state.
[ Regression potential ]
No proper borders are painted on buttons under Radiance
--
There is a typo in the file /usr/share/themes/Radiance/gtk-3.20/gtk-
widgets.css that causes focused buttons to be drawn incorrectly in the
radiance theme. The following change should be made to the file to fix
the incorrect assets link:
118c118
< url("assets/button-focused.png@2"));
---
> url("assets/button-focu...@2.png"));
ProblemType: BugDistroRelease: Ubuntu 18.04
Package: light-themes 16.10+18.04.20180421.1-0ubuntu1 [modified:
usr/share/themes/Radiance/gtk-3.20/gtk-widgets.css]
ProcVersionSignature: Ubuntu 4.15.0-28.30-generic 4.15.18
Uname: Linux 4.15.0-28-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Jul 14 15:41:53 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-06-23 (21 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: allSourcePackage: ubuntu-themes
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1781736/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795895] Re: Accelerators on selected menu-items are not readable
$ apt-cache policy light-themes light-themes: Installato: 16.10+18.04.20181004-0ubuntu1 Candidato: 16.10+18.04.20181004-0ubuntu1 I confirm this is fixed in bionic-proposed. No regression found on normal-menubars (terminal or gnome games), while nautilus right-click menu is fixed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1795895 Title: Accelerators on selected menu-items are not readable Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] As visible in the attached screenshot in the nautilus context menu, the accelerator is not readable when the item is selected: https://i.imgur.com/xabntIH.png [ Test case ] 1. Open Nautilus 2. Right-click on the files view 3. Select an item with an accelerator 4. The accelerator should be visible (white in Ambiance theme) [ Possible regressions ] Accelerators on menuitems on menubars might always be painted as when hovered To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1795895/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1761684] Re: Regression in lists like gnome-boxes
$ apt-cache policy light-themes light-themes: Installato: 16.10+18.04.20181004-0ubuntu1 Candidato: 16.10+18.04.20181004-0ubuntu1 I confirm this is fixed in bionic-proposed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1761684 Title: Regression in lists like gnome-boxes Status in gnome-boxes package in Ubuntu: Invalid Status in ubuntu-themes package in Ubuntu: Fix Released Status in gnome-boxes source package in Bionic: New Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] The theme regressed the actively selected item on gnome-boxes (hover is also hard to read). See attached screenshot. [ Test case ] 1. Run gnome-boxes (install the same package if not available) 2. Click on "New" box button 3. The first page should show a list of available machines, content should be readable. [ Regression potential ] Other gnome-boxes lists are not properly themed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-boxes/+bug/1761684/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1743373] Re: Combobox arrow and color are inverted
apt-cache policy light-themes light-themes: Installato: 16.10+18.04.20181004-0ubuntu1 Candidato: 16.10+18.04.20181004-0ubuntu1 I confirm this is fixed. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1743373 Title: Combobox arrow and color are inverted Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Test case ] Comobobox lists extenders use invalid arrows 1. Both at the top and at the bottom, the arrow (triangle) points downwards. 2. Colors of sensitive and insensitive arrows are swapped. [ Test case ] 1. Open gnome-terminal, in menu goes to: Edit -> Profile Preferences -> Compatibility -> Encoding 2. The arrow at the top should point upwards 3. Tha arrow at the bottom should point downwards 4. Arrows should be visible only when there's actually something to scroll up or down. [ Regression potential ] Arrows aren't shown as expected in menus or combo-box --- Open a combobox with plenty of entries. (Example: gnome-terminal -> Edit -> Profile Preferences -> Compatibility -> Encoding) Notice two bugs: 1. Both at the top and at the bottom, the arrow (triangle) points downwards. Expected: At the top, the arrow should point upwards. 2. Colors of sensitive and insensitive arrows are swapped. The arrow is black if you cannot scroll in that direction, gray if hovering starts to scroll. Expected: It should be black if you can scroll in that direction by hovering, and gray if you cannot. Adwaita doesn't suffer from either of these issues. ProblemType: BugDistroRelease: Ubuntu 17.10 Package: light-themes 16.10+17.10.20171115-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Jan 15 13:44:49 2018 InstallationDate: Installed on 2016-11-09 (431 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: allSourcePackage: ubuntu-themes UpgradeStatus: Upgraded to artful on 2017-09-21 (115 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1743373/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1782038] Re: Window buttons are small in a maximized Chromium window
$ apt-cache policy light-themes light-themes: Installato: 16.10+18.04.20181004-0ubuntu1 Candidato: 16.10+18.04.20181004-0ubuntu1 I confirm this is fixed in chrome and chromium. No regression on clicking area. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- 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/1782038 Title: Window buttons are small in a maximized Chromium window Status in ubuntu-themes package in Ubuntu: Fix Released Status in ubuntu-themes source package in Bionic: Fix Committed Bug description: [ Impact ] In maximized google-chrome / chromium window buttons for close, minimize, and restore buttons should be normal-sized, but instead appear small. [ Test case ] 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium or Google Chrome window. 3. Ensure that in chrome settings, the "Use system borders" option is unchecked 4. Maximize. 5. Window buttons should have normal size. [ Regression potential ] Other windows buttons could loose the padding used for being closed. --- Repro: 1. Use the Ambiance or Radiance themes. 2. Launch a Chromium window. 3. Maximize. The window close, minimize, and restore buttons should be normal- sized, but instead appear small. This is because the buttons have a padding of 9px on the top and bottom, causing Chromium to think they're taller than they really are, so it downsizes them to fit the smaller headerbar on the maximized window. The attached patch removes the padding. There are no changes in behavior in apps other than Chromium. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1782038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1797944] Re: sudoers entries with FQDN are ignored on Ubuntu 14.04
** Description changed: Here is the short example of /etc/sudoers in order to reproduce the issue that if host is defined as FQDN then such string is skipped on Ubuntu 14.04. The following sudo is installed on the host "1.8.9p5-1ubuntu1.4 amd64" ~ ~# cat /etc/sudoers Defaultssyslog=local3 Defaults!set_home Defaults!targetpw Defaults!insults Defaultsmailto=alert-sudo Defaults!mail_always Defaultsignore_dot Defaultstimestamp_timeout=5 Defaultslistpw=always Defaults!lecture_file Defaultsfqdn user1 host1.xxx..com = (root) /bin/true user1 host1 = (root) /bin/false ~ - ~$ sudo -l -U ovgumeny - Matching Defaults entries for ovgumeny on fmyuranch01: + ~$ sudo -l -U user1 + Matching Defaults entries for ovgumeny on host1: syslog=local3, !set_home, !targetpw, !insults, mailto=alert-sudo, !mail_always, ignore_dot, timestamp_timeout=5, listpw=always, !lecture_file, fqdn User user1 may run the following commands on host1: (root) /bin/false ~ ~$ hostname host1 ~$ hostname -f host1.xxx..com ~ ~# lsb_release -d Description:Ubuntu 14.04.5 LTS ~ ** Description changed: Here is the short example of /etc/sudoers in order to reproduce the issue that if host is defined as FQDN then such string is skipped on Ubuntu 14.04. The following sudo is installed on the host "1.8.9p5-1ubuntu1.4 amd64" ~ ~# cat /etc/sudoers Defaultssyslog=local3 Defaults!set_home Defaults!targetpw Defaults!insults Defaultsmailto=alert-sudo Defaults!mail_always Defaultsignore_dot Defaultstimestamp_timeout=5 Defaultslistpw=always Defaults!lecture_file Defaultsfqdn user1 host1.xxx..com = (root) /bin/true user1 host1 = (root) /bin/false ~ ~$ sudo -l -U user1 - Matching Defaults entries for ovgumeny on host1: + Matching Defaults entries for user1 on host1: syslog=local3, !set_home, !targetpw, !insults, mailto=alert-sudo, !mail_always, ignore_dot, timestamp_timeout=5, listpw=always, !lecture_file, fqdn User user1 may run the following commands on host1: (root) /bin/false ~ ~$ hostname host1 ~$ hostname -f host1.xxx..com ~ ~# lsb_release -d Description:Ubuntu 14.04.5 LTS ~ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sudo in Ubuntu. https://bugs.launchpad.net/bugs/1797944 Title: sudoers entries with FQDN are ignored on Ubuntu 14.04 Status in sudo package in Ubuntu: New Bug description: Here is the short example of /etc/sudoers in order to reproduce the issue that if host is defined as FQDN then such string is skipped on Ubuntu 14.04. The following sudo is installed on the host "1.8.9p5-1ubuntu1.4 amd64" ~ ~# cat /etc/sudoers Defaultssyslog=local3 Defaults!set_home Defaults!targetpw Defaults!insults Defaultsmailto=alert-sudo Defaults!mail_always Defaultsignore_dot Defaultstimestamp_timeout=5 Defaultslistpw=always Defaults!lecture_file Defaultsfqdn user1 host1.xxx..com = (root) /bin/true user1 host1 = (root) /bin/false ~ ~$ sudo -l -U user1 Matching Defaults entries for user1 on host1: syslog=local3, !set_home, !targetpw, !insults, mailto=alert-sudo, !mail_always, ignore_dot, timestamp_timeout=5, listpw=always, !lecture_file, fqdn User user1 may run the following commands on host1: (root) /bin/false ~ ~$ hostname host1 ~$ hostname -f host1.xxx..com ~ ~# lsb_release -d Description:Ubuntu 14.04.5 LTS ~ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1797944/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794690] Re: Backport 0.8.2 for a CVE update
leo: feel free to handle all updates via the security pocket(s), as I have no permission to upload there (AIUI). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu. https://bugs.launchpad.net/bugs/1794690 Title: Backport 0.8.2 for a CVE update Status in libxkbcommon package in Ubuntu: Fix Released Status in libxkbcommon source package in Bionic: In Progress Bug description: [Impact] 0.8.2 has completed the fuzzing work started in 0.8.1, so backport the package from cosmic to fix these CVE's: CVE-2018-15853 CVE-2018-15854 CVE-2018-15855 CVE-2018-15856 CVE-2018-15857 CVE-2018-15858 CVE-2018-15859 CVE-2018-15861 CVE-2018-15862 CVE-2018-15863 CVE-2018-15864. upstream NEWS: libxkbcommon 0.8.2 - 2018-08-05 == - Fix various problems found with fuzzing (see commit messages for more details): - Fix a few NULL-dereferences, out-of-bounds access and undefined behavior in the XKB text format parser. libxkbcommon 0.8.1 - 2018-08-03 == - Fix various problems found in the meson build (see commit messages for more details): - Fix compilation on Darwin. - Fix compilation of the x11 tests and demos when XCB is installed in a non-standard location. - Fix xkbcommon-x11.pc missing the Requires specification. - Fix various problems found with fuzzing and Coverity (see commit messages for more details): - Fix stack overflow in the XKB text format parser when evaluating boolean negation. - Fix NULL-dereferences in the XKB text format parser when some unsupported tokens appear (the tokens are still parsed for backward compatibility). - Fix NULL-dereference in the XKB text format parser when parsing an xkb_geometry section. - Fix an infinite loop in the Compose text format parser on some inputs. - Fix an invalid free() when using multiple keysyms. - Replace the Unicode characters for the leftanglebracket and rightanglebracket keysyms from the deprecated LEFT/RIGHT-POINTING ANGLE BRACKET to MATHEMATICAL LEFT/RIGHT ANGLE BRACKET. - Reject out-of-range Unicode codepoints in xkb_keysym_to_utf8 and xkb_keysym_to_utf32. [Test case] install the update, check that nothing breaks wrt keyboard handling [Regression potential] slim, this has been in cosmic for some time already, and upstream specifically asked to backport this to stable releases There are some other changes to the packaging, but these are harmless and won't regress anything. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1794690/+subscriptions -- Mailing list: https://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 1516410] Re: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurat
Thanks a lot! On Wed, Oct 17, 2018, 21:30 Launchpad Bug Tracker < 1516...@bugs.launchpad.net> wrote: > [Expired for cups (Ubuntu) because there has been no activity for 60 > days.] > > ** Changed in: cups (Ubuntu) >Status: Incomplete => Expired > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1516410 > > Title: > package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: > package is in a very bad inconsistent state; you should reinstall it > before attempting configuration > > Status in cups package in Ubuntu: > Expired > > Bug description: > This problem is strange. I keep seeing it after I have force installs > of the upgrades and updates. > > ProblemType: Package > DistroRelease: Ubuntu 15.04 > Package: cups-common 2.0.2-1ubuntu3.2 > ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 > Uname: Linux 3.19.0-33-generic x86_64 > ApportVersion: 2.17.2-0ubuntu1.7 > Architecture: amd64 > CupsErrorLog: >E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateAccess on > line 88 of /etc/cups/cupsd.conf. >E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateValues on > line 89 of /etc/cups/cupsd.conf. >E [15/Nov/2015:07:45:08 -0800] Unknown directive > SubscriptionPrivateAccess on line 90 of /etc/cups/cupsd.conf. >E [15/Nov/2015:07:45:08 -0800] Unknown directive > SubscriptionPrivateValues on line 91 of /etc/cups/cupsd.conf. > Date: Sun Nov 15 09:07:50 2015 > Dependencies: > > DpkgTerminalLog: >dpkg: error processing package cups-common (--configure): > package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > DuplicateSignature: package:cups-common:2.0.2-1ubuntu3.2:package is in a > very bad inconsistent state; you should reinstall it before attempting > configuration > ErrorMessage: package is in a very bad inconsistent state; you should > reinstall it before attempting configuration > InstallationDate: Installed on 2015-10-10 (35 days ago) > InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) > Lpstat: device for Samsung-M288x-Series: > dnssd://Samsung%20M288x%20Series%20(SEC30CDA7334F8A)._printer._tcp.local/ > MachineType: MSI MS-7693 > PackageArchitecture: all > Papersize: letter > PpdFiles: Samsung-M288x-Series: Samsung M288x Series PXL > ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed > root=UUID=e699cd80-60f5-41c8-9840-87a0884cec4a ro quiet splash vt.handoff=7 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed > root=UUID=e699cd80-60f5-41c8-9840-87a0884cec4a ro quiet splash vt.handoff=7 > RelatedPackageVersions: >dpkg 1.17.25ubuntu1 >apt 1.0.9.7ubuntu4.2 > SourcePackage: cups > Title: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: > package is in a very bad inconsistent state; you should reinstall it > before attempting configuration > UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 05/12/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: V22.3 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: 970 GAMING (MS-7693) > dmi.board.vendor: MSI > dmi.board.version: 4.0 > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: MSI > dmi.chassis.version: 4.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrV22.3:bd05/12/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0: > dmi.product.name: MS-7693 > dmi.product.version: 4.0 > dmi.sys.vendor: MSI > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1516410/+subscriptions > -- 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/1516410 Title: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in cups package in Ubuntu: Expired Bug description: This problem is strange. I keep seeing it after I have force installs of the upgrades and updates. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: cups-common 2.0.2-1ubuntu3.2 ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7 Uname: Linux 3.19.0-33-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CupsErrorLog: E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateAccess on line 88 of /etc/cups/cupsd.conf. E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateValues on line 89 of /etc/cups/cupsd.conf. E [15/Nov/2015:07:45:08 -0800] Unknown directive SubscriptionPrivateAccess on line
[Touch-packages] [Bug 1470730] Re: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work
Weird, today, again I plugged in my headphones in the docker and now, the internal speakers stay silent. It's weird because I didn't save the override settings permanently. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1470730 Title: [HP EliteBook 840 G2, Realtek ALC3228, HP UltraSlim Dock 2013] Line in/Line out on docking station doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: When I plug in external speakers to line in/line out combo on the laptop the internal speakers are turned off but when I plug the speakers into the docking station (HP UltraSlim Dock 2013 EURO, D9Y32AA) music keeps playing in the internal speakers. Similar behaviour (nothing happens) is experienced with microphone connected to line in on docking station. ### Expected behaviour Plugging in external speakers to docking station should turn off sound from laptop internal speakers. Plugging in microphone to line in on docking station should switch from "internal microphone" to "microphone" in Ubuntu sound settings. ### Current behaviour Sound keeps playing in internal speakers when plugging in external speakers to docking station. Plugging in microphone to line in on docking station, nothing happens. ### Hardware Laptop: HP EliteBook 840 G2 Product number: H9W19EA#AK8 Docking station: HP UltraSlim Dock 2013 EURO Product number: D9Y32AA ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8 Uname: Linux 3.19.0-21-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: chol 2001 F pulseaudio /dev/snd/controlC0: chol 2001 F pulseaudio /dev/snd/controlC1: chol 2001 F pulseaudio CurrentDesktop: Unity Date: Thu Jul 2 08:16:15 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-06-05 (26 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Right Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HP EliteBook 840 G2, Realtek ALC3228, Black Headphone Out, Right] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2015 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: M71 Ver. 01.04 dmi.board.name: 2216 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 96.54 dmi.chassis.asset.tag: 5CG5093YZ7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrM71Ver.01.04:bd02/24/2015:svnHewlett-Packard:pnHPEliteBook840G2:pvrA3009D410303:rvnHewlett-Packard:rn2216:rvrKBCVersion96.54:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G2 dmi.product.version: A3009D410303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1470730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798533] Re: Drucker
** Package changed: xorg (Ubuntu) => gnome-control-center (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/1798533 Title: Drucker Status in gnome-control-center package in Ubuntu: New Bug description: Der Drucker kann nicht installiert werden. Filter fehlt (Fehlermeldung) ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Thu Oct 18 08:47:12 2018 DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d] InstallationDate: Installed on 2018-03-08 (223 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6596 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-17 (0 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: LENOVO dmi.bios.version: EKKT25BUS dmi.board.name: Remore CRB dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: IdeaCentre dmi.product.name: 6596 dmi.product.version: Lenovo C445 dmi.sys.vendor: LENOVO 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.1 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 Oct 17 11:04:23 2018 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1798533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798533] [NEW] Drucker
Public bug reported: Der Drucker kann nicht installiert werden. Filter fehlt (Fehlermeldung) ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Thu Oct 18 08:47:12 2018 DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d] InstallationDate: Installed on 2018-03-08 (223 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6596 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-17 (0 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: LENOVO dmi.bios.version: EKKT25BUS dmi.board.name: Remore CRB dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: IdeaCentre dmi.product.name: 6596 dmi.product.version: Lenovo C445 dmi.sys.vendor: LENOVO 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.1 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 Oct 17 11:04:23 2018 xserver.configfile: default xserver.devices: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.8 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1798533 Title: Drucker Status in xorg package in Ubuntu: New Bug description: Der Drucker kann nicht installiert werden. Filter fehlt (Fehlermeldung) ? ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CompositorRunning: None Date: Thu Oct 18 08:47:12 2018 DistUpgraded: 2018-10-17 18:15:17,451 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess »./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 7340] [1002:9808] (prog-if 00 [VGA controller]) Subsystem: Lenovo Wrestler [Radeon HD 7340] [17aa:365d] InstallationDate: Installed on 2018-03-08 (223 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: LENOVO 6596 ProcEnviron: PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=ae1dcc47-b3c8-4069-bedd-acb8c12fdbfb ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-10-17 (0 days ago) dmi.bios.date: 08/28/2012 dmi.bios.vendor: LENOVO dmi.bios.version: EKKT25BUS dmi.board.name: Remore CRB dmi.board.vendor: LENOVO dmi.board.version: Win8 STD MM DPK IPG dmi.chassis.type: 13 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrEKKT25BUS:bd08/28/2012:svnLENOVO:pn6596:pvrLenovoC445:rvnLENOVO:rnRemoreCRB:rvrWin8STDMMDPKIPG:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.: dmi.product.family: IdeaCentre
Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail
Hy, in this moment I can't update my laptop or install any package or program Greetings El mié., 17 oct. 2018 23:11, Brian Murray escribió: > ** Tags added: bugpattern-written > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1792241). > https://bugs.launchpad.net/bugs/1773859 > > Title: > upgrades to 18.04 fail > > Status in systemd package in Ubuntu: > Fix Released > Status in systemd-shim package in Ubuntu: > Won't Fix > Status in systemd source package in Bionic: > In Progress > Status in systemd-shim source package in Bionic: > Won't Fix > Status in systemd source package in Cosmic: > Fix Released > Status in systemd-shim source package in Cosmic: > Won't Fix > > Bug description: > [Impact] > >* Some systems fail to upgrade due to conflicts between systemd and > the (now removed from the archive) systemd-shim / upstart. > >* Instead of trying to work out what's the problem in ordering / > removal of diverts, ensure that systemd is never unpacked whilst > systemd-shim/upstart are still on disk. Thus declare conflicts against > systemd-shim/upstart packages in systemd package. > > [Test Case] > >* monitor drop-off of upgrades with below reported problem > >* Check that it is possible to upgrade to bionic's libpam-systemd > from xenial with systemd-shim installed on xenial. > > [Regression Potential] > >* systemd-shim/upstart are both removed and not supported in bionic, > thus forcing their removal via conflicts should bring the system into > an expected state. > > [Other Info] > >* original bug report > > > $ sudo apt upgrade > Reading package lists... Done > Building dependency tree > Reading state information... Done > Calculating upgrade... Done > The following packages will be REMOVED: > systemd-shim > 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. > 1 not fully installed or removed. > After this operation, 71.7 kB disk space will be freed. > Do you want to continue? [Y/n] y > (Reading database ... 63 files and directories currently installed.) > 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): >subprocess installed post-removal script returned error exit status 2 > Errors were encountered while processing: >systemd-shim > E: Sub-process /usr/bin/dpkg returned an error code (1) > > Commenting out the dpkg-divert in systemd-shim's postrm solved this > for me and I was about to continue the upgrade. > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions > -- 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/1773859 Title: upgrades to 18.04 fail Status in systemd package in Ubuntu: Fix Released Status in systemd-shim package in Ubuntu: Won't Fix Status in systemd source package in Bionic: In Progress Status in systemd-shim source package in Bionic: Won't Fix Status in systemd source package in Cosmic: Fix Released Status in systemd-shim source package in Cosmic: Won't Fix Bug description: [Impact] * Some systems fail to upgrade due to conflicts between systemd and the (now removed from the archive) systemd-shim / upstart. * Instead of trying to work out what's the problem in ordering / removal of diverts, ensure that systemd is never unpacked whilst systemd-shim/upstart are still on disk. Thus declare conflicts against systemd-shim/upstart packages in systemd package. [Test Case] * monitor drop-off of upgrades with below reported problem * Check that it is possible to upgrade to bionic's libpam-systemd from xenial with systemd-shim installed on xenial. [Regression Potential] * systemd-shim/upstart are both removed and not supported in bionic, thus forcing their removal via conflicts should bring the system into an expected state. [Other Info] * original bug report $ sudo apt upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED: systemd-shim 0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 71.7 kB disk space will be freed. Do you want to continue? [Y/n] y (Reading database ...
