[Touch-packages] [Bug 1832060] [NEW] Backport "add an option that allows rewinds to be disabled"
Public bug reported: PulseAudio git master added an option that allows rewinds to be disabled. I backported it to v12.2, the patch is here: https://gitlab.com/nixtux-packaging/pulseaudio- ubuntu/blob/master/pulseaudio-12.2/debian/patches/0001-Backport-add-an- option-that-allows-rewinds-to-be-dis.patch This will help PulseEffects that is being packaged in https://bugs.launchpad.net/ubuntu/+bug/1832059 by fixing crackling sound when changing the volume level. It would be good to have this patches applied in Eoan if PulseAudio 13.0 does not get to it. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Patch added: "0001-Backport-add-an-option-that-allows-rewinds-to-be-dis.patch" https://bugs.launchpad.net/bugs/1832060/+attachment/5269487/+files/0001-Backport-add-an-option-that-allows-rewinds-to-be-dis.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1832060 Title: Backport "add an option that allows rewinds to be disabled" Status in pulseaudio package in Ubuntu: New Bug description: PulseAudio git master added an option that allows rewinds to be disabled. I backported it to v12.2, the patch is here: https://gitlab.com/nixtux-packaging/pulseaudio- ubuntu/blob/master/pulseaudio-12.2/debian/patches/0001-Backport-add- an-option-that-allows-rewinds-to-be-dis.patch This will help PulseEffects that is being packaged in https://bugs.launchpad.net/ubuntu/+bug/1832059 by fixing crackling sound when changing the volume level. It would be good to have this patches applied in Eoan if PulseAudio 13.0 does not get to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1832060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1636708] Re: ifup -a does not start dependants last, causes deadlocks with vlans/bonding
[Expired for ifupdown (Ubuntu Xenial) because there has been no activity for 60 days.] ** Changed in: ifupdown (Ubuntu Xenial) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1636708 Title: ifup -a does not start dependants last, causes deadlocks with vlans/bonding Status in ifupdown package in Ubuntu: Incomplete Status in ifupdown source package in Xenial: Expired Bug description: This is a problem I've been struggling with since moving to 16.04.1 from 14.04 (fresh install) I don't believe this problem affected 14.04. I have used an almost identical interfaces file on 14.04 without problem. On 16.04.1, however, 9/10 boots would hang during network configuration and leave the network incorrectly configured. When calling "ifup -a" all candidate interfaces appear to be started in parallel leading to collisions with locks. This causes hanging (until timeout) during booting and the network interfaces left incorrectly configured Imagine this /etc/network/interfaces auto eno1 bond0 bond0.1 iface eno1 inet manual bond-master bond0 iface bond0 inet manual bond-slaves eno1 bond-mode 4 bond-lacp-rate 1 bond-miimon 100 bond-updelay200 bond-downdelay 200 iface bond0.5 inet dhcp vlan-raw-device bond0 eno1 -> bond0 -> bond0.5 -> dhcp When calling "ifup -a" at boot time all three interfaces are started at the same time. bond0 and bond0.5 both attempt to share the same lock file: /run/network/ifstate.bond0 If bond0 wins the race, the system will start correctly (1/10): * bond0 starts and creates the bond0 device and the ifenslave.bond0 file to indicate the bond is ready * eno1 polls for the ifenslave.bond0 file, when it appears it attaches eno1 to bond0 * bond0 finishes and releases the lock * bond0.5 now acquires the lock. * bond0.5 starts dhclient, which can talk to the network and configure the interface If, however, bond0.2 wins the lock race, the system will hang at boot (5 mins) and fail to set up the network. * bond0.5 is awarded the ifstate.bond0 lockfile * bond0.5 starts dhclient waiting to hear from the network * bond0 is blocked, so bond0 is not created nor is the bond0.ifenslave file * eno1 polls but never finds the ifenslave.bond0 file so never attaches to bond0 * bond0.5's dhclient is trying to talk to a disconnected network and never receives an answer ! bond0.5 is stuck running dhclient ! bond0 is stuck waiting for bond0.5 to finish ! eno1 is stuck waiting for bond0 to create the ifenslave.bond0 file I believe ifup should start interfaces (that share lock files) in dependant order. The most basic interface must be awarded the lock over its dependants. In this case: 1 eno1 2 bond0 3 bond0.5 but never: 1 eno1 2 bond0.5 3 bond0 As a work arouund, in /etc/network/interfaces -auto eno1 bond0 bond0.1 +auto eno1 bond0 +allow-bond bond0.1 And also in /lib/systemd/system/networking.service ExecStart=/sbin/ifup -a --read-environment +ExecStart=/sbin/ifup -a --allow=bond --read-environment ExecStop=/sbin/ifdown -a --read-environment Then run: systemctl dameon-reload This causes all "auto" interfaces to start then, when they've completed, all allow-bond interfaces to start. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ifupdown 0.8.10ubuntu1.1 [modified: lib/systemd/system/networking.service] ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Wed Oct 26 06:32:57 2016 InstallationDate: Installed on 2016-10-24 (1 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.init.networking.conf: [modified] mtime.conffile..etc.init.networking.conf: 2016-10-26T04:52:05.750927 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1636708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1823532] Re: Não Entra no google. E as vezes fica com a tela azul
[Expired for evolution-data-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evolution-data-server (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1823532 Title: Não Entra no google. E as vezes fica com a tela azul Status in evolution-data-server package in Ubuntu: Expired Bug description: As vezes a tela fica azul ou preta impossibilita acessar as funções e tela e preta . As não entra no google e nas outras funções, e parece algo relacionado ao software que impedi e baixar e atualiza . ProblemType: Package DistroRelease: Ubuntu 16.04 Package: evolution-data-server 3.18.5-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Apr 7 09:39:51 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 ErrorMessage: problemas de dependência - deixando desconfigurado InstallationDate: Installed on 2019-02-24 (41 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.29ubuntu0.1 SourcePackage: evolution-data-server Title: package evolution-data-server 3.18.5-1ubuntu1.1 failed to install/upgrade: problemas de dependência - deixando desconfigurado UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1823532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
** Description changed: [Impact] TBD [Test Case] TBD [Regression Potential] + The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] + https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-online.debdiff;msg=22 [Discussion] [Original Report] - - My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is - managed manually in /etc/network/interfaces. + My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq 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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] TBD [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
** Description changed: + [Impact] + TBD + + [Test Case] + TBD + + [Regression Potential] + + [Fix] + + [Discussion] + + [Original Report] + My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq 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 dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: [Impact] TBD [Test Case] TBD [Regression Potential] The fix is just configuring the order of service startup, so is unlikely to create any regressions. Things to watch would be service related misbehaviors and general availability of the dnsmasq functionality. [Fix] https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=774970;filename=774970-network-online.debdiff;msg=22 [Discussion] [Original Report] My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file
This bug was fixed in the package initramfs-tools - 0.133ubuntu5 --- initramfs-tools (0.133ubuntu5) eoan; urgency=medium * Correctly serialize previously absent static ip configuration (declared as protocol 'none' by ipconfig) into runtime netplan yaml. LP: #1832042 * Adjust testsuite sample file to match reality * Set executable bit on resume script in local-premount -- Dimitri John Ledkov Fri, 07 Jun 2019 21:56:33 +0100 ** Changed in: initramfs-tools (Ubuntu Eoan) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832042 Title: static ip= address configuration does not end up in netplan file Status in initramfs-tools package in Ubuntu: Fix Released Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Status in initramfs-tools source package in Cosmic: New Status in initramfs-tools source package in Disco: New Status in initramfs-tools source package in Eoan: Fix Released Bug description: static ip= address configuration does not end up in netplan file klibc ipconfig process ip=...:$proto and dumps the state into a file, which is then parsed to generate runtime netplan configs. For static ip configuration ipconfig parses $proto values "off" "none" "static" as the same PROTO_NONE and encodes it as PROTO="none" in the serialized state file. The function that dumps ip data (_declare_ip_info()) has keys only values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig) or "off" (as valid by the kernel). This means that netplan files generated in /run for static ip configuration are incomplete. Imho we should accept "off" "none" "static" as all valid PROTO settings for static ip configuration. [Impact] * `netplan apply` will not reapply static ip configuration as declared in ip= kernel cmdline. [Test Case] * boot with static ip configuration in the kernel cmdline, e.g. ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none Check that /run/netplan/*.yaml contains addresses stanzas. [Regression Potential] * Runtime netplan configuration will now be more complete. Meaning that static ip addresses will now persist across `netplan apply` / downing, and reupping an interface. Whilst it was intended for static ip addresses to be there, it might be unexpected that they actually work properly now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792189] Re: linux-firmware does not depend on initramfs-tools
I.e. instead of the current $ cat debian/linux-firmware.postinst #!/bin/sh set -e if [ -x /usr/sbin/update-initramfs ]; then /usr/sbin/update-initramfs -u -k all fi #DEBHELPER# It should do instead $ cat cat debian/linux-firmware.triggers activate-noawait update-initramfs ** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => Won't Fix ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- 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/1792189 Title: linux-firmware does not depend on initramfs-tools Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: New Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1792189] Re: linux-firmware does not depend on initramfs-tools
Normally, postinst should only hint a trigger to run initramfs update. And not force creation of an initrd. -- 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/1792189 Title: linux-firmware does not depend on initramfs-tools Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux-firmware package in Ubuntu: New Bug description: In bug #1646197 the linux-firmware.postinst was added to call update- initramfs (provided by initramfs-tools. If the initramfs-tools package is not installed the installation of linux-firmware will fail. Recreate: sudo apt-get purge --assume-yes '^linux-.*' 'linux-base+' initramfs* sudo apt-get install --assume-yes linux-generic Result: Setting up linux-modules-4.15.0-34-generic (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34 (4.15.0-34.37) ... Setting up linux-headers-4.15.0-34-generic (4.15.0-34.37) ... Setting up initramfs-tools-bin (0.130ubuntu3.3) ... Setting up linux-firmware (1.173.1) ... update-initramfs: Generating /boot/initrd.img-4.15.0-1021-kvm /usr/sbin/mkinitramfs: 66: .: Can't open /etc/initramfs-tools/initramfs.conf update-initramfs: failed for /boot/initrd.img-4.15.0-1021-kvm with 2. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 2 ... Errors were encountered while processing: linux-firmware linux-image-generic linux-generic E: Sub-process /usr/bin/dpkg returned an error code (1) Impact: Builds of minimized images start with an image that has the linux-kvm kernel but lack initramfs-tools. Derivative builds that require a different kernel, linux-generic for example, will purge the existing kernel and install the correct kernel which could pull in linux-firmware and initramfs-tools. In that case the builds fail unless initramfs-tools is installed prior to kernel installation as a workaround for this missing package dependency. This has been recreated on cosmic and bionic, a fix is desired on each. (I was unable to recreate on Xenial but that package lacks the dependency as well). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1792189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/368566 -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file
** Merge proposal unlinked: https://code.launchpad.net/~xnox/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/368566 -- 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/1832042 Title: static ip= address configuration does not end up in netplan file Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Status in initramfs-tools source package in Cosmic: New Status in initramfs-tools source package in Disco: New Status in initramfs-tools source package in Eoan: New Bug description: static ip= address configuration does not end up in netplan file klibc ipconfig process ip=...:$proto and dumps the state into a file, which is then parsed to generate runtime netplan configs. For static ip configuration ipconfig parses $proto values "off" "none" "static" as the same PROTO_NONE and encodes it as PROTO="none" in the serialized state file. The function that dumps ip data (_declare_ip_info()) has keys only values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig) or "off" (as valid by the kernel). This means that netplan files generated in /run for static ip configuration are incomplete. Imho we should accept "off" "none" "static" as all valid PROTO settings for static ip configuration. [Impact] * `netplan apply` will not reapply static ip configuration as declared in ip= kernel cmdline. [Test Case] * boot with static ip configuration in the kernel cmdline, e.g. ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none Check that /run/netplan/*.yaml contains addresses stanzas. [Regression Potential] * Runtime netplan configuration will now be more complete. Meaning that static ip addresses will now persist across `netplan apply` / downing, and reupping an interface. Whilst it was intended for static ip addresses to be there, it might be unexpected that they actually work properly now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1531184] Re: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet
** Summary changed: - dnsmasq doesn't start on boot because its interface isn't up yet + [SRU] dnsmasq doesn't start on boot because its interface isn't up yet -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1531184 Title: [SRU] dnsmasq doesn't start on boot because its interface isn't up yet Status in One Hundred Papercuts: Confirmed Status in dnsmasq package in Ubuntu: Confirmed Status in dnsmasq package in Debian: New Bug description: My dnsmasq instance uses "interface=br-vz0" and the interface br-vz0 is managed manually in /etc/network/interfaces. During boot, dnsmasq is started before br-vz0 is created and this causes dnsmasq to exit: Jan 5 08:56:16 simon-laptop dnsmasq[1008]: dnsmasq: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: unknown interface br-vz0 Jan 5 08:56:16 simon-laptop dnsmasq[1008]: FAILED to start up Jan 5 08:56:17 simon-laptop NetworkManager[937]: NetworkManager (version 1.0.4) is starting... ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: interface-parser: parsing file /etc/network/interfaces ... Jan 5 08:56:18 simon-laptop NetworkManager[937]: found bridge ports none for br-vz0 Jan 5 08:56:18 simon-laptop NetworkManager[937]: adding bridge port none to eni_ifaces Jan 5 08:56:18 simon-laptop NetworkManager[937]: management mode: unmanaged ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: dnsmasq 2.75-1 ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3 Uname: Linux 4.3.0-5-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 5 09:53:30 2016 PackageArchitecture: all SourcePackage: dnsmasq UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1531184/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4
Hello Iain, or anyone else affected, Accepted gst-rtsp-server1.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gst-rtsp- server1.0/1.14.4-1~ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-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: gst-rtsp-server1.0 (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1829366 Title: [SRU] Bugfix release 1.14.4 Status in gst-libav1.0 package in Ubuntu: Fix Released Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Released Status in gst-plugins-good1.0 package in Ubuntu: Fix Released Status in gst-plugins-ugly1.0 package in Ubuntu: Fix Released Status in gst-python1.0 package in Ubuntu: Fix Released Status in gst-rtsp-server1.0 package in Ubuntu: Fix Released Status in gstreamer-editing-services1.0 package in Ubuntu: Fix Released Status in gstreamer-vaapi package in Ubuntu: Fix Released Status in gstreamer1.0 package in Ubuntu: Fix Released Status in gst-libav1.0 source package in Bionic: In Progress Status in gst-plugins-bad1.0 source package in Bionic: In Progress Status in gst-plugins-base1.0 source package in Bionic: In Progress Status in gst-plugins-good1.0 source package in Bionic: In Progress Status in gst-plugins-ugly1.0 source package in Bionic: In Progress Status in gst-python1.0 source package in Bionic: In Progress Status in gst-rtsp-server1.0 source package in Bionic: Fix Committed Status in gstreamer-editing-services1.0 source package in Bionic: In Progress Status in gstreamer-vaapi source package in Bionic: In Progress Status in gstreamer1.0 source package in Bionic: In Progress Bug description: [ Description ] We should keep up with GStreamer's bugfix releases in the 1.14 series that 18.04 shipped with. [ QA and testing ] Play a range of videos in Totem. Play a range of audio tracks in Rhythmbox. Try to stream audio and/or video. Try to install a missing codec. In all cases, make sure that everything which worked before still works. [ Regression potential ] If one of the fixes is bad then it might break video or audio playback, or could crash any application that tries to use gstreamer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1730908] Re: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/
Hello Robert, thanks for this; could you please file this bug against the man-db package, and mention that this needs to be adjusted similar to https://usn.ubuntu.com/4008-2/ ? Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1730908 Title: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux- gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Status in apparmor package in Ubuntu: Expired Bug description: Since I installed Ubuntu 17.10 I cannot print anymore. The only thing I see in the logs are many lines like the following: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 I'm not sure it is the cause of my problems, but there is at least a problem with apparmor's configuration in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1730908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832054] Re: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832054 Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: erro ao atualizar ubuntu 14.04 para 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 7 17:33:32 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-02 (97 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-06-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832054] [NEW] package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: erro ao atualizar ubuntu 14.04 para 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 7 17:33:32 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-02 (97 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-06-07 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832054 Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: erro ao atualizar ubuntu 14.04 para 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.21 ProcVersionSignature: Ubuntu 3.13.0-52.86+bdw1-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Fri Jun 7 17:33:32 2019 Dependencies: DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2019-03-02 (97 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: initramfs-tools Title: package linux-firmware 1.157.21 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2019-06-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
Could you then follow the instructions of the comment #7 and comment #9? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829913 Title: openconnect VPN is not propagating internal DNS anymore Status in network-manager package in Ubuntu: Incomplete Bug description: Openconnect VPN stopped propagating DNSes to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1730908] Re: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/
[35965.264754] audit: type=1400 audit(1559942671.706:29): apparmor="DENIED" operation="open" profile="man_groff" name="/usr/local/lib64/libgcc_s.so.1" pid=17962 comm="troff" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1730908 Title: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux- gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Status in apparmor package in Ubuntu: Expired Bug description: Since I installed Ubuntu 17.10 I cannot print anymore. The only thing I see in the logs are many lines like the following: [ 1549.847151] audit: type=1400 audit(1510129355.497:61): apparmor="DENIED" operation="file_mmap" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.14/modules/network_networkmanager.so" pid=2062 comm="evince" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 I'm not sure it is the cause of my problems, but there is at least a problem with apparmor's configuration in Ubuntu 17.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1730908/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
Hi. Doesn't solve an issue for me. No traffic comes via port 53 when making a dig for a private network's host. ** Attachment added: "Screenshot from 2019-06-08 00-51-17.png" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+attachment/5269449/+files/Screenshot%20from%202019-06-08%2000-51-17.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829913 Title: openconnect VPN is not propagating internal DNS anymore Status in network-manager package in Ubuntu: Incomplete Bug description: Openconnect VPN stopped propagating DNSes to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/bash/+git/bash/+merge/368573 ** Merge proposal linked: https://code.launchpad.net/~bryce/ubuntu/+source/bash/+git/bash/+merge/368574 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: In Progress Status in bash source package in Cosmic: In Progress Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1822776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1822776] Re: Apply Bash 4.4.20 to fix cpu spinning on built-in wait
** Description changed: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. + [Test Case] - [Test Case] + A PPA with the proposed fix included is at: + + https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 + + Install the PPA with the fix via: + + sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 + sudo apt-get update + sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. - [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will be generated in rare cases, but nothing should depend on how pids are generated, as the behavior is not specified to be anything but random. The patch adds a new warning message, "bgp_delete: LOOP: psi (%d) == storage[psi].bucket_next", but this only shows when the original bug would have been triggered. Using 'apt-get source bash' to get the original source version, I created a deb that includes the 4.4.20 patch and have been running it since April 2nd. The 100% CPU spinning is solved, and no other regressions have been observed. Ubuntu 18.04 is already at 4.4.19, which is one patch level behind, so this involves linearly progressing to the next version (so not skipping patches). - [Fix] Official patch to fix, and to bump to 4.4.20: http://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 The newest Ubuntu tar.xz with patches I could find at: http://archive.ubuntu.com/ubuntu/pool/main/b/bash/ also didn't have the 4.4.20 patch, so it seems no Ubuntu release has the fix yet. Although not completely sure, this problem seems to have been introduced in the 4.4 version of Bash, so in term of LTS versions, 18.04 and up are affected. - [Original Report] Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops when spawning sub processes and waiting for them. There is a fix: https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020 Our application started being affected (locking up) by this since migrating from Ubuntu 14.04 to 18.04. Ubuntu 14.04 has bash 4.3.11(1), Ubuntu 18.04 has bash 4.4.19 (that is, when running 'bash --version', because of their unusual versions as patches, apt shows it as 4.4.18-2ubuntu1). The 4.4-020 version needs to be included. I think it's actually quite critical. A justification for including the fix would be that a standard language feature in a script language is broken, and that it's indeterminate when it breaks. Considering the wide spread use of bash, I'm surprised not more people have reported issues. My and a client started having issues with independently of each other very soon after upgrading to an affected version. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1822776 Title: Apply Bash 4.4.20 to fix cpu spinning on built-in wait Status in bash package in Ubuntu: Fix Released Status in bash source package in Bionic: In Progress Status in bash source package in Cosmic: In Progress Bug description: [Impact] Long running bash loops that create and reap processes will crash, hanging at 100% CPU. [Test Case] A PPA with the proposed fix included is at: https://launchpad.net/~bryce/+archive/ubuntu/bash-sru-19-010-1 Install the PPA with the fix via: sudo add-apt-repository ppa:bryce/bash-sru-19-010-1 sudo apt-get update sudo apt-get install bash Run this loop for a few days/weeks: #!/bin/bash while true; do sleep 0.5 & wait done It will eventually cause the 'wait' statement to hang, consuming 100% after some indeterminate amount of time, dependent on how fast PIDs are cycled in the machine. The Bash bug report mentions longer running loops, but it seems hash collisions are the cause, meaning it's just a matter of chance, influenced by how fast PIDs are cycled on the machine. [Regression Potential] The fix has been reviewed and accepted upstream. The patch adds a test at time of pid determination for if the pid is already in use and if so, skip it and pick a different one. This does change behavior slightly in that different pid numbers will
[Touch-packages] [Bug 1829913] Re: openconnect VPN is not propagating internal DNS anymore
The SRU for systemd has arrived in bionic-proposed (see bug 1754671). Could you make sure that you have installed BOTH the network-manager and systemd SRUs from bionic-proposed (to make sure that I did not perhaps do something wrong with the systemd update in my PPA). Versions should be: network-manager: 1.10.14-0ubuntu2 systemd: 237-3ubuntu10.22 Note that these packages are only in bionic-proposed, not in the official updates, due to the fact that we need to sort out the regressions. So follow the instructions of installing the proposed packages in bug 1754671, comment #28 and comment #49. Does this combination solve your problem? Please reboot to make sure that everything gets replaced by the newer versions. If this still does not help, please follow my instructions in this bug report, comment #7 and comment #9. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829913 Title: openconnect VPN is not propagating internal DNS anymore Status in network-manager package in Ubuntu: Incomplete Bug description: Openconnect VPN stopped propagating DNSes to the system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
It was quite difficult to backport this even to 18.04, as I had to change the code in several places to make it compile. That was backporting only two releases back (5.11 → 5.9). 16.04 has 5.5 so that sounds impossible, however patches are welcome. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Status in qtbase-opensource-src package in Debian: Fix Released Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1803203] Re: Support preferred_lft for IPv6 addresses
@rlaager I've started a PR discussion on Netplan.io's Github with your proposed changes as they seemed the best way forward for now. I don't expect this to get merged right away, as the maintainers might want to discuss the changes to the schema in further detail. In any case, this should at least start a discussion on getting this fixed in upstream netplan. https://github.com/CanonicalLtd/netplan/pull/89 -- 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/1803203 Title: Support preferred_lft for IPv6 addresses Status in netplan: New Status in netplan.io package in Ubuntu: In Progress Status in systemd package in Ubuntu: Fix Released Bug description: There doesn't currently seem to be any way to set the preferred_lft of an IPv6 address. With the "ip" command it might be, for example: # ip address add 2001:db8::2/32 dev eth0 preferred_lft 0 In a systemd unit file it might be: [Match] Name=eth0 [Network] Address=2001:db8::2/32 Gateway=2001:db8::1/32 PreferredLifetime=0 but I can't find any way to express this with netplan. This is commonly used for per-service IP addresses that should never be used as source addresses for outgoing traffic. To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1803203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829566] Re: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns
The SRU for systemd has arrived in bionic-proposed (see bug 1754671). Could you make sure that you have installed BOTH the network-manager and systemd SRUs from bionic-proposed (to make sure that I did not perhaps do something wrong with the systemd update in my PPA). Versions should be: network-manager: 1.10.14-0ubuntu2 systemd: 237-3ubuntu10.22 Does this combination solve your problem? Please reboot to make sure that everything gets replaced by the newer versions. If this still does not help, please follow my instructions in comment #8 and comment #10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829566 Title: network-manager 1.10.14-0ubuntu2 ignores systemd-resolved configured dns Status in network-manager package in Ubuntu: Incomplete Status in network-manager source package in Bionic: Incomplete Bug description: On 18.04.2 the `upgrade network-manager:amd64 1.10.6-2ubuntu1.1 1.10.14-0ubuntu2` lead to scoped DNS servers defined in `/etc/systemd/resolved.conf.d/*.conf` being ignored. Downgrading with `sudo apt-get install network- manager=1.10.6-2ubuntu1.1` has resolved the issue for now. Example systemd-resolved conf: [Resolve] Cache=no DNS=127.0.0.54 Domains=~.local.org.com Where 127.0.0.54:53 is bound to a dnsmasq server capable of resolving queries in that subdomain. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829838] Re: 1.10.14-0ubuntu2 breaks DNS propagation from VPN
The SRU for systemd has arrived in bionic-proposed (see bug 1754671). Could you make sure that you have installed BOTH the network-manager and systemd SRUs from bionic-proposed (to make sure that I did not perhaps do something wrong with the systemd update in my PPA). Versions should be: network-manager: 1.10.14-0ubuntu2 systemd: 237-3ubuntu10.22 Does this combination solve your problem? Please reboot to make sure that everything gets replaced by the newer versions. If this still does not help, please follow my instructions in comment #8 and comment #10. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1829838 Title: 1.10.14-0ubuntu2 breaks DNS propagation from VPN Status in network-manager package in Ubuntu: Incomplete Bug description: I have an OpenVPN connection, and I use the update-systemd-resolved to correctly fetch the DNS from the VPN. The issue arose updating my Ubuntu 18.04: the script is no longer invoked, and even invoking it manually (sudo openvpn myfile.ovpn) does not work anymore, even if in that case systemd-resolve --status shows the new DNS on the interface correctly. As suggested in https://bugs.launchpad.net/ubuntu/+source/network- manager/+bug/120/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832042] Re: static ip= address configuration does not end up in netplan file
** Merge proposal linked: https://code.launchpad.net/~xnox/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+merge/368566 -- 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/1832042 Title: static ip= address configuration does not end up in netplan file Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Status in initramfs-tools source package in Cosmic: New Status in initramfs-tools source package in Disco: New Status in initramfs-tools source package in Eoan: New Bug description: static ip= address configuration does not end up in netplan file klibc ipconfig process ip=...:$proto and dumps the state into a file, which is then parsed to generate runtime netplan configs. For static ip configuration ipconfig parses $proto values "off" "none" "static" as the same PROTO_NONE and encodes it as PROTO="none" in the serialized state file. The function that dumps ip data (_declare_ip_info()) has keys only values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig) or "off" (as valid by the kernel). This means that netplan files generated in /run for static ip configuration are incomplete. Imho we should accept "off" "none" "static" as all valid PROTO settings for static ip configuration. [Impact] * `netplan apply` will not reapply static ip configuration as declared in ip= kernel cmdline. [Test Case] * boot with static ip configuration in the kernel cmdline, e.g. ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none Check that /run/netplan/*.yaml contains addresses stanzas. [Regression Potential] * Runtime netplan configuration will now be more complete. Meaning that static ip addresses will now persist across `netplan apply` / downing, and reupping an interface. Whilst it was intended for static ip addresses to be there, it might be unexpected that they actually work properly now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832042] [NEW] static ip= address configuration does not end up in netplan file
Public bug reported: static ip= address configuration does not end up in netplan file klibc ipconfig process ip=...:$proto and dumps the state into a file, which is then parsed to generate runtime netplan configs. For static ip configuration ipconfig parses $proto values "off" "none" "static" as the same PROTO_NONE and encodes it as PROTO="none" in the serialized state file. The function that dumps ip data (_declare_ip_info()) has keys only values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig) or "off" (as valid by the kernel). This means that netplan files generated in /run for static ip configuration are incomplete. Imho we should accept "off" "none" "static" as all valid PROTO settings for static ip configuration. [Impact] * `netplan apply` will not reapply static ip configuration as declared in ip= kernel cmdline. [Test Case] * boot with static ip configuration in the kernel cmdline, e.g. ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none Check that /run/netplan/*.yaml contains addresses stanzas. [Regression Potential] * Runtime netplan configuration will now be more complete. Meaning that static ip addresses will now persist across `netplan apply` / downing, and reupping an interface. Whilst it was intended for static ip addresses to be there, it might be unexpected that they actually work properly now. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Cosmic) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Disco) Importance: Undecided Status: New ** Affects: initramfs-tools (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: initramfs-tools (Ubuntu Cosmic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1832042 Title: static ip= address configuration does not end up in netplan file Status in initramfs-tools package in Ubuntu: New Status in initramfs-tools source package in Xenial: New Status in initramfs-tools source package in Bionic: New Status in initramfs-tools source package in Cosmic: New Status in initramfs-tools source package in Disco: New Status in initramfs-tools source package in Eoan: New Bug description: static ip= address configuration does not end up in netplan file klibc ipconfig process ip=...:$proto and dumps the state into a file, which is then parsed to generate runtime netplan configs. For static ip configuration ipconfig parses $proto values "off" "none" "static" as the same PROTO_NONE and encodes it as PROTO="none" in the serialized state file. The function that dumps ip data (_declare_ip_info()) has keys only values for dhcp dhcp4 dhcp6 static. But not "none" (used by ipconfig) or "off" (as valid by the kernel). This means that netplan files generated in /run for static ip configuration are incomplete. Imho we should accept "off" "none" "static" as all valid PROTO settings for static ip configuration. [Impact] * `netplan apply` will not reapply static ip configuration as declared in ip= kernel cmdline. [Test Case] * boot with static ip configuration in the kernel cmdline, e.g. ip=10.245.232.12::10.245.232.1:255.255.255.255:clound01:enc603:none Check that /run/netplan/*.yaml contains addresses stanzas. [Regression Potential] * Runtime netplan configuration will now be more complete. Meaning that static ip addresses will now persist across `netplan apply` / downing, and reupping an interface. Whilst it was intended for static ip addresses to be there, it might be unexpected that they actually work properly now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832042/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1831335] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Local certain, but it how could get gnarled that way? Here is a copy of the lines 78 # Set this to 'yes' to enable PAM authentication,... .(all lines are commented from 78 to 86) 86 # and ChallengeResponseAuthentication to 'no'. 87 Use PAM yes 88 Y I guess I should erase the Y? Isn't it bug if the file corrupts? I never use ssh On Mon, Jun 3, 2019 at 5:30 PM Andreas Hasenack wrote: > Thanks for filing this bug in Ubuntu. > > The error message is: > SSHDConfig: > Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: > /etc/ssh/sshd_config: line 88: Bad configuration option: Y > /etc/ssh/sshd_config: terminating, 1 bad configuration options > > That means that there is a configuration error in your > /etc/ssh/sshd_config file, specifically on line 80. That file isn't > attached to this bug report, so I cannot tell you what is wrong. > > What you should do is open that file, fix what's wrong in line 80, and > then you can issue these commands: > > sudo apt update > sudo apt -f install > > That should retry the operation and this time, if there are no other > errors, it should succeed. > > I'll mark this bug as invalid, since it's a local configuration issue. > If you disagree, then feel free to reopen the bug, but please state the > reasons why you think it's a valid bug, and steps to reproduce it. > > Thanks! > > > ** Changed in: openssh (Ubuntu) >Status: New => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1831335 > > Title: > package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: > subprocess installed post-installation script returned error exit > status 1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1831335/+subscriptions > -- Sincerely, Carlos A. Hevia -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1831335 Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in openssh package in Ubuntu: Invalid Bug description: Can not this be fixed? ProblemType: Package DistroRelease: Ubuntu 16.04 Package: openssh-server 1:7.2p2-4ubuntu2.8 ProcVersionSignature: Ubuntu 4.4.0-148.174-generic 4.4.177 Uname: Linux 4.4.0-148-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 Date: Sat Jun 1 12:03:59 2019 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-05-18 (743 days ago) InstallationMedia: Custom 14.04 - Release i386 RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.31 SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: /etc/ssh/sshd_config: line 88: Bad configuration option: Y /etc/ssh/sshd_config: terminating, 1 bad configuration options SourcePackage: openssh Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2018-10-11 (233 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1831335/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832008] Re: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1832008 Title: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: speaker and headphone jack has no sound ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iksn 1266 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 21:58:35 2019 InstallationDate: Installed on 2019-06-05 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iksn 1266 F pulseaudio Symptom_Jack: Green Headphone Out, Right Symptom_Type: No sound at all Title: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AFU Ver. F.61 dmi.board.name: 143D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 64.16 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AFUVer.F.61:bd04/25/2016:svnHewlett-Packard:pnHPProBook5220m:pvr:rvnHewlett-Packard:rn143D:rvrKBCVersion64.16:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 5220m dmi.product.sku: XN524AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1832008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832007] Re: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at all
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1832007 Title: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: the speaker and headphone jack has no sound ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-21-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iksn 1266 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 21:54:13 2019 InstallationDate: Installed on 2019-06-05 (1 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: iksn 1266 F pulseaudio Symptom_Jack: Green Headphone Out, Right Symptom_Type: No sound at all Title: [HP ProBook 5220m, IDT 92HD81B1X5, Green Headphone Out, Right] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AFU Ver. F.61 dmi.board.name: 143D dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 64.16 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AFUVer.F.61:bd04/25/2016:svnHewlett-Packard:pnHPProBook5220m:pvr:rvnHewlett-Packard:rn143D:rvrKBCVersion64.16:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 5220m dmi.product.sku: XN524AV dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1832007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
Just tested packages from your PPA on amd64. Problem is fixed. Thank you! It would be great if you SRU them to bionic. Does the SRU for 16.04 possible? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Status in qtbase-opensource-src package in Debian: Fix Released Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
@Martin Encrypted root is available in Ubuntu. -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
I will go with dracut syntax here: vlan=: And will only support the .id naming, e.g.: vlan=eth0.1:eth0 As i'd think dracut syntax is more popular, despite being a bit backwards parsing the pairs. With added support, that phydevice is activated as well on s390x. -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805203] Re: libcurl3-gnutls in cosmic breaks git with Azure DevOps
Thanks for pushing this fix through. Unfortunately, I went back to Bionic because of other hard dependencies and am unable to validate. Can others who hit this please try the fix? -- 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/1805203 Title: libcurl3-gnutls in cosmic breaks git with Azure DevOps Status in curl package in Ubuntu: Fix Released Status in curl source package in Cosmic: Fix Committed Bug description: * Impact Git auth fails when trying to work with an Azure DevOps repository * Test case Try to git clone from an Azure DevOps repository using a Personal Access Token The clone should work and not fail on an authentification error * Regression potential The diff is in the curl http code, it would be good to test a few rdepends to make sure they have no regression The version of libcurl3-gnutls in cosmic (7.61.0) causes authentication failures with Azure DevOps. This causes all git operations with the server to fail (eg clone, push, pull). For details see this curl bug: https://github.com/curl/curl/pull/2754 To work around this I downgraded libcurl3-gnutls to the version in bionic (7.58.0) From the curl change list https://curl.haxx.se/changes.html#7_61_1, this issue should be fixed in package version 7.61.1 or above. Request: please upgrade package in cosmic for libcurl3-gnutls to 7.61.1 or above Details: 1 - Ubuntu 18.10 2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others) 3 - Be able to git clone from an Azure DevOps repository using a Personal Access Token 4 - git operations fail to authenticate Thank you, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1805203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382054] Re: Add support for configuring VLAN interfaces in the initrd
** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Dimitri John Ledkov (xnox) ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High ** Changed in: initramfs-tools (Ubuntu) Milestone: None => ubuntu-19.06 -- 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/1382054 Title: Add support for configuring VLAN interfaces in the initrd Status in initramfs-tools package in Ubuntu: Confirmed Bug description: It would be helpful to be able to create VLAN network interfaces in initrd images provided by Ubuntu, based on kernel command line parameters. (i.e. VLAN=eth0.100, ) Some use cases for this feature addition are MAAS users trying to boot machines using a specific VLAN interface. On a specific case we have 2 physical network interfaces, one is plugged into a specific VLAN interface, Since we can specify the network interface on BIOS, the initial PXE boot occurs, but then the installation fails when using the fast-path installer because the specific VLAN is not configured on the ram disk. While we can use the other network interface because is a trunk interface that allows us to use several VLANs, this is not supported on all the network architectures and some security limitations doesn't allows this method. Reference Redhat implementation can be found here: - http://marc.info/?l=initramfs=133767307516594 Reference Suse implementation can be found here: - https://gitorious.org/opensuse/agrafs- mkinitrd/commit/6124f87f3132b6369c0335c319832619a49d0bf7 The command line syntax for this could be something like, similar to Redhat implementation vlan=: For an example: vlan=eth0.2:eth0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1382054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832019] Re: Error when going to 'Keyboard shortcuts' in 'Preferences'
** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Error when going to 'Keyboard shortcuts' in 'Preferences' + Error when going to 'Tools -> Preferences -> Keyboard shortcuts' in Spyder3 ** Description changed: Steps: - - 1. Start spyder - 2. Go to Tools -> Preferences -> Keyboard shortcuts - 3. Error - - Keyboards shortcuts are not accessible. + 1. Install spyder3 (sudo apt install spyder3) + 2. Run spyder3 + 3. Go to Tools -> Preferences -> Keyboard shortcuts + 4. Error + + Keyboard shortcuts are not accessible. Here is the error: - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint - textRect = style.subElementRect(QStyle.SE_ItemViewItemText, options) - TypeError: subElementRect(self, QStyle.SubElement, QStyleOption, QWidget): not enough arguments - Traceback (most recent call last): - File "/usr/lib/python3/dist-packages/spyder/widgets/helperwidgets.py", line 127, in paint
[Touch-packages] [Bug 1810346] Re: VLC interface not displayed correctly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtbase-opensource-src (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1810346 Title: VLC interface not displayed correctly Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: I use vlc on a Dell E-5530 laptop seated on its docking station. The laptop display cover is closed, the output is sent on an external LG TV with 1920x1080. This system has been working flawlessly for many years, resp. under late 14.04 and 16.04. After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - see attachment. This only occurs on the external display ; if I open the cover and use the internal display, there is no problem - except I cannot work on the internal display. regards, J.-Luc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vlc-bin 3.0.4-1ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 23:38:36 2019 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2018-12-19 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810346] Re: VLC interface not displayed correctly
Hi, I think it's the same bug, i got a laptop with a second screen plugged, optimus laptop, nvidia-drivers-390, on the integrated laptop screen, vlc works just fine, but as soon as i drag the vlc window to the second screen GUI elements gets extra zoomed, and unusable ( but i can see some parts of GUI buttons reacting to mouse-over events for exemple). If i drag n drop a video file to the vlc window while on second screen the vlc window gets extra large and still displays extra zoomed GUI elements. note that if i drag the window back the laptop screen it's back to normal. I tried to use QT_AUTO_SCREEN_SCALE_FACTOR=1 and QT_SCALE_FACTOR=1.5 but no change. "cvlc" can play the videos normally on second screen (started from a terminal). (stock Ubuntu 18.04) (note on the screenshots: it's running fluxbox window manager, first screen ends at the right of the bottom bar and system infos displays - then on the right the second screen) ** Attachment added: "Bug screenshot" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+attachment/5269364/+files/2019-06-07-161408_3286x1080_scrot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1810346 Title: VLC interface not displayed correctly Status in qtbase-opensource-src package in Ubuntu: New Bug description: I use vlc on a Dell E-5530 laptop seated on its docking station. The laptop display cover is closed, the output is sent on an external LG TV with 1920x1080. This system has been working flawlessly for many years, resp. under late 14.04 and 16.04. After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - see attachment. This only occurs on the external display ; if I open the cover and use the internal display, there is no problem - except I cannot work on the internal display. regards, J.-Luc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vlc-bin 3.0.4-1ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 23:38:36 2019 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2018-12-19 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1810346] Re: VLC interface not displayed correctly
Another screenshot playing a video... ** Attachment added: "2019-06-07-163228_3286x1080_scrot.png" https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+attachment/5269365/+files/2019-06-07-163228_3286x1080_scrot.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1810346 Title: VLC interface not displayed correctly Status in qtbase-opensource-src package in Ubuntu: New Bug description: I use vlc on a Dell E-5530 laptop seated on its docking station. The laptop display cover is closed, the output is sent on an external LG TV with 1920x1080. This system has been working flawlessly for many years, resp. under late 14.04 and 16.04. After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - see attachment. This only occurs on the external display ; if I open the cover and use the internal display, there is no problem - except I cannot work on the internal display. regards, J.-Luc ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vlc-bin 3.0.4-1ubuntu0.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 2 23:38:36 2019 ExecutablePath: /usr/bin/vlc InstallationDate: Installed on 2018-12-19 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard
Can you please try packages from https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/3731/+packages and see if they fix the issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1831505 Title: Qt5 incorrectly interpret keypresses from remote VNC keyboard Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: New Status in qtbase-opensource-src package in Debian: Fix Released Bug description: Steps to reproduce: 1. Have Ubuntu 18.04 LTS installed with VNC server 2. Connect to Ubuntu 18.04 LTS from other machine with VNC client 3. Launch any Qt5 based application such as `assistant`, `kate` or `retext` 4. Press keyboard combination on VNC client Expected results: all keypresses are recognized successfully Actual results: * produces `1` * produces `5` * <`> produces `p` * and are not working * all letters are messed Note: only Qt applications are affected, the GTK-based work as expected (including Chromium from which I write this bug-report) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: qt5-assistant 5.9.5-0ubuntu1 Uname: Linux 4.4.78-perf+ aarch64 NonfreeKernelModules: wlan exfat ApportVersion: 2.20.9-0ubuntu7 Architecture: armhf CurrentDesktop: MATE Date: Tue Jun 4 00:46:55 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: qttools-opensource-src UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot
I have added a file in /etc/sysctl.d/98-* setting up NFS sysctl parameters and they were not loaded by default until I have added: nfsd to /etc/modules, re-generated the initramfs and rebooted, checking it again, when it worked. ** Changed in: procps (Ubuntu) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: procps (Ubuntu) Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/50093 Title: Some sysctls are ignored on boot Status in procps package in Ubuntu: Confirmed Bug description: Binary package hint: procps /etc/init.d/procps.sh comes too early in the boot process to apply a lot of sysctl's. As it runs before networking modules are loaded and filesystems are mounted, there are quite a lot of commonly-used sysctl's which are simply ignored on boot and produce errors to the console. Simply renaming the symlink from S17 to > S40 probably isn't a great solution, as there are probably folk who want and expect some sysctl's to be applied before filesystems are mounted and so on. However, simply ugnoring something as important as sysctl settings isn't really on. Administrators expect the settings in /etc/sysctl.conf to take effect. One sto-gap solution would be to run sysctl -p twice; once at S17 and once at S41. There may still be some warnings and errors, but everything would be applied. A different, more complex approach might be to re-architect the sysctl configuration into something like; /etc/sysctl.d/$modulename and have the userland module-loading binaries take care of applying them after modules are loaded. Though this may take care of explicitly loaded modules only, I'm not sure. Incidentally, /etc/sysctl.conf still refers to /etc/networking/options, but hasn't that been deprecated? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 645404] Re: Support Private PPAs
> So multiple ssh subprocesses should not be a huge issue, you could after all > use ControlMaster and stuff to reuse the connection. nice, I hadn't used ControlMaster before; that's useful. > That said, it seems reasonable to create a shell script, or a Python script > and > execute that on the remote from stdin. the problem with that, or even with directly calling add-apt-repository on the remote system, is it needs to be called under sudo, and there is no guarantee the sudo call is passwordless on the remote system, so the request for password (stdin/stdout) needs to be provided to the user. I don't see any clean way of doing that, but also piping commands or a script into stdin for execution on the remote side, without significant complications, or pulling in an external lib like paramiko. > That said, it would be an entirely different code path which I think might be > worse > than it maybe not working if the remote is at an older version. Not sure how it would be worse. Apt is quite clear on what needs to be in place, and where, to add a new repo; place the apt source server conf in Dir::Etc::sourceparts/d, place the apt archive's gpg key in Dir::Etc::trustedparts/d, and place the apt archive login details (if any) in Dir::Etc::netrcparts/d. Is any of that incorrect, and/or will any of that ever change? If not, simply creating the proper files in- place on the remote host should be all that's needed; all the logic of figuring out the naming and content of the files takes place on the local host. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Bionic: In Progress Status in software-properties source package in Cosmic: In Progress Status in software-properties source package in Disco: In Progress Status in software-properties source package in Eoan: In Progress Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1832004] [NEW] display hanging after laptop opens lid
Public bug reported: ubuntu 19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 14:56:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-15-generic, x86_64: installed anbox, 1, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1680] InstallationDate: Installed on 2018-08-03 (308 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. E402BA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402BA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE402BA.311:bd09/06/2018:svnASUSTeKCOMPUTERINC.:pnE402BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE402BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: E402BA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages 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/1832004 Title: display hanging after laptop opens lid Status in xorg package in Ubuntu: New Bug description: ubuntu 19.04 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Toegang geweigerd: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 7 14:56:09 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: anbox, 1, 5.0.0-15-generic, x86_64: installed anbox, 1, 5.0.0-16-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-15-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-16-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Stoney [Radeon R2/R3/R4/R5 Graphics] [1002:98e4] (rev da) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Stoney [Radeon R2/R3/R4/R5 Graphics] [1043:1680] InstallationDate: Installed on 2018-08-03 (308 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: ASUSTeK COMPUTER INC. E402BA ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=nl_NL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=c593d94b-7cc0-45ca-a012-f79a49d00093 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E402BA.311 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E402BA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor:
[Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default
** Description changed: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro- optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) + + I booted grub2 and measured loading largish amount of files, ie. $ date; + initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd + (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd + (hd0,gpt5)/initrd.img; date + + To get a rough speed between 30 and 44 MB/s of loading these files off + ext4 on nvme. + + With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o + penalty is 0.18s whilst I gain over a second in faster decompression + time. Overall a win. + + xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining + 2.4s of decompression time, meaning overall worse than gzip. -- 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/1831736 Title: [MIR] lz4 by default Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"
** Tags added: id-5cf932c4a06ae8470c614fa6 -- 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/1798369 Title: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock" Status in APT: New Status in ubiquity: New Status in apt package in Ubuntu: Invalid Status in ubiquity package in Ubuntu: Confirmed Bug description: When trying to reinstall an existing Ubuntu cosmic installation using latest 18.10 desktop images, the install shows an error dialog around the end of the installation with an "Error restoring installed applications". Looking at the syslog such a traceback can be seen: apt_pkg.Error: E:Could not get lock /target/var/cache/apt/archives/lock - open (11: Resource temporarily unavailable), E:Unable to lock directory /target/var/cache/apt/archives/ After reproducing this on a live session, after chrooting into /target indeed any apt-get install operations result in the same lock-file error. The whole syslog of the reinstall attached to the bug. Test case: * Download latest cosmic image * Install cosmic on the whole disk (can be on a VM) * (optional) Boot into the system and leave a file in the home directory (to leave a trace, just in case) * Reboot and install cosmic using the first option in ubiquity: Reinstall Ubuntu * Finish configuration The install itself doesn't fail, but around the end of the installation process the error dialog appears. System is still bootable but left with old packages. To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour
** Tags added: id-5cf9304627a12b717bdbab7a
--
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/1831252
Title:
panic=-1 is completely ignored by the initrd causing unexpected
behaviour
Status in initramfs-tools package in Ubuntu:
New
Status in initramfs-tools source package in Xenial:
New
Status in initramfs-tools source package in Bionic:
New
Status in initramfs-tools source package in Eoan:
New
Bug description:
in Ubuntu Core we default to using panic=-1 on the kernel command line
(documented at [1]) to speed up the auto-rollback mechanism of the
kernel. on a kernel level this works just fine and the system reboots
immediately ...
when in the initramfs during boot and a panic occurs, no reboot
happens at all, the initrd spawns a shell regardless of the panic=
value ...
this is caused by a filter in /usr/share/initramfs-tools/init
panic=*)
panic="${x#panic=}"
case ${panic} in
*[![:digit:].]*)
panic=
;;
esac
;;
this function only lets positive values through, else panic= simply
gets unset
the panic() function itself is also not capable of handling negative
values, it has a sleep call that interprets negative values as
commandline options instead of simply ignoring a negative sleep time
[2] (line 11).
the filter in the init script should allow the -1 value (to comply
with the kernel documentation and behaviour) and the panic() function
should properly skip the sleep call when a negative value for panic=
is set.
[1]
https://github.com/torvalds/linux/blob/v4.17/Documentation/admin-guide/kernel-parameters.txt#L2931
[2] https://paste.ubuntu.com/p/mswD8Cd869/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831252/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1825000] Re: Add ability for mirrors to distinguish interactive and non-interactive apt runs
** Tags added: id-5cf9354bf2165a4e38392bbb -- 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/1825000 Title: Add ability for mirrors to distinguish interactive and non-interactive apt runs Status in apt package in Ubuntu: Triaged Status in apt source package in Eoan: Triaged Bug description: As part of a larger scale plan to manage traffic to the main archive servers it would be useful if apt could provide a facility for us to identify interactive vs. non-interactive traffic on the server side, ideally via a header of some kind. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1825000/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1820068] Re: specifying -O no-expr-simplify results in cache miss
This bug was fixed in the package apparmor - 2.13.2-9ubuntu7 --- apparmor (2.13.2-9ubuntu7) eoan; urgency=medium * lp1820068.patch: don't skip read cache when options are set (LP: #1820068) * reenable ubuntu/parser-conf-no-expr-simplify.patch -- Jamie Strandboge Thu, 06 Jun 2019 21:46:34 + ** Changed in: apparmor (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1820068 Title: specifying -O no-expr-simplify results in cache miss Status in AppArmor: Fix Released Status in apparmor package in Ubuntu: Fix Released Status in apparmor source package in Disco: In Progress Status in apparmor source package in Eoan: Fix Released Bug description: With 2.13.2 and the most recent testsuite patches from the 2.13 branch, I find that the cache works correctly when no options are specified. Eg # setup $ mkdir -p /tmp/aa/cache /tmp/aa/profiles $ cp /etc/apparmor.d/sbin.dhclient /tmp/aa/profiles/ # no options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # no options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache hit: /tmp/aa/cache/26b63962.0/sbin.dhclient # reset $ rm -rf /tmp/aa/cache/* # options, no cache, expect a miss and to write $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient # options, cache, expect a hit $ /sbin/apparmor_parser -k --write-cache --cache-loc=/tmp/aa/cache --skip-kernel-load -O no-expr-simplify --add -- /tmp/aa/profiles Cache: added primary location '/tmp/aa/cache' Cache miss: /tmp/aa/profiles/sbin.dhclient # SHOULD BE A HIT Wrote cache: /tmp/aa/cache/26b63962.0/sbin.dhclient Same thing happens if omitting -O no-expr-simplify but add Optimize =no-expr-simplify to /etc/apparmor/parser.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1820068/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831995] [NEW] Bluetooth earphone is connected but disconnected immediately.
Public bug reported: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Reference" https://bugs.launchpad.net/bugs/1831995/+attachment/5269290/+files/vokoscreen-2019-06-07_20-25-29.mkv -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1831995 Title: Bluetooth earphone is connected but disconnected immediately. Status in bluez package in Ubuntu: New Bug description: I have erased and reinstalled Pulseaudio. It seems like this can not be done since. I tried the following. sudo apt-get remove alsa-base pulseaudio sudo apt-get install alsa-base pulseaudio I did this again. sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils sudo apt-get install linux-sound-base alsa-base alsa-utils ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluetooth 5.50-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Fri Jun 7 20:33:05 2019 InstallationDate: Installed on 2019-04-04 (64 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 7559 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=5f78f31f-69d5-4c72-9eb4-b8c535f89c9f ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/03/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.9 dmi.board.name: 0H0CC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.2.9:bd09/03/2018:svnDellInc.:pnInspiron7559:pvr1.2.9:rvnDellInc.:rn0H0CC0:rvrA00:cvnDellInc.:ct10:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 7559 dmi.product.sku: 0706 dmi.product.version: 1.2.9 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 58:FB:84:C1:51:50 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:125274 acl:68 sco:0 events:1720 errors:0 TX bytes:15000 acl:64 sco:0 commands:861 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1831995/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default
** Description changed: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html + + [Regression Potential] + + We are trying to optimize for total boot speed, but performing a micro- + optimization upon time to create/unpack kernel/initrd is an insufficient + benchmark for total boot speed. This is because it ignores time to load + the kernel/initrd, and whether the firmware/bootloader were able to + stream decompress it whilst loading it. I.e. it is argued that in the + real world, subsecond decompression gains are irrelevant if UEFI + firmware, tftp boot, etc. take a lot longer than that to read extra 10s + of MBs of boot material. + + [TODO] + Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. + Re-evaluate if we should provide different compression mechanisms: + - ie. gzip instead of lz4 for most cases (revert) + - ie. xz for painful i/o cases (e.g. netboot) -- 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/1831736 Title: [MIR] lz4 by default Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default
** Changed in: lz4 (Ubuntu) Status: Confirmed => Fix Released ** 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 initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
> did you change any settings to make it use radeon instead?
No changes since the initial installation/configuration. It (normally)
defaults to the radeon. radeon module blacklisted. I'll come back later
with results.
> and to solve the downgrade issue, try uninstalling gnuplot
:(
This is a master piece in my data-analysis process.
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1831988] [NEW] msgfmt produces invalid UTF-8 sequences for desktop files
Public bug reported: VIM has recently added support for validating gnome desktop files and this is reporting errors due to invalid UTF-8 sequences produced by msgfmt. Steps to reproduce: 1. Checkout rev 1253704 from the VIM git repo on GitHub - https://github.com/vim/vim 2. Run ./configure in the repo to set up the build environment. 2. Change to the po directory in the repo - cd src/po 3. Process and validate the gvim desktop file using the Makefile - $ make gvim.desktop msgfmt --desktop -d . --template gvim.desktop.in -o tmp_gvim.desktop rm -f LINGUAS if command -v desktop-file-validate; then desktop-file-validate tmp_gvim.desktop; fi /usr/bin/desktop-file-validate tmp_gvim.desktop: warning: file contains lines that are not UTF-8 encoded. There is no guarantee the validator will correctly work. [Invalid UTF-8] tmp_gvim.desktop: error: value "\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa0\xe0\xad\x8d\xe0\xac\xaf \xe0\xac\xab\xe0\xac\xbe\xe0\xac\x87\xe0\xac\xb2\xe0\xac\x97\xe0\xad\x81\xe0\xac\xa1\xe0\xac\xbc\xe0\xac\xbf\xe0\xac\x95\xe0\xad\x81 \xe0\xac\xb8\xe0\xac\xae\xe0\xad\x8d\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa6\xe0\xac\xa8 \xe0\xac\x95\xe0\xac\xb0\xe0\xac\xa8\xe0\xad\x8d\xe0\xac\xa4\xe0\xad" for locale string key "Comment[or]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8 Makefile:176: recipe for target 'gvim.desktop' failed make: *** [gvim.desktop] Error 1 The template file has valid UTF-8 sequences so no errors are expected. The error is correct as the generated desktop file has a truncated 3 byte UTF-8 sequence at the end of the line as reported. The problem is msgfmt is emitting an invalid UTF-8 sequence for this one line. This is happening on an up to date 16.04 LTS - $ apt list gettext desktop-file-utils Listing... Done desktop-file-utils/xenial-updates,now 0.22-1ubuntu5.2 i386 [installed] gettext/xenial-updates,xenial-security,now 0.19.7-2ubuntu3.1 i386 [installed] There has been some discussion of this issue on the VIM developers mailing list - https://groups.google.com/d/msg/vim_dev/yYGCsJJPlA0/i1PNO_46AgAJ A candidate patch for the issue from upstream for the gettext package has been identified - https://groups.google.com/d/msg/vim_dev/yYGCsJJPlA0/6yAEzO9LAgAJ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gettext 0.19.7-2ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-51.55~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-51-generic i686 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CurrentDesktop: Unity Date: Fri Jun 7 10:30:31 2019 InstallationDate: Installed on 2019-02-05 (121 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release i386 (20180731) SourcePackage: gettext UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gettext (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1831988 Title: msgfmt produces invalid UTF-8 sequences for desktop files Status in gettext package in Ubuntu: New Bug description: VIM has recently added support for validating gnome desktop files and this is reporting errors due to invalid UTF-8 sequences produced by msgfmt. Steps to reproduce: 1. Checkout rev 1253704 from the VIM git repo on GitHub - https://github.com/vim/vim 2. Run ./configure in the repo to set up the build environment. 2. Change to the po directory in the repo - cd src/po 3. Process and validate the gvim desktop file using the Makefile - $ make gvim.desktop msgfmt --desktop -d . --template gvim.desktop.in -o tmp_gvim.desktop rm -f LINGUAS if command -v desktop-file-validate; then desktop-file-validate tmp_gvim.desktop; fi /usr/bin/desktop-file-validate tmp_gvim.desktop: warning: file contains lines that are not UTF-8 encoded. There is no guarantee the validator will correctly work. [Invalid UTF-8] tmp_gvim.desktop: error: value "\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa0\xe0\xad\x8d\xe0\xac\xaf \xe0\xac\xab\xe0\xac\xbe\xe0\xac\x87\xe0\xac\xb2\xe0\xac\x97\xe0\xad\x81\xe0\xac\xa1\xe0\xac\xbc\xe0\xac\xbf\xe0\xac\x95\xe0\xad\x81 \xe0\xac\xb8\xe0\xac\xae\xe0\xad\x8d\xe0\xac\xaa\xe0\xac\xbe\xe0\xac\xa6\xe0\xac\xa8 \xe0\xac\x95\xe0\xac\xb0\xe0\xac\xa8\xe0\xad\x8d\xe0\xac\xa4\xe0\xad" for locale string key "Comment[or]" in group "Desktop Entry" contains invalid UTF-8 characters, locale string values should be encoded in UTF-8 Makefile:176: recipe for target 'gvim.desktop' failed make: *** [gvim.desktop] Error 1 The template file has valid UTF-8 sequences so no errors are expected. The error is correct as the generated desktop file has a truncated 3 byte UTF-8 sequence at the end of the line as reported. The problem is msgfmt is emitting an invalid UTF-8 sequence for this one line. This is happening on an
[Touch-packages] [Bug 1831470] Re: systemd dhcp don't work on vlan
** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1831470 Title: systemd dhcp don't work on vlan Status in systemd package in Ubuntu: Invalid Bug description: root@gwd:~# uname -a Linux gwd 4.15.0-50-generic #54-Ubuntu SMP Mon May 6 18:46:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@gwd:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.2 LTS Release:18.04 Codename: bionic root@gwd:~# cat /etc/systemd/network/enp3s0.network [Match] Name=enp3s0 [Link] MACAddress=C8:D3:A3:50:02:33 [Network] VLAN=enp3s0.2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.netdev [NetDev] Name=enp3s0.2 Kind=vlan [VLAN] Id=2 root@gwd:~# cat /etc/systemd/network/enp3s0.2.network [Match] Name=enp3s0.2 [Network] DHCP=ipv4 [DHCP] UseRoutes=true - No ip on enp3s0.2 after boot! dhclient enp3s0.2 works fine, i create systemd service for it as temporary workaround To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1831470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1805203] Re: libcurl3-gnutls in cosmic breaks git with Azure DevOps
Hello Mark, or anyone else affected, Accepted curl into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/curl/7.61.0-1ubuntu2.5 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: curl (Ubuntu Cosmic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-cosmic -- 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/1805203 Title: libcurl3-gnutls in cosmic breaks git with Azure DevOps Status in curl package in Ubuntu: Fix Released Status in curl source package in Cosmic: Fix Committed Bug description: * Impact Git auth fails when trying to work with an Azure DevOps repository * Test case Try to git clone from an Azure DevOps repository using a Personal Access Token The clone should work and not fail on an authentification error * Regression potential The diff is in the curl http code, it would be good to test a few rdepends to make sure they have no regression The version of libcurl3-gnutls in cosmic (7.61.0) causes authentication failures with Azure DevOps. This causes all git operations with the server to fail (eg clone, push, pull). For details see this curl bug: https://github.com/curl/curl/pull/2754 To work around this I downgraded libcurl3-gnutls to the version in bionic (7.58.0) From the curl change list https://curl.haxx.se/changes.html#7_61_1, this issue should be fixed in package version 7.61.1 or above. Request: please upgrade package in cosmic for libcurl3-gnutls to 7.61.1 or above Details: 1 - Ubuntu 18.10 2 - libcurl3-gnutls (7.61.0-1ubuntu2.2 and others) 3 - Be able to git clone from an Azure DevOps repository using a Personal Access Token 4 - git operations fail to authenticate Thank you, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1805203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1830859] Re: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4
Hello Christian, or anyone else affected, Accepted qemu into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/qemu/1:3.1+dfsg- 2ubuntu3.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-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. 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: qemu (Ubuntu Disco) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1830859 Title: new libseccomp 2.4 (in proposed) makes rebuilds need but not generate a dependency to 2.4 Status in libseccomp package in Ubuntu: Won't Fix Status in qemu package in Ubuntu: Triaged Status in qemu source package in Disco: Fix Committed Bug description: [Impact] * Just as of yesterday we have a new libseccomp in all releases. This brings some new code and features which might impact packages. For qemu being one of the few that is not so much a problem in many cases. Prior to Disco we didn't have code in qemu using the new libseccomp bits. In Eoan we can assume that libseccomp 2.4 (being release level) will be installed. But in Disco people might have installed and not updated libseccomp but install/upgrade to a qemu that was built against that new libseccomp. Due to that qemu will get a runtime dependency that is not picked up automatically - this would break all qemu execution being blocked by a failure to install seccomp filters. * To fix that we will add an explicit versioned dependency to qemu to make sure the rebuild will ensure that the right library version is available. * This is needed for qemu-system* which all depend on qemu-system- common so to avoid too much noise changing all qemu-system* packages the dependency it added there. [Test Case] * ensure that the qemu install will ensure that libseccomp2 (>= 2.4.1) is also installed (not staying on 2.3) * Then install qemu and run $ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny which should not trigger this (when fixed) error: internal error: process exited while connecting to monitor: 2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed to install seccomp syscall filter in the kernel [Regression Potential] * Well, the regressions might be triggered by pushing the new libseccomp, not by this dependency fixup. The security Team has checked and this seems to be the only affected code in the archive. So libseccomp was pushed to fix CVEs. I have thought if it is a regression that users of qemu will now be forced to use the newer libseccomp, but since it would be unusable without that is no important argument. And it is strongly recommended to upgrade for security reasons as well. [Other Info] * n/a --- It started with some of my usual KVM checks and found them failing on Disco with: error: internal error: process exited while connecting to monitor: 2019-05-28T17:10:17.121934Z qemu-system-x86_64: -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny: failed to install seccomp syscall filter in the kernel I realized it works on X/B/C/E but not in a D container It worked ~4 weeks ago. This test can be simplified to one command: $ qemu-system-x86_64 -enable-kvm -nographic -nodefaults -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny With strace I found different behavior: Good: [pid 3487] 0.00 seccomp(SECCOMP_SET_MODE_FILTER, SECCOMP_FILTER_FLAG_TSYNC, NULL) = -1 EFAULT (Bad address) <0.11> [pid 3487] 0.003136 seccomp(SECCOMP_SET_MODE_STRICT, 1, NULL) = -1
[Touch-packages] [Bug 1813362] Re: lxc-top flash error and blkio write is always zero
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1813362 Title: lxc-top flash error and blkio write is always zero Status in lxc package in Ubuntu: Confirmed Bug description: When running lxc-top as root it flashes the following error messages for every container: Unable to read cgroup item memory.memsw.usage_in_bytes Unable to read cgroup item memory.memsw.limit_in_bytes Here output showing bad blkio write Container CPU CPU CPU BlkIOMem KMem Name Used Sys User Total(Read/Write) Used Used ltcd-root310.2298.26 196.88 315.06 MiB(315.06 MiB/ 0.00 ) 688.64 MiB 83.09 MiB ltcd-test236.0284.52 136.76 115.88 MiB(115.88 MiB/ 0.00 ) 384.39 MiB 31.89 MiB TOTAL 2 of 2 546.24 182.78 333.64 430.94 MiB(430.94 MiB/ 0.00 ) 1.04 GiB 114.97 MiB Doing an strace on lxc-top: openat(AT_FDCWD, "/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.usage_in_bytes", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) write(2, "Unable to read cgroup item memor"..., 55) = 55 openat(AT_FDCWD, "/sys/fs/cgroup/memory//lxc/ltcd-root/memory.memsw.limit_in_bytes", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) write(2, "Unable to read cgroup item memor"..., 55) = 55 Here is copy /sys/fs/cgroup/memory/lxc/ltcd-root mike@mike-desktop:/sys/fs/cgroup/memory/lxc/ltcd-root$ ls cgroup.clone_children memory.limit_in_bytes cgroup.event_control memory.max_usage_in_bytes cgroup.procs memory.move_charge_at_immigrate init.scopememory.numa_stat memory.failcntmemory.oom_control memory.force_emptymemory.pressure_level memory.kmem.failcnt memory.soft_limit_in_bytes memory.kmem.limit_in_bytesmemory.stat memory.kmem.max_usage_in_bytesmemory.swappiness memory.kmem.slabinfo memory.usage_in_bytes memory.kmem.tcp.failcnt memory.use_hierarchy memory.kmem.tcp.limit_in_bytesnotify_on_release memory.kmem.tcp.max_usage_in_bytes system.slice memory.kmem.tcp.usage_in_bytestasks memory.kmem.usage_in_bytesuser.slice ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lxc-utils 3.0.3-0ubuntu1~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-13.14~18.04.1-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Fri Jan 25 15:56:04 2019 InstallationDate: Installed on 2018-02-23 (336 days ago) InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: Upgraded to bionic on 2018-10-21 (95 days ago) mtime.conffile..etc.lxc.default.conf: 2019-01-24T17:40:41.527776 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1813362/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1828171] Re: New toolchain updates need to be rebuilt against -security only
Autopkgtests look good. Updated hints to see installability of all the packages. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1828171 Title: New toolchain updates need to be rebuilt against -security only Status in binutils package in Ubuntu: New Status in eclipse-titan package in Ubuntu: New Status in gcc-7 package in Ubuntu: New Status in gcc-7-cross package in Ubuntu: New Status in gcc-7-cross-ports package in Ubuntu: New Status in gcc-8 package in Ubuntu: New Status in gcc-8-cross package in Ubuntu: New Status in gcc-8-cross-ports package in Ubuntu: New Status in gcc-defaults package in Ubuntu: New Status in gcc-defaults-ports package in Ubuntu: New Status in ggcov package in Ubuntu: New Status in binutils source package in Bionic: Fix Committed Status in eclipse-titan source package in Bionic: Fix Committed Status in gcc-7 source package in Bionic: Fix Committed Status in gcc-7-cross source package in Bionic: Fix Committed Status in gcc-7-cross-ports source package in Bionic: Fix Committed Status in gcc-8 source package in Bionic: Fix Committed Status in gcc-8-cross source package in Bionic: Fix Committed Status in gcc-8-cross-ports source package in Bionic: Fix Committed Status in gcc-defaults source package in Bionic: Fix Committed Status in gcc-defaults-ports source package in Bionic: Fix Committed Status in ggcov source package in Bionic: Fix Committed Status in binutils source package in Cosmic: Fix Committed Status in eclipse-titan source package in Cosmic: Fix Committed Status in gcc-7 source package in Cosmic: Fix Committed Status in gcc-7-cross source package in Cosmic: Fix Committed Status in gcc-7-cross-ports source package in Cosmic: Fix Committed Status in gcc-8 source package in Cosmic: Fix Committed Status in gcc-8-cross source package in Cosmic: Fix Committed Status in gcc-8-cross-ports source package in Cosmic: Fix Committed Status in gcc-defaults source package in Cosmic: Fix Committed Status in gcc-defaults-ports source package in Cosmic: Fix Committed Status in ggcov source package in Cosmic: Fix Committed Bug description: [Impact] With LP: #1814369, the toolchain packages have been updated in both cosmic and bionic, but due to an error those packages were built in -proposed as any regular SRU. For toolchain updates there exists a policy that those should be always built against -security *only*, and then released to both -security and -updates. Since this is not the case with the current toolchain update, we need to no-change rebuild all of the previously released toolchain packages in a -security enabled devirt PPA, sync them to -proposed with binaries and then release into the archives. [Regression Potential] As these are toolchain packages, there is always some regression potential. These will be no-change rebuilds so in theory the risk should be low, but the current versions of the packages have not been built against -security only before. It is hard to say how any regressions could manifest themselves. [Test Case] Making sure there are no reported regressions in the GCC and binutils test suites. Hopefully this will be sufficient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1828171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
and to solve the downgrade issue, try uninstalling gnuplot..
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
it seems to be an intel/radeon hybrid machine, did you change any
settings to make it use radeon instead? Try to blacklist radeon kernel
module to rule it out
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
> And it took almost two weeks for you to notice this after the upgrade?
No. I noticed it immediately. However, since most of the time fixes come
within
a few days, I did not report the bug at the time, thinking I wasn't the
only one
with that desktop behavior.
> note that there were no changes to the radeon code in the libdrm update, so
> blaming
> the regression on it is weird, I'd suggest to look at KDE instead
I'm not "blaming" libdrm in a criticizing way :) It's just that it was the
ONLY
updated package at that time that could have caused the bug to appear since
I
doubt libreoffice could be the one that has an impact (see the previous
attachment
with the upgraded packages that day)... As a developper myself (bare-metal,
kernel,
CLI, QT) for the industry, I'm fully aware that there can be bugs at
several levels.
> You still have the old libdrm available in the archive btw, does downgrade do
> anything?
No in mine, I'm afraid. I tried to do that but apt do not want me to. When
I simulate
the downgrade here is what it gives:
$ cat libdrm2-packages-versions
libdrm-nouveau2=2.4.95-1~18.04.1
libdrm-amdgpu1=2.4.95-1~18.04.1
libdrm2=2.4.95-1~18.04.1
libdrm-intel1=2.4.95-1~18.04.1
libdrm-radeon1=2.4.95-1~18.04.1
libdrm-common=2.4.95-1~18.04.1
$ sudo apt-get -s install $(cat libdrm2-packages-versions)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
gnuplot : Depends: gnuplot-qt but it is not going to be installed or
gnuplot-x11 but it is not going to be installed or
gnuplot-nox
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by
held packages.
Trying to upgrade them 1 by 1 gives the results found in this post attached
file. I
did not go further in downgrading in the fear of having inconsistencies
between
packages versions.
** Attachment added: "apt-upgrade-libdrm2"
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+attachment/5269255/+files/apt-upgrade-libdrm2
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
[Touch-packages] [Bug 1829872] XorgLogOld.txt
apport information
** Attachment added: "XorgLogOld.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269252/+files/XorgLogOld.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269249/+files/ProcModules.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] XorgLog.txt
apport information
** Attachment added: "XorgLog.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269251/+files/XorgLog.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
It seems apport-collect cannot produce a useful result for now:
dpkg-query: no package matches libdrm
And I couldn't change the affected package to be libdrm2 instead.
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] xdpyinfo.txt
apport information
** Attachment added: "xdpyinfo.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269254/+files/xdpyinfo.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269250/+files/UdevDb.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Xrandr.txt
apport information
** Attachment added: "Xrandr.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269253/+files/Xrandr.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269248/+files/ProcInterrupts.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] DpkgLog.txt
apport information
** Attachment added: "DpkgLog.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269242/+files/DpkgLog.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269247/+files/ProcEnviron.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269245/+files/ProcCpuinfo.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269244/+files/Lsusb.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269246/+files/ProcCpuinfoMinimal.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269243/+files/Lspci.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: KDE
DistUpgraded: Fresh install
DistroCodename: bionic
DistroRelease: Ubuntu 18.04
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
InstallationDate: Installed on 2018-05-05 (397 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
MachineType: Dell Inc. Inspiron 5759
Package: libdrm (not installed)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Tags: bionic ubuntu
Uname: Linux 4.15.0-51-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
_MarkForUpload: True
dmi.bios.date: 12/21/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.5
dmi.board.name: 05NVNV
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5759
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1829872/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1829872] Re: No more desktop effects since libdrm upgrade in Bionic
apport information
** Tags added: apport-collected bionic ubuntu
** Description changed:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-common:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
I have an ATI Radeon that was working fine with KDE until then. I waited to
see if someone had realized it before creating a bug report... It really is
annoying : no more transparency, no
more auto-hide of windows : my workflow is strongly impacted.
System information :
$ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
$ apt-cache policy libdrm2
libdrm2:
Installé : 2.4.97-1ubuntu1~18.04.1
Candidat : 2.4.97-1ubuntu1~18.04.1
Table de version :
*** 2.4.97-1ubuntu1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-proposed/main amd64
Packages
100 /var/lib/dpkg/status
2.4.95-1~18.04.1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
2.4.91-2 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
+ CompositorRunning: None
+ CurrentDesktop: KDE
+ DistUpgraded: Fresh install
+ DistroCodename: bionic
+ DistroRelease: Ubuntu 18.04
+ DistroVariant: ubuntu
+ GraphicsCard:
+ Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07)
(prog-if 00 [VGA controller])
+Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06b2]
+Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7
M520] [1028:06b2]
+ InstallationDate: Installed on 2018-05-05 (397 days ago)
+ InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64
(20180426)
+ MachineType: Dell Inc. Inspiron 5759
+ Package: libdrm (not installed)
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic
root=UUID=2c061bef-bc89-4985-8670-ada8d7af157a ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
+ Tags: bionic ubuntu
+ Uname: Linux 4.15.0-51-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo vboxusers
wireshark
+ _MarkForUpload: True
+ dmi.bios.date: 12/21/2015
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.1.5
+ dmi.board.name: 05NVNV
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 9
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias:
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5759:pvr:rvnDellInc.:rn05NVNV:rvrA00:cvnDellInc.:ct9:cvr:
+ dmi.product.name: Inspiron 5759
+ dmi.sys.vendor: Dell Inc.
+ version.compiz: compiz N/A
+ version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1
+ version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1
+ version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
+ 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
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1829872/+attachment/5269241/+files/CurrentDmesg.txt
--
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/1829872
Title:
No more desktop effects since libdrm upgrade in Bionic
Status in libdrm package in Ubuntu:
Incomplete
Bug description:
Hello.
I upgraded my system on 2019-05-09 and since then desktop effects do not work
anymore. It installed
a new libdrm stack :
$ grep -A 3 "2019-05-09 *08:53:53" /var/log/apt/history.log | tail -n 1 | awk
-F "," '{for(i=1;i<=NF;i++){print $i}}' | grep -A1 libdrm
libdrm-nouveau2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-amdgpu1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm2:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-intel1:amd64 (2.4.95-1~18.04.1
2.4.97-1ubuntu1~18.04.1)
--
libdrm-radeon1:amd64 (2.4.95-1~18.04.1
